My second Windows Server 2003 domain controller is no longer able to connect to my network or ping other clients or servers, but I am able to remote into the server from a client. It was working fine up until I installed an IIS role, not sure if it's related to that or not. I am able to ping the server from a client. The server also acts as a VPN remote access server. Below is the result of an "ipconfig /all". There are two network connections. C:\Documents and Settings\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : nira-server4 Primary Dns Suffix . . . . . . . : local.nira.com Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : Yes DNS Suffix Search List. . . . . . : local.nira.com nira.com PPP adapter RAS Server (Dial In) Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface Physical Address. . . . . . . . . : 00-53-45-00-00-00 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.49 Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NETGEAR GA311 Gigabit Adapter Physical Address. . . . . . . . . : 00-0F-B5-FB-33-B4 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.110 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.100 NetBIOS over Tcpip. . . . . . . . : Disabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection Physical Address. . . . . . . . . : 00-C0-9F-1F-FE-82 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.104 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.100 NetBIOS over Tcpip. . . . . . . . : Disabled C:\Documents and Settings\Administrator>

There are many web pages devoted to the problems of multi-homed DCs. Here is one, for example: http://forums.techarena.in/active-directory/1206965.htm I suggest you disable one of your gigabit NICs and see if that improves the situation. Teaming those NICs might be tolerable (if indeed you will be able to team the Netgear NIC. The Intel NIC will team with Intel Proset software. Roger Faucher Microsoft MVP Most Valuable Professional 2004-2011 Roger Faucher Printing and Image MVP - Since 2004

The server also acts as a VPN remote access server. You should have a dedicated RRAS Server, do not use your DC for this. Multihoming a Windows Server http://networkadminkb.com/Shared%20Documents/Multihoming%20a%20Windows%20Server.aspx

Hi, Thanks for posting here. Yes, multihomed domain controller is always not recommended . Meanwhile, I suspect that this issue may due to the duplicate default gateway settings on these NICs. Could you please post the “route print” result from this server here ? See the recommended configuration for mulitihomed host form the link below: Default Gateway Configuration for Multihomed Computers http://support.microsoft.com/kb/157025 Thanks. Tiger LiPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.