Comcast claims not to be blocking P2P traffic, but Utorrent port checker claims the

  • Thread starter Thread starter Eric K
  • Start date Start date
E

Eric K

Guest
port is not forwarded.? Utorrent port checker reports the following:

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

Checking port 14213 on 68.33.196.38...

Error! Port 14213 does not appear to be open.
----------------------------------------------------
However, 68.33.196.38 is comcast - not me.
c-68.33.196.38.hsd1.md.comcast.net [68.33.196.38]
My ip address is 192.168.1.100, and I have the windows firewall off & my router has port 14213 forwarded

Nothing has changed on my end - and this setup has worked for over a year. Either Comcast is blocking this port (or Utorrent in general) or the utorrent port forwarder is acting funky. Normally, it checks your own router to see if it can get in.

Actually - I can download - but I'm trying to seed. It was OK at first, but then all connections dropped & it said maybe my port wasn't forwarded.
So now, I have a peer & am uploading - but utorrent port checker still reports that it doesn't think my port is open - but it's still looking at comcast's ip - not mine. Strange
I just figured it out. I use DHCP & have been turning the PC's off lately, since I was away. Port forwarding is to a specific pc - and the IP had changed, so .102 was invalid. I changed it to match what I was served up (.100) and it worked. None of the settings had changed - but they needed to, since my ip address changed through DHCP. Normally, I leave it up all the time, so it always has the same one.
 
Back
Top