Windows Forum

Ask something
Discussion Locked

Problems after renaming a WinNT 4 Srvr.

0 helpful
3 replies

by doug.schofield

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Why is it that after renaming a Windows NT 4 server, people are occasionally loosing a connection to the share. The drive is still mapped but it is unaccessible. If you click another drive letter and then refresh the Windows Explorer screen, you can go back to the mapped drive and it will work. No errors can be found. It has the newest drivers and is running sp6a. I'm guessing there might be a problem with the Server Account on the Domain controllers; however, there's no errors.

3 replies

by mckaytech

You haven't said much about your network architecture but we can infer this is a member server rather than a DC. It could be a problem with the machine account on the domain but it seems more likely to be a situation where there are stale WINS records under the old server name. It can be aggravated by WINS replication anomalies that tend to crop up in complex WINS architectures.

I think I would try deleting the WINS records on the primary WINS server, force a scavenging cycle, re-register the server with 'nbtstat -RR' and then force a WINS replication.

I've also heard of a similar problem being solved by removing the server from the domain, forcing a domain syncronization (or just waiting long enough to ensure that one occurs) and then re-adding the server to the domain.

paul

by doug.schofield

I didn't have access to the WINS server to delete the record, but I did submit the command to refresh the server with the WINS database. That appears to of fixed the problem. Thanks, Doug

This discussion is closed to new replies.