Windows XP/2000 Computer Clients Cannot Login to Windows 2000 Server D

[Knight2004K]

I have a new Windows 2000 Server installed as Active Directory PDC.
The domain user accounts are authorized to add workstations to the
domain. I verified this by checking the Local Policy Setting on the
Server.
>
When I enter the login information to change my Windows XP (or any
other)client to the Domain I get the error message
>
"The following error occurred attempting to join the domain
'myDomainName':
The network path was not found."
>
1. I can ping the PDC myDomainName.com from the XP clients.
2. My non-XP clients can ping the PDC myDomainIP address.
3. The PDC can ping the clients.
4. Tracert is successful.
5. NSLookup is successful with clients primary dns pointing toward PDC.
>
The final test performed was to use a client to PDC server connection with rollover cable.
Still I get the same 'network path not found' error message.
I have tried the suggestions from others in users groups who have had
similar problems to no avail. I have also used reference
documentation from master server books. Somehow resolving this issue
is not being presented clearly enough.
>
Is there something I am missing that is causing this problem? What
else can I do to resolve this issue. Any and all suggestions are
welcome.
>

 

[Binks7]

Knight:

Make sure the DNS setting on the clients is the server address and not the ISP DNS. Then setup a forwarder in DNS on the server with the ISP DNS address. In DNS highlight the server, go the action menu /properties/forwarder tab and put in ISP DNS. If forwarder option is dimmed - delete the "." root server zone in Forward Lookup, then refresh - should open up the option.

 

[Serbtastic]

Try entering the PDCs IP as the primary WINS server in the XP client's TCP/IP settings.

Let me know how that works out for you.

 

[alguzman]

Try to visit this site

http://www.almondeyes.net/

and go to the windows tab. There is an excellent article written about how to join a domain and troubleshooting problems joining. The author recently helped me solve my problems joing a workstation on wondows 2K domain.

Good Luck.

 

[SlntKnight]

Thanks All -

I followed your suggestions and I still get the "path not found" error message from the clients. I am still reading through the

http://www.almondeyes.com

tip and will continue with troubleshooting today. I am wide open to other suggestions or ideas.

 

[Binks7]

Knight:

I assume that Client for Microsoft networks is installed on your clients. This error is consistent with that missing. Is your DNS authorized?

 

[SlntKnight]

Client for Microsoft networks is installed. DNS is operational on the W2K server. Is there anywhere else I need to check for DNS authorization?

 

[GiaBetiu]

As the error is saying is not about authorization here.
Error 67 is "the network name cannot be found." So, you said that you follow the explainations from my site.
what is saying your computer when you are trying:
net use \\server\ipc$ password /user:domain/username ?
Same error?
What is saying when you are trying let's say:
net use \\server\c$ password /user:administrator ?

What is in that article is a comprehensive explaination of the process of joining. What didn't you understand? What debugging steps did you do and what are the results??


Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new:

http://www.almondeyes.net

(just started)

 

[SlntKnight]

GiaBetiu -

At my client pc I try...
c:\>net use \\server\ipc$ password /user:domain/username
I get...
The user context supplied is invalid.

More help is available by typing NET HELPMSG 3775.
-----------------------------------------------------------
When I try...
c:\>net use \\server\c$ password /user:administrator
I get...
System error 53 has occurred.

The network path was not found.
-----------------------------------------------------------
My clients have static IP addresses we don't have the server configured to act as dhcp server. We do have the server as dns ADPDC.
-----------------------------------------------------------
On my clientPC when I netdiag /v I get...
C:\>Netdiag /v

Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing IpConfig - pinging the DHCP Server... Failed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Failed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
Local Area Connection
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
Gathering Winsock information.
Testing DNS
Testing redirector and browser... Passed
Testing trust relationships... Skipped
Testing Kerberos authentication... Skipped
Gathering routing information
Gathering network statistics information.
Gathering configuration of bindings.
Gathering RAS connection information
Gathering Modem information
Gathering Netware information
Gathering IP Security information

Tests complete.

...and a lot more stuff.
-----------------------------------------------------------

On the ClientPC using just netdiag I get...
C:\>Netdiag

...............................

