Applying computer settings...

[tony]

We are on a win2k3 domain including laptop users. Everything is DHCP and
everything works fine on the lan. But when users take their laptops out of
the network, eg at home, obviously their dns settings are different and they
are stuck with
a very very slow logon applying network settings.... applying computer
settings..... applying your personal settings ......

etc etc etc

usually take at least 5 minutes to startup and logon.


What are people doing for laptop machines which joined the domain and need
to log on outside the network

 

[lforbes]

We are on a win2k3 domain including laptop users. Everything
is DHCP and
everything works fine on the lan. But when users take their
laptops out of
the network, eg at home, obviously their dns settings are
different and they
are stuck with
a very very slow logon applying network settings.... applying
computer
settings..... applying your personal settings ......

etc etc etc

usually take at least 5 minutes to startup and logon.


What are people doing for laptop machines which joined the
domain and need
to log on outside the network

Hi,

I setup a local login for the users for home use. I then allow them
access to their My Documents for their domain account.

Cheers,

Lara

 

[Bruce Sanderson]

Does the same problem happen when users logon while the computer is NOT
connected to any network at all?

Are the laptops in sleep or hibernation when they are taken home, then woken
up?

Does it make a difference if the laptops are powered on (or Windows
restarted) while already connected to the home network?

What version of Windows is on the laptop (2000, XP, what Service Pack)?

When a users logs on to a domain member computer and NO domain controller
can be contacted, the user will be logged on with locally cached (on the
laptop in this case) credentials (Windows NT and later). If your domain
controller's IP address is NOT exposed on the Internet and their DNS names
are similarly NOT exposed, then logging on from outside your "company"
network should be with locally cached credentials.

I've often taken laptops that are Domain Members home, connected them to my
home network ("router" and cable connection to an ISP) and logged on with
the domain user accounts with no problem and no appreciable delay (no slower
when connected to the "office" network). The Domain Controllers' DNS names
are "private" and can not be resolved from the Internet.

You might want to post this question in the
microsoft.public.windows2000.networking or
microsoft.public.windows.servers.networking newsgroups.