Networks

Ask something
Discussion Locked

W98 client won't log on to NT-network

0 helpful
7 replies

by borgesen

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

A W98 notebook client used to logon on to our NT-network problem free.

Suddenly, when the PC starts up, it has begun asking for a Windows logon instead of the Microsoft Network Logon. Regardless of wheater I hit "OK" og "Cancel", the client is not connected to our network.

To get the machine back on the network, I have tried and check the following my self:

* Primary network logon is already set to Microsoft Network
* Properties for "Client program til MS Network" is set to "Log on" & the domaine name is correct.
* The tab "Identifikation" data is correct
* The tab "Admission control" data is correct.
* There is _not_ an auto logon key in regedit
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Network\RealModeNet
* I have tried removing the Clientprogram and installing it again.
* Checked cabel and outlet connection: OK.

Now I am running short of idears and turn here for sugestions. How do I get the "Microsoft Network Logn" screen back, and how do I get the machine back on the network.

Borgesen

7 replies

by Former member

Check to see if the workgroup is the same name as the domain
Check to see if you can ping the domain controller, if not check the IP configuration

by borgesen

Domain and workgroup is the same.
No ping!

I think the only thing left is a faulty hardware...

Thanks for sugestion.

by borgesen

Been there, done that. All in vain.

As I mentioned to "-Q", I think the only thing left is a faulty hardware...

Thanks for sugestion.

by Former member

Well, to check the hardware, ping 127.0.0.1. If this is ok, then your adapter is working fine. I would then check you IP addresses, post them here, the IP/mask/gateway of both the client and the Domain Controller.

by borgesen

You hit the spot with the ping-sugestion. There is absolutely no hole through, confirming what I havent myself been able to establish finaly: Defekt in the on-board NIC. Trying to mount a 3COM PCI NIC returned the same result, sugesting a deeper lying hardware issue. The unit will be shiped to IBM for repair. Thanks for all suggestiones.

This discussion is closed to new replies.