Computer Name: *****29789635
DNS Host Name: *****29789635
System info : Windows 2000 Professional (Build 2600)
Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
List of installed hotfixes :
Q147222
Q323255
Q328310
Q329048
Q329115
Q329170
Q329390
Q329441
Q329834
Q331953
Q810565
Q810577
Q810833
Q811630
Q814033


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : *****29789635
Autoconfiguration IP Address : 192.168.1.9
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.254
***.***.232.10
***.***.232.11


AutoConfiguration results. . . . . . : Failed
[WARNING] AutoConfiguration is in use. DHCP not available.

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.

Adapter : IPX Internal Interface

Netcard queries test . . . : Passed

Ipx configration
Network Number . . . . : 00000000
Node . . . . . . . . . : 000000000001
Frame type . . . . . . : Ethernet II



Adapter : IpxLoopbackAdapter

Netcard queries test . . . : Passed

Ipx configration
Network Number . . . . : 1234cdef
Node . . . . . . . . . : 000000000002
Frame type . . . . . . : 802.2



Adapter : NDISWANIPX

Netcard queries test . . . : Passed

Ipx configration
Network Number . . . . : 00000000
Node . . . . . . . . . : 50fc20524153
Frame type . . . . . . : Ethernet II




Global results:


Domain membership test . . . . . . : Passed
Dns domain name is not specified.
Dns forest name is not specified.


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Failed
[FATAL] All adapters are autoconfigured.
The DHCP servers are unreachable. Please check cables, hubs, and taps.



IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Skipped


DC list test . . . . . . . . . . . : Skipped


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped


LDAP test. . . . . . . . . . . . . : Skipped


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed


Netware configuration
You are not logged in to your preferred server .
Netware User Name. . . . . . . :
Netware Server Name. . . . . . :
Netware Tree Name. . . . . . . :
Netware Workstation Context. . :

IP Security test . . . . . . . . . : Passed
Service status is: Started
Service startup is: Automatic
IPSec service is available, but no policy is assigned or active
Note: run "ipseccmd /?" for more detailed information


The command completed successfully
-----------------------------------------------------------
On the client using


C:\>netdiag /debug

Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing IpConfig - pinging the DHCP Server... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Failed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
Local Area Connection
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
Gathering Winsock information.
Testing DNS
Testing redirector and browser... Passed
Testing trust relationships... Skipped
Testing Kerberos authentication... Skipped
Gathering routing information
Gathering network statistics information.
Gathering configuration of bindings.
Gathering RAS connection information
Gathering Modem information
Gathering Netware information
Gathering IP Security information

Tests complete.


Computer Name: *****29789635
DNS Host Name: *****29789635
DNS Domain Name: (null)
System info : Windows 2000 Professional (Build 2600)
Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
Hotfixes :
Installed? Name
Yes Q147222
Yes Q323255
Yes Q328310
Yes Q329048
Yes Q329115
Yes Q329170
Yes Q329390
Yes Q329441
Yes Q329834
Yes Q331953
Yes Q810565
Yes Q810577
Yes Q810833
Yes Q811630
Yes Q814033


Netcard queries test . . . . . . . : Passed

Information of Netcard drivers:

---------------------------------------------------------------------------
Description: Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport
Device: \DEVICE\{94C4355B-B91D-49A8-9CAB-3672B5EC148D}

Media State: Connected

Device State: Connected
Connect Time: 00:51:23
Media Speed: 100 Mbps

Packets Sent: 3051
Bytes Sent (Optional): 0

Packets Received: 3257
Directed Pkts Recd (Optional): 2166
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

---------------------------------------------------------------------------
Description: Intel(R) PRO/100 VE Network Connection
Device: \DEVICE\{2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}

Media State: Connected

Device State: Connected
Connect Time: 00:51:23
Media Speed: 100 Mbps

Packets Sent: 3051
Bytes Sent (Optional): 0

Packets Received: 3257
Directed Pkts Recd (Optional): 2166
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

