With no network connection--user logs in to blank screen

[rexdart]

Hello All,

We're running Win2k SP4 on a Dell laptop--freshly installed copy with
all security hotfixes and patches applied.
This is a strange combination of offline files and blank login
screens: If the computer is logged into by a user utilizing offiline
files, and no network connection is present, the user is presented
with a blank screen--Ctrl-Alt-Del has no effect, and the system has to
be powered down with a hard reboot (holding down the power button
until it turns off).
If the computer HAS a network connection, everything works fine.
I can log in as a user without any offline files to synchronize, and
the system boots perfectly, but if I restart and (without a network
connection) login as a user who has offline files, I get the blank
(blue) screen with nowhere to go.

Help?

 

[Lanwench [MVP - Exchange]]

Hello All,

We're running Win2k SP4 on a Dell laptop--freshly installed copy with
all security hotfixes and patches applied.
This is a strange combination of offline files and blank login
screens: If the computer is logged into by a user utilizing offiline
files, and no network connection is present, the user is presented
with a blank screen--Ctrl-Alt-Del has no effect, and the system has to
be powered down with a hard reboot (holding down the power button
until it turns off).
If the computer HAS a network connection, everything works fine.
I can log in as a user without any offline files to synchronize, and
the system boots perfectly, but if I restart and (without a network
connection) login as a user who has offline files, I get the blank
(blue) screen with nowhere to go.

Help?

Event logs?

 

[rexdart]

The event logs don't seem to show anything crazy happening. The
eventlog service starts, then it writes a Netlogon event id 5719 ["No
Windows NT or Windows 2000 Domain Controller is available for domain
RG-DOMAIN..."]. Obviously, there's no domain controller to contact
because the network cable has been unplugged (so why doesn't it notice
this and then continue on its way?).
Then the W32Time service writes eventid 54 ["The Windows Time Service
was not able to find a Domain Controller..."]
Then the network adapters begin to log stuff. Source FW1 with eventid
3 says the FW1 driver is installed. Then the Broadcom integrated
controller says its driver initialized successfully, and one entry
after that, the Broadcom controller notes that the network link is
down.
There really doesn't seem to be any major eventid's that give away the
cause. I've enabled USERENV logging as well, but I don't quite know
what I'm looking for in there.
Not much to go on, eh?