Long login time following username/password

  • Thread starter Thread starter SchoolTechGuy
  • Start date Start date
S

SchoolTechGuy

I've got a lab of XP SP2 machines (all identical computers) on a 2003 server.
Two of the machines take about two minutes from the time the user types in
username/password to the time the desktop appears. Between login and desktop
it's a blank screen with the mouse cursor. It doesn't matter if the machine
is plugged into the network or not, login takes two minutes. Other machines
login very quickly. The slow login machines are fine once they're done
logging in.

I checked DNS settings on the machines and on the server, all are fine. We
are not using roaming profiles (even local administrator login displays the
same delay). I tried setting the "wait for network" setting through group
policy. I don't think it is strictly a domain issue since the machines are
having trouble even with local accounts, but I'm not sure.

Any suggestions?
 
SchoolTechGuy said:
I've got a lab of XP SP2 machines (all identical computers) on a 2003
server. Two of the machines take about two minutes from the time the
user types in username/password to the time the desktop appears.
Between login and desktop it's a blank screen with the mouse cursor.
It doesn't matter if the machine is plugged into the network or not,
login takes two minutes. Other machines login very quickly. The
slow login machines are fine once they're done logging in.

I checked DNS settings on the machines and on the server, all are
fine. We are not using roaming profiles (even local administrator
login displays the same delay). I tried setting the "wait for
network" setting through group policy. I don't think it is strictly
a domain issue since the machines are having trouble even with local
accounts, but I'm not sure.

Any suggestions?
Click to expand...

This is most likely a DNS misconfiguration. Do post the unedited ipconfig
/all for a workstation & also your DC.
 
Workstation:

Hostname lab14
Primary DNS suffix mydomain.local
node type mixed
ip routing enabled no
wins proxy enabled no
dns suffix search list mydomain.local and localdomain

connection specific dns suffix mydomain.local
description broadcom 440x 10/100 integrated controller
physical address (normal)
dhcp enabled yes
autoconfiguration enabled yes
ip address 10.0.122.153
subnet mask 255.255.0.0
default gateway 10.0.1.4
dhcp server 10.0.1.4
dns server 10.0.2.199
primary wins server 10.0.5.75
lease obtained thursday, january 29th 2009 9:53:59 AM
lease expires thursday February 5th 2009 9:53:59 AM

DC:

hostname server2003
primary dns suffix mydomain.local
node type unknown
ip routing enabled no
wins proxy enabled no
dns suffix search list mydomain.local

connection specific DNS suffix (blank)
description broadcom netxtreme gigabit extreme
physical address (normal)
dhcp enabled no
ip address 10.0.2.199
subnet mask 255.255.0.0
default gateway 10.0.1.4
dns servers 127.0.0.1

The workstation's IP address does appear in the server's DNS reverse lookup
zone and is attributed to the correct workstation.
 
SchoolTechGuy said:
Workstation:
Click to expand...


You know all you needed to do was type icpconfig /all >c:\myfilename.txt,
right? No need to retype all this stuff by hand.
Hostname lab14
Primary DNS suffix mydomain.local
node type mixed
ip routing enabled no
wins proxy enabled no
dns suffix search list mydomain.local and localdomain

connection specific dns suffix mydomain.local
description broadcom 440x 10/100 integrated controller
physical address (normal)
dhcp enabled yes
autoconfiguration enabled yes
ip address 10.0.122.153
Click to expand...

What's this subnet and how is that network connected to 10.0.2.0?
subnet mask 255.255.0.0
Click to expand...

I'm curious as to why you're using a 16-bit subnet mask?
default gateway 10.0.1.4
dhcp server 10.0.1.4
Click to expand...

Set up the Windows server to do DHCP. Don't use your router .
dns server 10.0.2.199
primary wins server 10.0.5.75
Click to expand...

What and where is the server at 10.0.5.75? That's yet a third subnet.
lease obtained thursday, january 29th 2009 9:53:59 AM
lease expires thursday February 5th 2009 9:53:59 AM

DC:

hostname server2003
primary dns suffix mydomain.local
node type unknown
ip routing enabled no
wins proxy enabled no
dns suffix search list mydomain.local

connection specific DNS suffix (blank)
description broadcom netxtreme gigabit extreme
physical address (normal)
dhcp enabled no
ip address 10.0.2.199
subnet mask 255.255.0.0
Click to expand...

(same question re subnet mask)
default gateway 10.0.1.4
dns servers 127.0.0.1
Click to expand...

Change the DNS server from 127.0.0.1 to 10.0.2.199
The workstation's IP address does appear in the server's DNS reverse
lookup zone and is attributed to the correct workstation.
Click to expand...

More info about your network is needed (including VLANs, routers, etc).
 
Subnet mask was wide open when I first started here. (ten dot with a
255.0.0.0 subnet). We're adding a link to an outside location in a week or
two and I wanted to get away from the wide open subnet mask. This location
uses 10.0.X.X for subnet, the other location uses 10.12.X.X. They're not
connected yet.

10.0.1.4 is an IPCop web proxy box/firewall that also serves as our DHCP
server.

Network setup is the network flowing traffic into the IPCop box, which then
flows out to a Cisco router. No VPNs at current.

Userenv.log shows the following:

11 second delay following "UnloadUserProfile: returning 1"
1.5 minute delay following "GetUserDNSDomainName: Domain name is NT
Authority. No DNS name available."
LoadUserProfiles do not fail out.
 
SchoolTechGuy said:
Subnet mask was wide open when I first started here. (ten dot with a
255.0.0.0 subnet). We're adding a link to an outside location in a
week or two and I wanted to get away from the wide open subnet mask.
Click to expand...

Yes, but how many hosts do you actually need in any given network location?
You could still use a 24-bit mask.

10.0.1.0/24 for one office
10.0.2.0/24 for the 2nd
10.0.3.0/24 for the third.

.....etc.

This location uses 10.0.X.X for subnet, the other location uses
10.12.X.X. They're not connected yet.
Click to expand...

I'd get your IP network tidied up before proceeding with that.
10.0.1.4 is an IPCop web proxy box/firewall that also serves as our
DHCP server.
Click to expand...
\
What does that run? I would recommend you use a Windows server for DHCP -
likely your DC. It will handle dynamic DNS registration a lot better.
Network setup is the network flowing traffic into the IPCop box,
which then flows out to a Cisco router. No VPNs at current.

Userenv.log shows the following:

11 second delay following "UnloadUserProfile: returning 1"
1.5 minute delay following "GetUserDNSDomainName: Domain name is NT
Authority. No DNS name available."
LoadUserProfiles do not fail out.
Click to expand...

Your DNS
 
Back
Top