Discussion Locked

No log on box in win95 workstations

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Network with a 200 computers mostly NT 4.0 but I have some Win 95 and win2k. I use TCP/IP as communication protocol and the MS system policies witch (among other things) is supposed to restrict users to enter the computer without login to the network. The problem I've found with the win 95 workstations is that, some times, they don't show the log on box and users don't even have a chance to connect to the network. After rebooting the computer several times, it shows the logon box. The only solution I've found so far to avoid this problem is to add Netbeui but this is not right since it increases the network traffic.

13 replies

by ataveras

You have to remove the network settings and re install them but make sura to add the service you need.
Simle TCP/IP Services, SNMP Service, RPC Configuration, and and make sure that you chosen workgroup.

by aperezalonso

This solution works temporaly to make the computer access the network but the proble will happen again.

by magetower

If you are running pure TCP/IP then make sure you are running a WINS server and that all clients are configured to use it. It sounds like the 95 systems are not seeing the logon server when they startup. This usually indicates that they are not resolving the server. WINS will correct this.

If you are subnetted you should have a DNS running to assist in name resolution.

If you are using DHCP you need to make sure that the DHCP settings include WINS and DNS addressing.

by aperezalonso

I have DHCP including WINS, plus I would have problem with the other workstations (NT and win2K) if they couldn't see the server.

by aperezalonso

That's precisely what I have but even with the poledit it doesn't show the box so they are not restricted. It only works this way with Netbeui.

by dcadmin

Go to the networking properties and click on Windows client (or Client for Windows Networking;whatever it is called),click on the properties box and make sure the settings are correct in there.

by shanghai sam

The settings are correct, plus, if it was a client configuration problem, it would not work with other protocols either.

by jwilczyn

Run "regedit", delete the AutoLogon entry in the registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Network\Real Mode Net
AutoLogon=xx
Restart PC.
If you need more information - go to MS Q141858.

by aperezalonso

I checked the registry of several computers that showed the problem and none of them have the AutoLogon entry in the registry.

by estebandelatorre

2 THINGS COULD BE

a.- they don't login to the network
a.1.- They press the esc key
a.2.- choose another domain or local machine)

For a.1 There is a key in the registry which forces win9x to log on the network. There is a very well documented issue at support.microsoft.com, seach for "force logon"

For a.2. You have to set policies in order to prohibit the log on to other domains and a local policy to inhibit local logon

b.- The users are NOT prompted for a logon box (in win9x). This may be due to a:
b1.- No ip address available from DHCP server scope (verify your DHCP scope)
b.2.- There's a conectivity problem in the network )phisical) or the nic cards are unable to match the hub/switch speed, due to autosensing features of one of both. It needs more than one try in order to get connected (boots)
b.3.- Update your nic card drivers to the latest available.
Hope it helps!!

This discussion is closed to new replies.