M
millh0use
I am currently running Outlook 2000 against Exchange 2003 at 200 remote
locations. The locations connect via my WAN with limited Internet
access. The clients have static IP addresses and are pointed to DNS
servers at our WAN provider. The DNS servers have entries pointing to
my Exchange 2003 server. Using this setup, all Clients work fine.
However, when I upgrade these clients to Outlook 2003 I cannot connect
to my Exchange server unless I change their primary DNS server to my
internal server address and reboot. I've attempted to delete and
recreate the entire profile but nothing seems to work except changing
the DNS entries. If I install Outlook 2003 when I am building the
client machines in my office, then ship them to the site, they work
fine through the WAN providers DNS servers. I am using the "Complete"
option when installing Outlook 2003.
Any ideas on what would cause this?
locations. The locations connect via my WAN with limited Internet
access. The clients have static IP addresses and are pointed to DNS
servers at our WAN provider. The DNS servers have entries pointing to
my Exchange 2003 server. Using this setup, all Clients work fine.
However, when I upgrade these clients to Outlook 2003 I cannot connect
to my Exchange server unless I change their primary DNS server to my
internal server address and reboot. I've attempted to delete and
recreate the entire profile but nothing seems to work except changing
the DNS entries. If I install Outlook 2003 when I am building the
client machines in my office, then ship them to the site, they work
fine through the WAN providers DNS servers. I am using the "Complete"
option when installing Outlook 2003.
Any ideas on what would cause this?