pleekmo
Triptoe Through The Tulips
Premium
join:2001-09-14
Manchester, CT
clubs:
| reply to mercury26
Re: Problems with DGL-4300
If you are using Windows XP you ought to be able to activate uPnP on the router and Azureus ought to pass the port test. You may wish to see if you have XPs uPnP service activated. (Start -> Administrative Tools -> Services -> Universal Plug and Play Device Host (service show as "started"). Also notice that this service depends upon the HTTP and the SSDP Discovery Services (both should be "started".)
If you have uPnP enabled and these three services activated you probably do not have to have any ports manually opened for BitTorrent (that is, entries for BitTorrent in any of the Gaming or Special Applications, etc., sections). I only have uPnP enabled and no manual entries for BitTorrent ports opened -- the router opens them for me. I am using the default BT ports.
This is how I have my own DGL-4100 (the wired-only version of this device) set up and I use Azureus extensively and it passes the port test here. I suppose I ought to mention that I have a BitTornado client uploading a Disco Biscuits show on one of my other computers with uPnP enabled for it as well and it also works fine.
I do not have DMZ enabled at all. In most cases, DMZ enabling will work for only one of the computers on your network (irrelevant, of course, if your network consists of only one computer). Because DMZ is enabled, any port rules you have created have been bypassed. This is, after all the purpose of DMZ: to bypass the router's NAT, if needed. I would suggest disabling DMZ. |
|
mercury26
join:2005-09-19
Broomfield, CO
| So I removed all of the DMZ and SPI settings, and then verified UPnP was activated in Windows. I then rebooted XP and restarted Azureus, but I am still getting a NAT error in the Azureus tool. I get the typical start up messages with Azureus that tell me that UPnp has successfully established ports, but I also get the following errors. Any further ideas? Maybe I need to reset my Azureus settings to factory default? Any more help would be appreciated.
Error:
Failed to establish listen on port 6969.
Check that other applications aren't already using this port.
Also check for another copy of Azureus running.
Error while processing advanced socket options.
Cannot assign requested address: bind
Error:
Failed to establish listen on port UDP:6881.
Check that other applications aren't already using this port.
Also check for another copy of Azureus running. |
|
pleekmo
Triptoe Through The Tulips
Premium
join:2001-09-14
Manchester, CT
clubs:
| said by mercury26  :Error: Failed to establish listen on port 6969. Check that other applications aren't already using this port. Also check for another copy of Azureus running. Error: Failed to establish listen on port UDP:6881. Check that other applications aren't already using this port. Also check for another copy of Azureus running. I'd had similar errors when I'd used an old NetworkEverywhere router which could supposedly implement uPnP, but I seemed able to connect to servers, torrents, and trackers just fine. My suspicion was that Azureus was attempting to open the ports before the router was ready to handle it. You may wish to open Azureus and click in the menu bar Plugins -> uPnP and view the messages there.
Here's mine, for instance (with suitable removals):
Status:Running
UPnP::SSDP: ignoring loopback address /127.0.0.1
UPnP::SSDP: ignoring loopback address /0:0:0:0:0:0:0:1
UPnP::SSDP: ignoring IPv6 address /xxx:0:0:0:0:0:0:1%1
UPnP::SSDP: group = /xxx.255.255.250:0/eth0:Intel(R) PRO/1000 MT Network Connection-/xxx.xxx.xxx.xxx,/xxx:xxx:xxx:xxx:xxx:xxx:xxx:xxx%4
UPnP::SSDP: ignoring IPv6 address /xxx:xxx:xxx:xxx:xxx:xxx:xxx:xxx%4
UPnP::SSDP: ignoring IPv6 address /xxx:xxx:xxx:xxx:xxx:xxx:xxx:xxx
UPnP::SSDP: ignoring IPv6 address /xxx:xxx:xxx:xxx:xxx:xxx:xxx:xxx%6
UPnP::SSDP: ignoring IPv6 address /xxx:xxx:xxx:xxx:xxx:xxx:xxx:xxx%2
Mapping request: UDP tracker client port (UDP/6881), enabled = true
Mapping request: Incoming Peer Data Port (TCP/6881), enabled = true
Mapping request: TCP Tracker Port (TCP/6969), enabled = true
Mapping request: TCP SSL Tracker Port (TCP/7000), enabled = false
Mapping request: UDP Tracker Port (UDP/6969), enabled = false
Mapping request: Distributed DB (UDP/6881), enabled = true
UPnP:SSDP: first response:
HTTP/1.1 200 OK
EXT:
SERVER: ipOS/6.4, UPnP/1.0, ipSSDPDevice/1.0
ST: upnp:rootdevice
LOCATION: »xxx.xxx.xxx.xxx/getxml?file=/root.xml
CACHE-CONTROL: max-age=1800
USN: uuid: [removed]::upnp:rootdevice
Content-Length: 0
UPnP: root discovered = »xxx.xxx.xxx.xxx/getxml?file=/root.xml, local = /xxx.xxx.xxx.xxx
Downloading: »xxx.xxx.xxx.xxx/getxml?file=/root.xml
Relative URL base is »xxx.xxx.xxx.xxx
GamerLounge DGL-4300 Wireless 108G Gaming Router
»xxx.xxx.xxx.xxx/getxml?file=/l3fw.xml, »xxx.xxx.xxx.xxx:4444/l3fw
WANDevice
»xxx.xxx.xxx.xxx/getxml?file=/WAN···IFC1.xml, »xxx.xxx.xxx.xxx:4444/wcommifc
WANConnectionDevice *
»xxx.xxx.xxx.xxx/getxml?file=/WANIPConn1.xml, »xxx.xxx.xxx.xxx:4444/wipconn
Found WANConnectionDevice
Found WANIPConnection
Downloading: »xxx.xxx.xxx.xxx/getxml?file=/WANIPConn1.xml
mapping [0] 53444/UDP [svchost (xxx.xxx.xxx.xxx:1041) 53444 UDP] -> xxx.xxx.xxx.xxx
mapping [1] 6892/TCP [BT-z-Fq] -> xxx.xxx.xxx.yyy
mapping [2] 36816/UDP [svchost (xxx.xxx.xxx.yyy:4183) 36816 UDP] -> xxx.xxx.xxx.yyy
mapping [3] 6893/TCP [BT-LYuw] -> xxx.xxx.xxx.yyy
mapping [4] 6895/TCP [BT-FthO] -> xxx.xxx.xxx.yyy
UPnP: Mapping 'UDP tracker client port (UDP/6881)' established
UPnP: Mapping 'Incoming Peer Data Port (TCP/6881)' established
UPnP: Mapping 'TCP Tracker Port (TCP/6969)' established
Mapping Distributed DB (UDP/6881) already established
with a well-working connection. |
|
mercury26
join:2005-09-19
Broomfield, CO
| Ok, here are the results for my UPnP Log. Does ths help at all? I am still having NAT Issues.
Also, does anyone know how to completely reset the Azureus settings. A complete uninstall did not work, nor clearing the registry. Where are the settings kept at?
Thanks,
Chuck
UPnP::SSDP: ignoring loopback address /127.0.0.1
UPnP::SSDP: group = /239.255.255.250:0/eth1:Belkin Gigabit Desktop Card - Packet Scheduler Miniport-/192.168.0.142
Mapping request: UDP tracker client port (UDP/6881), enabled = true
Mapping request: Incoming Peer Data Port (TCP/6881), enabled = true
Mapping request: TCP Tracker Port (TCP/6969), enabled = true
Mapping request: TCP SSL Tracker Port (TCP/7000), enabled = false
Mapping request: UDP Tracker Port (UDP/6969), enabled = true
Mapping request: Distributed DB (UDP/6881), enabled = true
UPnP:SSDP: first response:
HTTP/1.1 200 OK
EXT:
SERVER: ipOS/6.4, UPnP/1.0, ipSSDPDevice/1.0
ST: upnp:rootdevice
LOCATION: »192.168.0.1/getxml?file=/root.xml
CACHE-CONTROL: max-age=1800
USN: uuid:83EA8F24-BE12-3E7C-87CE-181927911B83::upnp:rootdevice
Content-Length: 0
UPnP: root discovered = »192.168.0.1/getxml?file=/root.xml, local = /192.168.0.142
Downloading: »192.168.0.1/getxml?file=/root.xml
Relative URL base is »192.168.0.1
GamerLounge DGL-4300 Wireless 108G Gaming Router
»192.168.0.1/getxml?file=/l3fw.xml, »192.168.0.1:4444/l3fw
WANDevice
»192.168.0.1/getxml?file=/WANCommonIFC1.xml, »192.168.0.1:4444/wcommifc
WANConnectionDevice *
»192.168.0.1/getxml?file=/WANIPConn1.xml, »192.168.0.1:4444/wipconn
Found WANConnectionDevice
Found WANIPConnection
Downloading: »192.168.0.1/getxml?file=/WANIPConn1.xml
mapping [0] 21/TCP [FTP] -> 192.168.0.142
mapping [1] 3389/TCP [REMOTE DESKTOP] -> 192.168.0.142
UPnP: Mapping 'UDP tracker client port (UDP/6881)' established
UPnP: Mapping 'UDP tracker client port (UDP/6881)' established
UPnP: Mapping 'Incoming Peer Data Port (TCP/6881)' established
UPnP: Mapping 'Incoming Peer Data Port (TCP/6881)' established
UPnP: Mapping 'TCP Tracker Port (TCP/6969)' established
UPnP: Mapping 'TCP Tracker Port (TCP/6969)' established
UPnP: Mapping 'UDP Tracker Port (UDP/6969)' established
UPnP: Mapping 'UDP Tracker Port (UDP/6969)' established
Mapping Distributed DB (UDP/6881) already established
UPnP: reset
UPnP: Lost connection to service 'WANIPConnection' on UPnP device '192.168.0.1'
UPnP: root discovered = »192.168.0.1/getxml?file=/root.xml, local = /192.168.0.142
Downloading: »192.168.0.1/getxml?file=/root.xml
Relative URL base is »192.168.0.1
GamerLounge DGL-4300 Wireless 108G Gaming Router
»192.168.0.1/getxml?file=/l3fw.xml, »192.168.0.1:4444/l3fw
WANDevice
»192.168.0.1/getxml?file=/WANCommonIFC1.xml, »192.168.0.1:4444/wcommifc
WANConnectionDevice *
»192.168.0.1/getxml?file=/WANIPConn1.xml, »192.168.0.1:4444/wipconn
Found WANConnectionDevice
Found WANIPConnection
Downloading: »192.168.0.1/getxml?file=/WANIPConn1.xml
mapping [0] 6881/UDP [Azureus UPnP 6881 UDP] -> 192.168.0.142
mapping [1] 6881/TCP [Azureus UPnP 6881 TCP] -> 192.168.0.142
mapping [2] 6969/TCP [Azureus UPnP 6969 TCP] -> 192.168.0.142
mapping [3] 6969/UDP [Azureus UPnP 6969 UDP] -> 192.168.0.142
mapping [4] 21/TCP [FTP] -> 192.168.0.142
mapping [5] 3389/TCP [REMOTE DESKTOP] -> 192.168.0.142
Mapping UDP tracker client port (UDP/6881) already established
Mapping Incoming Peer Data Port (TCP/6881) already established
Mapping TCP Tracker Port (TCP/6969) already established
Mapping UDP Tracker Port (UDP/6969) already established |
|
pleekmo
Triptoe Through The Tulips
Premium
join:2001-09-14
Manchester, CT
clubs:
1 edit | This looks good except for this brief item:
UPnP: reset
UPnP: Lost connection to service 'WANIPConnection' on UPnP device '192.168.0.1'
You may wish to attempt to determine what caused this, though it appears that he uPnP connection was re-established.
I think you will have to learn to ignore the error messages.
Edit: Stupid proofreading lapse. |
|
mercury26
join:2005-09-19
Broomfield, CO | I am not worried about the error messages. I am worried about the NAT Error message in the NAT Testing tool. The tracker I am connected to is listing me as non-connectable.
Thanks,
:: Chuck |
|
pleekmo
Triptoe Through The Tulips
Premium
join:2001-09-14
Manchester, CT
clubs: | Perhaps the tracker is using non-standard ports?... |
|
mercury26
join:2005-09-19
Broomfield, CO | Hmmm, I do not believe so, but I will check. It used to work with my Microsoft Wireless router. I only started to experience this issue after I switched to the D-Lnk router.
Thanks,
:: Chuck |
|
