Originally posted by: trip42
Yeah, I haven't had a chance to take a look at this yet. Maybe tonight. Router just might need a swift boot to the head. Hopefully I'll get a chance to fix it soon.
Originally posted by: Darth Mallwalker
trip42 is currently closed so you can't connect to him (seeder's prerogative), but if you wait patiently his client should connect to you eventually.
trip42 is currently closed so you can't connect to him (seeder's prerogative), but if you wait patiently his client should connect to you eventually.
Yeah, I haven't had a chance to take a look at this yet. Maybe tonight. Router just might need a swift boot to the head. Hopefully I'll get a chance to fix it soon.
Two things that threw me off that you may also have wrong -
- I had to restart my torrent program for it (and MySpleen) to read the port as open.
- I had to make sure that my actual computer on the network was selected for the open port profile (torrent1). My firewall had defaulted to its own name (I think - CHX-142 or CVX or something - almost like a droid name) rather than the computer name for the open port profile, so the computer port was still closed.
- PS - my standard "vanilla" BitTorrent works fine.
