Solved

Setting up 2nd Exchange 2003 Account, can't login even though credentials work with owa and iphone.

Posted on 2014-01-31
9
317 Views
Last Modified: 2014-02-13
I've got a bit of an odd situation.

I've got a user who works for two different clients. Both Client A and Client B run their own sbs 2003 server running exchange.

User is member of domain for Client A and that exchange account works fine both on and offsite. However, exchange for client B works neither on nor offsite, refuses credentials.

Backstory

Originally, the user was primarily at Client B location. He was connected to their domain and e-mail worked fine both on and offsite. We connected him to Exchange for Client A through RPC. Took a bit of fiddling, but then worked fine.

After a couple of years, the companies got rearranged. I reloaded the user's laptop. I added it to the domain for client A. E-mail works fine on and offsite.

However, no end of trouble connecting to exchange for Client B. Finally took laptop to location of Client B. got working locally. Took back to Client A location, would not work. Traced error to certificate. Bought new certificate and installed. The error went away, but now credentials fail. This happens on and offsite now.

OWA Testing

I have tested and retested the credentials for owa. They work fine. I can use both user and domain\user to successfully login.

On the laptop though, I think I am forced to use domain\user as otherwise it assumes the domain for Client A.

Smartphones

This user also accesses both exchange accounts without issue.
0
Comment
Question by:MJCS
  • 7
9 Comments
 
LVL 13

Assisted Solution

by:imkottees
imkottees earned 250 total points
ID: 39826142
Hi,

make sure that you are giving correct proxy addresses while connecting over the internet.

http://office.microsoft.com/en-in/outlook-help/use-outlook-anywhere-to-connect-to-your-exchange-server-without-vpn-HP010102444.aspx
0
 
LVL 31

Assisted Solution

by:Gareth Gudger
Gareth Gudger earned 250 total points
ID: 39826397
If the client is a member of domain A, you will need to manually configure the Outlook client for domain B, or it will always pick up those settings. So, pick the manually configure method when setting up an account in Outlook and type in everything manually; server, Outlook Anywhere setting etc.
0
 
LVL 2

Author Comment

by:MJCS
ID: 39826590
imkottees,

There's not much for proxy options. These are my main settings.

I have also tried the only connect to proxy servers that have this principal in their certificate. (mail.domain.com)

I have also tried on fast networks, connect using HTTP first...


diggisaur,


I am manually configuring. Autoconfigure doesn't work. I believe this is due to exchange 2003 + Outlook 2010.
RPC-Domain-Proxy.PNG
0
Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 2

Author Comment

by:MJCS
ID: 39839590
It gets better.

I created a local user on the users computer.

I was able to manually connect Outlook to Client B's server. It worked fine. It detected that there were two users with the same first name and had me select which one.

I had thought maybe the key was to connect first before changing the rpc/http settings.

I logged out, then went back to the other users main DOMAIN\User account. Deleted the Office B Exchange profiles. Recreated and it could not find SERVER.local.

Then I tried pinging the SERVER.local. pinged successfully.

Then I tried the ip address of the server and that worked.

So I thought that I was finally clear, went to test it and:

cannot open your default email folders. you must connect to microsoft exchange with the current ost...

So I tracked down the ost folder location and cleared out all of my junk osts from troubleshooting this.

Tried again, no change.

Then I recreated the profile and checked file permissions, even re-ttok ownership of it, same message.
0
 
LVL 2

Author Comment

by:MJCS
ID: 39839605
I disabled offline, now I get "Cannot open your default e-mail folders. The attempt to log on to Microsoft Exchange has failed."
0
 
LVL 2

Author Comment

by:MJCS
ID: 39839685
I dug out the hosts file. Found entries tying the IP Address to SERVER.local, deleted them, rebooted.

Same message.

Deleted profile.

Created New profile with new name, could not finder SERVER.local... !!!
0
 
LVL 2

Author Comment

by:MJCS
ID: 39839709
Tried the internal IP address, resolves to FQDN and inserts it in box, finds user, allows profile creation without error.

GO to open profile in Outlook.

"The server is unavailable"
0
 
LVL 2

Accepted Solution

by:
MJCS earned 0 total points
ID: 39844148
The problem appears to be either an obscure issue related to the domain from Office A, or the user profile is corrupted.

Ended up removing computer from the domain @ Office A to resolve.
0
 
LVL 2

Author Closing Comment

by:MJCS
ID: 39855699
Figured out two possible explanations through my own troubleshooting.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
This article explains how to install and use the NTBackup utility that comes with Windows Server.
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video discusses moving either the default database or any database to a new volume.

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question