![]() |
Re: More port blocking
Quote:
If its the former then there are better alternatives available , if its the latter then he's not affected. |
Re: More port blocking
Quote:
To clear up any mis-understanding, Yes I am referring to connecting to other machines over the Internet, not on an internal Lan. How I connect to them it is my choice, they are all windows machines and the data is not confidential in any manner, windows file sharing is the easyest method and has served my well for 5+ years thank you. |
Re: More port blocking
Quote:
It appears that you may well be on of the unfortunate small number who may be affected although there are many ISPs (certainly Zen does, Telewest did for a while, not sure about BT and in the US it's becoming more common place) now that are blocking Netbios on the public network and indeed it is something which I believe Microsoft themselves have advised ISPs to do. |
Re: More port blocking
Quote:
|
Re: More port blocking
ATM - the evidence would seem to suggest thay have used a bit of common sense and only blocked incoming connection requests on the offending ports - i.e. I can still connect to my servers but my firewall logs suggest that incoming traffic on those ports has been blocked.
|
Re: More port blocking
Quote:
|
Re: More port blocking
sorry if this has already been asked/answered, but I couldn't see it anywhere.
so if ntl are blocking ports are they going to post a list of which ports are blocked, so people can work around the problem. does anybody know what ports are blocked? is there any way to find out which ones are blocked? thanks |
Re: More port blocking
Well the original article we were discussing was posted on .com so it's inaccessible now :rolleyes:
I just tried to look on community but that seems dead again as well :confused: |
Re: More port blocking
Quote:
totally from memory so I may be wrong, but I think it is ports 135. 137, 139, 445 & any over 1200. |
Re: More port blocking
would that explain why online games have started having problems. e.g ut2k3 uses ports 7777, 7778, 7787, 7788, 28900, 28902
|
Re: More port blocking
Quote:
As I recall it was 135, 137, 138, 139, 445, 1433, 1434 & port in the 27xxx range that sub seven uses (can't remember it exactly). |
Re: More port blocking
Quote:
|
Re: More port blocking
Quote:
|
Re: More port blocking
Here is an RFC:
NTL could do with blocking inbound connections to port 17300. It seems the hackers are trying to get their revenge. My router is recording quite an increase in connection attempts to TCP port 17300 from various IP addresses. The problem is that port blocking is not really an answer. There will come a point where so many ports will be blocked that it will be becoming impossible to use the Internet. I was rediculed for the suggestions some months ago, but really NTL should upgrade their UBR's or firewalls so the customer has some basic contol over what can connect to his/her equipment. By default every inbound port should be blocked. This would not be a problem because reply ports will not be blocked. Routers already so this and have been doing this for years. Un-educated users, I think, would not touch these options. 'cos they don't know how it all works. The customer would be given three simple options that can be changed at any time. Option 1: Block all inbound connections, unless to a reply port. Option 2: Block all inbound connections selected by NTL. Option 3: Block all inbound connections only for ports 135, 137, 139 and 445. Any customer that would select option 3 would automatically be put on NTL's watch list so any suspicious traffic would be looked by at NTL's network operations centre and appropriate action taken. Just three simple filter sets that can be defined network wide and each customer could choose only one of them. You would not want to allow the customer to define their own filter sets as then it will be totally unmanagable and the memory and processing power of the router might now be enough. The option suggested here would work as it already implemented as option 3 in the suggestion above. |
Re: More port blocking
Quote:
Edit: FFS why can't every forum have the same smilies ... Grrrrrrr ...... |
| All times are GMT. The time now is 16:01. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum