Bad port forwarding, probablybut I'm not fucking with it, as it's connecting, which is good enough for me. We're using wifi, and we're the kind of technosavages that don't entirely know how we got it to work in the first place, so we're not going to change ANYTHING.
(
Captain Wow currently being a cunt in Infamous,
Thu 30 Oct 2008, 11:24,
archived)
If all your torrents get poor speeds then it'll be a port forwarding issue, which is easy enough to fix.If it's just the odd torrent then it'll be poor seeding.
(
Ttssattsr,
Thu 30 Oct 2008, 11:26,
archived)
Well, if you know the name of your router, then tap it into www.portforward.com and it'll tell you what to do.But it's basically just a matter of allowing the correct ports to be open to traffic. Tap in your internal IP into your browser (192.168.0.1 - usually. Tap in ipconfig into cmd to find out what it is). Then you just have to navigate the menu to allow certain TCP traffic through the correct ports (which you can set in your torrent client).
( Ttssattsr,
Thu 30 Oct 2008, 11:29,
archived)
I have no clue what you just said. Captain Wow currently being a cunt in Infamous,
Thu 30 Oct 2008, 11:31,
archived)
Poor blossom. Take the easy, step by step guide on www.portforward.com. Ttssattsr,
Thu 30 Oct 2008, 11:34,
archived)
Thanks dollface. Captain Wow currently being a cunt in Infamous,
Thu 30 Oct 2008, 11:35,
archived)
