Strange network connection problem

I have a network of PCs all running Windows 98. Most of the machines
have Netgear cards, and the network uses a Netgear unmanaged switch to
connect the machines together. All the machines have fixed IP
addresses.

I am experiencing a problem with one of the machines. When it is
booted up, it will not connect to the network. The user is unable to
browse the network, and even pinging other machines does not work.
However, if I change the Priamary Network Logon from Client for
Microsoft Networks to Microsoft Family Logon, or vice-versa, when the
machine reboots it connects instantly.

The following may also shed some light on the problem:

I have just recently changed the network from DHCP assigned IP
addresses to fixed IP addresses. Before I made the change, I still had
a problem with this machine, in that it would sometimes be slow, or
refuse to connect to the network. Running WINIPCFG and repeatedly
refreshing the connection would eventually restore the connection, but
of course that is not an option now.

I am totally baffled, is there anyone out there who can shed any light
on the problem?

Try running the registry editor, open this registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\
Network\Real Mode Net

and delete the value named "AutoLogon".

Then reboot.

Carey



"Dave Bradshaw" <"dave"&"."&"bradshaw"&"@"&"bowbros"&"."&"co"&"."& "uk">
wrote in message news:(E-Mail Removed)...
>I have a network of PCs all running Windows 98. Most of the machines
> have Netgear cards, and the network uses a Netgear unmanaged switch to
> connect the machines together. All the machines have fixed IP
> addresses.
>
> I am experiencing a problem with one of the machines. When it is
> booted up, it will not connect to the network. The user is unable to
> browse the network, and even pinging other machines does not work.
> However, if I change the Priamary Network Logon from Client for
> Microsoft Networks to Microsoft Family Logon, or vice-versa, when the
> machine reboots it connects instantly.
>
> The following may also shed some light on the problem:
>
> I have just recently changed the network from DHCP assigned IP
> addresses to fixed IP addresses. Before I made the change, I still had
> a problem with this machine, in that it would sometimes be slow, or
> refuse to connect to the network. Running WINIPCFG and repeatedly
> refreshing the connection would eventually restore the connection, but
> of course that is not an option now.
>
> I am totally baffled, is there anyone out there who can shed any light
> on the problem?