B
boofhead
Ok,
I have been trying to migrate to Exchange 2003 and so far everything
seemed to be honky dory until today. I'm now having a problem with my Outlook
Clients connecting to the Mailboxes on the Exchange 5.5 or 2003 server. Here
is what I had and now have:
The Past:
Running NT Domain with Exchange 5.5 on a W2k Server in our trusted
network and Outlook 2000 and Outlook 2001 for the Macintosh client in the
DMZ. With ports 135(RPC), 50110(DS Info) and 50111(Information Store) open
through our firewall to our Exchange 5.5 server. The last two were hard coded
into our Exchange server. The machines in the DMZ were not part of our DOMAIN
but the users had accounts in the domain for email access. This configuration
worked flawlessly.
Today:
Now we have upgraded the NT Domain to Active Directory and added an
Exchange 2003 to the mix. All of my mailboxes are still on the Exchange 5.5
server with one test box on the 2003 server. After testing everything works
fine in the Trusted network. But when we went to test Outlook 2000 and 2003
they fail to connect to the server or even resolve the mailbox. The system
times out. The Outlook 2001 for the Mac continues to work as normal. The
firewall hasn't been changed as of yet so the DMZ clients are still pointing
to the same 5.5 server. I see connectivity going accross the Firewall on Port
135 to get the services info but then nothing else happens except an error
stating that it failed to connect.
I assume the problem is that Exchange 2003 and AD have elevated the 5.5
architecture and now the 5.5 is telling the Outlook 2000 or higher that they
need to have AD authentication before then can connect to the Exchange.
My question is that how can I reconnect those clients to the old
Exchange 5.5 server without having an extended downtime? I know I could do it
via RPC over HTTP but that isn't really an option as of yet since we haven't
moved that far into the project at this time. Does anyone have any further
ideas that can resolve this issue quickly but painlessley.
If not then when did this connection break is my last question? Was it
AD or adding the Exchange 2003 server to the mix?
Thank-you to anyone who can shed some light on this issue.
-Chris
I have been trying to migrate to Exchange 2003 and so far everything
seemed to be honky dory until today. I'm now having a problem with my Outlook
Clients connecting to the Mailboxes on the Exchange 5.5 or 2003 server. Here
is what I had and now have:
The Past:
Running NT Domain with Exchange 5.5 on a W2k Server in our trusted
network and Outlook 2000 and Outlook 2001 for the Macintosh client in the
DMZ. With ports 135(RPC), 50110(DS Info) and 50111(Information Store) open
through our firewall to our Exchange 5.5 server. The last two were hard coded
into our Exchange server. The machines in the DMZ were not part of our DOMAIN
but the users had accounts in the domain for email access. This configuration
worked flawlessly.
Today:
Now we have upgraded the NT Domain to Active Directory and added an
Exchange 2003 to the mix. All of my mailboxes are still on the Exchange 5.5
server with one test box on the 2003 server. After testing everything works
fine in the Trusted network. But when we went to test Outlook 2000 and 2003
they fail to connect to the server or even resolve the mailbox. The system
times out. The Outlook 2001 for the Mac continues to work as normal. The
firewall hasn't been changed as of yet so the DMZ clients are still pointing
to the same 5.5 server. I see connectivity going accross the Firewall on Port
135 to get the services info but then nothing else happens except an error
stating that it failed to connect.
I assume the problem is that Exchange 2003 and AD have elevated the 5.5
architecture and now the 5.5 is telling the Outlook 2000 or higher that they
need to have AD authentication before then can connect to the Exchange.
My question is that how can I reconnect those clients to the old
Exchange 5.5 server without having an extended downtime? I know I could do it
via RPC over HTTP but that isn't really an option as of yet since we haven't
moved that far into the project at this time. Does anyone have any further
ideas that can resolve this issue quickly but painlessley.
If not then when did this connection break is my last question? Was it
AD or adding the Exchange 2003 server to the mix?
Thank-you to anyone who can shed some light on this issue.
-Chris