In the following discussion: http://www.antionline.com/showthread...light=port+135
jinxy provides a snippet from Reg Review of a list of ports/services that ought to be disabled.

After reading the forum and receiving guidance from a great deal of sources regarding disabling unnecessary services, then checking the results through running netstat -ano (I'm running Win XP) from the command line I manged to clear a great many services and close a few ports.

For some unknown reason, port 135 re-appeared due to process svchost.exe. Performing an advanced search on the AP forums using 'port 135' as a search term, I came across the link above. Disabling the services as suggested by Reg Review, I then rebooted, opened up a command prompt and ran netstat -ano. To my surprise, there were no services at all running. Nothing. Zilch. Nada. I also noticed that ZA had failed to load in my system tray. I fired up Firefox to find that the server couldn't be found ..

Roh ro! Oh kay .. time to figure out what service I had disabled. At first I thought it was the Remote Access Control Manager -- enabled, tried to start but wouldn't start due to an RPC dependency. Hmmm .. Rebooted. Same problem. No services running, no ZA and no connection. Using a reductive approach, I figured I would turn each disabled service on, then reboot and see if my connection would be restored. Well, I jump-started the reductive process by only examining the disabled services (Start/Run/services.msc) that had affected network connections. I noticed that DHCP Client had been disabled (as per Reg Review) so I set it to Automatic, then re-started it.

Bingo! Connectivity once more!

Hopefully, this has resolved my connectivity problems, but just a warning for users in case they experience a lack of connectivity.

Regards,
Riotgirl