help with slow login

[Guest scripttron75]

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

[Guest Robert L [MVP - Networking]]

Re: help with slow login

 

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@discussions.microsoft.com> 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

[Guest Ehren]

RE: help with slow login

 

DNS server addresses set correctly on all workstations? DNS functioning on

both DCs? DNS successuflly replicating between DCs?

 

Sounds like a DNS issue to me.

 

"scripttron75" wrote:

> 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

[Guest scripttron75]

RE: help with slow login

 

thanks for the tips, when i login to the win2003 server which is a domain

controller with our admin account or any other account for that matter it is

so slow, how can i determine on this DC if the dns is set proerply??

 

"Ehren" wrote:

> DNS server addresses set correctly on all workstations? DNS functioning on

> both DCs? DNS successuflly replicating between DCs?

>

> Sounds like a DNS issue to me.

>

> "scripttron75" wrote:

>

> > 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

[Guest Ehren]

RE: help with slow login

 

Check the event logs on the DNS servers and see if they are throwing any

errors. Make sure the DNS server addresses are configured properly in your

dhcp server (I assume you hand the DNS server addresses out to clients via

dhcp). do Ipconfig /all on the clients to make sure the Ip and dns addresses

are proper. Attempt to ping FQDN's (Fully qualified domain names, aka

computer3.subdomain.doman.intranet) and see if you get a response.

 

There are several tools in the 2003 resource kit that are for

troubleshooting dns, you can find it at the MS downloads section.

 

"scripttron75" wrote:

> thanks for the tips, when i login to the win2003 server which is a domain

> controller with our admin account or any other account for that matter it is

> so slow, how can i determine on this DC if the dns is set proerply??

>

> "Ehren" wrote:

>

> > DNS server addresses set correctly on all workstations? DNS functioning on

> > both DCs? DNS successuflly replicating between DCs?

> >

> > Sounds like a DNS issue to me.

> >

> > "scripttron75" wrote:

> >

> > > 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

[Guest scripttron75]

RE: help with slow login

 

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.

 

 

"Ehren" wrote:

> Check the event logs on the DNS servers and see if they are throwing any

> errors. Make sure the DNS server addresses are configured properly in your

> dhcp server (I assume you hand the DNS server addresses out to clients via

> dhcp). do Ipconfig /all on the clients to make sure the Ip and dns addresses

> are proper. Attempt to ping FQDN's (Fully qualified domain names, aka

> computer3.subdomain.doman.intranet) and see if you get a response.

>

> There are several tools in the 2003 resource kit that are for

> troubleshooting dns, you can find it at the MS downloads section.

>

> "scripttron75" wrote:

>

> > thanks for the tips, when i login to the win2003 server which is a domain

> > controller with our admin account or any other account for that matter it is

> > so slow, how can i determine on this DC if the dns is set proerply??

> >

> > "Ehren" wrote:

> >

> > > DNS server addresses set correctly on all workstations? DNS functioning on

> > > both DCs? DNS successuflly replicating between DCs?

> > >

> > > Sounds like a DNS issue to me.

> > >

> > > "scripttron75" wrote:

> > >

> > > > 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

[Guest scripttron75]

RE: help with slow login

 

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.

 

 

"Ehren" wrote:

> Check the event logs on the DNS servers and see if they are throwing any

> errors. Make sure the DNS server addresses are configured properly in your

> dhcp server (I assume you hand the DNS server addresses out to clients via

> dhcp). do Ipconfig /all on the clients to make sure the Ip and dns addresses

> are proper. Attempt to ping FQDN's (Fully qualified domain names, aka

> computer3.subdomain.doman.intranet) and see if you get a response.

>

> There are several tools in the 2003 resource kit that are for

> troubleshooting dns, you can find it at the MS downloads section.

>

> "scripttron75" wrote:

>

> > thanks for the tips, when i login to the win2003 server which is a domain

> > controller with our admin account or any other account for that matter it is

> > so slow, how can i determine on this DC if the dns is set proerply??

> >

> > "Ehren" wrote:

> >

> > > DNS server addresses set correctly on all workstations? DNS functioning on

> > > both DCs? DNS successuflly replicating between DCs?

> > >

> > > Sounds like a DNS issue to me.

