Networking Forums

Networking Forums > Computer Networking > Windows Networking > Cannot join client PC to domain

Reply
Thread Tools Display Modes

Cannot join client PC to domain

 
 
John Straumann
Guest
Posts: n/a

 
      02-10-2008, 03:32 PM
HI all:

I am trying to join a client to a domain in a lab environment. The server IP
is set to 192.168.1.150, the client to 192.168.1.151, and I have the client
primary DNS server set to 192.168.1.150. The server name is server1, and if
I open a command prompt on the server and type "nslookup server1" the name
resolves correctly. If I do the same thing on the client, I get an error:


*** server1.testdomain.com can't find server1: Server failed"

and when I try to go into the Client properties to add the client to the
domain, after I type the new domain info and click "OK" I get the prompt for
a username and password for and account with permission to join the domain,
but when I enter the credentials and click OK again, I get an error:

"The following error occurred attempting to join the domain "testdomain":
The network path was not found"

In DNS on the server I have a Host (A) entry for 192.168.1.150, and a
reverse Pointer.

Can anyone make some suggestions to start tracking this down?

Thanks.

John.

 
Reply With Quote
 
 
 
 
Meinolf Weber
Guest
Posts: n/a

 
      02-10-2008, 05:25 PM
Hello John,

Please post an ipconfig /all from both machines.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> HI all:
>
> I am trying to join a client to a domain in a lab environment. The
> server IP is set to 192.168.1.150, the client to 192.168.1.151, and I
> have the client primary DNS server set to 192.168.1.150. The server
> name is server1, and if I open a command prompt on the server and type
> "nslookup server1" the name resolves correctly. If I do the same thing
> on the client, I get an error:
>
> *** server1.testdomain.com can't find server1: Server failed"
>
> and when I try to go into the Client properties to add the client to
> the domain, after I type the new domain info and click "OK" I get the
> prompt for a username and password for and account with permission to
> join the domain, but when I enter the credentials and click OK again,
> I get an error:
>
> "The following error occurred attempting to join the domain
> "testdomain": The network path was not found"
>
> In DNS on the server I have a Host (A) entry for 192.168.1.150, and a
> reverse Pointer.
>
> Can anyone make some suggestions to start tracking this down?
>
> Thanks.
>
> John.
>



 
Reply With Quote
 
John Straumann
Guest
Posts: n/a

 
      02-10-2008, 06:52 PM
Hi:

Thanks for the response, here is the info:

John

Client
C:\Users\John>ipconfig /all
Windows IP Configuration

