Crazy IT Professionals

We have to Block Production server access from below three network on cisco router and only allowed access from specific IPs Three internal network In Office 1)       10.10.32.0/24 2)       10.10.128.0/24 3)       10.10.62.0/24 Specific IP Address:- 1)       10.10.128.70 Production Network 1)       10.13.40.139 2)       10.13.40.142 Script:- Creating Object group to added internal Network Pool WAN-R1#sh object-group Network object group Internal   10.10.32.0 255.255.255.0   10.10.128.0 255.255.255.0   10.10.62.0 255.255.255.0 Added access-list:- WAN-R1#sh access-lists 123 Extended IP access list 123     10 permit ip host 10.10.128.70 host 10.13.40.139     20 permit ip host 10.10.128.70 host 10.13.40.142     30 deny ip object-group Internal host 10.13.40.139     40 deny ip object-group Internal host 10.13.40.142     50 permit ip any any Applied access-list on Outside Interface Interface Serial2/0 Description “Outsid

This tutorial describes the procedure that a Check Point administrator should follow in order to become able to use SFTP (Secure File Transfer Protocol) or SCP (Secure Copy Protocol) for transferring files to/from a Check Point (CP) SecurePlatform (SPLAT) or Gaia gateway. The major question is why a CP SPLAT or Gaia gateway cannot be accessed with an SFTP/SCP client (e.g. WinSCP), even though the gateway is accessible via SSH (SecureShell, tcp port 22)? Before proceeding and answering the above question, it is important to mention that an authorized user (for example the network security administrator) can use SSH to access a CP SPLAT/Gaia gateway in two modes: The Standard Mode which is the default mode that an administrator first accesses (via SSH) the CP SPLAT gateway by providing the “admin” user credentials. In this mode, the user is logged in with administrator permissions and can perform only a limited number of operations on the CP SPLAT gateway. The shell

Source Knowledge From :-  http://geekswing.com/geek/vmware-cpu-and-ram-reservations-fixing-insufficient-resources-to-satisfy-configured-failover-level-for-ha/ VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA This post comes from a few days of poring over manuals as well as some technical support. This is a good one. The error came from trying to power on a VM in our VMware cluster and we would get these errors: “Insufficient resources to satisfy configured failover level for HA” And this alert on our cluster “Insufficient resources to satisfy HA failover level on cluster vmCluster in vmTST” Our way of thinking was we had to power one off to power another one on. But that didn’t work. Here we is the actual solution. (p.s. Great VMware HA education for me on this one!) PROBLEM SOURCE: VMware HA is turned on and you are violating constraints VMware HA is turned on, and you have it co

There’s no doubting the fact that Skype is the most amazing VoIP services around. Hundreds of millions of people use it everyday, and it’s supported by almost all mobile and desktop platforms. But just like many top notch tech solutions, Skype isn’t without its shortcomings. If you use Skype on Windows, you’d probably be aware that it doesn’t let you remove the chat history of a single contact only and the only (official) way is to delete it is by clearing the entire chat history from Preferences. You’re not completely out of luck though, as there is a way to delete Skype conversation of one user if you want. And in this guide we will show you how. So without any further ado, let’s get straight to it. Skype basically stores all the text chats with contacts in the SQL database file called “main.db” which is stored inside the Roaming folder of Windows. This database file in fact also carries other information related to settings and options stored by the user. Fortunate

If you ever jump in to this Checkpoint issue with an error message that looks like this: The connection has been refused due to one of following SmartCenter Server certificate problems: 1. The SmartCenter Server’s clock is not setup properly. 2. The certificate’s issue date is later than the date of the SmartCentre Server’s clock. 3. The Gui Client’s clock and the SmartCenter Server’s clock are not synchronized. 4. The certificate has expired. 5. The certificate is invalid. Here is the steps on how to remedy it: Switch directories: cd $CPDIR/conf or C:/program files/checkpoint/cpshared/R??/conf Backup and remove the sic_cert.p12 file: cp sic_cert.p12 sic_cert.p12old rm sic_cert.p12 Revoke the certificate from the SmartCenter’s Objects file: cpca_client revoke_cert -n “CN=cp_mgmt” Recreate a brand new sic cert for the SmartCenter: cpca_client create_cert -n “CN=cp_mgmt” -f sic_cert.p12 Restart the Check Point processes: cpstop cpstart There would