C
Chris-n-Jordan
Greetings All!
I wonder if you could help me with an irritating problem. I have a lab
of 31 XP Pro computers logging in to a domain (Win2003 Server- AD
Domain Controller and main DNS server) using a profile I have named
"Student." The student profile is pretty locked down but has access to
a network share on the server where it pulls some app files and gets
its desktop background.
Everything was great...the students would log in using the profile and
connect and there were no problems. Then I decided to save myself the
headache of loggin in 31 computers and did the registry modifications
to have the computer auto-login. These mods were four keys in the
SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon section of the
registry. I modified:
Default User- Student; Default Password- Student; Default Domain - AMP;
AutoLogin = 1
When I did this all heck broke loose. All of the sudden, the computers
that logged in beautifully when I did it manually, DID NOT MAP THE
NETWORK DRIVE (Z:- It was set in the User Profile). I checked the
event log and found Event 1054- Windows cannot obtain the domain
controller name for your computer network. (The Specified domain either
does not exist or could not be contacted.) Group Policy processing
aborted.
I remove the autologin and the problem goes away. It is the same for
all of my computers. There are no anomolies in the DNS Events...it is
up and working fine as far as I can tell. The DHCP server has the
domain controller listed in the Options. When I log on manually, I get
DNS, Default Gateway...a full lease.
I can't figure it out. The only thing I could guess is that the speed
of the login causes something to be missed from the DHCP Server. Any
thoughts?
I wonder if you could help me with an irritating problem. I have a lab
of 31 XP Pro computers logging in to a domain (Win2003 Server- AD
Domain Controller and main DNS server) using a profile I have named
"Student." The student profile is pretty locked down but has access to
a network share on the server where it pulls some app files and gets
its desktop background.
Everything was great...the students would log in using the profile and
connect and there were no problems. Then I decided to save myself the
headache of loggin in 31 computers and did the registry modifications
to have the computer auto-login. These mods were four keys in the
SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon section of the
registry. I modified:
Default User- Student; Default Password- Student; Default Domain - AMP;
AutoLogin = 1
When I did this all heck broke loose. All of the sudden, the computers
that logged in beautifully when I did it manually, DID NOT MAP THE
NETWORK DRIVE (Z:- It was set in the User Profile). I checked the
event log and found Event 1054- Windows cannot obtain the domain
controller name for your computer network. (The Specified domain either
does not exist or could not be contacted.) Group Policy processing
aborted.
I remove the autologin and the problem goes away. It is the same for
all of my computers. There are no anomolies in the DNS Events...it is
up and working fine as far as I can tell. The DHCP server has the
domain controller listed in the Options. When I log on manually, I get
DNS, Default Gateway...a full lease.
I can't figure it out. The only thing I could guess is that the speed
of the login causes something to be missed from the DHCP Server. Any
thoughts?