Yet another multisite VPN DNS question!

Tech-Archive recommends: Speed Up your PC by fixing your registry

I've browsed through some of the other threads here searching off of VPN and
I've found some useful info but nothing that I can see directly addresses my
problem.

I have a four office locations connected via VPN. At first, I had my two
servers (one is PDC, other is DC w/ Exchange 2003 installed) at a single
location but now I've moved the DC/Exchange server to another office. So now
I have two branch offices that have no server machines onsite, and they each
have VPN tunnels directing to the offices holding Server1 and Server2.

Originally, per the way Microsoft helped me configure them, my DC/Exchange
server was not a Global Catalog machine, but now that I've moved it I believe
this will be more important, so I enabled that.

Now to my problem!

Since moving Server2, I've had workstations at the location I moved the
server into affected by login problems. Lonnnnngggg delays to login,
sometimes 20min or more. One thing I've noticed is that DNS entries are not
being updated for a lot of workstations. I'm thinking this is causing a lot
of my issues with login times. I know I need to fix the DNS issue regardless,
because AD is thinking a workstation has a certain IP address whereas it now
has a new one.

As far as my DHCP information is concerned, workstations at all four
locations are receiving IP addresses via the routers are those offices. The
main offices hosting the two servers both have Cisco routers in place
handling DHCP, whereas the smaller branch offices that have no on-site
servers are utlizing DHCP off of LinkSys routers.

A lot of the threads here refer back to using the DHCP service on the
Windows Servers, but that wouldn't work for my offices that lack server
equipment.

Can anyone give me some pointers in the right direction for how I should
ensure things are setup properly? I think ensuring both servers are Global
Catalogs, and having workstations at those offices point to their respective
servers will help with those machines, but what about the machines at
locations without servers? Is there a proper way to obtain IP information
from a router and ensure that it gets updated into DNS?
.

Relevant Pages

  • RE: Optimize SMB on server to accomodate slow WAN link
    ... The lack of bursting is really a function of the carrier, ... especially if you have servers in the ... Advertising of shares/printers by workstations and servers ... the central office that they do not need to be connecting to. ...
    (microsoft.public.win2000.networking)
  • Slow Logins and Slow Boot-up
    ... I have a 2003 AD and my workstations are very slow to apply computer settions ... I have 2 AD servers on my local site and 2 other sites each with a AD server. ... an backup server (connected via VPN) ... I wonder if some of my clients are connecting to the othere sites for their ...
    (microsoft.public.windows.server.active_directory)
  • Re: Very Slow(60mins) XP logon
    ... The DNS on the servers is set to internal only, workstations get their dns through dhcp which also sets them up for internal dns. ... The slow logon happens with any AD account. ...
    (microsoft.public.win2000.networking)
  • Re: HP, Intel becoming laughing stock of computer industry
    ... > workstations and dozens of HP-UX servers. ... As well as a Linux port there is also a Windows ...
    (comp.os.vms)
  • Re: HP, Intel becoming laughing stock of computer industry
    ... > workstations and dozens of HP-UX servers. ... As well as a Linux port there is also a Windows ...
    (comp.os.vms)