---------------------------------------------------------------------------
[PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

Adapter : Local Area Connection
Adapter ID . . . . . . . . : {2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : *****29789635
Description. . . . . . . . : Intel(R) PRO/100 VE Network Connection - Packet Scheduler Minip
ort
Physical Address . . . . . : 00-07-E9-EB-74-96
Dhcp Enabled . . . . . . . : Yes
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
Autoconfiguration IP Address : 192.168.1.9
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.254
***.***.232.10
***.***.232.11

IpConfig results . . . . . : Passed
Pinging DHCP server - reachable

AutoConfiguration results. . . . . . : Failed
[WARNING] AutoConfiguration is in use. DHCP not available.

Default gateway test . . . : Passed
Pinging gateway 192.168.1.1 - reachable
At least one gateway reachable for this adapter.

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}
*****29789635 <00> UNIQUE REGISTERED
KPUKTNTVW1 <00> GROUP REGISTERED
*****29789635 <20> UNIQUE REGISTERED
*****29789635 <03> UNIQUE REGISTERED
KPUKTNTVW1 <1E> GROUP REGISTERED

NetBios Resolution : via DHCP

Netbios Remote Cache Table
Name Type HostAddress Life [sec]
---------------------------------------------------------------
KPUKTNTVW <1B> UNIQUE 192.168.1.4 597
MUSIC <20> UNIQUE 192.168.1.130 597
WTTW2K <20> UNIQUE 192.168.1.253 597


WINS service test. . . . . : Skipped
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
There are no WINS servers configured for this interface.

Adapter : IPX Internal Interface
Adapter ID . . . . . . . . : Internal

Netcard queries test . . . : Passed

Ipx configration
Network Number . . . . : 00000000
Node . . . . . . . . . : 000000000001
Frame type . . . . . . : Ethernet II



Adapter : IpxLoopbackAdapter
Adapter ID . . . . . . . . : IpxLoopbackAdapter

Netcard queries test . . . : Passed

Ipx configration
Network Number . . . . : 1234cdef
Node . . . . . . . . . : 000000000002
Frame type . . . . . . : 802.2



Adapter : NDISWANIPX
Adapter ID . . . . . . . . : NDISWANIPX

Netcard queries test . . . : Passed

Ipx configration
Network Number . . . . : 00000000
Node . . . . . . . . . : 50fc20524153
Frame type . . . . . . : Ethernet II




Global results:


IP General configuration
LMHOSTS Enabled. . . . . . . . : Yes
DNS for WINS resolution. . . . : Enabled
Node Type. . . . . . . . . . . : Broadcast
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No



Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Standalone Workstation
Netbios Workgroup name . . . . : KPUKTNTVW1
Dns domain name is not specified.
Dns forest name is not specified.
Domain Guid. . . . . . . . . . : {00000000-0000-0000-0000-000000000000}
Logon User . . . . . . . . . . : Blofeld
Logon Domain . . . . . . . . . : *****29789635


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Failed
[FATAL] All adapters are autoconfigured.
The DHCP servers are unreachable. Please check cables, hubs, and taps.



IP loopback ping test. . . . . . . : Passed
PASS - pinging IP loopback address was successful.
Your IP stack is most probably OK.


Default gateway test . . . . . . . : Passed
PASS - you have at least one reachable gateway.


NetBT name test. . . . . . . . . . : Passed
No NetBT scope defined

PASS - The NetBT is properly configured.
There is at least one interface where the <00> 'WorkStation Service',
<03> 'Messenger Service', <20> 'WINS' names are defined and they are
not in conflict.


Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 19
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: RSVP UDP Service Provider
Provider Version :6
Description: RSVP TCP Service Provider
Provider Version :6
Max message size : Stream Oriented
Description: MSAFD nwlnkipx [IPX]
Provider Version :2
Description: MSAFD nwlnkspx [SPX]
Provider Version :2
Max message size : depends on MTU
Description: MSAFD nwlnkspx [SPX] [Pseudo Stream]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD nwlnkspx [SPX II]
Provider Version :2
Max message size : depends on MTU
Description: MSAFD nwlnkspx [SPX II] [Pseudo Stream]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD NetBIOS [\Device\NwlnkNb] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NwlnkNb] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{42622052-BD89-4331-8785-94DA85244E93}] SEQP
ACKET 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{42622052-BD89-4331-8785-94DA85244E93}] DATA
GRAM 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}] SEQP
ACKET 2
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}] DATA
GRAM 2
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{76F10697-EC3D-473F-A87D-943DFD25FA6B}] SEQP
ACKET 3
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{76F10697-EC3D-473F-A87D-943DFD25FA6B}] DATA
GRAM 3
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{67B7A0A8-5532-425F-8623-E885AFE35C2C}] SEQP
ACKET 4
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{67B7A0A8-5532-425F-8623-E885AFE35C2C}] DATA
GRAM 4
Provider Version :2

Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
Interface {2EC17AFE-DCEB-4A81-9EE8-1B67DD036669}
DNS Domain:
DNS Servers: 192.168.1.254 ***.***.232.10 ***.***.232.11
IP Address: 192.168.1.9

