Windows Forum

Ask something
Discussion Locked

No domain server available in NT-98

0 helpful
12 replies

by xanderoth

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Ok, not as easy as it first appears. A firewall/router is handing out DHCP addresses on a custom network. The client computer receives an address. The client can get on the internet through the network. WINS is enabled on the server. The server, gateway, and all other clients on the network can be pinged by address but not resolved by name. The client cannot map a drive or login to the server with windows or through a command prompt entry. Any ideas?

12 replies

by faisalmasood

1) Make sure u have latest Service packs installed
2) Do u have subnets configured or using single subnet? If there are more than 1 subnets, then did u configured WINs proxy agent?
3) Try to check WINS. Is it working properly?
4) Check event log in NT for any errors.

by xanderoth

Service pack 6a installed on server. Single subnet being used, no errors in NT Event Viewer, and WINS is working correctly. No other computer has a problem on the network.

by mphoffar

Try adding your PDC and BDC names and adresses to a hosts file local on the machine. It sounds like you're getting DNS resolution, but not WINS resolution

Mark

by xanderoth

I have created static routing tables for WINS and DNS. No good. No other clients are having any other network issues.

by xanderoth

I found that the file win.com exists in many different directories. MKB said to remove them, as they can cause problems with WINS, I did and it did nothing. I also found that this particular WIN98 machine was forcing browser elections every 12 minutes or so on the network. Im gonna assume I got a bad NIC unless anyone has another suggestion?

by ins413

Just a thought, and you may have already tried this. Check the tcp/ip properties of the nic. There should be a check box or radio button, something to the effect of "Enable netbios over tcp/ip" or "use wins settng from DHCP server". I aplogize for not being able to be more specific. Good luck.

by xanderoth

The enable NetBIOS over tcp/ip box is actually grayed out. It appears to be checked though, I am simply unable to de-select it.

by nettek

If you can ping by IP address but not by name, and you have a WINS server running, then you have a problem with WINS. There could be a number of different issues. Check the following:

1. You do not say if your WINS server is receiving an IP address from your DHCP server. Your WINS server requires a static address. Otherwise, how will the clients know how to find your WINS server?
2. The WINS server must point to itself in it's network properties as both the primary and secondary WINS server.
3. Your WINS server should not be multihomed. That is, it should only have one NIC installed that resides on your internal network.
4. If your DHCP server is not configured to give your clients the address of your WINS server, then you must manually configure the setting on your clients.

Check out the following MSKB article for more info:
Q185786

by nettek

I apologize. I thought this was happening to all your clients, but apparently it is only happening to one.

Try using the Find Computer on the client. This uses NetBIOS broadcasts for resolution. If you can find computers by name using the Start -> Find -> Computer, then my guess is that your client cannot find the WINS server. You may want to add an LMHOSTS file to that client to see if that solves the problem.

If you cannot find computers using the Find Computer feature, then my guess isthat you have a corrupted protocol stack. Try removing all network setting, reboot, and then reinstall the adapters and protocol.

by xanderoth

I already created a lmhosts file with no success. The WINS server is set to a static IP. The client can ping the WINS server by IP. My final attempt was actually to remove the adapter and uninstall it, then reinstall. Alas, to my misfortune, it was unsuccesful. I am going to replace the NIC altogether.

by xanderoth

I am closing this seeing how I am going to replace the NIC and forget about it. And if all else fails, fdist format and forget it.

This discussion is closed to new replies.