Re: Azureus BitTorrent client - firewall problems



seale.j@xxxxxxxxx wrote:

For some odd reason, I can't get any ports to work with Azureus, Its
NAT/Firewall tester always reads 'NAT Error' every tme I give it a port
to test. I even tried putting my router in the DMZ and still got nada.
Is there something I need to do with AppArmor to make this work or do I
need to start playing with the network services in YaST now?

This is what I do:

In Azureus' PlugIns menu under UPnP check "Enable UPnP" and "Release
mappings on closedown."

In your router setup options enable UPnP and any other option that states
"Enable configuration changes through UPnP."

In YAST / Security and Users / Firewall / Allowed Services / Advanced add
the TCP port you would like to use, I use 49194, and give it a name in the
"IP Protocols" slot such as "Az".

This assumes your router supports UPnP, if your router does not then see if
a firmware upgrade is available for your router.



.



Relevant Pages

  • Re: Messenger SP2 Voice Chat
    ... >> your router firmware and enable UPnP. ... >> You will notice to things after you have enabled UPnP ... >> Nat information found in Advanced Connection ... and found "enable UPnP" checkbox under Administration of the router setup. ...
    (microsoft.public.windowsxp.messenger)
  • Re: Upnp vs no Upnp Router
    ... Best practice is not to allow Upnp to be used. ... Certainly in most cases port ... If I let windows use Upnp on the router, the RWW works perfectly, but It ...
    (microsoft.public.windows.server.sbs)
  • Re: NAT firewall and Messenger
    ... Agree with Mike. ... services to automatically program a 'path' through the router. ... information from the internet port and translates it to the local PC ... So if you dont have UPnP, you may need to enter the details manually. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Should server be accessible through Remote Desktop from outside la
    ... I realized it by chance when I forgot to connect to the VPN before I started RDC to our server. ... If you definitely mean RDC, then that's port 3389, which really shouldn't be open. ... The router will currently be forwarding it, and should be told to stop. ... Whoever configured the system didn't have a really good reason to open 3389, and it's possible the router was configured by the SBS CEICW wizard using uPnP. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop
    ... UPnP simplifies port forwarding as it won't require any user action to ... >>Forward TCP Port 3389 through the router to the private LAN IP of the desktop PC. ...
    (microsoft.public.windowsxp.work_remotely)