Dell PowerEdge T110
MS SBS 2008 SP2
Exchange 2007 SP3
A bit of background...
Long story short, customer lets BT hijack there nice gig lan and stick an IP phone system on it with a 10/100 switch and 10/100 IP phones, with the computers now plugged in the phones, everytime the phone system crashes (and thats alot) the phones say 'server is unreachable' so they go to the server and switch the power off and back on - sigh...
Surprisingly the server copes with this for nearly two years before the OS is so corrupt it wont boot.
So a few weeks ago we have to wipe and reinstall the server as what backups they have will be as corrupt as the os.
Now they have a nice clean install of SBS patched up to date, we managed to pull back all the user emails either using tools that can extract them from the edb file or from the ost file.
They have now been up and running for a few weeks without issue and under strict instruction never to just turn the server off.
A user calls yesterday saying they cant connect to there exchange email account, on closer investigation this user is using Outlook 2010 on windows 7 Pro, and has 5 profiles in outlook setup, each one a seperate exchange account.
4 of the 5 profiles log into there respective exchange accounts without issue, however the 5th (and last in the list) wont log in and gets the following error message:
"Cannot open your default folders. The attempt to log on to Microsoft Exchange has failed."
What we have tried so far...
As there on exchange we just removed and re added the profile, no change.
Completely removed the profile and the ost file, recreated it and set it not to cache data, disabled the ost, and set the profile to prompt for username and password, no change.
Logged in from the PC in question using webmail, works fine.
Created a profile on the server, setup outlook and added the exchange account in question, works fine.
So only this specific exchange account wont work on this specific pc, other exchange accounts work, and the account in question works elsewhere.
A trawl of the web has not shed any further light on what could be causing this.
Has anyone else come across this before, the error message in question seems to indicate a conectivity issue and articles related to the message are working on the asumption you cannot connect at all, yet in this case you can connect to other exchange account from this pc?