In class we are working with Server 2008 R2 Core, now I'm stuck with trying to build a router of the whole thing since RRAS isn't available. However, since all I need is a static route I figured a route addition on the server should suffice. Let me first try and explain my setup and scenario Server [Baal] has two NICs: NIC 2: Local Area Connection #2: DHCP This NIC is assigned to NAT in VMWare and has been assigned IP address 192.168.244.143 Netmask 255.255.255.0 Gateway 192.168.244.2 NIC 1: Local Area Connection: Static IP address 192.168.1.1 Netmask 255.255.255.0 No gateway On NIC 1 I have DHCP, AD DS and DNS running to provide domain access and DHCP leasing to connected clients. DHCP is configured to use both DNS and Gatway 192.168.1.1 Now, the scenario is that I want the clients connected to NIC 1 to be able to contact WAN on NIC 2. My first attempt was to add a 0.0.0.0 route with my interface NIC 1: route add 0.0.0.0 mask 0.0.0.0 192.168.244.2 metric 30 if 0x3 (NIC 1) But to no use. I'm sorry if I'm not supplying all required information to solve this, please say so in case and I'll post whatever is necessary.

I am not very clear on your scenario, but it doesnt sound like you are on the right track. Maybe a network diagram will help. If you are trying to assign clients on the 192.168.1.1 network, you can do so and the 192.168.1.1 will be their gateway. However, adding a route isnt going to help. Your server needs to be able to route the packets. I am not an expert on CORE, so I am not familiar if you can or cannot run RRAS on that box. If you are unable to run RRAS, then you can resort to IP Fowarding since you only have two interfaces. How to Enable IP Forwarding on Windows Server 200x http://www.anitkb.com/2010/02/how-to-enable-ip-forwarding-on-windows.html Keep in mind that if you'll need to manage the networks in VMWARE so your NIC 1 and NIC 2 should be on their own "VLAN".Visit: anITKB.com, an IT Knowledge Base.

I plotted together a small network diagram. There's a line between 192.168.93.1/24 and 192.168.244.143/24 saying "Route !192.168.93.0/24". In case you don't get what I mean with this is that I want everything but the 192.168.93.0/24 net.

Ok, i understand the network layout. With regard to !192.168.93.0, you are saying "Not to Route 192.168.93.0" where "!=Not"? I am not sure what you mean by not routing. Back to my previous recommendation, if you are unable to take advanatage of RRAS services, if you want to route traffic between the 192.168.93.1 and 192.168.244.143 interface, your only solution is to configure IP FORWARDING on that server. There really is no need for RRAS if routing between two interfaces is the only requirement. Visit: anITKB.com, an IT Knowledge Base.