NTL to block port 135 - Page 5

**Paul** · 26-05-2004, 19:16

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

quadplay · 26-05-2004, 20:22

Oops, so I did!

bobby · 27-05-2004, 01:13

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

Stockport in manchester

**Paul** · 27-05-2004, 02:29

Quote:

Originally Posted by bobby

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

Stockport in manchester

BBKing · 27-05-2004, 06:03

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.

td444 · 31-05-2004, 11:19

Quote:

Originally Posted by downquark1

Here's a much better solution:

How about microsoft don't have the port open by default???

Wouldnt that destroy SMB?

downquark1 · 31-05-2004, 11:37

Quote:

Originally Posted by td444

Wouldnt that destroy SMB?

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.

**Paul** · 31-05-2004, 12:05

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

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

td444 · 31-05-2004, 14:52

Quote:

Originally Posted by downquark1

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.

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.