Solved

Isolating one machine from all but one network resource?

Posted on 2007-11-14
2
317 Views
Last Modified: 2010-04-12
I have two subnets at this location,  .60 and .61.  I need to have a server (Windows Server 2k3 Standard R2) located at 60.44 connect to another server at 61.40. They currently communicate perfectly across both subnets- the issue is that the server on 60.44 needs to have all network resource restricted to ONLY communicating with the other server at 61.40. To clarify, the 60.44 server needs to accept an RDP connection, speak with the 61.40 server, and have no other access to the network. Additionally the server at 61.40 needs to retain its full connectivity to all network resources.
0
Comment
Question by:KinjinZero
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 9

Expert Comment

by:svs
ID: 20283845
You could put a firewall between 60.44 and the rest of its subnet.  It could even retain its IP, with some magic (arp proxy).
0
 
LVL 2

Accepted Solution

by:
pinkisthenewblue earned 500 total points
ID: 20303842
Not sure what versions of Server2003 come with the option of installing this, but try using "routing and remote access" - install it on the server you want to isolate and create rules, not letting it connect to anything except this specific IP (and possibly the router in between if applicable). I did this on an Enterprise edition and worked like a charm.

Alternatively, remove the routes on the server you want to isolate (this doesn't require any install).
cmd prompt:
route print >> (mybackupfile.backup)                              
route delete 0.0.0.0                            
route delete xxx.xxx.60.255
route delete xxx.xxx.61.255 (if applicable)

THEN add the route to your second server. If you have a router in between you'll need to add that route back, if not just this one:

route add xxx.xxx.61.40 mask 255.255.240.0 xxx.xxx.61.40

With router:

route add (routers IP) mask 255.255.240.0 (routers IP)
route add xxx.xxx.61.40 mask 255.255.240.0   (routers IP)

I would recommend both reading up and testing this first, there might be more rules you need to delete and it can potentially do a lot of damage.                          
0

Featured Post

Major Incident Management Communications

Major incidents and IT service outages cost companies millions. Often the solution to minimizing damage is automated communication. Find out more in our Major Incident Management Communications infographic.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

#Citrix #Citrix Netscaler #HTTP Compression #Load Balance
Arrow Electronics was searching for a KVM  (Keyboard/Video/Mouse) switch that could display on one single monitor the current status of all units being tested on the rack.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question