> > >

> > > "scripttron75" wrote:

> > >

> > > > 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

[Guest Ehren]

RE: help with slow login

 

Did you check those things?

 

"scripttron75" wrote:

> 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.

>

>

> "Ehren" wrote:

>

> > Check the event logs on the DNS servers and see if they are throwing any

> > errors. Make sure the DNS server addresses are configured properly in your

> > dhcp server (I assume you hand the DNS server addresses out to clients via

> > dhcp). do Ipconfig /all on the clients to make sure the Ip and dns addresses

> > are proper. Attempt to ping FQDN's (Fully qualified domain names, aka

> > computer3.subdomain.doman.intranet) and see if you get a response.

> >

> > There are several tools in the 2003 resource kit that are for

> > troubleshooting dns, you can find it at the MS downloads section.

> >

> > "scripttron75" wrote:

> >

> > > thanks for the tips, when i login to the win2003 server which is a domain

> > > controller with our admin account or any other account for that matter it is

> > > so slow, how can i determine on this DC if the dns is set proerply??

> > >

> > > "Ehren" wrote:

> > >

> > > > DNS server addresses set correctly on all workstations? DNS functioning on

> > > > both DCs? DNS successuflly replicating between DCs?

> > > >

> > > > Sounds like a DNS issue to me.

> > > >

> > > > "scripttron75" wrote:

> > > >

> > > > > 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

[Guest Ehren]

RE: help with slow login

 

What log entries preceeded the run time event?

 

"scripttron75" wrote:

> 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.

>

>

> "Ehren" wrote:

>

> > Check the event logs on the DNS servers and see if they are throwing any

> > errors. Make sure the DNS server addresses are configured properly in your

> > dhcp server (I assume you hand the DNS server addresses out to clients via

> > dhcp). do Ipconfig /all on the clients to make sure the Ip and dns addresses

> > are proper. Attempt to ping FQDN's (Fully qualified domain names, aka

> > computer3.subdomain.doman.intranet) and see if you get a response.

> >

> > There are several tools in the 2003 resource kit that are for

> > troubleshooting dns, you can find it at the MS downloads section.

> >

> > "scripttron75" wrote:

> >

> > > thanks for the tips, when i login to the win2003 server which is a domain

> > > controller with our admin account or any other account for that matter it is

> > > so slow, how can i determine on this DC if the dns is set proerply??

> > >

> > > "Ehren" wrote:

> > >

> > > > DNS server addresses set correctly on all workstations? DNS functioning on

> > > > both DCs? DNS successuflly replicating between DCs?

> > > >

> > > > Sounds like a DNS issue to me.

> > > >

> > > > "scripttron75" wrote:

> > > >

> > > > > 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

[Guest scripttron75]

RE: help with slow login

 

on the windows 2000 box, i checked the forwarders tab and the ip address

10.1.1.15 is not in there so i dont know why we are getting this warning. ???

 

"Ehren" wrote:

> Did you check those things?

>

> "scripttron75" wrote:

>

> > 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.

> >

> >

> > "Ehren" wrote:

> >

> > > Check the event logs on the DNS servers and see if they are throwing any

> > > errors. Make sure the DNS server addresses are configured properly in your

> > > dhcp server (I assume you hand the DNS server addresses out to clients via

> > > dhcp). do Ipconfig /all on the clients to make sure the Ip and dns addresses

> > > are proper. Attempt to ping FQDN's (Fully qualified domain names, aka

> > > computer3.subdomain.doman.intranet) and see if you get a response.

> > >

> > > There are several tools in the 2003 resource kit that are for

> > > troubleshooting dns, you can find it at the MS downloads section.

> > >

> > > "scripttron75" wrote:

> > >

> > > > thanks for the tips, when i login to the win2003 server which is a domain

> > > > controller with our admin account or any other account for that matter it is

> > > > so slow, how can i determine on this DC if the dns is set proerply??

> > > >

> > > > "Ehren" wrote:

> > > >

> > > > > DNS server addresses set correctly on all workstations? DNS functioning on

> > > > > both DCs? DNS successuflly replicating between DCs?

> > > > >

> > > > > Sounds like a DNS issue to me.

> > > > >

