Windows Forum

Ask something
Discussion Locked

win2k pro in NT4 network

0 helpful
10 replies

by dcadmin 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a few win2k machines in a nt4 network and I am having problems doing basic management function from the win2k boxes. In computer management I will try and "manage another computer" and I can't see my own domain, but if I put in the UNC it will connect. Same with trying to add a user to my computer, I can't see the domain, the groups, or users. I checked the other NT 4 workstations and there is no problem. Also I can see another domain (two way trust) without a problem. Other simuluar related problems are happening. Any Solutions?

10 replies

by bearded_wonder

Sound like your W2k machines are trying to use DDNS for name resolution and not WINS(this is the default for W2k). If you don't plan on upgrading your DNS servers to DDNS (bind 8.2.2) you may solve your name resolution problems by just turning off the DDNS client on the W2k machines as follows:
1) Right click "My Network Places", select "Properties"
2) Right click "Local Area Connection...", then select ""Properties"
3) Select "Internet Protocol (TCP/IP)" from the list, click "Properties", click "Advanced", select the "DNS" tab.
4) Deselect "Register this connection's address in DNS" check box.
You may need to restart for this to take effect.
If this doesn't help- follow up with info about what you have for DNS, WINS, and DHCP- maybe someone can pick it up from there.
Good Luck!

by dcadmin

Good start, but that box wasn't checked, there is a DNS and Wins server in the other domain and a wins server in my domain, all are setup like the nt4 boxes, and we are not using DHCP.

Thanks for trying, maybe I'll hear from you again.

by bearded_wonder

OK, so I don't have the answer...
Maybe if I ask a few questions I can help you think it through.
If you do an ipconfig /all do you get the answers you expect?
Do the W2k machines have problems browsing the network outside of the MMC? If so, I would still look for a NetBios name resolution problem. Maybe toss an LMHOSTS file onto one of the machines and see if that helps it navigate.
Do the W2k machines show up in server manager as being domain members? Even if they do you might try removing one of them and then adding it back to the domain.
Good Luck!

by dcadmin

Thanks for tossing things at me, but I can see the computers on the domain, apps like spquery can access them, I added the lmhosts, the problem is when I reference the domain by name, it can't find it, but if I reference the pdc for User Manager forfrom Resource kit, it will say pdc in domain "domain" setting the focus in "domain". and then it works. I don't mean to reject the answer, but I would like to get it fully functional. Thanks!

by vagab0nd

Hi,

Looks like the first guy is right in some way. I had a similar problem with W2K pro workstation in NT 4 net.
The issue was solved when I found out that someone has set WINS address in TCP/IP properties while we were using DHCP to give clients this info. Although address was correct it didn't seem to work. So I just cleaned it out and let DHCP do its work.
Thats not completely true for you as you don't use DHCP but may be this will help you find the solution.

Good luck

by lastsurvivor

Are you synching the time on your domain. We had a similar problem with Win2000 Servers in a WinNT 4.0 Domain. By default Win2000 uses NT5DS Time Service with W32TIME while NT 4.0 uses NTP. You can change the registry on the Win2000 Box to use NTP if you are using w32time in your domain. The Q article is Q258059. If you are using TimeServ you should update to w32time.

by dcadmin

I have solved the problem, apparently over the weekend the wins database, decided to tombstone the master browser entry for the domain "domain[1bh]" so I couldn't see the network. For some reason the nt4 machines could perform functions that win2000 machines couldn't with that entry tombstoned. So I went and added a static mapping for it and everything came back. Thanks for all the suggestions!! I hope I can help all of you in the future

This discussion is closed to new replies.