"MS Exchange Server Unavailable"?

[Nick Blawat]

Following the brew-ha-ha of the MBlaster virus and all its
variants, I can no longer access my academic institution's
MS Exchange Server. Since all of my Outlook data resides
there, I can't even open Outlook 2002 in offline mode.
Obviously I am pulling my hair out.

To date, I have updated windows XP, updated Norton Anti-
Virus, downloaded and ran latest mBlaster removal tool
from symantec...no virus found on my system. Have access
to the internet through my Earthlink DSL connection...no
problem accessing webmail.

Spoke to two different Earthlink Tech Support people.
Really pushed them to be honest about whether or not they
are blocking Port 135 (school's MS Exchange Port for
Outlook). Both denied it and admitted to blocking Port 25
for SPAM. They offered possible solutions to my problem
including:

1. Commercial Firewall package causing problems...I've
never installed any. Relying on XP for this.

2. Anti-Virus software causing problem...Unlikely. I
don't recall if I lost access to the server after
installing the updates, but just to check I disabled
Norton completely, restarted, and tried to access the
server...no luck!

3. Some kind of router or home network conflict. Not
applicable, my desktop is connected to my DSL modem which
goes straight into the wall. No home network at all.

The final recommendation from Earthlink was to rebuild my
email accounts in Outlook. Which sounds like a good idea
until I try to open Outlook AND I CAN'T BECAUSE I CAN'T
ACCESS THE SERVER AND I CAN'T WORK OFFLINE!!!!

So, as far as I can tell I am completely helpless...please
advise...uninstall Outlook maybe?

Nick

(e-mail address removed)

 

[Milly Staples [MVP - Outlook]]

Have you checked with your University to see if they are blocking port 135?
That sounds like the most likely culprit to me. They may be blocking until
they can verify that all the machines that connect to Exchange have been
patched. Universities are notorious for being hotbeds of infection - yours
is probably taking the cautious role.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact.


After searching google.groups.com and finding no answer
Nick Blawat <[email protected]> asked:

| Following the brew-ha-ha of the MBlaster virus and all its
| variants, I can no longer access my academic institution's
| MS Exchange Server. Since all of my Outlook data resides
| there, I can't even open Outlook 2002 in offline mode.
| Obviously I am pulling my hair out.
|
| To date, I have updated windows XP, updated Norton Anti-
| Virus, downloaded and ran latest mBlaster removal tool
| from symantec...no virus found on my system. Have access
| to the internet through my Earthlink DSL connection...no
| problem accessing webmail.
|
| Spoke to two different Earthlink Tech Support people.
| Really pushed them to be honest about whether or not they
| are blocking Port 135 (school's MS Exchange Port for
| Outlook). Both denied it and admitted to blocking Port 25
| for SPAM. They offered possible solutions to my problem
| including:
|
| 1. Commercial Firewall package causing problems...I've
| never installed any. Relying on XP for this.
|
| 2. Anti-Virus software causing problem...Unlikely. I
| don't recall if I lost access to the server after
| installing the updates, but just to check I disabled
| Norton completely, restarted, and tried to access the
| server...no luck!
|
| 3. Some kind of router or home network conflict. Not
| applicable, my desktop is connected to my DSL modem which
| goes straight into the wall. No home network at all.
|
| The final recommendation from Earthlink was to rebuild my
| email accounts in Outlook. Which sounds like a good idea
| until I try to open Outlook AND I CAN'T BECAUSE I CAN'T
| ACCESS THE SERVER AND I CAN'T WORK OFFLINE!!!!
|
| So, as far as I can tell I am completely helpless...please
| advise...uninstall Outlook maybe?
|
| Nick
|
| (e-mail address removed)

 

[Lanwench [MVP - Exchange]]

Earthlink is indeed blocking 135 to the best of my knowledge. You really
need to look into implementing VPN for remote access via Outlook, and keep
those firewall ports closed.

 

[Mike Morrison]

You are not alone on this. I have recently had this
problem since msblast came out and i have taken all the
necessary precautions to not be infected. Now here is
where I differ, I host my own mail on my own server which
is sitting in my room. I have the same problem
connecting to it that you do, only I know that I'm not
blocking port 135. Now i know for a fact that to open
exchange just to get it open i never have to leave my
internal network, so that obviously isn't the case here.
Try hitting retry on yours, eventually i get in but it is
very very very slow. I also am not the only person to
have this problem. the company i work for also is having
this problem and I have yet to find a resolution for it.

-Mike Morrison
Microsoft MCP
(e-mail address removed)

 

[Nick Blawat]

No dice here...University confirmed they are not blocking
Port 135. They have no reason not to be upfront with this
since their students rely on it to survive from a
communications standpoint. They have also taken every
measure possible to help us protect our computers. I have
no doubt that the problem doesn't reside at my academic
institution.

 

[Lanwench [MVP - Exchange]]

Note - if they're really taking every measure possible to protect your (and
their) computers, they'll put in VPN or SSL/OWA ;-)

 

[Lanwench [MVP - Exchange]]

Use VPN and keep your firewall working properly to block all potentially
dangerous ports.