XP Pro Can't Join Domain - WITS END!!

[danomaniac]

I really tried to solve this on my own before asking for help. Now that I have bald spots on my head, here I am.

I have read through as many posts as I could find on the subject and tried everything suggested, but still can't join the domain.

Here's the deal:

Win 2K server - AD/DNS/DHCP
XP Pro Client - Dell Precision 360 - Delivered today.
Local Area Network Properties -
1. Client for Microsoft Networks
2. File and Printer Sharing for Microsoft Networks
3. Qos Packet Scheduler
4. NWLink NetBIOS
5. NWLink IPX/SPX/NetBIOS Comp. Transport Protocol
6. Internet Protocol (TCP/IP)

TCP/IP Properties:

General:
- Obtain IP address automatically
- Use the following DNS server addresses:
- Preferred DNS Server: 10.1.0.100 (Win2K srv IP)

Advanced:
- IP Settings:
- DHCP Enabled
- Default Gateway - 10.1.0.254 - Metric Automatic

- DNS:
DNS server addresses...
10.1.0.100

Append these DNS suffixes ...
domainname

DNS Suffix for this connection: domainname
Register this connection's addresses in DNS checked

-WINS:

Enable LMHOSTS Lookup NOT checked
NetBIOS setting: Enable NetBIOS over TCP/IP



I can ping the server using both IP and Server Name.
I can ping the XP Pro from another Client using both IP and NetBIOS name

I can see all computers on the network through My Network Places EXCEPT the Domain Controller.

When I try to join the domain I get the error message '...network path not found.'

I have tried a different wall jack.
I have tried a different NIC
I am almost ready to try a 12-guage.

Please - if I've missed something - please help.

thanks

Dan



"It's more like it is now, than it ever has been."

 

[bcastner]

"Network path not found."

Maybe you are using an incorrect IP for the Domain Name Service (DNS) server?

Make sure you have correct DNS and WINS settings.

If you cannot ping and/or nslookup the Domain Controller, it is suggestive of a typing error or somesuch thing in the DNS entry.

 

[danomaniac]

From the XP Pro Client I can ping the domain controller using both IP and server name.

From the Domain Controller I can ping the XP client using both IP and computer name.

From the XP Pro Client I can use nslookup the domain controller name and resolve a valid IP address.

I can browse the network from any PC on the network and see the XP Pro Client pc as a member of the domain - yet from the XP Pro machine, I can NOT see the domain controller NOR can I join the domain - never did.

From another pc on the network, if I type: Ping xpclient

I get back 'Pinging xpclient.domain ...'

Make any sense at all?



"It's more like it is now, than it ever has been."

 

[bcastner]

In the absence of a WINS server, I am going to make a tentative guess that it is a Master Browser issue.

On the XP workstation, start, run, services.msc

Scroll down to Computer Browser
Stop the service
Set the startup setting to Disabled

If you could as well right-click Network Places, Properties, Advanced, and see if you can be certain that the Novell/NW/IPX protocol stuff is moved last in the priority order of bindings.

Reboot.

The Master Browser in a Domain setting has to be the Domain Controller. XP has at least coequal status with your DC in a browser war. This is not a good thing in a Domain setting. This is one reason why WINS or even LMHOSTS are usually used in the a Domain setting.

 

[jtrovato]

Any reason why you are using netware and QOS?

I removed QOS on the XP machines.
You don't need WINS, DNS will work fine without WINS.

I was having the same problem... and I was pulling my hair out too.

A few things to maybe check for:

1. Did you update to the latest service packs on both 2000 srv and Xp pro?
2. What is displayed when you do IPCONFIG /ALL on both machines?
3. The server's DNS on the ethernet adapter should be 127.0.0.1 according MS.
4. I disable 802.1x authentication on the XP pro clients.
5. I also removed the built in firewall on the XP pro. I know this is not a fix for the issue you are hauving, but if you don't need it, get rid of it.

Send us the IPCONFIG /ALL output for both.

 

[bcastner]

From:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

Troubleshooting the Domain Locator Process

To troubleshoot the domain locator process:
Check Event Viewer to see whether the event logs contain any error information. On both the client and the server, check the System log for failures during the logon process. Also, check the Directory Service logs on the server and the DNS logs on the DNS server.

