Discussion Locked

Windows 98 Will Not Log On To Domain

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello all,

To be quite frank, i'm not sure if this question should be under this topic or a networking topic. Anyhow, here is the scenario. About a week ago all of our Windows 98 machines quit logging onto our network (Win NT 4.0) with a message saying that a domain server could not be found. There is not one particular brand of PC, or network card, and the only commonality that I could find was that they were all Win 98. I've tried reconfiguring the network card, and even installing different network cards. All of our Windows NT and 2000 computers continue to connect to the network succesfully. The only recent changes in our network were the replacement of our old 10 mbps hubs with new cisco 10/100 switches. Does anyone out there have an explanation, or even better a resolution?

Any help is greatly appreciated.

Thanks,

Mike Lyter
tech@aejtc.org

7 replies

by admin-stuart

I assume you've checked one or more of the affected clients' Network components and their settings to make sure nothing has changed?

If so, and no settings are awry, you might try uninstalling the components and reinstalling all of them (adapter, protocol, and client) on one of the affected clients to see if that restores network logon.

by digital maverick

I?ve had a similar problem & found that windows 98 doesn't have as much patience as NT, after a quick look for a network it gives up.

If both the hub & NIC?s speed settings are on auto detect then it can time out the connection, force one of thema fixed speed.

You don?t say how many network protocols you?re running, the more protocols the slower the network. If you only need to run one, TCP, then remove the rest.

Hope this helps

by caper

Are you using DHCP on the server? If so once the clients have been disconnected and cannot immediatly contact the DHCP server they will autoconfigure an IP in the APIA range. Check this with the winipcfg command. I would uninstall the TCP\IP stack and remove all traces of TCP\IP from the registry of each affected computer...check the MS KB for the exact keys to delete from the registry. Make sure the DHCP server is fired up and then try making connections.

This discussion is closed to new replies.