Slow Logins

We have just set up a new W2003 Server using high-end Dell hardware, a
domain with a single PDC. The workstations are Dells as well, but Dimension
4700s, running XP Pro.

The process of logging into the server is amazingly slow, requiring
sometimes 60-120 secs. There are no special profiles or drive mappings,
essentially the most basic of configurations.

Can anyone suggest what might be causing this? BTW, workstations are Fast
Ethernet and the server/switch link is a Gigabit Ethernet connection.

--
Sincerely,

David Ray
ProSystems, Inc.

=============
All outgoing mail has been virus scanned by Norton Anti-Virus.

sounds like DNS issue. quoted from http://ChicagoTech.net
Why is XP running slower while logon 1

When I login into a Windows 2000 active directory from a new xp pro machine
the login in is extremely slow. After logged on, everything works fine. But
other windows versions don't have this problem.
A: This is almost like name resolution issue. Comparing with previous
versions, XP is heavily dependent on DNS to find DC. If the DNS is
configured incorrectly, XP will take longer time waiting for it to timeout
before it tries using NetBIOS. Make sure
1) The DNS setup correct and have the server information.
2) XP clients can find the DNS server.
3) XP machine's DNS server is pointed to your internal DNS server rather
than your ISP's DNS server.
4) Make sure no errors on logon scripts or GPO's that could be causing
the delay.
5) Check any errors on event viewer.
6) Disable NetBIOS on the interfaces that client will not use.

--
For more and other information, go to http://howtonetworking.com and
http://ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on
http://www.HowToNetworking.com
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
"David Ray" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> We have just set up a new W2003 Server using high-end Dell hardware, a
> domain with a single PDC. The workstations are Dells as well, but
> Dimension
> 4700s, running XP Pro.
>
> The process of logging into the server is amazingly slow, requiring
> sometimes 60-120 secs. There are no special profiles or drive mappings,
> essentially the most basic of configurations.
>
> Can anyone suggest what might be causing this? BTW, workstations are Fast
> Ethernet and the server/switch link is a Gigabit Ethernet connection.
>
> --
> Sincerely,
>
> David Ray
> ProSystems, Inc.
>
> =============
> All outgoing mail has been virus scanned by Norton Anti-Virus.
>
>

Most likely the DNS for the clients is not correct. The Primary DNS IP on
the clients (and the DC) should be your DC. If the primary DNS is anything
but a DNS server for your domain, login will be slow and other issues will
appear.

http://thelazyadmin.com/2004/11/dns-tips-1.htm


--

Rod
Http://thelazyadmin.com


"David Ray" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> We have just set up a new W2003 Server using high-end Dell hardware, a
> domain with a single PDC. The workstations are Dells as well, but
> Dimension
> 4700s, running XP Pro.
>
> The process of logging into the server is amazingly slow, requiring
> sometimes 60-120 secs. There are no special profiles or drive mappings,
> essentially the most basic of configurations.
>
> Can anyone suggest what might be causing this? BTW, workstations are Fast
> Ethernet and the server/switch link is a Gigabit Ethernet connection.
>
> --
> Sincerely,
>
> David Ray
> ProSystems, Inc.
>
> =============
> All outgoing mail has been virus scanned by Norton Anti-Virus.
>
>

Hi David,

