|
It was probably related to the DHCP client starting up. AFAIK, windows starts a DHCP client process when the logon screen appears. If you still don't have an IP address after you have logged in, it waits for the DHCP client to time out before assuming you're not a member of a domain or something, and proceeds with a standard login. The second login goes quickly because the DHCP client isn't waiting anymore; the system already knows the status of the ethernet adapter.
This may not be your problem, but this is what I traced my problem to when I had a similar issue.
|