server 2008 network path not found joining 2003 domain
I have a new server that I loaded Windows Server 2008 Ent x64 on and I am receiving the error "Network Path not Found" when joining to an existing 2003 domain. The IP of the server is a static address. My DNS server is running on my DC which is running 2003. I have double checked this setting in my TCP/IP settings. When I ping other servers on the domain their names resolve properly. The 2008 box has not been activated because my Product Key is for 2008 R2, and I installed 2008 (non-R2). I am downloading the R2 DVD right now, but I don't think that this is the problem is it? I have turned the firewall off on the 2008 box and have not yet installed antivirus.
December 5th, 2010 1:44pm

Hello, please post an unedited ipconfig /all from the existing DC/DNS server and the new one.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 1:51pm

the new server is not going to be a DC. existing dc (2003) C:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : dc1-phoenix1 Primary Dns Suffix . . . . . . . : mere.tns.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : mere.tns.com tns.com Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : mere.tns.com Description . . . . . . . . . . . : HP NC7760 Gigabit Server Adapter #2 Physical Address. . . . . . . . . : 00-12-79-92-3F-71 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 172.16.12.3 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.16.12.1 DNS Servers . . . . . . . . . . . : 172.16.12.3 172.16.10.2 Primary WINS Server . . . . . . . : 192.168.100.19 new server (2008) C:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : fs4-phoenix1 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Team 1: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : BASP Virtual Adapter Physical Address. . . . . . . . . : 84-2B-2B-62-66-C6 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 172.25.12.5(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.25.12.1 DNS Servers . . . . . . . . . . . : 172.25.12.3 172.25.10.2 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 8: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{74E5A9AE-DBBA-457C-8596-B2BFDC4CF 2D9} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes thanks for your help!
December 5th, 2010 2:37pm

Hello, your DC/DNS dc1-phoenix1 is located in a complete different subnet as the new server. Also the new server doesn't use it as DNS server on the NIC, please clarify this kind of setup.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 2:49pm

my appologies here is the new ipconfig... C:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : fs4-phoenix1 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Team 1: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : BASP Virtual Adapter Physical Address. . . . . . . . . : 84-2B-2B-62-66-C6 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 172.16.12.5(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.16.12.1 DNS Servers . . . . . . . . . . . : 172.16.12.3 172.16.10.2 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 8: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{74E5A9AE-DBBA-457C-8596-B2BFDC4CF 2D9} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes thanks for your help!
December 5th, 2010 3:45pm

Hello, please use only the 172.16.12.3 as DNS server on the NIC so only the same subnet is used. After change run ipconfig /flushdns. Is the new machine running on a Virtual server as VM, if yes which Virtual server software i used? Is the time/date and time zone the same as on the domain you like to join?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 3:58pm

ok, I was reading elsewhere about network teaming. So I disolved the team and disabled one of the NICs and changed it to DHCP (DC is also my DHCP server). Now when I do an IP config on the new server I get an ip of .162 and a DNS suffix of mere.tns.com ...so far so good. Side Note - I have been able to join Win7 boxes with no problems and they were on DHCP. I then flushed the DNS as you requested, and then pinged the DC by name and received a reply. I then pinged the new server by name from the DC and received the reply of the new IP address (.162). I then tried to add it to the domain again and again received the error "network path not found". I am rebooting the server now, and will try again, but I don't think that will have an impact.thanks for your help!
December 5th, 2010 4:24pm

ok the problem was the time like you suggested. I forgot to check that, but was going back over your list and found that the new server was one hour off! Thank you for your time and for sticking with me.thanks for your help!
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 4:33pm

Hello, for teamed NICs it is important when using DCs, only Failover is supported from Microsoft NOT load balancing so check the DCs for it. Nice to hear that you found it, thanks for the feedback.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
December 5th, 2010 4:46pm

huh, didn't know that. I will check that on my DC. I have a network team on that server as well and it was set to load balance. I was having problems so I disabled one with the intentions of going back and addressing it later. I can't remember the specifics of the issue, but today I just noticed it was disabled. Funny you brought it up. I will take your advice. I definately don't need load balancing on that server!thanks for your help!
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2010 4:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics