Just got a new Belkin N+ F5D8235-4 router with my MacBook Pro 17, OS 10.8.2. Transmission 2.75 (13665).
UPnP is enabled, automatically map port is on, port forwarding and static IP address is set up in router and laptop. But my port, 60410, still shows as closed in the network preference pane. But in the log, it says the port is forwarded:
2012-12-28 08:52:45 +0000 port-forwarding.c:181 [Info] Port Forwarding: Stopped
2012-12-28 08:52:45 +0000 upnp.c:245 [Info] Port Forwarding (UPnP): Stopping port forwarding through "http://192.168.2.1:5432/upnp/control/WANIPConnection1", service "urn:schemas-upnp-org:service:WANIPConnection:1"
2012-12-28 08:52:45 +0000 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Forwarded" to "Not forwarded"
2012-12-28 08:53:03 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2012-12-28 08:53:03 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2012-12-28 08:53:03 +0000 upnp.c:104 [Debug] Port Forwarding (UPnP): upnpDiscover failed (errno 0 - Undefined error: 0)
2012-12-28 08:53:03 +0000 upnp.c:202 [Info] Port Forwarding (UPnP): Found Internet Gateway Device "http://192.168.2.1:5432/upnp/control/WANIPConnection1"
2012-12-28 08:53:03 +0000 upnp.c:204 [Info] Port Forwarding (UPnP): Local Address is "192.168.2.30"
2012-12-28 08:53:03 +0000 upnp.c:279 [Info] Port Forwarding (UPnP): Port forwarding through "http://192.168.2.1:5432/upnp/control/WANIPConnection1", service "urn:schemas-upnp-org:service:WANIPConnection:1". (local address: 192.168.2.30:60410)
2012-12-28 08:53:03 +0000 upnp.c:282 [Info] Port Forwarding (UPnP): Port forwarding successful!
2012-12-28 08:53:03 +0000 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Not forwarded" to "Forwarded"
So, is my port really closed? Or is it open and the Belkin router is confusing Transmission? Or is Transmission buggy? Any help is appreciated!
Is my port really closed?
Re: Is my port really closed?
Same problem with 10.8.2 and Transmission 2.7.5. Just started when upgraded to Mountain Lion
-
- Posts: 35
- Joined: Fri Dec 05, 2008 11:26 pm
Re: Is my port really closed?
I have the same problem, seemingly, but I am on 10.6.8 with a new Airport Extreme set to the same profile as my old Airport Extreme.
As posted in this thread, the log says that the port was successfully opened, but the preferences pane show that the port is closed.
now, if only I could understand the search that x190 suggests.
As posted in this thread, the log says that the port was successfully opened, but the preferences pane show that the port is closed.
now, if only I could understand the search that x190 suggests.
-
- Posts: 4
- Joined: Sat Dec 29, 2012 2:31 am
Re: Is my port really closed?
I'm having the same problem...
2012-12-28 20:18:39 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2012-12-28 20:18:39 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2012-12-28 20:18:39 -0600 upnp.c:214 [Debug] Port Forwarding (UPnP): UPNP_GetValidIGD failed (errno 0 - Unknown error: 0)
2012-12-28 20:18:39 -0600 upnp.c:217 [Debug] Port Forwarding (UPnP): If your router supports UPnP, please make sure UPnP is enabled!
2012-12-28 20:18:39 -0600 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
2012-12-28 20:18:47 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2012-12-28 20:18:47 -0600 natpmp.c:141 [Info] Port Forwarding (NAT-PMP): Found public address "MY PUBLIC IP OMITTED"
2012-12-28 20:18:47 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12)
2012-12-28 20:18:48 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2012-12-28 20:18:48 -0600 natpmp.c:221 [Info] Port Forwarding (NAT-PMP): Port 4654 forwarded successfully
2012-12-28 20:18:48 -0600 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Starting" to "Forwarded"
That's the transcript from the message log, which looks like the port is forwarded correctly. However, it is still saying "Port is closed" in the network tab of my preferences. What's going on?
2012-12-28 20:18:39 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2012-12-28 20:18:39 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2012-12-28 20:18:39 -0600 upnp.c:214 [Debug] Port Forwarding (UPnP): UPNP_GetValidIGD failed (errno 0 - Unknown error: 0)
2012-12-28 20:18:39 -0600 upnp.c:217 [Debug] Port Forwarding (UPnP): If your router supports UPnP, please make sure UPnP is enabled!
2012-12-28 20:18:39 -0600 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
2012-12-28 20:18:47 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2012-12-28 20:18:47 -0600 natpmp.c:141 [Info] Port Forwarding (NAT-PMP): Found public address "MY PUBLIC IP OMITTED"
2012-12-28 20:18:47 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12)
2012-12-28 20:18:48 -0600 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2012-12-28 20:18:48 -0600 natpmp.c:221 [Info] Port Forwarding (NAT-PMP): Port 4654 forwarded successfully
2012-12-28 20:18:48 -0600 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Starting" to "Forwarded"
That's the transcript from the message log, which looks like the port is forwarded correctly. However, it is still saying "Port is closed" in the network tab of my preferences. What's going on?
-
- Posts: 4
- Joined: Sat Dec 29, 2012 2:31 am
Re: Is my port really closed?
When I probe the port at the GRC site, it tells me the status is "STEALTH"...
On canyouseeme.com
Error: I could not see your service on MY IP on port (4654)
Reason: Connection timed out
However, I get the same thing with port 80 and port 21. Is it a firewall issue?
On canyouseeme.com
Error: I could not see your service on MY IP on port (4654)
Reason: Connection timed out
However, I get the same thing with port 80 and port 21. Is it a firewall issue?
-
- Posts: 4
- Joined: Sat Dec 29, 2012 2:31 am
Re: Is my port really closed?
I posted exactly what was in my message log in blue. Yes, 4654 is listed. I don't believe I have a 2nd NAT device... It's just my Motorola Surfboard modem, Apple Airport Extreme router, and my computer. I know my NAT is open because I just played Call of Duty today, and it needs an open NAT for matchmaking. There are no firewall levels to set with the Airport that I can see with Airport Utility.x190 wrote:Check Message Log (Debug). Is 4654 listed? Do you have a second NAT device? Is your router firewall level set appropriately (usually 'Low")?
2012-12-28 19:48:49 -0700 net.c:558 [Debug]Transmission: Bound socket 12 to port 4654 on 0.0.0.0
-
- Posts: 4
- Joined: Sat Dec 29, 2012 2:31 am
Re: Is my port really closed?
I have been using Transmission with this set up for about 3 years now without a problem. I am on version 2.75.
-
- Posts: 35
- Joined: Fri Dec 05, 2008 11:26 pm
Re: Is my port really closed?
Perhaps viewtopic.php?f=4&t=14255 will explain this observation.