Something blocking quite a few ports on my connection

[mrSHEiK124]

About one month ago, I realized that Remote Desktop stopped working. When I got home, I realized that my computer wasn't on the DMZ list, so I fixed that, but never bother trying to connect remotely again, until yesterday. This morning, I noticed that uTorrent couldn't upload anything, and had the "port blocked" error. I tried their port checker, and got this result:

Welcome to the µTorrent Port Checker.
A test will be performed on your computer to check if the specified port is opened.

Checking port 32003 on MY IP YO...

Error! Port 32003 does not appear to be open.

Please see www.portforward.com for more information about how to map a port.

Please make absolutely sure that PeerGuardian2 or Protowall is allowing utorrent.com (72.20.34.145) in either of those programs. Those of you using ipfilter.dat should make sure the list does not include the website's IP. After making sure of this, re-run this test by refreshing the page (F5).

I'm not running PeerGuardian2 or Protowall or any other firewall app, and Windows Firewall is disabled. I disabled all WAN security features on my router (WRT54G with HyperWRT2) and made sure my IP was DMZ'd. Then I tried a traceroute to utorrent.com, and got these results:

traceroute to www.utorrent.com (72.20.34.145), 30 hops max, 40 byte packets
1 10.103.0.1 (10.103.0.1) 7.173 ms 5.692 ms 6.473 ms
2 pch15.50.tampflerl-rtr1.tampabay.rr.com (65.32.14.254) 10.695 ms 8.165 ms 8.886 ms
3 pos6-0-OC-192.tampflerl-rtr3.tampabay.rr.com (65.32.8.133) 69.639 ms 60.571 ms 103.381 ms
4 pop1-tby-P3-0.atdn.net (66.185.136.57) 10.976 ms 10.238 ms 9.529 ms
5 bb1-tby-P0-0.atdn.net (66.185.136.160) 155.571 ms 133.776 ms 34.618 ms
6 bb2-atm-P2-0.atdn.net (66.185.152.186) 21.985 ms 25.608 ms 22.105 ms
7 pop1-atm-P4-0.atdn.net (66.185.150.1) 23.291 ms 21.392 ms 22.416 ms
8 so-5-2-0.mpr1.atl6.us.above.net (209.249.119.241) 22.099 ms 22.169 ms 22.572 ms
9 so-3-1-0.mpr2.iah1.us.above.net (64.125.29.62) 35.926 ms 36.738 ms 36.290 ms
10 so0-0-0.mpr3.iah1.us.above.net (64.125.26.13) 36.814 ms 36.685 ms 35.698 ms
11 so-5-1-0.mpr2.lax9.us.above.net (64.125.29.97) 72.570 ms 72.212 ms 72.789 ms
12 utorrent.com (72.20.34.145) 76.923 ms 77.075 ms 77.422 ms
Trace complete

Anyone have any clue as to what's wrong or what I should be checking?

 

[spidey07]

Could very well be your ISP blocking those ports, especially if it is torrent traffic.

 

[mrSHEiK124]

Originally posted by: spidey07
Could very well be your ISP blocking those ports, especially if it is torrent traffic.

Why would they block remote desktop too?

 

[spidey07]

Originally posted by: mrSHEiK124

Originally posted by: spidey07
Could very well be your ISP blocking those ports, especially if it is torrent traffic.

Why would they block remote desktop too?

In your terms of service you probably see something about not running servers. That is a server. Wouldn't hurt to just call them and find out to eliminate that which is beyond your control

 

[kevnich2]

Just out of curiousity OP, what city do you live in? If you don't want to disclose, send me a PM. It looks like your in the same city I am which tells me your using Road Runner through Bright House? Just from personal experience, Road Runner in this area doesn't block any ports. I can run remote desktop, web server, etc without any problems. Unless RR is blocking these ports only on specific MAC addresses for users, which is very possible if they see alot of traffic coming from you.

 

[mrSHEiK124]

Originally posted by: kevnich2
Just out of curiousity OP, what city do you live in? If you don't want to disclose, send me a PM. It looks like your in the same city I am which tells me your using Road Runner through Bright House? Just from personal experience, Road Runner in this area doesn't block any ports. I can run remote desktop, web server, etc without any problems. Unless RR is blocking these ports only on specific MAC addresses for users, which is very possible if they see alot of traffic coming from you.

Yep, I'm in Tampa using RR through BHN. I know RR doesn't block any ports; they never have, and if anything traffic on my connection has decreased significantly over the last couple of months because I'm more tied up with school now. I think the issue may be related to my router somehow, I'm going to try connecting directly through my modem tomorrow.

 

[RebateMonger]

Try running "Shields Up!" on http://grc.com. First, try scanning all your ports up to 1024 and see the results. Then you can try some higher ranges if you wish. That'll give you a better idea if EVERYTHING is being blocked, or if it's something your ISP is doing.

 

[mrSHEiK124]

Originally posted by: RebateMonger
Try running "Shields Up!" on http://grc.com. First, try scanning all your ports up to 1024 and see the results. Then you can try some higher ranges if you wish. That'll give you a better idea if EVERYTHING is being blocked, or if it's something your ISP is doing.

Thanks! That's a very beneficial tool.

GRC Port Authority Report created on UTC: 2007-03-30 at 00:16:04

Results from scan of ports: 0-1055

0 Ports Open
0 Ports Closed
1056 Ports Stealth
---------------------
1056 Ports Tested

ALL PORTS tested were found to be: STEALTH.

TruStealth: FAILED - ALL tested ports were STEALTH,
- NO unsolicited packets were received,
- A PING REPLY (ICMP Echo) WAS RECEIVED.

I'm guessing that's not good?

 

[mrSHEiK124]

Fvck. I feel retarded now. I was looking through my router settings and noticed that traffic from ALL PORTS was being forwarded to 192.168.1.124 (which is unused) and labeled Wii; why, I don't know. Apparently it overrides DMZ settings and was keeping the DMZ of 192.168.1.100 (me) from working. Sorry!!!

 

[kevnich2]

Just so you know, having your PC in the DMZ isn't a smart idea security wise? The best thing (obviously aside from not forwarding any ports) is to only forward the ports you need. If you only need RDP (remote desktop), only forward port 3389 to that specific IP. It'll keep the security in check.