*Yawn*... Port closed.

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
mojojojo0
Posts: 5
Joined: Fri Feb 20, 2009 12:27 am

*Yawn*... Port closed.

Post by mojojojo0 »

Sorry to be a crashing bore, but...

Yet another "Port is closed" story. Been through the helpfiles, followed all the instructions about Port Forwarding, but still Transmission tells me it's a no-go. I have a Netgear router, with UpnP enabled, using the nightly build from 19th Feb. (Last night). Checked and unchecked "Automatically map port", and while the Message Log reads 'Port Forwarding successful', the red light tells me otherwise.

Log results:

2009-02-20 17:11:53 +0100 upnp.c:140 [Info] Port Forwarding (UPnP): Stopping port forwarding through "http://192.168.2.1:80/Public_UPNP_C3", service "urn:schemas-upnp-org:service:WANIPConnection:1"
2009-02-20 17:11:53 +0100 port-forwarding.c:101 [Info] Port Forwarding: State changed from "Forwarded" to "Not forwarded"
2009-02-20 17:11:58 +0100 upnp.c:175 [Info] Port Forwarding (UPnP): Port forwarding through "http://192.168.2.1:80/Public_UPNP_C3", service "urn:schemas-upnp-org:service:WANIPConnection:1". (local address: 192.168.2.2:50001)
2009-02-20 17:11:58 +0100 upnp.c:178 [Info] Port Forwarding (UPnP): Port forwarding successful!
2009-02-20 17:11:58 +0100 port-forwarding.c:101 [Info] Port Forwarding: State changed from "Not forwarded" to "Forwarded"

But what I see...
Image

Any other details you need?
Jordan
Transmission Developer
Posts: 2312
Joined: Sat May 26, 2007 3:39 pm
Location: Titania's Room

Re: *Yawn*... Port closed.

Post by Jordan »

Looks like the router is correctly forwarding the port, so my first guess would be that it's a firewall issue -- make sure you've got a hole for that port poked in the firewall(s) on the router and/or your computer.
mojojojo0
Posts: 5
Joined: Fri Feb 20, 2009 12:27 am

Re: *Yawn*... Port closed.

Post by mojojojo0 »

I did... I have the firewall turned off on my Mac.
On a more interesting note, before I started all this fiddling around, I could not browse while downloading. It completely killed Safari and Mail. But Adium was fine. Now, all access is fine.

Except, of course, the file that is burning down the cables at a princely 10.6kb/s through Transmission.

Incidentally, the file I am downloading is DL from 5 of 21 peers, UL 62.8kb/s. And a friend downloaded the same file and was done in one night. I've been at it for a few days and still not yet a quarter way through.
essiw
Posts: 567
Joined: Sat Aug 23, 2008 10:40 am
Location: the Netherlands

Re: *Yawn*... Port closed.

Post by essiw »

mojojojo0 wrote:I did... I have the firewall turned off on my Mac.
On a more interesting note, before I started all this fiddling around, I could not browse while downloading. It completely killed Safari and Mail. But Adium was fine. Now, all access is fine.

Except, of course, the file that is burning down the cables at a princely 10.6kb/s through Transmission.

Incidentally, the file I am downloading is DL from 5 of 21 peers, UL 62.8kb/s. And a friend downloaded the same file and was done in one night. I've been at it for a few days and still not yet a quarter way through.
make sure to cap your upload speed, if your upload speed is to high it cuts of your download speed.
mojojojo0
Posts: 5
Joined: Fri Feb 20, 2009 12:27 am

Re: *Yawn*... Port closed.

Post by mojojojo0 »

Still never got this sorted, by the way.
I even tried downgrading to an earlier version (from back in the days when it worked okay) but to no avail. Still my port is closed.
Post Reply