jg210007 Posted March 5, 2007 Report Share Posted March 5, 2007 First, let me say....my utorrent works flawlessly, very fast, no problems. The only reason I bring this up here is because it started after I began using utorren and seems to be related. Some posts here touch on traffic coming in after closing utorrent and explain exactly what is causing it. My problem differs slightly.I have an SMC7004VBR wired router with only the utorrent port forwared.I also have ZoneAlarm Pro installed on my PC which is reporting incoming traffic as such (just shortly after running utorrent):-multiple IPs incoming on a port not setup for use with utorrent-the port will change after a dozen or so attempts-some IPs occasionally attempt connections on different portsQuestions:1- Is this normal, and if so, how can i capture those lost comms? Near as I can tell, incoming should ONLY be on the designated port.2- The instructions mention only TCP/IP for port forwarding, but I usually get some hits on that UDP port. Should it also be forwarded?Much appreciated. Link to comment Share on other sites More sharing options...
jg210007 Posted March 5, 2007 Author Report Share Posted March 5, 2007 Here's an example in case my post was not completely clear...these are not ports set to receive traffic from utorrent, and came in a few seconds apart:222.129.75.191:52864,192.168.2.x:1620,UDP86.218.231.69:1273,192.168.2.x:1620,TCP (flags:S)199.120.124.189:27473,192.168.2.x:1620,TCP (flags:S)87.74.22.161:2844,192.168.2.x:1620,TCP (flags:S)125.228.86.168:11977,192.168.2.x:1620,UDP219.91.0.103:13977,192.168.2.x:1620,UDP70.121.182.142:32828,192.168.2.x:1620,UDP87.74.22.161:2927,192.168.2.x:1620,TCP (flags:S)121.35.5.226:55256,192.168.2.x:4665,UDP199.120.124.189:27620,192.168.2.x:1620,TCP (flags:S)221.202.108.159:22757,192.168.2.x:1620,UDP155.53.0.252:10621,192.168.2.x:4665,UDP87.74.22.161:3020,192.168.2.x:1620,TCP (flags:S)87.74.22.161:3136,192.168.2.x:1620,TCP (flags:S) Link to comment Share on other sites More sharing options...
Firon Posted March 5, 2007 Report Share Posted March 5, 2007 The UDP port should be forwarded if you use DHT.ANyway, there's nothing you can do about it. Just ignore your firewall logs. Link to comment Share on other sites More sharing options...
jg210007 Posted March 5, 2007 Author Report Share Posted March 5, 2007 Firon,Thanks for your answer on UDP port forwarding.However, I find it deeply troubling that outside addresses are trying to access my internal PC address, bypassing my router (or so it seems.) Can you point me in the right direction? Why would this have started with my use of utorrent? Thx. Link to comment Share on other sites More sharing options...
Firon Posted March 5, 2007 Report Share Posted March 5, 2007 Your router rewrites the IP address so it looks like it's internal. Link to comment Share on other sites More sharing options...
Switeck Posted March 5, 2007 Report Share Posted March 5, 2007 If you've EVER used those ports in the past, traffic can continue incoming for days/weeks on end. There are some REALLY STUPID BitTorrent clients out there that don't know when to quit!(...and no, I don't think it's BitComet.)It's quite likely that whatever is doing that is NOT µTorrent and is NOT following BitTorrent protocol specifications. So it is really beyond anything you, we, or µTorrent designers do to correct it. It can only be blocked by your firewall/router...and best ignored. Link to comment Share on other sites More sharing options...
5parky Posted March 5, 2007 Report Share Posted March 5, 2007 your log shows all UDP connections coming in on port 4665 and all TCP connections comming in on port 1620I think youre confusing the remote outbound ports with your local incoming ports Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.