One of first things to check is DNS configuration on the clients. You
clients DNS settings (Preferred DNS IP address under TCP/IP Settings) should
point to your active directory DNS (probably your Active Directory server).
Clients should not use any other DNS servers (e.g. your ISP's DNS).

Another thing to check is DNS settings of your domain controller. Just like
clients domain controller must also point to active directory DNS -- in this
case probably back to itself. If you domain controller is also DNS server
then you can enter 127.0.0.1 for preferred DNS server on your domain
controller.

Note: it is not very smart to only have one domain controller in production
environment. Restoring domain from tape can be pretty hard task - specially
with users calling every few minutes and asking when the domain will work
again.

--
Mike
Microsoft MVP - Windows Security

"David Ray" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> We have just set up a new W2003 Server using high-end Dell hardware, a
> domain with a single PDC. The workstations are Dells as well, but
> Dimension
> 4700s, running XP Pro.
>
> The process of logging into the server is amazingly slow, requiring
> sometimes 60-120 secs. There are no special profiles or drive mappings,
> essentially the most basic of configurations.
>
> Can anyone suggest what might be causing this? BTW, workstations are Fast
> Ethernet and the server/switch link is a Gigabit Ethernet connection.
>
> --
> Sincerely,
>
> David Ray
> ProSystems, Inc.
>
> =============
> All outgoing mail has been virus scanned by Norton Anti-Virus.
>
>

Thanks for these replies. Sounds like there is a consensus.

In fact, we have not configured DNS at all -- assuming we needed it only for
Internet access, we would merely use the ISP's DNS as we always have with
NT4.

Obviously, out of my league with this new server version.



"David Ray" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> We have just set up a new W2003 Server using high-end Dell hardware, a
> domain with a single PDC. The workstations are Dells as well, but
Dimension
> 4700s, running XP Pro.
>
> The process of logging into the server is amazingly slow, requiring
> sometimes 60-120 secs. There are no special profiles or drive mappings,
> essentially the most basic of configurations.
>
> Can anyone suggest what might be causing this? BTW, workstations are Fast
> Ethernet and the server/switch link is a Gigabit Ethernet connection.
>
> --
> Sincerely,
>
> David Ray
> ProSystems, Inc.
>
> =============
> All outgoing mail has been virus scanned by Norton Anti-Virus.
>
>

That won't work with Active Directory. NT used Netbios names to find a
logon server. Active Directory clients use DNS for this. So the clients need
to point to your local DNS to find a logon server (and a lot of other AD
services as well).

To get the clients access to "foreign" DNS names, set your DNS server to
forward requests to a public DNS service (such as your ISP).

"David Ray" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks for these replies. Sounds like there is a consensus.
>
> In fact, we have not configured DNS at all -- assuming we needed it only
> for
> Internet access, we would merely use the ISP's DNS as we always have with
> NT4.
>
> Obviously, out of my league with this new server version.
>
>
>
> "David Ray" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> We have just set up a new W2003 Server using high-end Dell hardware, a
>> domain with a single PDC. The workstations are Dells as well, but
> Dimension
>> 4700s, running XP Pro.
>>
>> The process of logging into the server is amazingly slow, requiring
>> sometimes 60-120 secs. There are no special profiles or drive mappings,
>> essentially the most basic of configurations.
>>
>> Can anyone suggest what might be causing this? BTW, workstations are
>> Fast
>> Ethernet and the server/switch link is a Gigabit Ethernet connection.
>>
>> --
>> Sincerely,
>>
>> David Ray
>> ProSystems, Inc.
>>
>> =============
>> All outgoing mail has been virus scanned by Norton Anti-Virus.
>>
>>
>
>

Thanks for your help, everyone.

I guess I'm going to have to come out of the dark ages, after all...

David


"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> That won't work with Active Directory. NT used Netbios names to find a
> logon server. Active Directory clients use DNS for this. So the clients
need
> to point to your local DNS to find a logon server (and a lot of other AD
> services as well).
>
> To get the clients access to "foreign" DNS names, set your DNS server
to
> forward requests to a public DNS service (such as your ISP).
>
> "David Ray" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Thanks for these replies. Sounds like there is a consensus.
> >
> > In fact, we have not configured DNS at all -- assuming we needed it only
> > for
> > Internet access, we would merely use the ISP's DNS as we always have
with
> > NT4.
> >
> > Obviously, out of my league with this new server version.
> >
> >
> >
> > "David Ray" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >> We have just set up a new W2003 Server using high-end Dell hardware, a
> >> domain with a single PDC. The workstations are Dells as well, but
> > Dimension
> >> 4700s, running XP Pro.
> >>
> >> The process of logging into the server is amazingly slow, requiring
> >> sometimes 60-120 secs. There are no special profiles or drive
mappings,
> >> essentially the most basic of configurations.
> >>
> >> Can anyone suggest what might be causing this? BTW, workstations are
> >> Fast
> >> Ethernet and the server/switch link is a Gigabit Ethernet connection.
> >>
> >> --
> >> Sincerely,
> >>
> >> David Ray
> >> ProSystems, Inc.
> >>
> >> =============
> >> All outgoing mail has been virus scanned by Norton Anti-Virus.
> >>
> >>
> >
> >
>
>