> > > > > "scripttron75" wrote:

> > > > >

> > > > > > 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

[Guest scripttron75]

RE: help with slow login

 

here is another event that proceeeds it, The DNS server encountered an

invalid domain name in a packet from 206.13.29.12. The packet is rejected.

 

"scripttron75" wrote:

> on the windows 2000 box, i checked the forwarders tab and the ip address

> 10.1.1.15 is not in there so i dont know why we are getting this warning. ???

>

> "Ehren" wrote:

>

> > Did you check those things?

> >

> > "scripttron75" wrote:

> >

> > > 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.

> > >

> > >

> > > "Ehren" wrote:

> > >

> > > > Check the event logs on the DNS servers and see if they are throwing any

> > > > errors. Make sure the DNS server addresses are configured properly in your

> > > > dhcp server (I assume you hand the DNS server addresses out to clients via

> > > > dhcp). do Ipconfig /all on the clients to make sure the Ip and dns addresses

> > > > are proper. Attempt to ping FQDN's (Fully qualified domain names, aka

> > > > computer3.subdomain.doman.intranet) and see if you get a response.

> > > >

> > > > There are several tools in the 2003 resource kit that are for

> > > > troubleshooting dns, you can find it at the MS downloads section.

> > > >

> > > > "scripttron75" wrote:

> > > >

> > > > > thanks for the tips, when i login to the win2003 server which is a domain

> > > > > controller with our admin account or any other account for that matter it is

> > > > > so slow, how can i determine on this DC if the dns is set proerply??

> > > > >

> > > > > "Ehren" wrote:

> > > > >

> > > > > > DNS server addresses set correctly on all workstations? DNS functioning on

> > > > > > both DCs? DNS successuflly replicating between DCs?

> > > > > >

> > > > > > Sounds like a DNS issue to me.

> > > > > >

> > > > > > "scripttron75" wrote:

> > > > > >

> > > > > > > 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

[Guest Ehren]

RE: help with slow login

 

Isnt DNS FUN! Its really tough for me to say what the problem is without

sitting in front of your box, it looks like it might be a bit complex though.

I would see if you can find any local DNS experts if ther is not one in your

company. Too many things to look at and too many things to ask to come up

with a productive solution through a medium like this.

 

Unless of course someone can come up with a lucky guess :)

 

"scripttron75" wrote:

> here is another event that proceeeds it, The DNS server encountered an

> invalid domain name in a packet from 206.13.29.12. The packet is rejected.

>

> "scripttron75" wrote:

>

> > on the windows 2000 box, i checked the forwarders tab and the ip address

> > 10.1.1.15 is not in there so i dont know why we are getting this warning. ???

> >

> > "Ehren" wrote:

> >

> > > Did you check those things?

> > >

> > > "scripttron75" wrote:

> > >

> > > > 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.

> > > >

> > > >

> > > > "Ehren" wrote:

> > > >

> > > > > Check the event logs on the DNS servers and see if they are throwing any

> > > > > errors. Make sure the DNS server addresses are configured properly in your

> > > > > dhcp server (I assume you hand the DNS server addresses out to clients via

> > > > > dhcp). do Ipconfig /all on the clients to make sure the Ip and dns addresses

> > > > > are proper. Attempt to ping FQDN's (Fully qualified domain names, aka

> > > > > computer3.subdomain.doman.intranet) and see if you get a response.

> > > > >

> > > > > There are several tools in the 2003 resource kit that are for

> > > > > troubleshooting dns, you can find it at the MS downloads section.

> > > > >

> > > > > "scripttron75" wrote:

> > > > >

> > > > > > thanks for the tips, when i login to the win2003 server which is a domain

> > > > > > controller with our admin account or any other account for that matter it is

> > > > > > so slow, how can i determine on this DC if the dns is set proerply??

> > > > > >

> > > > > > "Ehren" wrote:

> > > > > >

> > > > > > > DNS server addresses set correctly on all workstations? DNS functioning on

> > > > > > > both DCs? DNS successuflly replicating between DCs?

> > > > > > >

> > > > > > > Sounds like a DNS issue to me.

> > > > > > >

> > > > > > > "scripttron75" wrote:

> > > > > > >

> > > > > > > > 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