Exchange Authentication Fails
Enivironment:
Server 1 - Windows Server 2008 Standard SP1 64-bit, Active Directory.
Server 2 - Windows Server 2008 Standard SP1 64-bit, Exchange 2007.
Client 1 - Outlook 2007.
Server 1 and 2 are on Domain 2 and Client 1 is on Domain 1.
I have set up a profile on Client 1 which connected to the Exchange Server and found the mail box fine. However, on opening Outlook I now get a password request box. Entering the password does nothing. I have reset the password on AD to make sure no errors to no avail.
Domain 2 is a new Domain we will gradually migrate to. In this first stage it is providing Exchange only.
Any help would be greatly appreciated.
Server 1 - Windows Server 2008 Standard SP1 64-bit, Active Directory.
Server 2 - Windows Server 2008 Standard SP1 64-bit, Exchange 2007.
Client 1 - Outlook 2007.
Server 1 and 2 are on Domain 2 and Client 1 is on Domain 1.
I have set up a profile on Client 1 which connected to the Exchange Server and found the mail box fine. However, on opening Outlook I now get a password request box. Entering the password does nothing. I have reset the password on AD to make sure no errors to no avail.
Domain 2 is a new Domain we will gradually migrate to. In this first stage it is providing Exchange only.
Any help would be greatly appreciated.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are these domians in different forests o sub-domains?
ASKER
Yes completely seperate. Different subnets. I am now guessing that Domain 2 just can't be found by the Client when I put in Domain2\Username. I can enter IP's for the new subnet in DNS but don't know if there is a way to do something similar for Domains.
I am avoiding trusts like the plague. The reason being I have quite a number of existing domains, eventually all to be replaced by the new one, and this are a mixed bunch including Novell and SBS which doesn't support trusts.
I am avoiding trusts like the plague. The reason being I have quite a number of existing domains, eventually all to be replaced by the new one, and this are a mixed bunch including Novell and SBS which doesn't support trusts.
I assume you are trying to connect using Outlook Anywhere, right?
ASKER
No. Not even familiar with Outlook Anywhere. Will do some quick reading. The seperate subnets are all part of a managed WAN so there is free access between them.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah, new name for an old method. What is the benefit of using Outlook Anywhere over OWA. Forget that, full featured Outlook and offline email is probably enough.
The better question would be, after setting up several hundred users to use this method would you go back to the traditional connection once we start moving everyone to the new domain and retire the existing ones. What are the pros and cons bettween a normal exchange connection and OA?
The better question would be, after setting up several hundred users to use this method would you go back to the traditional connection once we start moving everyone to the new domain and retire the existing ones. What are the pros and cons bettween a normal exchange connection and OA?
Normal exchange connection are for users who have a local exchange server. As your case is different, Outlook Anywhere will be the best option, as it works much better and can be accessed from anywhere.
It will be the best option for all your mobile users, still getting to use the full Outlook rather than OWA.
When you have two forests, I wouldn't even try to connect using MAPI connections!
It will be the best option for all your mobile users, still getting to use the full Outlook rather than OWA.
When you have two forests, I wouldn't even try to connect using MAPI connections!
ASKER
I started setting up Outlook Anywhere when I discovered there was a pre-windows 2000 name specified on the DC. I wasn't involved in the build process so wasn't aware this was applied. I tried this and logged in immediately, so what I expected to work intially has worked as hoped.
ASKER
Thank you for the input on this it is very much appreciated
if there aren't any more questions, please close the call.
ASKER