C
Cheryl S.
Scenario:
One domain, 4 subnets/sites at various locations connected
via high-speed VPN tunnels. DC's located at each site
with DHCP, DNS, AD, WINS running. Windows 2000 servers
with XP clients.
When a user goes to another site/subnet, they log on and
get a new address from the local DHCP. But, within DNS,
they are showing the previous address. Therefore, there
are networking issues, printing and browsing difficulties.
Normally, if the person stays at the new site for a 2nd
day, everything corrects itself which leads me to believe
it's related to all DC's being updated over a period of
time.
Question: Can I do something on the server or client side
for these "traveling" employees to make sure they can
continue to use network resources without losing
connectivity during the period before AD & DNS are updated?
This happens frequently to me as the Systems Admin because
I go to several different locations. Sorry to be so
lengthy. Thanks for any help.
Cheryl
..
One domain, 4 subnets/sites at various locations connected
via high-speed VPN tunnels. DC's located at each site
with DHCP, DNS, AD, WINS running. Windows 2000 servers
with XP clients.
When a user goes to another site/subnet, they log on and
get a new address from the local DHCP. But, within DNS,
they are showing the previous address. Therefore, there
are networking issues, printing and browsing difficulties.
Normally, if the person stays at the new site for a 2nd
day, everything corrects itself which leads me to believe
it's related to all DC's being updated over a period of
time.
Question: Can I do something on the server or client side
for these "traveling" employees to make sure they can
continue to use network resources without losing
connectivity during the period before AD & DNS are updated?
This happens frequently to me as the Systems Admin because
I go to several different locations. Sorry to be so
lengthy. Thanks for any help.
Cheryl
..