(?) Unable to contact the outgoing mail server (?)

  • Thread starter Thread starter TimWalsh
  • Start date Start date
T

TimWalsh

Suddenly Outlook doesn't work. Upon Send/Receive I get:

"Unable to contact the outgoing mail server (SMPT)..."

It's NOT my provider. I can connect via the Web to my email and get it fine.
Plus I have TWO providers. Both are set up as accounts in Outlook and both
give the above error.

I've already backed up my pst and stuff in case Outlook totally pukes on me,
but any ideas how to fix this?

Thanks,
Tim
 
Solved.

I uninstalled ZoneAlarm.

Even though I had ZA disabled and not started (even through MSConfig), it
took absolute uninstalling it and a reboot to get things working again. I
have now seen ZA interfere with many conection types since upping to WinXP
SP2. They just plain don't like each other.

-Tim
 
TimWalsh said:
Even though I had ZA disabled and not started (even through
MSConfig), it took absolute uninstalling it and a reboot to get
things working again. I have now seen ZA interfere with many
conection types since upping to WinXP SP2. They just plain don't like
each other.

And yet many people use ZA with XP SP2 with no trouble at all. I, for
example, am one. However, I stick with ZA V2.1.5.
 
Brian Tillman said:
And yet many people use ZA with XP SP2 with no trouble at all. I, for
example, am one.

Being around support people, being one, and using them myself, I know a
guaranteed groan comes with mention of "SP2" or "ZA". No kidding. I hear it
all the time, and many times it's UNjustified. People love to jump to the
conclusion it's ZA's fault. For example, problems with Bellsouth DSL and a
mention of ZA got a stern statement that ZA flat-out cannot be used with
their service - end of story. I tweaked it to work, however.

But then along came SP2 and BAM my DSL was now hit and miss <sticking to the
example>. I often had to reboot to get connection. No solutions anywhere.
Finally I shut down ZA and it worked. Now, most recently, CITRIX failed to
work and no solutions were found by the staff.... until I uninstalled ZA.

Yes, I too sometimes find ZA to be at fault, but I don't jump to that
conclusion. However, if there are no other solutions found and uninstalling
ZA works.... that IS the solution.

However, I stick with ZA V2.1.5.

I don't know any users still with v2. Maybe the ZA people ought to recommend
that version as a "special" WinXP-SP2 ZA patch. <lol>

-Tim
 
Back
Top