Host Name . . . . . . . . . . . . : Danube_Client
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adaper (Emulated)
Physical Address. . . . . . . . . : 00-03-FF-1A-C6-62
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::546:f408:f82e:1e4c%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.151(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.150
Primary WINS Server . . . . . . . : 192.168.1.150
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4137:9e66:ccd:2e0c:3f57:fe68(Preferred)
Link-local IPv6 Address . . . . . : fe80::ccd:2e0c:3f57:fe68%9(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{F3B26C91-E2BE-4642-A33D-1368B5FC7E9}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::5efe:192.168.1.151%10(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.150
NetBIOS over Tcpip. . . . . . . . : Disabled

Server
C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Server1
Primary Dns Suffix . . . . . . . : testdomain.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : testdomain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-03-FF-FB-A8-9C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.150
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.150



"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:(E-Mail Removed) .com...
> Hello John,
>
> Please post an ipconfig /all from both machines.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> HI all:
>>
>> I am trying to join a client to a domain in a lab environment. The
>> server IP is set to 192.168.1.150, the client to 192.168.1.151, and I
>> have the client primary DNS server set to 192.168.1.150. The server
>> name is server1, and if I open a command prompt on the server and type
>> "nslookup server1" the name resolves correctly. If I do the same thing
>> on the client, I get an error:
>>
>> *** server1.testdomain.com can't find server1: Server failed"
>>
>> and when I try to go into the Client properties to add the client to
>> the domain, after I type the new domain info and click "OK" I get the
>> prompt for a username and password for and account with permission to
>> join the domain, but when I enter the credentials and click OK again,
>> I get an error:
>>
>> "The following error occurred attempting to join the domain
>> "testdomain": The network path was not found"
>>
>> In DNS on the server I have a Host (A) entry for 192.168.1.150, and a
>> reverse Pointer.
>>
>> Can anyone make some suggestions to start tracking this down?
>>
>> Thanks.
>>
>> John.
>>

>
>

 
Reply With Quote
 
Meinolf Weber
Guest
Posts: n/a

 
      02-10-2008, 06:58 PM
Hello John,

Is it a Vista machine or did you enable IPv6 on a XP client? I assume you
can ping the server? Disable IPv6 from the client and try again.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi:
>
> Thanks for the response, here is the info:
>
> John
>
> Client
> C:\Users\John>ipconfig /all
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : Danube_Client
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
> Ethernet
> Adaper (Emulated)
> Physical Address. . . . . . . . . : 00-03-FF-1A-C6-62
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::546:f408:f82e:1e4c%8(Preferred)
> IPv4 Address. . . . . . . . . . . : 192.168.1.151(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.150
> Primary WINS Server . . . . . . . : 192.168.1.150
> NetBIOS over Tcpip. . . . . . . . : Enabled
> Tunnel adapter Local Area Connection* 6:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Teredo Tunneling
> Pseudo-Interface
> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> IPv6 Address. . . . . . . . . . . :
> 2001:0:4137:9e66:ccd:2e0c:3f57:fe68(Preferred)
> Link-local IPv6 Address . . . . . :
> fe80::ccd:2e0c:3f57:fe68%9(Preferred)
> Default Gateway . . . . . . . . . : ::
> NetBIOS over Tcpip. . . . . . . . : Disabled
> Tunnel adapter Local Area Connection* 7:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . :
> isatap.{F3B26C91-E2BE-4642-A33D-1368B5FC7E9}
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::5efe:192.168.1.151%10(Preferred)
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.1.150
> NetBIOS over Tcpip. . . . . . . . : Disabled
> Server
> C:\Documents and Settings\Administrator>ipconfig /all
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Server1
> Primary Dns Suffix . . . . . . . : testdomain.com
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : testdomain.com
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
> Ethernet
> Adapter (Generic)
> Physical Address. . . . . . . . . : 00-03-FF-FB-A8-9C
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.150
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.150
> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news:(E-Mail Removed) .com...
>
>> Hello John,
>>
>> Please post an ipconfig /all from both machines.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> HI all:
>>>
>>> I am trying to join a client to a domain in a lab environment. The
>>> server IP is set to 192.168.1.150, the client to 192.168.1.151, and
>>> I have the client primary DNS server set to 192.168.1.150. The
>>> server name is server1, and if I open a command prompt on the server
>>> and type "nslookup server1" the name resolves correctly. If I do the
>>> same thing on the client, I get an error:
>>>
>>> *** server1.testdomain.com can't find server1: Server failed"
>>>
>>> and when I try to go into the Client properties to add the client to
>>> the domain, after I type the new domain info and click "OK" I get
>>> the prompt for a username and password for and account with
>>> permission to join the domain, but when I enter the credentials and
>>> click OK again, I get an error:
>>>
>>> "The following error occurred attempting to join the domain
>>> "testdomain": The network path was not found"
>>>
>>> In DNS on the server I have a Host (A) entry for 192.168.1.150, and
>>> a reverse Pointer.
>>>
>>> Can anyone make some suggestions to start tracking this down?
>>>
>>> Thanks.
>>>
>>> John.
>>>



 
Reply With Quote
 
John Straumann
Guest
Posts: n/a

 
      02-10-2008, 08:03 PM
Hi:

Yes it is a Vista machine. I disabled IPv6 but still get the same error
message,

"The following error occurred attempting to join the domain
"testdomain": The network path was not found"

also, nslookup server1 returns:

C:\Users\John>nslookup server1
Server: server1.testdomain.com
Address: 192.168.1.150:53

*** server1.testdomain.com can't find server1: Server failed

but if I I try:

C:\Users\John>nslookup server1.testdomain.com
Server: server1.testdomain.com
Address: 192.168.1.150:53

Name: server1.testdomain.com
Address: 192.168.1.150

I also don't understand what the :53 is for, why port 53??

John.

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:(E-Mail Removed) .com...
> Hello John,
>
> Is it a Vista machine or did you enable IPv6 on a XP client? I assume you
> can ping the server? Disable IPv6 from the client and try again.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hi:
>>
>> Thanks for the response, here is the info:
>>
>> John
>>
>> Client
>> C:\Users\John>ipconfig /all
>> Windows IP Configuration
>> Host Name . . . . . . . . . . . . : Danube_Client
>> Primary Dns Suffix . . . . . . . :
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
>> Ethernet
>> Adaper (Emulated)
>> Physical Address. . . . . . . . . : 00-03-FF-1A-C6-62
>> DHCP Enabled. . . . . . . . . . . : No
>> Autoconfiguration Enabled . . . . : Yes
>> Link-local IPv6 Address . . . . . :
>> fe80::546:f408:f82e:1e4c%8(Preferred)
>> IPv4 Address. . . . . . . . . . . : 192.168.1.151(Preferred)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>> Primary WINS Server . . . . . . . : 192.168.1.150
>> NetBIOS over Tcpip. . . . . . . . : Enabled
>> Tunnel adapter Local Area Connection* 6:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Teredo Tunneling
>> Pseudo-Interface
>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
>> DHCP Enabled. . . . . . . . . . . : No
>> Autoconfiguration Enabled . . . . : Yes
>> IPv6 Address. . . . . . . . . . . :
>> 2001:0:4137:9e66:ccd:2e0c:3f57:fe68(Preferred)
>> Link-local IPv6 Address . . . . . :
>> fe80::ccd:2e0c:3f57:fe68%9(Preferred)
>> Default Gateway . . . . . . . . . : ::
>> NetBIOS over Tcpip. . . . . . . . : Disabled
>> Tunnel adapter Local Area Connection* 7:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . :
>> isatap.{F3B26C91-E2BE-4642-A33D-1368B5FC7E9}
>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>> DHCP Enabled. . . . . . . . . . . : No
>> Autoconfiguration Enabled . . . . : Yes
>> Link-local IPv6 Address . . . . . :
>> fe80::5efe:192.168.1.151%10(Preferred)
>> Default Gateway . . . . . . . . . :
>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>> NetBIOS over Tcpip. . . . . . . . : Disabled
>> Server
>> C:\Documents and Settings\Administrator>ipconfig /all
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : Server1
>> Primary Dns Suffix . . . . . . . : testdomain.com
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : testdomain.com
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
>> Ethernet
>> Adapter (Generic)
>> Physical Address. . . . . . . . . : 00-03-FF-FB-A8-9C
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.150
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>> news:(E-Mail Removed) .com...
>>
>>> Hello John,
>>>
>>> Please post an ipconfig /all from both machines.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> HI all:
>>>>
>>>> I am trying to join a client to a domain in a lab environment. The
>>>> server IP is set to 192.168.1.150, the client to 192.168.1.151, and
>>>> I have the client primary DNS server set to 192.168.1.150. The
>>>> server name is server1, and if I open a command prompt on the server
>>>> and type "nslookup server1" the name resolves correctly. If I do the
>>>> same thing on the client, I get an error:
>>>>
>>>> *** server1.testdomain.com can't find server1: Server failed"
>>>>
>>>> and when I try to go into the Client properties to add the client to
>>>> the domain, after I type the new domain info and click "OK" I get
>>>> the prompt for a username and password for and account with
>>>> permission to join the domain, but when I enter the credentials and
>>>> click OK again, I get an error:
>>>>
>>>> "The following error occurred attempting to join the domain
>>>> "testdomain": The network path was not found"
>>>>
>>>> In DNS on the server I have a Host (A) entry for 192.168.1.150, and
>>>> a reverse Pointer.
>>>>
>>>> Can anyone make some suggestions to start tracking this down?
>>>>
>>>> Thanks.
>>>>
>>>> John.
>>>>

>
>

 
Reply With Quote
 
Meinolf Weber
Guest
Posts: n/a

 
      02-10-2008, 08:13 PM
Hello John,

It is the port from DNS. Is the firewall from vista enabled or disabled?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi:
>
> Yes it is a Vista machine. I disabled IPv6 but still get the same
> error message,
>
> "The following error occurred attempting to join the domain
> "testdomain": The network path was not found"
>
> also, nslookup server1 returns:
>
> C:\Users\John>nslookup server1
> Server: server1.testdomain.com
> Address: 192.168.1.150:53
> *** server1.testdomain.com can't find server1: Server failed
>
> but if I I try:
>
> C:\Users\John>nslookup server1.testdomain.com
> Server: server1.testdomain.com
> Address: 192.168.1.150:53
> Name: server1.testdomain.com
> Address: 192.168.1.150
> I also don't understand what the :53 is for, why port 53??
>
> John.
>
> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news:(E-Mail Removed) .com...
>
>> Hello John,
>>
>> Is it a Vista machine or did you enable IPv6 on a XP client? I assume
>> you can ping the server? Disable IPv6 from the client and try again.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hi:
>>>
>>> Thanks for the response, here is the info:
>>>
>>> John
>>>
>>> Client
>>> C:\Users\John>ipconfig /all
>>> Windows IP Configuration
>>> Host Name . . . . . . . . . . . . : Danube_Client
>>> Primary Dns Suffix . . . . . . . :
>>> Node Type . . . . . . . . . . . . : Hybrid
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> Ethernet adapter Local Area Connection:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
>>> Ethernet
>>> Adaper (Emulated)
>>> Physical Address. . . . . . . . . : 00-03-FF-1A-C6-62
>>> DHCP Enabled. . . . . . . . . . . : No
>>> Autoconfiguration Enabled . . . . : Yes
>>> Link-local IPv6 Address . . . . . :
>>> fe80::546:f408:f82e:1e4c%8(Preferred)
>>> IPv4 Address. . . . . . . . . . . : 192.168.1.151(Preferred)
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>>> Primary WINS Server . . . . . . . : 192.168.1.150
>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>> Tunnel adapter Local Area Connection* 6:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Teredo Tunneling
>>> Pseudo-Interface
>>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
>>> DHCP Enabled. . . . . . . . . . . : No
>>> Autoconfiguration Enabled . . . . : Yes
>>> IPv6 Address. . . . . . . . . . . :
>>> 2001:0:4137:9e66:ccd:2e0c:3f57:fe68(Preferred)
>>> Link-local IPv6 Address . . . . . :
>>> fe80::ccd:2e0c:3f57:fe68%9(Preferred)
>>> Default Gateway . . . . . . . . . : ::
>>> NetBIOS over Tcpip. . . . . . . . : Disabled
>>> Tunnel adapter Local Area Connection* 7:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . :
>>> isatap.{F3B26C91-E2BE-4642-A33D-1368B5FC7E9}
>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>> DHCP Enabled. . . . . . . . . . . : No
>>> Autoconfiguration Enabled . . . . : Yes
>>> Link-local IPv6 Address . . . . . :
>>> fe80::5efe:192.168.1.151%10(Preferred)
>>> Default Gateway . . . . . . . . . :
>>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>>> NetBIOS over Tcpip. . . . . . . . : Disabled
>>> Server
>>> C:\Documents and Settings\Administrator>ipconfig /all
>>> Windows IP Configuration
>>> Host Name . . . . . . . . . . . . : Server1
>>> Primary Dns Suffix . . . . . . . : testdomain.com
>>> Node Type . . . . . . . . . . . . : Hybrid
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : testdomain.com
>>> Ethernet adapter Local Area Connection:
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
>>> Ethernet
>>> Adapter (Generic)
>>> Physical Address. . . . . . . . . : 00-03-FF-FB-A8-9C
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.150
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>>> news:(E-Mail Removed) .com...
>>>> Hello John,
>>>>
>>>> Please post an ipconfig /all from both machines.
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> HI all:
>>>>>
>>>>> I am trying to join a client to a domain in a lab environment. The
>>>>> server IP is set to 192.168.1.150, the client to 192.168.1.151,
>>>>> and I have the client primary DNS server set to 192.168.1.150. The
>>>>> server name is server1, and if I open a command prompt on the
>>>>> server and type "nslookup server1" the name resolves correctly. If
>>>>> I do the same thing on the client, I get an error:
>>>>>
>>>>> *** server1.testdomain.com can't find server1: Server failed"
>>>>>
>>>>> and when I try to go into the Client properties to add the client
>>>>> to the domain, after I type the new domain info and click "OK" I
>>>>> get the prompt for a username and password for and account with
>>>>> permission to join the domain, but when I enter the credentials
>>>>> and click OK again, I get an error:
>>>>>
>>>>> "The following error occurred attempting to join the domain
>>>>> "testdomain": The network path was not found"
>>>>>
>>>>> In DNS on the server I have a Host (A) entry for 192.168.1.150,
>>>>> and a reverse Pointer.
>>>>>
>>>>> Can anyone make some suggestions to start tracking this down?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> John.
>>>>>



 
Reply With Quote
 
Robert Bollinger
Guest
Posts: n/a

 
      02-10-2008, 09:00 PM
some questions...

Do you only have 2 machines?

if you run dcdiag on the server does it pass? (support tools will need to be
installed)

have you tired joining like this: testdomain.com ?

I have seen where windows will fail on joining the domain using the netbios
based domain name (testdomain)

you can also run netdiag and and see if it passes ...

assuming you have done basic troubleshooting, such as verifying
connectivity, pinging etc. this sounds like a dns issue. to me.

I would try joing with testdomin.com (btw, you should never use a resolvable
..COM, .NET, etc TLD when setitng up your DC).

Also make sure to disable the WIndows server firewall for this test.

RObert


"John Straumann" wrote:

> HI all:
>
> I am trying to join a client to a domain in a lab environment. The server IP
> is set to 192.168.1.150, the client to 192.168.1.151, and I have the client
> primary DNS server set to 192.168.1.150. The server name is server1, and if
> I open a command prompt on the server and type "nslookup server1" the name
> resolves correctly. If I do the same thing on the client, I get an error:
>
>
> *** server1.testdomain.com can't find server1: Server failed"
>
> and when I try to go into the Client properties to add the client to the
> domain, after I type the new domain info and click "OK" I get the prompt for
> a username and password for and account with permission to join the domain,
> but when I enter the credentials and click OK again, I get an error:
>
> "The following error occurred attempting to join the domain "testdomain":
> The network path was not found"
>
> In DNS on the server I have a Host (A) entry for 192.168.1.150, and a
> reverse Pointer.
>
> Can anyone make some suggestions to start tracking this down?
>
> Thanks.
>
> John.
>

 
Reply With Quote
 
John Straumann
Guest
Posts: n/a

 
      02-10-2008, 09:17 PM
HI:

It was enabled, so I disabled it and tried again but got the same error.

John.


"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:(E-Mail Removed) .com...
> Hello John,
>
> It is the port from DNS. Is the firewall from vista enabled or disabled?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hi:
>>
>> Yes it is a Vista machine. I disabled IPv6 but still get the same
>> error message,
>>
>> "The following error occurred attempting to join the domain
>> "testdomain": The network path was not found"
>>
>> also, nslookup server1 returns:
>>
>> C:\Users\John>nslookup server1
>> Server: server1.testdomain.com
>> Address: 192.168.1.150:53
>> *** server1.testdomain.com can't find server1: Server failed
>>
>> but if I I try:
>>
>> C:\Users\John>nslookup server1.testdomain.com
>> Server: server1.testdomain.com
>> Address: 192.168.1.150:53
>> Name: server1.testdomain.com
>> Address: 192.168.1.150
>> I also don't understand what the :53 is for, why port 53??
>>
>> John.
>>
>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>> news:(E-Mail Removed) .com...
>>
>>> Hello John,
>>>
>>> Is it a Vista machine or did you enable IPv6 on a XP client? I assume
>>> you can ping the server? Disable IPv6 from the client and try again.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> Hi:
>>>>
>>>> Thanks for the response, here is the info:
>>>>
>>>> John
>>>>
>>>> Client
>>>> C:\Users\John>ipconfig /all
>>>> Windows IP Configuration
>>>> Host Name . . . . . . . . . . . . : Danube_Client
>>>> Primary Dns Suffix . . . . . . . :
>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>> IP Routing Enabled. . . . . . . . : No
>>>> WINS Proxy Enabled. . . . . . . . : No
>>>> Ethernet adapter Local Area Connection:
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
>>>> Ethernet
>>>> Adaper (Emulated)
>>>> Physical Address. . . . . . . . . : 00-03-FF-1A-C6-62
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Link-local IPv6 Address . . . . . :
>>>> fe80::546:f408:f82e:1e4c%8(Preferred)
>>>> IPv4 Address. . . . . . . . . . . : 192.168.1.151(Preferred)
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>>>> Primary WINS Server . . . . . . . : 192.168.1.150
>>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>>> Tunnel adapter Local Area Connection* 6:
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : Teredo Tunneling
>>>> Pseudo-Interface
>>>> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> IPv6 Address. . . . . . . . . . . :
>>>> 2001:0:4137:9e66:ccd:2e0c:3f57:fe68(Preferred)
>>>> Link-local IPv6 Address . . . . . :
>>>> fe80::ccd:2e0c:3f57:fe68%9(Preferred)
>>>> Default Gateway . . . . . . . . . : ::
>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
>>>> Tunnel adapter Local Area Connection* 7:
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . :
>>>> isatap.{F3B26C91-E2BE-4642-A33D-1368B5FC7E9}
>>>> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> Link-local IPv6 Address . . . . . :
>>>> fe80::5efe:192.168.1.151%10(Preferred)
>>>> Default Gateway . . . . . . . . . :
>>>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>>>> NetBIOS over Tcpip. . . . . . . . : Disabled
>>>> Server
>>>> C:\Documents and Settings\Administrator>ipconfig /all
>>>> Windows IP Configuration
>>>> Host Name . . . . . . . . . . . . : Server1
>>>> Primary Dns Suffix . . . . . . . : testdomain.com
>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>> IP Routing Enabled. . . . . . . . : No
>>>> WINS Proxy Enabled. . . . . . . . : No
>>>> DNS Suffix Search List. . . . . . : testdomain.com
>>>> Ethernet adapter Local Area Connection:
>>>> Connection-specific DNS Suffix . :
>>>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
>>>> Ethernet
>>>> Adapter (Generic)
>>>> Physical Address. . . . . . . . . : 00-03-FF-FB-A8-9C
>>>> DHCP Enabled. . . . . . . . . . . : No
>>>> IP Address. . . . . . . . . . . . : 192.168.1.150
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.1.1
>>>> DNS Servers . . . . . . . . . . . : 192.168.1.150
>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>>>> news:(E-Mail Removed) .com...
>>>>> Hello John,
>>>>>
>>>>> Please post an ipconfig /all from both machines.
>>>>>
>>>>> Best regards
>>>>>
>>>>> Meinolf Weber
>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>> and
>>>>> confers no rights.
>>>>> ** Please do NOT email, only reply to Newsgroups
>>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>> HI all:
>>>>>>
>>>>>> I am trying to join a client to a domain in a lab environment. The
>>>>>> server IP is set to 192.168.1.150, the client to 192.168.1.151,
>>>>>> and I have the client primary DNS server set to 192.168.1.150. The
>>>>>> server name is server1, and if I open a command prompt on the
>>>>>> server and type "nslookup server1" the name resolves correctly. If
>>>>>> I do the same thing on the client, I get an error:
>>>>>>
>>>>>> *** server1.testdomain.com can't find server1: Server failed"
>>>>>>
>>>>>> and when I try to go into the Client properties to add the client
>>>>>> to the domain, after I type the new domain info and click "OK" I
>>>>>> get the prompt for a username and password for and account with
>>>>>> permission to join the domain, but when I enter the credentials
>>>>>> and click OK again, I get an error:
>>>>>>
>>>>>> "The following error occurred attempting to join the domain
>>>>>> "testdomain": The network path was not found"
>>>>>>
>>>>>> In DNS on the server I have a Host (A) entry for 192.168.1.150,
>>>>>> and a reverse Pointer.
>>>>>>
>>>>>> Can anyone make some suggestions to start tracking this down?
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> John.
>>>>>>

>
>

 
Reply With Quote
 
John Straumann
Guest
Posts: n/a

 
      02-10-2008, 09:30 PM
Yes only 2 machines right now

Yes, dcdiag passes

When I tried testdomain.com, I get the same error. Windows firewall was
disabled.

When I ran netdiag, I got a "skipped" message on WINS saying no WINS server
is configured.

Yes I can ping 192.168.1.150, I think it is a DNS error too, but haven't the
foggiest how to track it down.

John.




"Robert Bollinger" <(E-Mail Removed)> wrote in
message news:33E1E0AE-98D3-4DA0-A668-(E-Mail Removed)...
> some questions...
>
> Do you only have 2 machines?
>
> if you run dcdiag on the server does it pass? (support tools will need to
> be
> installed)
>
> have you tired joining like this: testdomain.com ?
>
> I have seen where windows will fail on joining the domain using the
> netbios
> based domain name (testdomain)
>
> you can also run netdiag and and see if it passes ...
>
> assuming you have done basic troubleshooting, such as verifying
> connectivity, pinging etc. this sounds like a dns issue. to me.
>
> I would try joing with testdomin.com (btw, you should never use a
> resolvable
> .COM, .NET, etc TLD when setitng up your DC).
>
> Also make sure to disable the WIndows server firewall for this test.
>
> RObert
>
>
> "John Straumann" wrote:
>
>> HI all:
>>
>> I am trying to join a client to a domain in a lab environment. The server
>> IP
>> is set to 192.168.1.150, the client to 192.168.1.151, and I have the
>> client
>> primary DNS server set to 192.168.1.150. The server name is server1, and
>> if
>> I open a command prompt on the server and type "nslookup server1" the
>> name
>> resolves correctly. If I do the same thing on the client, I get an error:
>>
>>
>> *** server1.testdomain.com can't find server1: Server failed"
>>
>> and when I try to go into the Client properties to add the client to the
>> domain, after I type the new domain info and click "OK" I get the prompt
>> for
>> a username and password for and account with permission to join the
>> domain,
>> but when I enter the credentials and click OK again, I get an error:
>>
>> "The following error occurred attempting to join the domain "testdomain":
>> The network path was not found"
>>
>> In DNS on the server I have a Host (A) entry for 192.168.1.150, and a
>> reverse Pointer.
>>
>> Can anyone make some suggestions to start tracking this down?
>>
>> Thanks.
>>
>> John.
>>

 
Reply With Quote
 
John Straumann
Guest
Posts: n/a

 
      02-10-2008, 09:39 PM
Found it:

http://support.microsoft.com/kb/258500




"Robert Bollinger" <(E-Mail Removed)> wrote in
message news:33E1E0AE-98D3-4DA0-A668-(E-Mail Removed)...
> some questions...
>
> Do you only have 2 machines?
>
> if you run dcdiag on the server does it pass? (support tools will need to
> be
> installed)
>
> have you tired joining like this: testdomain.com ?
>
> I have seen where windows will fail on joining the domain using the
> netbios
> based domain name (testdomain)
>
> you can also run netdiag and and see if it passes ...
>
> assuming you have done basic troubleshooting, such as verifying
> connectivity, pinging etc. this sounds like a dns issue. to me.
>
> I would try joing with testdomin.com (btw, you should never use a
> resolvable
> .COM, .NET, etc TLD when setitng up your DC).
>
> Also make sure to disable the WIndows server firewall for this test.
>
> RObert
>
>
> "John Straumann" wrote:
>
>> HI all:
>>
>> I am trying to join a client to a domain in a lab environment. The server
>> IP
>> is set to 192.168.1.150, the client to 192.168.1.151, and I have the
>> client
>> primary DNS server set to 192.168.1.150. The server name is server1, and
>> if
>> I open a command prompt on the server and type "nslookup server1" the
>> name
>> resolves correctly. If I do the same thing on the client, I get an error:
>>
>>
>> *** server1.testdomain.com can't find server1: Server failed"
>>
>> and when I try to go into the Client properties to add the client to the
>> domain, after I type the new domain info and click "OK" I get the prompt
>> for
>> a username and password for and account with permission to join the
>> domain,
>> but when I enter the credentials and click OK again, I get an error:
>>
>> "The following error occurred attempting to join the domain "testdomain":
>> The network path was not found"
>>
>> In DNS on the server I have a Host (A) entry for 192.168.1.150, and a
>> reverse Pointer.
>>
>> Can anyone make some suggestions to start tracking this down?
>>
>> Thanks.
>>
>> John.
>>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Unable to join SBS 2003 Domain on XP client Beterman Windows Networking 8 07-11-2009 05:15 AM
Client cannot join the domain john Windows Networking 7 02-13-2009 05:55 AM
How to configure VPN client to join a domain? Jack Tan Windows Networking 3 08-23-2004 08:18 PM
XP client cannot join domain in other VLAN julian Windows Networking 4 06-09-2004 05:13 PM
Cannot Join Windows 2000 Client to Windows Server 2003 Domain Nicholas White Windows Networking 1 05-03-2004 01:23 PM



1 2 3 4 5 6 7 8 9 10 11