S
Strater
Clients: Windows XP Pro SP2 + Outlook 2003
Server: Exchange 5.5 SP4
Story: We recently acquired two new branch offices. Previously both offices
had been using Outlook 2003 connecting to an Exchange server in Tampa called
TAMPAMAIL. I have no access to TAMPAMAIL. It was run by a third party.
Our Exchange server is in Houston. It is called HOUSTONMAIL.
I need to change each client so that it no longer connects to TAMPAMAIL, but
instead goes now to HOUSTONMAIL.
I went to each client and removed the mail profile through control panel. I
then clicked on Outlook and went through the auto setup, using MS Exchange
Server, with a server name of HOUSTONMAIL and whatever the user names are.
I unchecked the "use cache" box.
When I click on "check name" it asks for a username and password. It takes
a VERY long time, but it finally underlines both the server name and the
user name. So far, so good, I guess, although it shouldn't take this long.
But when Outlook tries to open, it hangs for about two minutes and then says
the exchange server is unavailable.
More details:
Each office is part of a single Active Directory Win2K domain called
hou.fmg.com. Each server is a doman controller, and each runs DNS.
I added a host entry for HOUSTONMAIL into DNS. From the servers, I can ping
HOUSTONMAIL and can do an NSLOOKUP.
From the clients I can ping HOUSTONMAIL. It replies very quickly.
For good measure, I added HOUSTONMAIL to the hostfile of the client
machines.
So connectivity looks fine, but still no luck. I have seen several comments
in newsgroups that suggest it is a DNS issue -- but DNS is kind of a broad
subject. Is there a specific DNS entry I need to add? Or could it be that
the clients are appending a DNS suffix that is causing Outlook to misfire
when it launches? Or is there something else I should be looking at?
Thanks
Server: Exchange 5.5 SP4
Story: We recently acquired two new branch offices. Previously both offices
had been using Outlook 2003 connecting to an Exchange server in Tampa called
TAMPAMAIL. I have no access to TAMPAMAIL. It was run by a third party.
Our Exchange server is in Houston. It is called HOUSTONMAIL.
I need to change each client so that it no longer connects to TAMPAMAIL, but
instead goes now to HOUSTONMAIL.
I went to each client and removed the mail profile through control panel. I
then clicked on Outlook and went through the auto setup, using MS Exchange
Server, with a server name of HOUSTONMAIL and whatever the user names are.
I unchecked the "use cache" box.
When I click on "check name" it asks for a username and password. It takes
a VERY long time, but it finally underlines both the server name and the
user name. So far, so good, I guess, although it shouldn't take this long.
But when Outlook tries to open, it hangs for about two minutes and then says
the exchange server is unavailable.
More details:
Each office is part of a single Active Directory Win2K domain called
hou.fmg.com. Each server is a doman controller, and each runs DNS.
I added a host entry for HOUSTONMAIL into DNS. From the servers, I can ping
HOUSTONMAIL and can do an NSLOOKUP.
From the clients I can ping HOUSTONMAIL. It replies very quickly.
For good measure, I added HOUSTONMAIL to the hostfile of the client
machines.
So connectivity looks fine, but still no luck. I have seen several comments
in newsgroups that suggest it is a DNS issue -- but DNS is kind of a broad
subject. Is there a specific DNS entry I need to add? Or could it be that
the clients are appending a DNS suffix that is causing Outlook to misfire
when it launches? Or is there something else I should be looking at?
Thanks