...and a whole lot more stuff.
-----------------------------------------------------------

Is there anything else you need?

 

[Binks7]

The errors listed might indicate a conflict with the NIC. Check to see if there are any interupt conflicts with the NIC.

 

[GiaBetiu]

Till I will have an indepth look on your netdiag ( that I don't like that you cut the real values btw), try the right commands. Don't tell me that you typed exaclty what I said.
You should have:
- a domain name, let's say that is named: mycompany
- user account used for joining workstation, le't say that is JohnDoe. So his full name is: mycompany\johndoe (take care is \ not / .. as i misstyoed before)
- your domain controller should have a name, let's say: mydc1
here is how your command will look then:
net use \\mydc1\ipc$ /user:mycompany\johndoe
after this it should ask you for a password.

second command will be:
net use \\mydc1\c$ /user:administrator


Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new:

http://www.almondeyes.net

(just started)

 

[GiaBetiu]

Since you have this problem on al your clients, (you said this), then I suppose that you just connected them to a hub an let them run.
That could be the explaination why your Ip configuration is autoconfigured. = when windows cannot find a DHCP server, then is assigning itslef an address.
If you don't want to use DHCP, then configure them with fixed addresses. = manually added.
Another thing is that all your computers have a local DNS there and also the two DNSes from your provider. Is not a mistake this, but better leave your local DNS doing this through DNS forwarding.
I see that you have also IPX installed there. Do you need it? Not that is an error, but one advie is remove the protocols that you don't need.

Send me please via email this time the
c:\winnt\debug\netsetup.log file also.

Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new:

http://www.almondeyes.net

(just started)

 

[tlcscousin]

Also what is the default gateway pointing to? If the server is running DNS and its IP is not 192.168.1.1 and is in fact 192.168.1.254 then set the default gateway pointing to that IP address. If the machine running192.168.1.1 is not running DNS it will not be able to tell the clients where the server is by FQDN name.

 

[tomselvam]

Can u please check the name of your new domain whether it has any unwanted characters. If so change and try.

Tom

 

[Redfox1]

A couple of possible solutions - may already have been said before

********************
On the client the command should be:
net use \\server\ipc$ password /user:domain\username

NOT:
net use \\server\ipc$ password /user:domain/username

This will fail because you're trying to use the local admin to create a computer account in an AD!
net use \\server\ipc$ password /user:administrator
********************
What is the &quot;workgroup&quot; name that the clients are in?
Could you make it the same as the domain name? What happens?



Even though you're not a member of the domain you should still be able to map a drive letter:
Right click on network neighborhood and type in:
X:
\\<server>\<sharename>

login as:
<domain>\administrator

See what you get...

********************
Also, install network monitor OR ethereal on both the DC and a client and watch the traffic. It will Reveal a LOT of information about the possible traffic you might be seeing from a badly configured network card or a setting in one of the NIC properties.

*******************
Although they all look good:
Double check your subnet masks... a lot of times that would mess things up pretty bad...

********************
Even though you can ping:
Do you have a router between the clients & the DC?
If so, does the DC's Default gateway point to that inbetween gateway or to another router (to the internet?)

If there is a router (router A) between the clients & the DC AND your DC is pointing to ANOTHER router (router B) as it's default gateway AND router A doesn't about the client's network you'll need to add a route on the DC for the client network

<internet?>
|
Router A (DC's default gateway)
|
|
DC (IP: 192.168.1.100)
Lan: 192.168.1.x/24 or 255.255.255.0)
|
|
Router B (192.168.1.254 and 192.168.2.1)
|
|
Clients
Lan: 192.168.2.x/24 or 255.255.255.0)

Execute the followin as admon on the DC:
route add 192.168.2.0 MASK 255.255.255.0 192.168.1.254

 

[Janufa]

Is this problem allready solved?