Last Active: Apr 16, 2024
Threads: 24
Posts: 83
Reputation:
2
Hello,
I cannot get my Windows 10 system to seed a torrent. I tried everything I could to use port forwarding, but no luck. "Simple Port Forwarding" did nothing for me. Hopefully someone can help. Here's my stats:
Windows 10 64 bit
NordVPN (seeding does not work with this on or off)
Windows Defender AV/Firewall
uTorrent 2.0 (I like an older version without all the bloatware crap)
Netgear Wi-Fi repeater box
XFinity modem
Last Active: Yesterday
Threads: 135
Posts: 3,416
Reputation:
16
Oct 14, 2019, 20:12 pm
(This post was last modified: Oct 14, 2019, 20:22 pm by RodneyYouPlonker.)
Well firstly, seeing that nobody else wants to offer any help on this...
I want to say that it has happened to me before. It's not really anything to do with Windows 10 because it's the same in Windows 7. It is most likely a lot of your equipment has been left switched on too long. To solve these problems turn the whole lot off, leave it off a while, put it all back on again and see if it works.
If it still doesn't work then it could be a config problem. I have found myself that if you don't keep turning your equipment off and back on again and resetting things then things like seeding don't work anymore. All kinds of things like whether it's a home computer, your home router or a server somewhere like a seedbox. They all need to be restarted after a while even if you're using Linux. You can upload and download for a while but it comes to the point where eventually you've just gotta restart your programs and turn off and on again your hardware otherwise these kinds of issues will occur.
Depending on the kind of broadband you have could have lots of different factors that relate to this. Without lots of information about what kind of setup you have it's hard to pin point the exact cause but usually it is something simple like just restart all your gear. Config problems are things we have to understand these days to get to where we are going. Not always easy if you've learned things in the past could be easier to fix.
We're all different and work in different ways.
If you want me to be honest about uTorrent, I think running the very latest version is fine as long as you know what you're doing. I've been using the latest uTorrents now for years and it's been great and it's worked really well there's just a few things you need to know about the program really and make sure you fix these problems.
I used to do Port Forwarding quite a while ago but have since found other ways to avoid it. Now I don't even bother with forwarding anymore because I changed a lot of things. I can't go into too many details with you but really I couldn't myself put up with using one of those old uTorrent versions. I have had nothing but total success with all recent ones and just takes a bit of messing around with. Also with things like anti virus and anti malware programs it's knowing how to go about making sure that these things don't end up trying to block programs like uTorrent because if they can they will. Anything these days to do with Torrents those people out there don't like and want to annoy us all the time with false positives. It is just something I've gotten used to over the last few years now...
Could it be that if you are making these torrents yourself that you are seeding? Could it be that you're not putting correct Announces in so that there's nothing for it to connect to? Without at least putting in 2 or 3 it could be related to the fact that it can't even see the torrent because it's not linked through an announce address..
Last Active: Apr 16, 2024
Threads: 24
Posts: 83
Reputation:
2
I turn my PC off every night, but I will try the off and on advice for my wi-fi repeater and modem. The torrents are not my own. I used to share a lot, but not anymore. As far as uTorrent, unless it is absolutely necessary, I don't want the latest version. It is ridiculous with ads and crap. If you can PM any guidance to avoid port forwarding, I would be grateful.
Last Active: Oct 03, 2024
Threads: 67
Posts: 6,379
You can't avoid port forwarding. You are either forwarding a port and can accept incoming connections, or you are unreachable and can only connect to others in the swarm who are able to accept connections.
Last Active: Yesterday
Threads: 135
Posts: 3,416
Reputation:
16
One suggestion, just seed from a seedbox instead. Sign up with somebody and get yourself started that way. It's a lot better really and plus you don't have to leave your own computer uploading all the time.
I can't go into the reasons why I don't port forward whether publicly or in private like a private message because I said I'm not willing to share how I do my own set up.
Last Active: Apr 16, 2024
Threads: 24
Posts: 83
Reputation:
2
(Oct 14, 2019, 21:49 pm)Moe Wrote: You can't avoid port forwarding. You are either forwarding a port and can accept incoming connections, or you are unreachable and can only connect to others in the swarm who are able to accept connections.
Technically, my situation could be called "avoiding" port forwarding because it isn't working. That stupid "Simple Port Forwarding" program did NOTHING for me but add more confusion. I can't find my wi-fi repeater on the router list, so I can't use it.
Last Active: Nov 16, 2022
Threads: 44
Posts: 845
Reputation:
12
Since I always use a VPN with torrents I *believe* that all port forwarding is a function of the remote servers. Forwarding is after all, a router function, and with a VPN, their servers are in effect encrypting routers.
This may be different with IPV6. Something I try to kill on Win and Linux.
For the publically spirited, a seedbox would indeed be the best and safest option. Servers designed for the purpose of accepting remote connections.
These folk have my respect and gratitude.
Oddly, with a VPN and two hardware firewalls (neither forwarded) I can do a reasonable amount of seeding. Enough to feel somewhat useful.
Rebooting the machines is especially needed on the Win machines here. The TAP driver seems especially prone to 'clogging' often manifesting by full running torrents, but blockages to web access from the browsers. Restarting them often, but not always helps. Reboot usiually solves the problem for a day or two.
Linux also seems to occasionally clot up its TUN. Especially if the VPN is at full 4MB speed (B, not b). There I often have to terminate OpenVPN gracefully (for it to restore the routung table) and restart. Sometimes a full reboot needed.
I suppose I should try to reboot the routers, but I'd rather not, as its a bit of a bother.
Last Active: Apr 16, 2024
Threads: 24
Posts: 83
Reputation:
2
I just want to be able to share, like I have always done. This is ridiculous.
Last Active: Oct 03, 2024
Threads: 67
Posts: 6,379
Port forwarding is a part of NAT, and as NAT doesn't exist in the IPv6 world, isn't a thing.
Port forwarding is only necessary when on a private network masquerading behind a public IP address. If you are using a seedbox or your computer is directly connected to the internet, it is not necessary, though in both cases there may or may not be a firewall that has to be open to TCP and UDP traffic on your listening port.
If you are using a VPN, the service may or may not offer the ability to forward one or more ports.
Having the ability to accept incoming connections is not a necessity. It just allows you access to the entire swarm rather than just those who can accept an incoming connection.
It may even have nothing to do with this conversation. If OP can join swarms to download, then OP can seed. It may just be a few specific torrents that don't work.
If nothing works, it is likely a networking issues that needs to be sorted out.
There are many missing details.
Last Active: Yesterday
Threads: 135
Posts: 3,416
Reputation:
16
OP - Not really into Wifi much myself, much prefer Wired connections instead. In your setup where is your router and why haven't you mentioned one? You can't expect to port forward if there's no router present?
|
