![]() |
Re: More port blocking
PS: Note the bit that the customer is able to select any of the options at any time, changed as many times as required.
The majority of the people who buy a computer from the likes of Tiny or PC World do not have a clue so for those the default of `block all inbound` will work. For us educated lot, we will know how to open up inbound ports. For the newbies that become educated, they will also be a able to open up inbound ports. The method would work. For sure port 135 is now a totally lost cause so that one may as well be blocked until the end of time. Only thing is that NTL have blocked UDP port 135 in both directions and TCP port 135 inbound only. My suggestion only relates to inbound connections and excludes reply ports. |
Re: More port blocking
Quote:
port 1433 Microsoft SQL Server port 1434 Microsoft SQL Monitor this may cause some problems |
Re: More port blocking
NTL posted this document some weeks ago,
http://www.ntlworld.com/tunnel.php?task=portBlocking You can navigate to it from the ---> help index ---> Important virus information Advice for Microsoft XP/NT/2000 users ---> ntl:home take new measures to protect against worms From the above NTL document: We are blocking Internet ports 137 (UDP), 138 (UDP), 139 (TCP), 445 (UDP & TCP), 593 (TCP), 1433 (TCP), 1434 (UDP) and 27374 (TCP) Inbound only. NTL may also be blocking other ports e.g. 4662 used by emule file sharing. The sub 1023 ports I generally agree with, but the high ports are causing me issues already, with lost connections. I'm tempted to PAT the listed high ports to a nul address on my firewall router, to prevent them being used as an outbound source. though this could quickly get out of hand if NTL keep blocking more ports. Also considering the range 1024 - 5000, since I have no inbound services on these addresses (only one rule as well). Time to do another port scan on my firewall I think, and look for the missing hits. |
Re: More port blocking
I have never come across anything that uses TCP593.
|
Re: More port blocking
Quote:
Port 135 (tcp/udp) Port 137 (udp) Port 138 (udp) Port 139 (tcp) Port 445 (tcp/udp) Port 593 (tcp) Basically the following formula applies: (NT4 or W2K or XP or W2K3) and no patch and no firewall = pant's down For the more anorak explanation try http://www.hkcert.org/salert/english...win_rpcss.html |
Re: More port blocking
NTL posted this document some weeks ago,
http://www.ntlworld.com/tunnel.php?task=portBlocking You can navigate to it from the ---> help index ---> Important virus information Advice for Microsoft XP/NT/2000 users ---> ntl:home take new measures to protect against worms From the above NTL document: We are blocking Internet ports 137 (UDP), 138 (UDP), 139 (TCP), 445 (UDP & TCP), 593 (TCP), 1433 (TCP), 1434 (UDP) and 27374 (TCP) Inbound only. NTL may also be blocking other ports e.g. 4662 used by emule file sharing. The sub 1023 ports I generally agree with, but the high ports are causing me issues already, with lost connections. I'm tempted to PAT the listed high ports to a nul address on my firewall router, to prevent them being used as an outbound source. though this could quickly get out of hand if NTL keep blocking more ports. Also considering the range 1024 - 5000, since I have no inbound services on these addresses (only one rule as well). Time to do another port scan on my firewall I think, and look for the missing hits. |
Re: More port blocking
Actually, ports 1433 (TCP) and 1434 (UDP) are not going to cause a problem for Windows XP equipped computers. Because ......
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters ReservedPorts=REG_MULTI_SZ:1433-1434 Only problem at the moment will be if anything legitimate wants to use ephemeral port 27374 (TCP). I wonder if it is allowable to amend the above key value from 1433-1434 to 1433-1434,27374? Or are the values specified on a separate line? See: http://support.microsoft.com/default...b;en-us;812873 http://support.microsoft.com/default...b;en-us;196271 http://www.jsiinc.com/SUBO/tip7000/rh7082.htm I'm going to try setting the value of this ReservedPorts key to following .... 1433-1434 27374-27374 17300-17300 It's either going to work, or I'll be quickly changing it back to just 1433-1434. |
Re: More port blocking
Unless you have modified your system then it will not attempt to use 17300 or 27374 anyway since they are above the default maximum of 5000.
AFAIK you can only have one range in the reserved ports value so use 1433 - 1434. |
Re: More port blocking
Just tried it and the ports I nominated to be reserved were not used as ephemeral ports. That'll do me. This is with Windows XP SP-1.
|
Re: More port blocking
Quote:
|
Re: More port blocking
Quote:
Set the value of the ReservedPorts registry key to 1433-1434 3010-3050 Then restart the computer and as soon as you get the desktop open a DOS command prompt and pre-type the command `netstat`. Start the browser, so to a web site. I used www.bbc.co.uk. In the case of Windows XP the port allocation starts from 3000 and not 1024. Here is the result I got as provided by the NETSTAT command ... 3008 3051 3052 3056 3058 3059 3062 3063 etc.... Notice that no ports were allocated between and including 3010 to 3050. It's always a good idea to prove that the theory is fact and that's a habit I got. Seems with Windows XP and quite possibly other versions of Windows, it is possible to exclude the use of the ports that NTL are blocking. Wish NTL would be more helpful with this issue, but it's guru's like me that have to discover these sort of useful pieces of information. |
Re: More port blocking
I thought about reserving ports, but would need to do it on my router (linksys) which does not have this facility. Annoying isn't it. (And unneccessary)
|
Re: More port blocking
I've just now reported this issue to LinkSys. Will LinkSys act on the information given? Anyones guess.......
We could take bets, maybe? |
Re: More port blocking
Quote:
-- Chris / Noodle (chris@woaf.net) |
Re: More port blocking
Ah, here is the best bit. A very polite note stating the issue that ISP's are blocking ports and that the firmware in all of their routers will be affected by this issue.
Now, I wonder what would happen if enough people would run into this problem and report the same shortcoming of their router? As in having the ability to reserve ports so the router would not use the reserved ports as response ports? (NUDGE, WINK, HINT, SLAP, etc....) I suppose one person bringing up the issue would not trigger a response from LinkSys but should enough people experience problems using the Internet because of this issue then maybe LinkSys's software engineers will put in an option to allow the owner of the router to reserve inbound ports? Well, techincally not reserve, but an exclusion list. :angel: |
| 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