Re: NTL to block port 135
 

In the case of TCP it is only incoming SYN requests that are being blocked so you can establish outgoing connections ok (which should allow you to use exchange ok) - oh, and Jimbo has actually missed port 135 (TCP) from the above list ;)

Re: NTL to block port 135
 

Oops, so I did!

Re: NTL to block port 135
 

81 is North west.
mine is 81.97... etc

Stockport in manchester

Re: NTL to block port 135
 

:confused:

Re: NTL to block port 135
 

NTL have a block of addresses starting with 81 (.96 to .111 IIRC) but it definitely isn't limited to the North-West - we just happened to add a load of new addressing in that area while working through that range.

81.97 is, however, entirely in the NW, from Burnley to Stoke, Birkenhead to Ashton.

Re: NTL to block port 135
 

Wouldnt that destroy SMB?

Re: NTL to block port 135
 

I don't see why. If you are know how to use SMB you know how to open the port.

Same thing with their messenger service.

Re: NTL to block port 135
 

Port 135 is not SMB, it is the RPC service which is an integral part of the OS. :cool:

It would be a bit like saying you could stop people hacking into a web server by not opening port 80 on it :D

Re: NTL to block port 135
 

Have you ever tried reconfiguring SMB in Windows to use another port? It doesnt work like that. My point is, you cant just go blocking off ports within the operating system, other applications can make use of them too.