Logon problem

[Axel Boggio]

When a specific user is loggin onto his laptop, connected
to the WAN but not to the LAN, it takes ages to have the
desktop starting. If I launch it manually (CTRL + ALT +
DELETE, Task Manager, File, New Task, Explorer) it is
working. If I don't fo this, I have to wait for more than
5 minutes.

If I logon with a different username, I have no problem.

If I logon without the network cable attached to the
network, I have no problem.

If I logon when connected to the LAN where I have a
Domain controller, I have no problem.

Please help urgently, this is the PC of my European
President !!!

Thanks in advance

 

[Malke]

When a specific user is loggin onto his laptop, connected
to the WAN but not to the LAN, it takes ages to have the
desktop starting. If I launch it manually (CTRL + ALT +
DELETE, Task Manager, File, New Task, Explorer) it is
working. If I don't fo this, I have to wait for more than
5 minutes.

If I logon with a different username, I have no problem.

If I logon without the network cable attached to the
network, I have no problem.

If I logon when connected to the LAN where I have a
Domain controller, I have no problem.

Please help urgently, this is the PC of my European
President !!!

It sounds like the user is having trouble being authenticated. Check the
dns settings on the laptop. Also, because it is a laptop, does your
user log onto different networks regularly (home and work for example).
S/he may need to run third-party network switching software. Post your
dns settings, and you may also consider posting this question (with a
bit more detail re dns, etc.) to the Microsoft server general
newsgroup. The regulars in that newsgroup are awesome.

Malke

 

[Alex Nichol]

When a specific user is loggin onto his laptop, connected
to the WAN but not to the LAN, it takes ages to have the
desktop starting. If I launch it manually (CTRL + ALT +
DELETE, Task Manager, File, New Task, Explorer) it is
working. If I don't fo this, I have to wait for more than
5 minutes.

If I logon with a different username, I have no problem.

If I logon without the network cable attached to the
network, I have no problem.

If I logon when connected to the LAN where I have a
Domain controller, I have no problem.

This sounds like the problem of having the LAN set up to be accessed via
DHCP, and if there is no LAN active, it will wait for ever for the
search for the DHCP service to time out. Hopefully the connection gets
the same settings each time of logon - if so set them manually in the
Network connection to the LAN, so that DHCP is disabled for it