Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

nt4 server and windows xp

Status
Not open for further replies.

Bl0x

IS-IT--Management
Jan 10, 2004
7
GB
i have a windows nt4 server and an assortment of op systems logging on to it but the xp sp1 client keep losing network connection when logged in for a duration of time.
 

How about checking the Event Viewer in XP to see what's going on?

More information is needed.
 
I am having a similar problem.

I have a new XP SP1 workstation which I am trying to add to a NT 4.0 domain. I go through the process from the workstation, it welcomes me to the domain then reboots. I check Server Manager and the workstation is there, but it gives me an error:
"The trust relationship between the workstation and the primary domain controller failed".
I am able to ping the workstation name, so it is getting DNS and DHCP. When I try to log into the workstation, I get this error:
"Windows cannot connect to the domain because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear, contact your system administrator for assistance."

As I said before, I can see the account in Server Manager on my BDC, and have deleted and re-added it from there as well as un-joining and re-joining the domain from the workstation...

Any ideas?
 
I tried a few options I found from MS:

1) Set Local Policy called "DomainMember: Digitally encrypt or sign secure channel data (always)" to Disabled. Still no dice. This was suggested because the encryption would not work with WinNT, so it needed to be disabled.

2) ENabled NetBios over TCP/IP in WINS. Not sure why, but this was mentioned specifically in response to the error recieved. This did not work either.

3) There was a suggestion to update or disable FSecure Antivirus, but since I'm not running that product, I disregarded this solution.

4) Lastly, they suggested I install the netdom.exe and the nltest.exe utilities from the XP CDRom and try to reset the security channel that way. It denied me access, so that didn't work either.

5) There appears to be a registry hack to try as well, though that makes me nervous.

BTW, the server is NT 4.0 Terminal Server, SP 6.
 
Use a known brand of network card that you know works well in WinXP. Do not mix and match network card on your network environment. Big headache!

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top