Outlook 2003 on Vista not connecting to SBS 2003
Wierd problem.
I'm running SBS 2003 SP2 server with about 40 clients connecting to it.
Yesterday we had a server crash, event logs said that it couldn't access the gpt.ini file and the whole network fell over. Hard to do a hard reboot and everything seemed fine. But.
Since then the Vista clients have been unable to connect to the Exchange server using Outlook 2003, the status bar at the bottom shows as disconnected.
All XP clients are uneffected by this (which is why I didn't know about it until the CEO asked me the server was still down! He's on vista, I'm on XP).
All other network resources such as AV, intranet, internet, shared files etc. are fully operational to all users.
The vista users are able to access their emails using the OWA, but the CEO doesn't like using that.
Any ideas?
Re: Outlook 2003 on Vista not connecting to SBS 2003
Re: Outlook 2003 on Vista not connecting to SBS 2003
Thanks Einstein07 but none of those threads that related to my problem came to a resolution.
I'm not getting the 0x80040115 message. The only error message I'm getting says that I must connect to the Exchange server to update offline files. If I try and log in as the admin and connect to the exchange server for the first time I get a message saying that I must connect to the server.
At the same time a box flashes up on the bottom of the screen next to the Outlook icon in the active icon bar telling me that the Exchange connection has been restored.
Click OK on the error message Outlook closes icon vanishes.
Two entries in the event log every time, one saying connection to exchange down, will restore when possible, the second saying connection restored.
It's as though Outlook is too quick to quit.
From the look sof the dates on the threads you gave this issue has been around for a couple of months.
Is there a fix for this issue?
Re: Outlook 2003 on Vista not connecting to SBS 2003
Re: Outlook 2003 on Vista not connecting to SBS 2003
Thanks Birdie, it was the firewall, the work around in 939321 fixed it.
Still wierd that we've had five months without a problem then suddenly port 1723 gets blocked.
Again a million thanks.
