Definatly will do my best to get 135 and the others shut off. THe main reason they were left open was so that users can have access to MS Outlook and such from home. I know bad idea, have them VPN and such. But I didn't create the network... I only inheirted it.

So the main problem withs shutting off 135 is we need to touch all the PC's communicate to the users... blah blah blah.. the ususal stuff... However I don't believe that 139 effects this so I should be able to get a seperate plan setup to just shut 139 off and provide some type better security

Just as a side note... I found out why we didn't have this problem before was because we were using W2k which allows you to set Restrict Anonomous to 2(deny null connections). However when we upgraded to W2k3, it does not allow you to have a value of 2 in the registry. If you put a value of 2, it treats it as a value of 1. Therefore stuff is still open.