2000 Server Hanging at Logon

[Guest]

I have a 2000 Server SP4 running AD and DNS that is hanging at logon. The
server boots normally and does not hang at building network connections.
However when you logon it loads a blank desktop and hangs for approximately 2
minutes, then it will load the rest of the desktop. After the desktop is
loaded the “Local Area Network Connection†Icon does not appear in the
taskbar (Even though that option is selected in the NIC properties) and any
application that requires network access hangs (IE: Internet Explorer, My
Network Places, etc.) I cannot even access the properties of the NIC without
it hanging. However, if I physically unplug the patch cord from the NIC and
then plug it back in, the “Local Area Network Connection Icon†will appear in
the task bar and then everything works fine.

I have tried switching NIC’s, updated NIC drivers, and re-service packing,
nothing has changed this behavior. Any suggestions would be appreciated.

Thanks in advance,

Rob Scott

 

[Dave Patrick]

Check Event Viewer and Device Manager for errors and or non-starting
devices.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I have a 2000 Server SP4 running AD and DNS that is hanging at logon. The
| server boots normally and does not hang at building network connections.
| However when you logon it loads a blank desktop and hangs for
approximately 2
| minutes, then it will load the rest of the desktop. After the desktop is
| loaded the "Local Area Network Connection" Icon does not appear in the
| taskbar (Even though that option is selected in the NIC properties) and
any
| application that requires network access hangs (IE: Internet Explorer, My
| Network Places, etc.) I cannot even access the properties of the NIC
without
| it hanging. However, if I physically unplug the patch cord from the NIC
and
| then plug it back in, the "Local Area Network Connection Icon" will appear
in
| the task bar and then everything works fine.
|
| I have tried switching NIC's, updated NIC drivers, and re-service packing,
| nothing has changed this behavior. Any suggestions would be appreciated.
|
| Thanks in advance,
|
| Rob Scott
|

 

[Guest]

Thanks for the advice unfortunatly there seems to be no clues in either of
these sources. Device Manager looks fine no red x's or yellow ?'s and there
are no entries in the event log for failed services or non-starting devices.
In fact even before I unplug the NIC all normal services are showing in a
started state. It is very strange indeed!!

 

[Glenn L]

Do these apps hang forever?
"and any application that requires network access hangs (IE: Internet
Explorer, My Network Places, etc.)"
If you initiate a ping to another computer, does it resolve?
Is the behavior the same in safemode with networking? AD restore mode?

This is a weird one.
This sounds like the media sense is detecting the link as down, therefore
the protocols don't bind to the NIC.
Though I can't explain the missing icon and the lack of being able to access
the properties.

You might try disabling the media sense.
http://support.microsoft.com/default.aspx?scid=kb;en-us;239924

If this fixes it, then I suspect there is a problem with the spanning tree
setup on your switch port.

 

[Guest]

Glenn,

Good questions...I have not tried pinging to see if it resolves or even
replies. I will test and post my results. As far as the apps hanging, yes
they hang forever, until the patch cord is removed and re-plugged in. Once
it is re-plugged in, the "Local Area Network" Icon appears in the task bar
and all apps that were hung, take off.

The thing that confuses me is...Why does the server not hang during boot at
"Building Network Connections"? I have seen this issue many times usually
when DNS is configured incorrectly, but if the server has networking issues
post logon you would think it would have issues during boot??? Very Strange
Indeed.

I will try pinging and disabling the media sense and see what happens.

Thanks again,

Rob

 

[Guest]

Ok this gets even stranger....I rebooted the server it came up in its failed
state as described in this post. I went to another machine and pinged it by
IP and then by name, it replyed both by IP and by name. I then went back to
the server and the "Local Area Network" Icon was in the task bar and all
network apps were working, so unplugging and re-plugging in the NIC and
pinging it seem to correct the issue????