Printable View
We have recently upgraded to exchange 2010 and since then when people try to load outlook sometimes they will randomly get cannot connect to server. Server may be offline etc. Upon checking the mailbox settings under control panel -> Mail, the mailbox has changed to looking at one of our very old exchange servers. If you change it the current exchange name and then hit check name it will all start working instantly.
Any one have idea as to why this would start happening all of a sudden.
What's the old server? 2003? 2010?
Do you have a CAS Array defined?
Using PF?
Load balancing CAS array?
It was a 2003 server but it hasn't been in existence for at least 4 years?
Which one does it connect to? 3 or 18?Quote:
Originally Posted by mdench
And from what I understand of your CAS setup its slightly wrong anyway so that won't help.
If it is 18 then the install of office defaults to connect to the it using the MS Office customization tool
what about the other questions?
Have you ever used prf for olk config?
A PRF was used in the days before Windows 7 and new profiles (18 months ago)Quote:
Originally Posted by sukh
(I'm only saying that as he probably wouldn't know as i replaced it 18 months ago).
@glennda - Seems like you know the env?
Do you know about the other questions or has the env changed since then?
I built 90% of it! Erm no they have moved to Exchange 2010 since then but it is not 100% setup from what i understand.Quote:
Originally Posted by sukh
I had this previously with the users and the local PRF file - the prf file referenced an older server (server 3 as mentioned above) and this was replaced on all XP built machines with the one mentioned (18). Although this was replaced with the Office customization tool setup on all Windows 7 machines (whole school was wiped at once). And everybody's outlook re setup.
From What I understand of the 2010 setup - there are 2 cas servers but they are not load balanced - clients access from and individual servername instead of say outlook.localdomain.local which resolved to either of the cas servers.
OK, the only strange thing is why the server is picking up the old server 3 even if the CAS array exists. Do you know what's specified on the RPCClientAccess attribute on the DB's?
not a clue i have had nothing to do with the exchange 2010 upgrade. the old server 3 was removed not all that long ago (def not 4 years) as they had this strange problem that when they turned it off outlook stopped which was the why outlook was configured.Quote:
Originally Posted by sukh
Wait & see if Mdench can provide further info.