Allow for user-configurable authentication port!

[thom]

After the MSBlaster problem, ISPs are blocking 135.
Outlook cannot communicate to Remote Exchange Servers!

The security hole that allowed 135 to be vulnerable was
Cause. Most ISPs now INDEFINTELY blocking 135 to prevent
uneducated end users with outdated systems from allowing
the worm(s) to propogate, is Effect. To put the onus on
ISPs to release the very port which was vulnerable in the
first place makes no sense. Until we as administrators
can manually configure the authentication port, we are
unable to connect to our Remote Exchange Servers. This is
an unacceptable level of customer service on your part.
Please resolve this issue.

 

[Milly Staples [MVP - Outlook]]

This is not Microsoft.

--
Milly Staples [MVP - Outlook]

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


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

| After the MSBlaster problem, ISPs are blocking 135.
| Outlook cannot communicate to Remote Exchange Servers!
|
| The security hole that allowed 135 to be vulnerable was
| Cause. Most ISPs now INDEFINTELY blocking 135 to prevent
| uneducated end users with outdated systems from allowing
| the worm(s) to propogate, is Effect. To put the onus on
| ISPs to release the very port which was vulnerable in the
| first place makes no sense. Until we as administrators
| can manually configure the authentication port, we are
| unable to connect to our Remote Exchange Servers. This is
| an unacceptable level of customer service on your part.
| Please resolve this issue.