MSBLASTER and outlook

[FRED]

Some of my clients with outlook 2000 can not connect to
our exchange 2000 SP3 server. They keep getting "server
not found" errors. This only started since the MSBlaster
worm was released Monday. I assume that since Exchange
requires port 135 for clients to connect, that with all
the scanning by the virus on port 135 it is just bieng
Denied. All the patches and virus scanners have been
updated on the Xchng Server and most clients. Our
firewall shows several denies a minute for port 135.

Can someone at MS confirm this or are there more steps
needed to remedy this problem. I assume with al the
traffic caused by the worm that the clients are just
timing out.

Thanks,

 

[Diane Poremsky [MVP]]

where are the Exchange server and Outlook clients in relation to the
firewall? Both on the same side, I hope. Unless the file made it inside
your firewall, it should not be causing problems on the inside of the
network.

--
Diane Poremsky [MVP - Outlook]
http://www.poremsky.com - http://www.cdolive.com

Expert Zone http://www.microsoft.com/windowsxp/expertzone

Search for answers: http://groups.google.com
Most recent posts to the Outlook newsgroups:
http://groups.google.com/groups?as_ugroup=microsoft.public.outlook.*&num=30

 

[Steve]

It is my understanding that many ISPs have started
blocking port 135, which is the port Outlook and Exchange
server use. SBC seems to be blocking all port 135
traffic. Anyone else heard this?

-----Original Message-----
where are the Exchange server and Outlook clients in relation to the
firewall? Both on the same side, I hope. Unless the file made it inside
your firewall, it should not be causing problems on the inside of the
network.

--
Diane Poremsky [MVP - Outlook]
http://www.poremsky.com - http://www.cdolive.com

Expert Zone http://www.microsoft.com/windowsxp/expertzone

Search for answers: http://groups.google.com
Most recent posts to the Outlook newsgroups:
http://groups.google.com/groups? as_ugroup=microsoft.public.outlook.*&num=30

Some of my clients with outlook 2000 can not connect to
our exchange 2000 SP3 server. They keep getting "server
not found" errors. This only started since the MSBlaster
worm was released Monday. I assume that since Exchange
requires port 135 for clients to connect, that with all
the scanning by the virus on port 135 it is just bieng
Denied. All the patches and virus scanners have been
updated on the Xchng Server and most clients. Our
firewall shows several denies a minute for port 135.

Can someone at MS confirm this or are there more steps
needed to remedy this problem. I assume with al the
traffic caused by the worm that the clients are just
timing out.

Thanks,

 

[FRED]

The clients with the problem are on the Internet side of
the firewall. OWA and Outlook via VPN work just fine, but
a couple connect just via the internet.

-----Original Message-----
where are the Exchange server and Outlook clients in relation to the
firewall? Both on the same side, I hope. Unless the file made it inside
your firewall, it should not be causing problems on the inside of the
network.

--
Diane Poremsky [MVP - Outlook]
http://www.poremsky.com - http://www.cdolive.com

Expert Zone http://www.microsoft.com/windowsxp/expertzone

Search for answers: http://groups.google.com
Most recent posts to the Outlook newsgroups:
http://groups.google.com/groups? as_ugroup=microsoft.public.outlook.*&num=30

Some of my clients with outlook 2000 can not connect to
our exchange 2000 SP3 server. They keep getting "server
not found" errors. This only started since the MSBlaster
worm was released Monday. I assume that since Exchange
requires port 135 for clients to connect, that with all
the scanning by the virus on port 135 it is just bieng
Denied. All the patches and virus scanners have been
updated on the Xchng Server and most clients. Our
firewall shows several denies a minute for port 135.

Can someone at MS confirm this or are there more steps
needed to remedy this problem. I assume with al the
traffic caused by the worm that the clients are just
timing out.

Thanks,

.