Vuze Change Your Port and Try Again

To fix a NAT issue, you have to consider multiple factors that can cause information technology. Here'southward a quick outline of what you have to do; for more detailed explanations and instructions accept a look at the next chapter.

Understand what a NAT problem is [edit]

Basically, a Network Address Translation problem is acquired by a router not beingness able to do what it's supposed to; it is not correctly re-directing data it has received from the outside world to a estimator that is connected to it (the one running Vuze in this case).

Tin this folio assistance you to resolve the NAT issue? That entirely depends on several factors. Every computer out there is ready up slightly differently - dissimilar makes/models of modems and/or routers, different software firewalls, different antivirus programs, receiving service from unlike providers - these are all factors that must be considered when attempting to solve a NAT fault. We'll attempt to approach a NAT problem broadly so as to encompass and assistance as many users as possible. Below we'll cover some basic terminology and acronyms earlier yous really give it a shot.

Isp: Net Service Provider
Router: A device that forwards data packets along networks. A router is continued to at least two networks, commonly two LANs (Local Surface area Networks), WANs (Broad Area Network), WLANs (Wireless LAN), or a LAN and its Isp?s network. Routers are located at gateways, the places where 2 or more networks connect. Routers use headers and forwarding tables to determine the best path for forwarding the packets, and they use protocols such as TCP/UDP to communicate with each other and configure the best route betwixt any two hosts.
IP Address: Net Protocol Address. This is a unique string of numbers that identifies a figurer or server on the Net. These numbers are unremarkably shown in groups separated past periods (example: 216.239.57.99 is Google's IP accost).
- Public IP Address: An address that is given to you by your service provider when you connect to them. The majority of users have a dynamic public IP accost (this tin change every time a connection is established).
- Private IP Accost: An address that can be assigned past a router or your Operating System for your connexion to a LAN, WAN, or WLAN. The world will never run into this address and can be made static (this will never change once ready correctly).
DHCP: Dynamic Host Configuration Protocol. Used for assigning dynamic IP addresses to devices on a network. With dynamic addressing, a device can have a different IP address every time it connects to the network. DHCP also supports a mix of static and dynamic IP addresses.
- DHCP Pool/Range: The available addresses a router is instructed to employ when automatically assigning IP addresses to devices. Case: LinkSys routers almost all default with a starting IP address of 192.168.ane.100 with fifty available users, effectively making the range 192.168.one.100 - 192.168.i.149
MAC Accost: Media Admission Command Accost (sometimes referred to as a device's physical address). MAC addresses are a unique code assigned to most forms of networking hardware (for example: A0:99:E3:76:BE:01). The address is permanently assigned to the hardware (network cards/wireless adapters/routers) to act equally a security characteristic for limiting access on closed networks. This is extremely useful when securing a wireless network.
- MAC Address Binding: An option on some routers to bind a MAC address to an IP address on a closed LAN or WAN network. When available, this method tin can be used to create a static IP accost for port forwarding purposes.
UPnP: Universal Plug 'north Play. A technological stab at attempting to make networking devices a uncomplicated task. This has been met by mixed reviews and levels of effectiveness by manufacturers and consumers. Your network hardware and Operating System may or may not properly employ this applied science.
Port Forwarding: The act of forwarding a network port from one machine to another. One utilize of this technique can allow an external user to achieve a port on a private IP address (within a LAN) from the outside via a NAT-enabled router.
Port Triggering: This allows computers behind a NAT-enabled router access to a special server or use a special application on the Internet using a specified port number. While like to port forwarding, it is not recommended for usage with bittorrents due to the timing discrepencies involved with a port constantly being told to open with so many connections existence generated. It has more than functions for gaming servers.
DMZ: The De-Militarized Zone. When this pick is enabled in a router, the figurer is at present outside of the internal/protected network. Since a DMZ'd figurer will be open to allow public access to services, it is considered extremely insecure and unsafe. Do NOT use DMZ in lieu of port forwarding.

Ready your NAT problem [edit]

Then you really have a NAT trouble and never get dark-green smilies and you are not using 1 of those Net service providers that do not like file sharing? OK, read on.

Please Note: If you are using file sharing where you take no access to the router (corporate or campus network, public WLAN from a cyber-cafe or a neighbor, or a housing development where everyone shares the connexion), you lot must contact the network ambassador.

You lot desire to select a port that will forward incoming information to your computer'southward IP address using the port of choice, and ensure that software firewalls and antivirus programs do not interfere. If you skimmed the above passages, you lot may be confused by the following procedures. Yous should read the entire folio before proceeding.

If you know you lot ain a router, continue reading this folio in its intended order.

If you own a router and you are absolutely positive it properly supports UPnP, enable UPnP in Vuze (Tools->Options->Plugins->UPnP) and try the nat/firewall exam once more. If this doesn't work, skip downwardly to the Software Firewall section.

If y'all are unsure as to whether or not you own a router (some broadband modems accept routers with NAT features built-in), consult your ISP or see your modems manual.

A uncomplicated test for Windows operating system users is to use ipconfig (win2K/XP) or winipcfg (win9X/ME). Go to Start>Run (or hold the Windows cardinal and hitting "r"), and type in the command "cmd /k ipconfig" or "winipcfg.exe" without the quotes, then printing the Enter key. If the Default Gateway starts with x.*.*.*, 172.*.*.* or 192.*.*.*, so it is very likely that in that location is a router involved.

Apple Mac 8.x/9.x: Pull downwardly the Apple menu, select Control Panels. Open the control panel TCP/IP. Look for the line Router address.
Apple tree Mac Os Ten: use either of the following methods:
- Pull down the Apple carte du jour, select System Preferences, click Network. In the pull-downward Prove: select the network interface in use. Click tab TCP/IP and look for the line Router.
  - Leopard (10.5.x): Apple menu > System Preferences > Network. From list on the left select your connection (Ethernet, AirPort, etc.), which is probably already selected. Click "Advanced" button and from there the TCP/IP tab. The "Router" line will accept an IP accost listed if you lot are connected through a router.
- Open a Terminal window, type the command ipconfig getoption en0 router (where en0 is the name of the interface in use)

If y'all are positive you do not own a router or a broadband modem with NAT features, please skip down to the Software Firewall department.

Routers And NAT Enabled Broadband Modems [edit]

Ensure you are using a port number that is not already reserved by a computer procedure or PC on your network, or that is possibly existence blacklisted/throttled past your Isp. (Avoid 6881-6999. Anything from 49160-65534 is fine)
Create a static IP address for the estimator that is running Vuze.
- Log into your router's configuration table. This is normally done by typing the router's Gateway Address into your browser's URL edit box and pressing the Enter key. You should be prompted for a username/password earlier proceeding. If you don't know the information, consult your owner's transmission or ISP if it originated from them. (Annotation: some devices require utilizing Telnet for access and forwarding; the steps will exist left out here due to their uniqueness. Again, refer to the owner's transmission for the correct procedure).
- If your router supports MAC address bounden, exercise then save/apply your changes, and skip downward to the "Port Forwarding Through The Router" section.
- If your router does non use MAC address binding, disable or limit the DHCP range in the router, then create a static IP address for your computer that is OUTSIDE the router'southward DHCP server's IP puddle/range (example: the DHCP range is 192.168.ane.100 - 192.168.ane.149 .. you would select 192.168.1.200 every bit your new static IP address). Here is a static IP guide for individual Operating Systems. Once this pace completed, your connection to your router will be temporarily broken and then reconnected a few moments later - this is to be expected. At this point, you lot should restart both your router and calculator(s) on your LAN (some routers do not release the previous login and volition interefere with the actual port forwarding stride detailed farther beneath).
  - Once your reckoner and router are restarted, utilise ipconfig or winipcfg to ensure the new static IP accost is being used and continue reading the instructions on this page.

Port Forwarding Through The Router [edit]

At this bespeak yous should now have a static internal/individual IP address for the reckoner that is running Vuze. Log into your router's configuration table then that we may actually port forward. Depending on the device'south manufacturer and the model itself, the "identify" where y'all exercise the forwarding will differ: NAT, NATP, Custom Services, and Virtual Server are the well-nigh commonly named sections, though it'due south entirely feasible yours is named something else, but the primal procedure for creating a port forwarding rule is more or less the same and cocky-explanatory.

Y'all may be lucky and find a step-by-step guide for this process at http://www.portforward.com/routers.htm . They take an splendid list of home routers and modems and configuring advice for them. They have a browseable list of routers/modems, from which

you tin can select your router
jump over the advertising page. (In top-right corner: Click here to skip this advertizing...)
arrive to the application page, where Vuze is listed (and besides 'Azureus', the onetime name for Vuze)
select Vuze there and follow the communication nearly configuring your router.

Typically a forwarding dominion for a router contains at least these elements:

The Rule volition demand a unique Service Name or a Number to place information technology.
The Dominion will need to know what port number to have forwarded to it.
- If the option asks for a range, merely input the same number for From and To (example: From: 56912 To: 56912).
The Rule will need to know which protocol to use for that port. Use both TCP and UDP.
- Vuze requires the TCP protocol for "regular" incoming data transmissions.
- Vuze (ii.3.0.0 and newer) requires the UDP protocol to be enabled for DHT to part properly.
  - If the router does not ask for one protocol or the other, it should be safe to presume it defaults to using both.
  - If the router just allows you to choose one protocol or the other, and then y'all will need to create two rules for that port (apply a different Service Proper noun or Number), one for each protocol.
- The Dominion volition need to know which IP accost to forward to. You will, of course, use the static IP address y'all have already assigned yourself.
The Rule volition need to be enabled, then saved/practical.

Instance:

Port forwarding with two routers [edit]

If you lot take both a smart NATting modem and a NATting router/basestation, or ii NAT routers, you lot may need to configure port forwarding in both of them.

You need to set port forwarding at each router all the way from "public internet" upto your PC, always setting the forward to the next device inwards (from smart modem to router, and from router to PC). Meet an caption here: http://world wide web.portforward.com/assistance/doublerouterportforwarding.htm

If you have non port forwarded from your modem to your router, it will exist pointless to port forward from the router to your calculator as the TCP traffic from Vuze will never fifty-fifty arrive past the modem to the router.

A clear sign of the need for double router port forwarding is if your router has a individual IP address too on its WAN/ADSL/internet side (whatever information technology is chosen in router condition/config screens). "Individual" IP address ranges are x.x.10.x, 172.x.x.x and 192.168.x.x, and IP addresses inside those areas are different from other addresses, as they can not be reached from outside without port forwarding.

Port Forwarding through Windows XP Internet Connection Sharing [edit]

Is your Vuze client running on a computer backside Windows XP ICS? ICS is a bad excuse for a router in quite a lot of means but it can be configured to forwards services (read: ports) to other machines in the local network.

To practice it:

On the ICS calculator, open Control Console|Network Connections.
Right click on your Cyberspace Connection (eg, Local Area Connection X - that accommodates your dial-up/broadband modem connection) and click Properties.
In the "Local Surface area Connection X Properties" dialog, become to the Advanced tab.
Now click the Settings... push button in the Internet Connexion Sharing grouping.
You get the Advanced Settings dialog and a list of services.
Click the Add together... push button to display the Service Settings dialog.
For "Description of service:", type in something to remind you that this is for Vuze' Distributed DB, eg., Vuze DistDB-T.
In the "Proper name or IP address ..." field, type in the local network proper noun of the reckoner that is running Vuze, eg., livingroom.
In the "External Port ..." and "Internal Port ..." fields type in the port number you have configured your Vuze to use (the port number in Vuze' Tools|Options|Connection).
Cull TCP (should be default) and click the Ok push and you are washed. You now accept the DistDB-T service in your Advanced Settings dialog.
You lot need UDP admission to the port also, so yous accept to repeat the in a higher place steps to add a UDP service. Just change the service proper name (eg., Vuze DistDB-U) and call up to cull UDP instead of TCP this time.

You could follow the "Make sure you really have a NAT trouble" advice to check if you've done information technology right, only, actually, the more enjoyable test is looking in "My Torrents" to see your smileys start to turn green as soon as you have airtight the Advanced Settings dialog.

Port Forwarding on Linux, specifically Ubuntu [edit]

Firstly the earlier notes on port forwarding for your router employ as before. Computers running Ubuntu, by default, come with all the ports locked down and you lot need to open the ports in ubuntu by using the iptables control. Other flavours of linux deport similarly

The commands below can exist entered in a root terminal session to open up the ports (TCP and UDP)

iptables -I INPUT -p tcp --dport <your_port_number> -j Have
iptables -I INPUT -p udp --dport <your_port_number> -j ACCEPT

<your_port_number> is the port number you have used for port forwarding (Avoid 6881-6999, whatever from 49125-65535 is fine)

One time yous've established the port is open you need to make the change persist through a reboot; edit file /etc/rc.local and add the lines beneath:

sleep 220 /sbin/iptables -I INPUT -p tcp --dport <your_port_number> -j Have /sbin/iptables -I INPUT -p udp --dport <your_port_number> -j Take

The sleep 220 is at that place to brand the script look a few minutes to let subsequent firewall configuration scripts to run. 220 seconds is a large value and you may cull to configure a lower value. The key is that the opening of the Vuze port is non countermanded past the firewall initialisation which runs later.

Your configuration change will at present persist through reboots. Farther info on the startup process in this ubuntu howto

Futher Ubuntu Support hither

VPNs and Windows Routing and Remote Access [edit]

VPNs [edit]

If you are connected to a VPN (Virtual Private Network) and getting a NAT error when trying to run Vuze, it is nigh probable due to all of your internet traffic being routed through the remote network you are connected to. It is possible to configure the remote network to allow the traffic through, simply given the added overhead of a VPN, it is better to run Vuze when non connected to the VPN. Vuze will run improve and your downloads will be faster.

If you lot take no choice and must be connected to a VPN, so you must contact the network administrator of the remote network you connect to, and hash out allowing the Vuze port through the VPN to your PC.

Note: If yous're using Check Point SecuRemote Client, it will give you NAT problems fifty-fifty when you're Not connected to any remote networks.

Note: If you're using the Cisco Systems VPN Client, you lot must disable the Stateful Firewall nether Options. (Information technology is disabled if the checkmark next to Stateful Firewall does not appear.)

To avoid the bug, get to network settings and temporarily disable information technology, earlier starting Vuze. Or, if y'all take 2 network adapters, simply run the VPN client on one, and Vuze on the other.

Windows Routing and Remote Access [edit]

Microsoft Windows 2000 and XP incorporate a service for supporting VPNs, that tin can cause NAT issues in Vuze if enabled. Even if yous don't connect to a VPN, but this service is enabled, it can cause bug. If you lot're sure you lot don't use VPN connections, then information technology's safe to assume you don't need the Routing and Remote Access service enabled.

To disable the Routing and Remote Access service in Windows

Go to the Windows Control Console (In Windows XP, switch to Classic View if non already.)
Open up the Administrative Tools
Open up Services
Find the Routing and Remote Access service, and double-click information technology.
If the server condition is 'stopped', and so it is not running and information technology is non your trouble.
If the server status is 'started', and then utilize the cease button to stop the service, and run across if your NAT trouble changes.

If this fixes your NAT problem, and the Routing and Remote Access Service's startup type is set to Automatic, alter it to Manual or disabled to forbid it from running upon next reboot.

Software Firewalls [edit]

Main article: Firewalling

Just like the wide array of routers available to consumers, and so too is the list of software firewalls, and each has different features and capabilities. Because of this huge variance, we will again attempt to approach this as broadly equally possible. A software firewall can offering the same protection that a router can and it can mimic the symptoms of a NAT error. So why should you use both? A router tin can only protect yous from incoming information on certain ports - a good software firewall tin can monitor outbound traffic also. Consider this an added layer of security.

For those that apply a software firewall on their PC, the following data applies to everyone who hopes to set up their NAT error.

You lot should never accept more i software firewall installed and in use at any given time (analogy: ii drivers wanting control of a steering wheel).
In gild for Vuze to run correctly, admission/permission must be allowed.
- If your software firewall has options for a security level, reduce it from "high" to "medium" if it isn't already at that place.
- If you are using Vuze 2.iii.0.four or older, your software firewall must let "javaw.exe" accesss/permission.
- If you are using the electric current batch of Vuze Betas or a newer stable version later it is released, you will need to allow "Vuze.exe" instead.

Beneath is a list of some of today's common software firewalls guides that should help. Boosted data on how to open your firewall with some programs and Operating Systems hither: Firewalling

For XP SP1/SP2 firewall at http://back up.microsoft.com/default.aspx?scid=kb;en-us;283673
For Microsoft ISA 2004 Firewall http://Vuze.aelitis.com/wiki/index.php/Router_configuration#Microsoft.27s_ISA_Server_2004
For F-Secure http://firewalling.com/personalfirewalls/f-secure/f-secure.htm
For McAfee V6.0 Firewall Plus http://firewalling.com/personalfirewalls/McAfeeV6.0FirewallPlus.htm
For Norton Personal Firewall 2004 http://firewalling.com/personalfirewalls/nortonpersonalfirewall.htm
For Norton Internet Security 2005 http://firewalling.com/personalfirewalls/nortoninternetsecurity2005.htm
For Sygate Personal Firewall Pro http://firewalling.com/personalfirewalls/sygatepersonalfirewallpro.htm
For ZoneAlarm Pro http://firewalling.com/personalfirewalls/ZoneAlarmPro.htm
Tendency Micro PC-cillin Cyberspace Security 2006 Firewall http://kb.trendmicro.com/solutions/search/chief/search/solutionDetail.asp?solutionID=26628

Also, confirm whether or not your motherboard is based on the NF4 (nVidia nForce 4 chipset). Many of these new motherboards come with onboard firewalls that are enabled at the time the drivers are installed.

Anti-virus Programs [edit]

Some anti-virus programs are extremely sensitive to incoming data and will report "simulated positives" when used in conjunction with file sharing applications (though this is no reason to completely remove your anti-virus software). Instead, you should use Google and see if other users accept encountered such reports. Other anti-virus programs can at times contribute to a NAT fault. At the fourth dimension this is being written, only ane stands out, and others will be added if/when they've been confirmed.

Norton AntiVirus 2005 and 2006 employ "internet worm protection" past default and should be either disabled or made an exception. Ideally, it would be best to make an exception for Vuze' communications.

Open Norton AntiVirus 2005 - Click "Options"-- Click "Internet Worm Protection"--- Make sure "Enable Internet Worm Protection recommended" is checked.--- Click "Trojan Rules"---- Uncheck "Unused Windows Services Block", (all the fashion at the bottom of the list)----"OK"---"OK"

goto general rules inside the internet worm protection,add a new rule, yous need to let your Incoming TCP Listen Port(tools-options-connection)

Mobile/3G/satellite connections [edit]

Very often the diverse mobile internet connections, either through 3G/mobile dongles or satellite dishes, have been limited past the ISPs network architecture to only have private IP addresses.

If your "outermost" device, due east.g. the 3G modem, has a individual IP address (10.x.x.10, 172.16-31.10.ten and 192.168.x.x) in its config/status screens as WAN/internet accost, then it has been given by ISP's network and in that location isn't much y'all tin can do. Every bit you take no config access to ISPs routers, yous might take to live with the yellowish smileys and the NAT problem.

Notation: Vuze NAT test will non find this out, as information technology will always evidence the first real public IP address it reaches. In the example of mobile dongles with private addresses, the shown IP accost is probably a router somewhere at the Internet access provider.

Last Thoughts [edit]

We have seen many Vuze users mistakenly enable or disable an option in Vuze without knowing what they do. While exploring your client is encouraged, some of these options may take adverse effects. 2 things of note:

In Options->Connection->Advanced Network Settings, the "demark to local IP address box" should be left empty. This is NOT the aforementioned affair as the "MAC address binding" or creating a "static IP address". This should just be used past experienced users, and those that have more than than ane network adapter in their computer. Be sure to press Relieve after clearing this box if y'all accidentally used it.
On the other hand - some people take actually reported success by enabling this choice. You may want to effort it equally a last resort (though if information technology doesn't solve the trouble, then remember to remove it).
Often, users will go out UPnP enabled in Vuze (it is on past default.. Tools->Options->Plugins->UPnP), and simply disabling this may help clear things upwards when all the above steps in this guide have been taken. Be sure to press Save after disabling UPnP.

Conclusion [edit]

This page'due south purpose should assistance the vast majority of those who have encountered a NAT error while using Vuze with a "typical" setup. There are other circumstances, though, that require further investigation. More aid sections will be added to this guide in time.

Some figurer owners may non realize in that location are two NAT enabled devices on their network (modem/router AND router).
Some users may not have a routing device at all, but instead, are using ICS (Cyberspace Connection Sharing) and not properly port mapping to other machines.

Notwithstanding Non Working? [edit]

Come up to the Vuze forums and inquire for assistance there. Exist patient. Be prepared to answer these questions:

What is your Operating Organisation?
What is your Java Version?
What is the exact make/model/revision is your router? (if y'all use i)
Does the router apply UPnP and MAC binding?
What is the exact make/model/revision of your broadband modem?
What software firewall(s) do y'all utilise?
What anti-virus program practise yous use?
Which (if whatsoever) of the above steps accept you already attempted and with what level of success?

Special case: But private IP addresses

If your ISP is using NAT itself, information technology may exist impossible to get the NAT/Firewall exam to piece of work because it is existence cut off at your ISP. Some ISPs (especially mobile/cellular/3G service providers) use carrier course NAT, meaning they simply give users private IP address from those private ranges and then users are virtually probable doomed to alive with yellow faces. (Annotation: Vuze NAT test will non notice this out, as it will e'er bear witness the outset real public IP address it reaches.) If your "outermost" device has a individual IP address (10.x.x.10, 172.x.10.x and 192.168.x.x) in its config/status screens equally its outer WAN/internet accost, and so it has been given by Internet access provider'south network and there isn't much you can do.

Read the Vuze FAQ

greenhathouty.blogspot.com

Source: https://wiki.vuze.com/w/NAT_problem