XP not finding domain

[RIOT]

I've set up an XP Pro Ed. computer on my companies domain, but when I try to log-in, I get an error that the domain could not be reached. If I log-in as administrator on the computer's "domain" I can browse the domain I'm trying to log-in. Another thing... when I'm browsing the network response is very, very slow... when it works. Most of the time Windows Explorer stops responding and I have to go to task manager to shut the thing off. I have tcp/ip, client for Microsoft Networks, File and Print Sharing, QoS Packet Scheduler, and NWlink ipx/spx/NetBIOS Compatible Transport Protocol. The domain controller for the domain in a Windows 2000 server.

[Mr_Miner]

Try enabling NetBIOS over TCP/IP. That worked for me.

[RIOT]

[quote]Originally posted by Mr_Miner:
<strong>Try enabling NetBIOS over TCP/IP. That worked for me.</strong><hr></blockquote>

Didn't work for me....

[tha 4NiK8R]

remove IPX

[RIOT]

[quote]Originally posted by tha 4NiK8R:
<strong>remove IPX</strong><hr></blockquote>

Did that, but it didn't help. I also tried installing NetBEUI from the XP CD, but that didn't help. Should I have to do anything to the server? All the user accounts are in organizational unit in the domain. Would I have to include that info on the login somehow? Never had to do that for 95/98/NT.

[Ya_know]

[quote]Originally posted by RIOT:
<strong>

Did that, but it didn't help. I also tried installing NetBEUI from the XP CD, but that didn't help. Should I have to do anything to the server? All the user accounts are in organizational unit in the domain. Would I have to include that info on the login somehow? Never had to do that for 95/98/NT.</strong><hr></blockquote>

Have you any NT4/2K/XP workstations functioning normally in active Directory, and on the Network? If not, and this is your first NT PC added, you may want to try to add the PC through AD Users and Computers first. You are supposed to be able to add the PC from the Network ID tab in system properties, (as long as you have the ability to add workstations to the domain with your login), but it seems that you can't see the domain to get denied permission. It sounds fishy that you can browse the domain, you just can't authenticate to it through a domain controller.

Have you double checked the NIC drivers, and maybe download a newer version from the manufacture and test it out? If anything, just to eliminate the variable.

[RIOT]

[quote]Originally posted by Ya_know:
<strong>

Have you any NT4/2K/XP workstations functioning normally in active Directory, and on the Network? If not, and this is your first NT PC added, you may want to try to add the PC through AD Users and Computers first. You are supposed to be able to add the PC from the Network ID tab in system properties, (as long as you have the ability to add workstations to the domain with your login), but it seems that you can't see the domain to get denied permission. It sounds fishy that you can browse the domain, you just can't authenticate to it through a domain controller.

Have you double checked the NIC drivers, and maybe download a newer version from the manufacture and test it out? If anything, just to eliminate the variable.</strong><hr></blockquote>

Nope, we have 95/98/NT all connected to this server. All of those work great. I've tried manually adding a computer to the domain, but that didn't quite work. Something else that's fishy. When I set up the computer, I got it to reconize the domain, I think. Under 'Computer Name' in 'System Properties', the computer shows the domain as the one I'm wanting it to log on to. I've tried using 'Network ID' to reconnect the machine to the domain, but I get the error "DNS name does not exist." The error code is 0x0000232B RCODE_NAME_ERROR. I've searched the KB for this error, but I haven't found anything that would seem to fix this. I'll look for newer drivers.

Nope. Newer drivers didn't help at all.

[Ya_know]

Well damn it man! We gotta work something out!

Just to clarify my suspicion...this is the same company that had the new PC's with XP Home by mistake; you then ordered Pro, right?

I am going to bang this around my head a little bit. Hopefully someone will have solved your problem by the time I check back.

Good luck!

[RIOT]

[quote]Originally posted by Ya_know:
<strong>Well damn it man! We gotta work something out!

Just to clarify my suspicion...this is the same company that had the new PC's with XP Home by mistake; you then ordered Pro, right?

I am going to bang this around my head a little bit. Hopefully someone will have solved your problem by the time I check back.

Good luck!</strong><hr></blockquote>

Yep!! Actually my boss ordered them. I first tried an upgrade, but the computer wasn't named what I wanted it to be, and I couldn't change it. I could use my user account to log-on the domain, but no one else's would work. Not even the Admin account. I figured it was something screwed up with the upgrade, so I completely wiped the hard drive, reformatted (NTFS), and reinstalled. Now I'm sitting here wondering what else to try. If you go to MS Help Newsgroups, you'll see that I posted this same problem
<a href="http://communities.microsoft.com/newsgroups/default.asp?icp=GSS&slcid=us" target="_blank">there</a>. (under Windows, Windows XP, Windows XP: Networking and the Web) I posted using my real name, Jonathan Conn.

A woman that works here gave me a hammer for a wedding present back in March that never made it home.... I'm about to relieve some stress with it and this computer!!

[RIOT]

Oh Hell Yeah!!!!

I got it to work!!!

Someone on the Microsoft Newsgroup pointed out that XP requires DNS for Active Directory to work correctly. This wasn't needed for 95/98/ME, so I had never configured DNS. I configured it on my W2K server, pointed my XP machine to it only, and it FREAKIN' WORKS!!!

Here are some KB articles that cover DNS:
Q237675
Q260371

[Ya_know]

No sh!t! DNS, I bet your network was only using WINS. I can't believe none of us even suggested a DNS issue. You would have then said, "DNS I don't currently use DNS..."

Anyway, I am glad to hear things worked out without us...