Log in to a domain on a slow connection

  • Thread starter Thread starter Artificer
  • Start date Start date
A

Artificer

Guest
Do I have to configure windows XP in any way in order to improve the
log in speed and policies synchronization on a slow connection?
 
RE: Log in to a domain on a slow connection

On a slow connection, I suggest you to configure a Site .
Put a GC in your local environment.

"Artificer" wrote:

> Do I have to configure windows XP in any way in order to improve the
> log in speed and policies synchronization on a slow connection?
>
 
Re: Log in to a domain on a slow connection

In news:474165b1-f36b-475b-a771-63a58b555451@y21g2000hsf.googlegroups.com,
Artificer <eliezerfigueroa@gmail.com> typed:
> Do I have to configure windows XP in any way in order to improve the
> log in speed and policies synchronization on a slow connection?

Slow domain logons are indicative of a few possible things:

1. The workstation (or even the domain controller itself) are using the
wrong DNS server IP address in their IP properties. You may have the
internal DNS server listed, or an ISP, or both. AD's requirements of DNS are
absolute. This means you CANNOT use your ISP's or your router's IP address
as a DNS server on ANY machine in a domain.

2. The domain is a single label name. Meaning the name is of the form of
"DOMAIN" instead of the required 'domain.com' or 'domain.local,' etc,
format.

3. The domain controller is multihomed, meaning it has more than one NIC or
has RRAS installed, which creates multiple interfaces.

4. Network settings, such as subnet mask, and other things, are incorrect.

There are more, but this is the basics. Usually the wrong DNS server is
specified, usually an ISP's. AD asks DNS, "hey, where's my domain controller
so I can logon?" If the ISP's or the router's IP address in the machine's IP
properties, those servers will respond, "I have no idea," and the
workstation fails authentication and other things go wrong as well.

You can't even mix ISP, router and internal DNS. It must only be the
internal DNS listed on all machines.

If you need additional assistance, to help us understand your configuration
to provide specifics, please post an unedited "ipconfig /all" from the
workstation having the problem and from the domain controller too.

Thank you.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations
 
Re: Log in to a domain on a slow connection

In news:da98ae7c-ff89-44d1-8570-0620f4612f9e@a70g2000hsh.googlegroups.com,
Artificer <eliezerfigueroa@gmail.com> typed:
> Please take a look to the following post for a description of the
> environment:
>
> http://groups.google.com/group/micr.../browse_thread/thread/671b0806b53064c2?hl=en#

If this is a new AD domain that was implemented recently, the links are just
too slow. Minimum for GPOs to properly apply, including the default Domain
GPO, requires a minimum of 500Kb. The line is now being saturated by
client-domain controller authentication traffic, especially intial logon
traffic when the client's GetDcList, GetGpoList and numerous other functions
are running in the background at logon.

Besides the min 500Kb link speed requirements, when there are 10 or more
clients at a remote location, a DC is recommended to be placed out there as
well as create AD Sites to control logon traffic from those clients to their
local DC/GC only. You can get around that fact by upping the speed. Now for
20 users, I would suggest a minimum of 768Kb to eliminate any question about
the 500Kb minimum, but higher if possible.

Parse through the following to help understand more about AD design,
including user, DC and GC placement. Keep in mind, if you are using remote
tools and other utilities and features that eat up bandwidth, it will slow
it down further. If you put Exchange in, that complicates matters and
increases speed requirements.

Download details Windows Server 2003 Active Directory Branch Office Guide
v1.1:
http://www.microsoft.com/downloads/...f6-a8a8-40bb-9fa7-3a95c9540112&displaylang=en

Ace
 
Back
Top