blocking tcp port 125

[ycp]

Hi all,
My organization got hit pretty bad with the blaster worms. Network folks decide to close all the tcp port 125 on the routers to slow down the infection. Since then Exchange Server 5.5 that I use for private internal email (sending status messages) seem to have performace issues. Someone told me that Exchange clients utilize port 125 for authenication and probably timing out due to the block and using different port to communicate. Could this be the cause of the problems?
Also separate issue. Getting multiple logons from same people. Usually three logons. This is causing problem with licensing. Any ideas?
As you can tell I'm cluesless with Exchange. Just one of those things that I got stuck with.

thanks in advance.

-Patrick-

 

[jackofalltrades99]

look at this article for info.

http://support.microsoft.com/defaul...port/kb/articles/q176/4/66.asp&NoWebContent=1

 

[devastator]

Ports 69, 593, and 4444 and 135 should be shut down for the blaster virus. Not sure what port 125 does exactly but that is not afected by blaster.

Either way we have those ports shut down and are having no issues.