To view Event Viewer in Windows XP, click Start, click Control Panel, double-click Administrative Tools, and then double-click Event Viewer.

Check the IP configuration by running the ipconfig /all command at a command prompt. Verify that the configuration is correct for your network.

Use the Ping utility to verify network connectivity and name resolution. Ping both the IP address and the server name.

Check the Network Diagnostics tool in Help and Support under "Use Tools to view your computer information and diagnose problems" to determine whether the network components are correctly installed and working properly. Network Diagnostics also runs some tests and provides information about the network configuration, information that can be helpful.

Use the nltest /dsgetdc:domainname command to verify that a domain controller can be located for a specific domain. The NLTest tool is installed with the Windows XP support tools.

For information about how to install these tools, refer to the following article in the Microsoft Knowledge Base:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;306794

How to Install the Support Tools from the Windows XP CD-ROM

Use the NSLookup tool to verify that DNS entries are correctly registered in DNS. Verify that the server host records and GUID SRV records can be resolved.

For example, to verify record registration, use the following commands:
nslookup server_name.child_of_root_domain.root_domain.com
nslookup guid._msdcs.root_domain.com

If either of these commands does not succeed, use one of the following methods to reregister records with DNS:

To force host record registration, type ipconfig /registerdns.

To force domain controller service registration, stop and then restart the Netlogon service.

· To verify appropriate LDAP connectivity, use the Ldp.exe tool to connect and bind to the domain controller. Ldp.exe is a support tool that you can install from the Windows XP CD-ROM.

For information about how to install these tools, refer to the following article in the Microsoft Knowledge Base:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;306794

How to Install the Support Tools from the Windows XP CD-ROM

If you suspect that a particular domain controller has problems, turn on the Netlogon debug logging. Use the NLTest utility by typing nltest /dbflag:0x2000ffff at a command prompt. The information is logged in the Debug folder in the Netlogon.log file.

If you still have not isolated the problem, use Network Monitor to monitor network traffic between the client and the domain controller.

********* end citation

To see suggestions for the entries on the DNS server, see this thread:

http://support.microsoft.com/?kbid=288801?scid=kb;en-us;314861

 

[bcastner]

XP Slow Browsing Domain
thread779-540080

 

[danomaniac]

Thanks for all the great replies...Still can't join the domain. Here's what I've done:

I've installed the resource kit from the cd...

nslookup

nltest /dclist:domain -
I_NetGetDCList Failed:Status=2453 0x995 NERR_DCNotFound

I can ping from either machine using both IP and computer name.

I stopped the Master Browser service.

Netlogon service starts then immediately stops - message says it's normal to stop if it has nothing to do...it's set to automatic.

ipconfig /displaydns -
Windows IP Configuration
1.0.0.127.in-addr.arpa
-------------------------------------------------------
Record Name . . . . . :1.0.0.127.in-addr.arpa.
Record Type . . . . . :12
Time To Live. . . . . :604046
Data Length . . . . . :4
Section . . . . . . . :Answer
PTR Record. . . . . . :localhost

localhost
-------------------------------------------------------
Record Name . . . . . :localhost
Record Type . . . . . :1
Time To Live. . . . . :604046
Data Length . . . . . :4
Section . . . . . . . :Answer
A (Host) Record . . . :127.0.0.1



ldp connects to the server fine.

I can browse the network via My Network Places, but I can't see the server - everything else is there.


I've removed QoS

...I think that's it.

"It's more like it is now, than it ever has been."

 

[danomaniac]

In case anyone is interested...Problem resolved. I installed NetBEUI and voila - I could see the server. I'm not sure if this is the best fix, but I'm not going to jack with it anymore. Thanks for all the help.

"It's more like it is now, than it ever has been."

 

[bcastner]

That will work, but I do not like it. But I have done the same to solve intractable problems with name resolution.

I do recommend you follow the advice of using the Win2k Netbui service rather than XP's, and other tips found in this very good article by Finney:

http://www.scotsnewsletter.com/40.htm

 

[danomaniac]

Thanks for the tip. I don't much care for it either. I'll read the article later, but it looks like good info.

thanks again,

Dan

"It's more like it is now, than it ever has been."