Blackadder222
Technical User
Server is running NT4 and Exchange 5.5.
Clients are all running Outlook 2002.
On my internal network there is no problem, Outlook 2002 connects to Exchange normally.
And until yesterday, remote access using Outlook 2002 from my home office was no problem.
But for some reason, since yesterday mid-morning, I cannot get Outlook to connect remotely (from several different clients on different ISP's/connections.
Interestingly, I can still access my Exchange account using IMAP (I'm using Opera's mail client to do so as a temp workround), and remote web access (OWA) is also working fine. Unfortunately this gives only limited functionality!
I'm not sure if it's relevant, but I've discovered that port 135 now seems to be blocked on both client and server machines - however I've no way of knowing whether this was the case before my problem arose. I've been assured by the ISP through which the server is connected that they have not/do not block port 135 (or any ports).
I was wondering if there is any connection with the "blaster" worm that is causing problems currently - although my AV software reports no infection.
I've spent the last 24 hours struggling to find a solution and so far have failed - some guidance would be much appreciated!
Clients are all running Outlook 2002.
On my internal network there is no problem, Outlook 2002 connects to Exchange normally.
And until yesterday, remote access using Outlook 2002 from my home office was no problem.
But for some reason, since yesterday mid-morning, I cannot get Outlook to connect remotely (from several different clients on different ISP's/connections.
Interestingly, I can still access my Exchange account using IMAP (I'm using Opera's mail client to do so as a temp workround), and remote web access (OWA) is also working fine. Unfortunately this gives only limited functionality!
I'm not sure if it's relevant, but I've discovered that port 135 now seems to be blocked on both client and server machines - however I've no way of knowing whether this was the case before my problem arose. I've been assured by the ISP through which the server is connected that they have not/do not block port 135 (or any ports).
I was wondering if there is any connection with the "blaster" worm that is causing problems currently - although my AV software reports no infection.
I've spent the last 24 hours struggling to find a solution and so far have failed - some guidance would be much appreciated!