Hi There I am having a problem with two network cards attached to a windows server 2003 machine. NIC 1 is on the 10.38.9.x 255.255.255.0 gw: 10.38.9.1 and NIC 2 is on a static 192.168.1.x 255.255.255.0 network on a seprate switch. NIC 1 is the corporate network and NIC 2 is a private door access system. From the server I can ping any 192.168.1.x address thats connected but cant ping out to the 10 network. Firewalls are disabled and this machine is standalone not controlled by any policies. The door access system talks to and from the server and the server must be able to connect to an SQL box in order to work. I have RRAS enabled in a basic sense and have tried some simlar suggestions but cant seem to get it to work. Any help would be appeicated. Thanks DaveICT Development Officer

Hi, can you post the output from the command prompt when you run the route print command? My hunch is that you are going to need to modify the interface metric for each interface where the preferred interface has a relatively low value (like 100) and the non-preferred interface has a metric that is relatively high (999). You will then have to create static routes for networks that you want to use a specific interface for using the route -p add command. Note that the -p adds the route as a persistent (across reboots) route. -- Mike Burr

Please make sure a default gateway is configured for both connections. You can troubleshoot and resolve routing issues from the command line. Open a command promt and type route print Then confirm with "enter". You should have at least 2 routing entries: destination 0.0.0.0 should be routed to the default gateway of the normal LAN. Also you should have a route to the 192.168.1.0 network which has to be the gateway on this network. To add a route, refer to http://technet.microsoft.com/en-us/library/cc757323(WS.10).aspx There is no need for RRAS services on a multihomed server unless it has to act as a router between the network (i.e. be the gateway himself). Please clarify what you are trying to achieve and post some results from route print so we can help you even better!MCP/MCSA/MCTS/MCITP

IPv4 Route Table =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x10003 ...00 15 5d 23 2d 11 ...... Intel 21140-Based PCI Fast Ethernet Adapter (Generic) 0x10004 ...00 15 5d 23 2d 10 ...... Microsoft Virtual Machine Bus Network Adapter #2 =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.38.9.1 10.38.9.31 20 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 10 10.38.9.0 255.255.255.0 10.38.9.31 10.38.9.31 20 10.38.9.31 255.255.255.255 127.0.0.1 127.0.0.1 20 10.255.255.255 255.255.255.255 10.38.9.31 10.38.9.31 20 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.1.0 255.255.255.0 192.168.1.2 192.168.1.2 10 192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1 10 192.168.1.255 255.255.255.255 192.168.1.2 192.168.1.2 10 224.0.0.0 240.0.0.0 10.38.9.31 10.38.9.31 20 224.0.0.0 240.0.0.0 192.168.1.2 192.168.1.2 10 255.255.255.255 255.255.255.255 10.38.9.31 10.38.9.31 1 255.255.255.255 255.255.255.255 192.168.1.2 192.168.1.2 1 Default Gateway: 192.168.1.1 =========================================================================== Persistent Routes: NoneICT Development Officer

what are you trying to achive? Will this host be the gateway between the networks? Or should it just be a multihomed server?MCP/MCSA/MCTS/MCITP

If there is no plans to route packets between the 192.168.1.x network and 10.38.9.x network, I would recommend the following: 1) Disable RRAS on this server. There is no need for this service, unless the systems on 192.168.1.x need to communicate with the production network. 2) if there are no other remote subnets on the side of 192.168.1.x, REMOVE the default gateway from the 192.168.1.1 interface. There is no where to go past this subnet, so no gateway is needed. For instance if you tried to ping 65.87.100.1, why would you want your server to send out the packet through the 192.168.1.1 interface? 3) If you DO want computers on the 192.168.1.x network to access 10.x.x.x hosts, you will need to enable RRAS and install the NAT service. Otherwise, packets from your 10.x.x.x network will not RETURN. The routers on that network have no routes defined to get back to the 192.168.1.x network. By enabling NAT, all packets that pass through this server will have a source IP of 10.39.9.31. How IP Packets are Routed on a Local Area Network http://www.anitkb.com/2010/06/how-ip-packets-are-routed-on-local-area.html Visit: anITKB.com, an IT Knowledge Base.

Hi, Thank you for your post here. I agree with JM's advice that you should disable the RRAS service on the server if you don't need network connectivity between 192.168.1.x and 10.X.X.X network. If you need RRAS service on the server enabled to provide routing between two networks, please also check whether there is any inbound/outbound filters on the server's interface which may block the traffic.

Many thanks for all your replies. i have diabled RRAS as i dont need the 192 to talk to the 10 and i have removed the gateway on the local network. this is now working ok. Thanks again Dave