XP can't get on a NT 4 domain?!?!?
Hey all, I'm having a big problem, and I appricate it if someone who knows the answer could help out. I've just been given to new XP computers, that I have setup on a domain. The domain server is a NT 4.
Hey all,
I'm having a big problem, and I appricate it if someone who knows the answer could help out. I've just been given to new XP computers, that I have setup on a domain. The domain server is a NT 4.0 server. I've setup a computer account under Server Manager, and I've given user names under user manager for each of the computers. Now here is the strange part. When ever I try to logon to the domain, the XP computers claim the domain server is not avalible! However, I can still get files over the network etc on the XP computers, just no one else on the domain can see the XP computers! Also, when I goto server manager, and click on the XP computers, it says "The trust relationship between this workstation and the primary domain failed." How should I fix this?!?!? It's driving me off the wall :-(.
I'm having a big problem, and I appricate it if someone who knows the answer could help out. I've just been given to new XP computers, that I have setup on a domain. The domain server is a NT 4.0 server. I've setup a computer account under Server Manager, and I've given user names under user manager for each of the computers. Now here is the strange part. When ever I try to logon to the domain, the XP computers claim the domain server is not avalible! However, I can still get files over the network etc on the XP computers, just no one else on the domain can see the XP computers! Also, when I goto server manager, and click on the XP computers, it says "The trust relationship between this workstation and the primary domain failed." How should I fix this?!?!? It's driving me off the wall :-(.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
If you've added the computer names ahead of time using server manager. Then delete them. Only add computers to the domain from the workstations themselves. I've had no end of phone calls from Help Desk techs adding computers to the domain using Server Manager for a quick fix instead of doing it from the workstation.
Hmmmm, r u using DHCP? If so go into the network properties of each workstation and make sure that the unselected network settings are blank of all settings. Make sure that no IP settings are specified.
It seems to me that these workstations aren't joined to the domian. Are you sure you've added them?
Right-click on my computer. Properties. Computer Name.
It seems to me that these workstations aren't joined to the domian. Are you sure you've added them?
Right-click on my computer. Properties. Computer Name.
Sounds more like the workstations cannot determine who and where the domain controllers are. Just because they can ping them by name (assuming they can at this point), that doesn't mean they are "aware" that the servers are DCs. What are you using to host DHCP? Are you using the NT Server, or some other DHCP hosting service?
One more thing, if you added the clients manually in server manager (which you are supposed to be able to, and it does *sometimes* work ) they may take a while to get cycled out of the domain. If possible, you could try renaming one of the workstations, and then having it rejoin the domain but this time attempt the join from the workstation directly.
One more thing, if you added the clients manually in server manager (which you are supposed to be able to, and it does *sometimes* work ) they may take a while to get cycled out of the domain. If possible, you could try renaming one of the workstations, and then having it rejoin the domain but this time attempt the join from the workstation directly.
Actually, it isn't that buggy itself, put more an issue of domain behavior (SIDs, replication, etc.). Once you have managed (as in added and removed many objects) a domain for a year or so, you tend to get used to its behavior and can anticipate it. I used to add systems to the domain like you did initially as that was how I was taught, but after adding my first workstation during installation by mistake I haven't had a reason to go back.
As for your systems, try enabling NetBIOS over TCP/IP and make sure that your servers are setup the same way (which they should be).
As for your systems, try enabling NetBIOS over TCP/IP and make sure that your servers are setup the same way (which they should be).
Help, I seem to have a very similar issue. I have a company who has 8 XP workstations and had to reformat 2 of them. Now they cannot join the NT 4.0 Domain and get the Error "The network name cannot be found."
I verified the XP Pro machine can resolve the name to IP by pinging the seerver by name successfully. I also checked the "Enable NetBIOS overTCP/IP" box to make sure.
At this time I am at a stand still and not sure what is going wrong with the joining process.
Any help would be greatly appreciated.
I verified the XP Pro machine can resolve the name to IP by pinging the seerver by name successfully. I also checked the "Enable NetBIOS overTCP/IP" box to make sure.
At this time I am at a stand still and not sure what is going wrong with the joining process.
Any help would be greatly appreciated.
Try this:
Obviously you need the Browser and Server services running. Add the 2 RPC services.
Start
Run
Type Gpedit.msc
Local computer policy
Windows settings
Secutity settings
Local policy
Security options
Select Network security; lAN manager authenticate
from drop down select Send LM & NTLM - Use NTLMv2 session security if negotiated
Reboot
If that doesnt work, try joining to workgroup instead of domain.
Obviously you need the Browser and Server services running. Add the 2 RPC services.
Start
Run
Type Gpedit.msc
Local computer policy
Windows settings
Secutity settings
Local policy
Security options
Select Network security; lAN manager authenticate
from drop down select Send LM & NTLM - Use NTLMv2 session security if negotiated
Reboot
If that doesnt work, try joining to workgroup instead of domain.
