Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Slow login issue

Active Directory, Domain, DNS, WINS, DHCP, SBS, New Releases.

Slow login issue

Postby chicagotech » Thu Jul 26, 2007 9:28 am

I would check the DNS settings first. Any errors if using nslookup command?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"scripttron75" <scripttron75> wrote in message news:EA9A229B-43C4-4988-8A7C-BB0F594F0521@microsoft.com...
I am on a windows enviroment, we have 2 domain controllers the oldest one is
a windows 2000 server with active directory and the second is a windows 2003
domain controller that was promoted to a domain controller a year ago, lately
we have been experiencing slow log in times for some users including our
admin account. i can not pinpoint the issue, we use dhcp with reserved
addresses, plenty are available, we use roaming profiles with folder
rediaretion of the my documents folder. please help the slow login takes
forever at least 45min
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 6352
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Postby chicagotech » Thu Jul 26, 2007 9:29 am

i checked the dns server that is on our win2003 box and under the event
viewer dns i get a warning The DNS server has encountered numerous run-time
events. To determine the initial cause of these run-time events, examine the
DNS server event log entries that preceded these run-time events. The data is
the number of events that have been suppressed in the last 60 minute interval.

I checked our other dns server that is a windows 2000 server box and under
that ev for dns i get this as a warning:The DNS server encountered a packet
addressed to itself -- IP address 10.1.1.15.

The DNS server should never be sending a packet to itself. This situation
usually indicates a configuration error.

Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS
server unless subzone is also on this server.

Example of self-delegation:
-> This DNS server dns1.foo.com is the primary for the zone foo.com.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 6352
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA


Return to Windows

Your Ad Here

Who is online

Users browsing this forum: No registered users and 5 guests