Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Here i want to ask you that is there any way through which i can allow only my machine to access client servers as i want to secure my servers from hackers. for this i have find a lot but not able find a specific way to allow only my ip to access. If i blocks all IP then it blocks all the IP's but when create a rule to allow only my IP then the rule dosent works.

Can you suggest what may be the reason or can you suggest the solution.

Its for windows server 2003

share|improve this question
Which Operating System? – Kyle Brandt Jun 1 '09 at 13:13

If you're talking Windows, yes. You set up a default block rule that applies to all IPs. Then you set up another rule that permits TCP communication (or UDP, if that's necessary) to your set of IPs that you wish to permit. It could also be protocol based. For instance, a DMZ web server which needs to connect to a back-end SQL Server:

  • Block all TCP/UDP from any source to the destination server.
  • Permit all TCP/80 (HTTP) and TCP/443 (HTTPS) traffic from an external IP to the destination server.
  • Permit mirrored TCP/1433 (assuming default TCP port for MSSQLServer) to internal IP address of the SQL Server.
share|improve this answer

It sounds like this question is about firewalling rather than IPSEC. If you are only allowing IPSEC secured connections then you would simply only have an IPSEC SA (Security Association) for the chosen client. This would not necessarily need to be tied to a specific IP and would be a good choice if you do not know the IP that you will be accessing the server from. Any client you do not have an SA for will not be able to get access.

If you know your IP address it is more likely what you want is to install either a software firewall on the client server or a hardware firewall in front of it that only allow access from your nominated IP.

You could also combine the approach so that your management traffic is encrypted in transit using IPSEC and the server is protected to only accept traffic from your host by a firewall. IPSEC encryption may not be needed if the management already uses an encrypted channel (e.g. SSH or HTTPS).

share|improve this answer
In Windows, you can handle this with an IPSEC policy, too. In fact, it's best if you can do both, firewall and IPSEC policy. Defense in depth. – K. Brian Kelley Jun 1 '09 at 14:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.