• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 349
  • Last Modified:

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

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
MJCS
Asked:
MJCS
  • 7
3 Solutions
 
imkotteesSenior Messaging EngineerCommented:
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
 
Gareth GudgerCommented:
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
 
MJCSAuthor Commented:
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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
MJCSAuthor Commented:
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
 
MJCSAuthor Commented:
I disabled offline, now I get "Cannot open your default e-mail folders. The attempt to log on to Microsoft Exchange has failed."
0
 
MJCSAuthor Commented:
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
 
MJCSAuthor Commented:
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
 
MJCSAuthor Commented:
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
 
MJCSAuthor Commented:
Figured out two possible explanations through my own troubleshooting.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now