Hi, hopefully someone can point me in the right direction. I have 3 servers on a network all running Windows Server 2008 10.0.0.2 DC and RAS server for NAT 10.0.0.5 DC and DHCP Server and SQL200810.0.0.7 Exchange Server 200710.0.0.2 and 10.0.0.7 work fine as do all the clients 10.0.0.5 will resolve ip addreses on the local network, but won't connect to internet or any external ip addresses? IPCONFIG /ALL produces the following output which all looks fine except for default gateway entry as there is not two entries on the connection config? Ethernet adapter LAN 1: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-0F-1F-6C-68-52 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::7c03:d0d4:6b81:3316%10(Preferred) IPv4 Address. . . . . . . . . . . : 10.0.0.5(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 0.0.0.0 10.0.0.2 DNS Servers . . . . . . . . . . . : ::1 10.0.0.2 NetBIOS over Tcpip. . . . . . . . : Enabled Any thoughts on why it won't route traffic to 10.0.02? Regards Rupertthe problem is not what you don't know it's what you think you know that's wrong

It won't route to the Internet without a default gateway configured. Routing on the local subnet does not require a DG, but to get out to the Internet you need it (unless you are runnng a proxy server). Set the DG to your Internet router (which I presume is the RRAS/NAT server). Get rid of the 0.0.0.0 . Is this server also a DNS server? If not you need to set the DNS server address to your local DNS server, not ::1 (which is the local computer's IPv6 loopback address). Running NAT on a DC is not a good idea. It can give you some strange problems with name resolution.Bill

Bill, Thanks, you confirmed what I suspected. The issue now is that the entries shown above that you indicate are causing the problemare not configured values:Default Gateway . . . . . . . . . : 0.0.0.0 10.0.0.2 DNS Servers . . . . . . . . . . . : ::1 10.0.0.2 The default gateway 0.0.0.0 is not a registered entry on the network interface- where does it come from?The DNS Servers entry ::1 is not a registered entry on the network interface - where does it come from?And as you can see the actual entries 10.0.0.2 and 10.0.0.2 respectively for DG and DNS point to the correct server.Any thoughts on removing the offending entries?Secondly and I know i'm probably trying your patience, if I dont run NAT ona DC then are you simply suggesting running it on a standard server?RegardsRupertthe problem is not what you don't know it's what you think you know that's wrong

Bill,Just a final note, I swapped the network cable to the second card and rebooted the server, this removed the offending config entries and all works fine.Just a response on your favoured setup for servers, clients and NAT if you have a moment.RegardsRupertthe problem is not what you don't know it's what you think you know that's wrong

The preferred method is to run NAT on a hardware device. If you do use a server, do not use a DC. Also do not use a DC as a remote access server. The reason for this is an old problem called multihoming. If a server has more that one NIC it has two IP addresses associated with its name. If a client gets the "wrong" IP for its Netbios or DNS name lookup, things go wrong.Bill