Sridhar Cherukuri
asked on
Windows 2003 takes several minutes to login
Hi All
Recently i promoted my windows 2003 pc to Domain Controller. I found a small problem when i on my server it takes several minutes at "preparing network connections" (approx 5 mins.) and then its displaying the login screen. What could be the problem here? i did not configured and DSN i just select to confgure automatically while promoting it to domain. Before i promoted it to DC the login was very fast (less then a min) can some help on this issue.
Regards
Cherukuri
Recently i promoted my windows 2003 pc to Domain Controller. I found a small problem when i on my server it takes several minutes at "preparing network connections" (approx 5 mins.) and then its displaying the login screen. What could be the problem here? i did not configured and DSN i just select to confgure automatically while promoting it to domain. Before i promoted it to DC the login was very fast (less then a min) can some help on this issue.
Regards
Cherukuri
Run Netdiag /v and output the results to a text file. The command is like so:
netdiag /v > c:\netdiag.txt
Run through the file and see if there are any DNS errors. Normally, long boot times are attributed to a DNS entry that is missing or incorrect.
netdiag /v > c:\netdiag.txt
Run through the file and see if there are any DNS errors. Normally, long boot times are attributed to a DNS entry that is missing or incorrect.
ASKER
Dear Friend as you recommended i ran through netdiag and posting the DNS Test results here:
DNS test . . . . . . . . . . . . . : Fail
[WARNING] Cannot find a primary authoritative DNS server for the name
'server.DOMAIN.'. [RCODE_SERVER_FAILURE]
The name 'server.DOMAIN.' may not be registered in DNS.
[WARNING] Cannot find a primary authoritative DNS server for the name
'server.DOMAIN.'. [RCODE_SERVER_FAILURE]
The name 'server.DOMAIN.' may not be registered in DNS.
[WARNING] Cannot find a primary authoritative DNS server for the name
'server.DOMAIN.'. [RCODE_SERVER_FAILURE]
The name 'server.DOMAIN.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '203.121.16.85'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '203.121.16.120'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '202.188.0.133'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '202.188.1.5'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
Please can you tell me what went wrong, with the above description
Thanks and Regards
Sridhar
DNS test . . . . . . . . . . . . . : Fail
[WARNING] Cannot find a primary authoritative DNS server for the name
'server.DOMAIN.'. [RCODE_SERVER_FAILURE]
The name 'server.DOMAIN.' may not be registered in DNS.
[WARNING] Cannot find a primary authoritative DNS server for the name
'server.DOMAIN.'. [RCODE_SERVER_FAILURE]
The name 'server.DOMAIN.' may not be registered in DNS.
[WARNING] Cannot find a primary authoritative DNS server for the name
'server.DOMAIN.'. [RCODE_SERVER_FAILURE]
The name 'server.DOMAIN.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '203.121.16.85'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '203.121.16.120'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '202.188.0.133'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '202.188.1.5'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
Please can you tell me what went wrong, with the above description
Thanks and Regards
Sridhar
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It is not unusual to see a longer boot time when a machine is a DC vs. a member server.
(Try adding Exchange to the server if you want to see a really long boot time.....)
Dave Dietz