General discussion

Locked

From WINS to DNS woes on NT 4.0

By luciusism ·
We have a network where computer name are all unique, but unfortunately I don't know if the DNS hostnames are all unique. We recently removed WINS from our NT server and are now solely relying on a registered DNS server that also provides our internet access.

After removing WINS, some users cannot get ip address from our dhcp server. Yet if I go to winipcfg, I can release and renew manually and it works.

The problem seems that when the user boots, they can't get an ip address from our dhcp server, but if they logon locally, then release/renew, THEN they can logon to the network. This seems weird, and I was wondering if anyone had ideas what?s wrong?

Thanks!

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

From WINS to DNS woes on NT 4.0

by dmiles In reply to From WINS to DNS woes on ...

Check your printer setup,at times printers will cause the IP addresses to be missed read or changed once it hits the DHCP server.

Collapse -

From WINS to DNS woes on NT 4.0

by luciusism In reply to From WINS to DNS woes on ...

The question was auto-closed by TechRepublic

Collapse -

From WINS to DNS woes on NT 4.0

by Stillatit In reply to From WINS to DNS woes on ...

1. If you are using a registered DNS server (not on your NT), ask the admin to print a list of your registered names for you. You can check the list for duplicates.

2. Note that if you do not use WINS then the best you can do with stations that receive DHCP addresses is to have static DNS names for each possible IP address. You have no way of knowing, in DNS, which addresses are currently assigned to computers, and what those computer names are. (This changes in Win2K.)

3. When you removed WINS, did you change the node type that DHCP was specifying to DHCP clients? If you were forcing type H-node (Hybrid) when using WINS you need to take it out or change it to B-node (1). This may somehow be affecting your ability to broadcast for aDHCP address (although I don't see how).

4. It sounds from your description that something else changed. Your DHCP server sounds like it is reponding to direct tcp/ip traffic (a renew message) but not to a broadcast (bootup -- give me an address). If your network has multiple segments, does this problem affect all of them? If it only affects the ones where the DHCP server is not, you may have somehow turned off bootp request forwarding.

5. Another possibility is that your DHCP server is out of addresses. If you release the address on a station without renewing, and then reboot the station, does it find the DHCP server?

Good luck.

Collapse -

From WINS to DNS woes on NT 4.0

by luciusism In reply to From WINS to DNS woes on ...

The question was auto-closed by TechRepublic

Collapse -

From WINS to DNS woes on NT 4.0

by dbowlin In reply to From WINS to DNS woes on ...

In addition to the above answers. One other easy thing to check is the NIC. Try swapping another NIC into the machine to see if the problem goes away.

Collapse -

From WINS to DNS woes on NT 4.0

by luciusism In reply to From WINS to DNS woes on ...

The question was auto-closed by TechRepublic

Collapse -

From WINS to DNS woes on NT 4.0

by luciusism In reply to From WINS to DNS woes on ...

This question was auto closed due to inactivity

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums