Hi, I have a SBS 2003 and it has two network cards. One ip address is 10.0.0.2 and another is 172.16.0.2. The desktop clients are on the 10.0.0.x network. I have a linux server (172.16.0.1) that I would like my desktop clients to access. On the server it can see the web page of the linux box. On the desktop clients when I ping the Windows server adapter (172.16.0.2) it gives a reply. When the desktop clients try to ping (linux server adapter) 172.16.0.1, it has a request time out. I did a tracert from the desktop clients to see what is going on, and I see the traffic go to the 10.0.0.2 adapter and then the traffic times out. I thought I would use static routes to get around this...so I created static routes on the server as the desktop clients hits the server (10.0.0.2) interface first. However I still get the same problem. (Timeout on ping). I have a list of the static routes here. Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.16.0.1 172.16.0.2 20 0.0.0.0 0.0.0.0 172.16.0.254 172.16.0.2 20 10.0.0.0 255.255.255.0 10.0.0.2 10.0.0.2 10 10.0.0.2 255.255.255.255 127.0.0.1 127.0.0.1 10 10.255.255.255 255.255.255.255 10.0.0.2 10.0.0.2 10 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 172.16.0.0 255.255.255.0 172.16.0.2 172.16.0.2 20 172.16.0.0 255.255.255.255 172.16.0.2 172.16.0.2 1 172.16.0.1 255.255.255.255 172.16.0.2 172.16.0.2 1 172.16.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20 172.16.255.255 255.255.255.255 172.16.0.2 172.16.0.2 20 224.0.0.0 240.0.0.0 10.0.0.2 10.0.0.2 10 224.0.0.0 240.0.0.0 172.16.0.2 172.16.0.2 20 255.255.255.255 255.255.255.255 10.0.0.2 10.0.0.2 1 255.255.255.255 255.255.255.255 172.16.0.2 172.16.0.2 1 Default Gateway: 172.16.0.254 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 172.16.0.1 255.255.255.255 172.16.0.2 1 172.16.0.0 255.255.255.255 172.16.0.2 1 I am not quite sure if its correct or not but any help would be appreciated.

That isn't how IP routing works. You don't simply add static routes and hope for the best. 1. It is never a good idea you use a DC as a router, even if it is SBS. 2. A Windows machine will only forward packets from one subnet to another if IP routing is enabled. All the static routes you can think of have no effect without that. You can enable routing by a registry change or by enabling LAN routing in RRAS. 3. If IP routing is enabled and the routing is configured properly you should not need any static routes on the client machine or the router itself. The only place you might need a static route is on your gateway router. 4. Routing is a two-way process. Adding routes to get traffic from A to B gets you nowhere unless there is also a route to get the reply back from B to A. You don't need any routes on the client. All non-local traffic will go to the default gateway (as you have found). Where it goes after that depends on what routes the router has, not on anything set up on the client. What is the default route of the linux server? Even if you enable IP routing on your DC (and I wouldn't) you will only be able to route to it if the linux server's default router is your DC. If the default route of your linux server is to some other router, you do need a static route (either on the server itself or on its default router) to send traffic for 10.0.0.1 to your sbs server. Personally I would remove the 172.16 NIC from your server. If you want to route between these two subnets, set up a router (not on your DC) and route traffic between the subnets through that. Exactly how you do that depends on how these subnets are set up, including how they access the Internet and what they use as default gateway. The simplest wat to route between two subnets is to make the router the default gateway for both segments. As long as IP routing is enabled, it just works. 192.168.0.x dg 192.168.0.254 | 192.168.0.254 dg blank router 172.16.0.254 dg blank | 172.16.0.x dg 172.16.0.254 If either segment has an Internet connection and uses some other router as its default, it becomes a bit more complex and you need static routes (but not on the clients). Bill

Bill's summary is on the money. In any case, here is a simple overview on enabling IP Routing on a Windows Server: http://www.anitkb.com/2010/02/how-to-enable-ip-forwarding-on-windows.html Visit my blog: anITKB.com, an IT Knowledge Base.

Thank you for the replies. I agree, looking back in hindsight that having two network cards may not have been a good idea for our infrastructure now, but so far it is working. I don't have to use static routes and I haven't...I just used the ip forwarding and I can now see the linux web server from the desktop clients. Thank you once again and the next time I look at setting up a server I would think twice about two network card setup on the DC.