Check the WAN IP address of your router - if it looks like 10.x.x.x, 192.168.x.x or 172.16.x.x to 172.31.x.

x then you have what is known as an RFC1918 IP address (often referred to as private addresses). You will need to contact your ISP to find out how to get a public IP address, or have traffic routed to you. Until that is done you won`t be able to get anything else working. only way to be certain of the WAN address is to look at your router, or if you have one your ADSL modem. You can use one of the many web pages that will tell you what your WAN IP address appears to be. Be warned however that if you are behind a proxy server, or you have one of the RFC1918 IP addresses referred to above, they will report the wrong IP address and you will waste time trying to get this working. Summary There are 6 general steps: Create your Dynamic DNS hostname or Standard DNS hostname. If you have a dynamic IP address (if you don`t know - you have one), configure a device on your network (that is always on) to update your DynDNS hostname with your IP address. DynDNS publish a list of approved clients that you should consult. There are also community maintained lists of devices known to work and those known to cause problems. Configure the device you want to forward traffic to with either a static IP address, or a static DHCP lease. This ensures that the time spent configuring the router (in a moment) isn`t wasted if/when the IP on your device changes. Test the device from your LAN. Configure your router to forward traffic to your device. How you do this depends on your router, and what you want to access. Fortunately there is a web site that publishes guides. Test your setup from outside your LAN. ADSL or multiple routers If you have a separate ADSL modem and router, or you have multiple routers, what follows isn`t enough. You`ll also need to forward the same ports from the external network device (ADSL modem or router) to the internal router before forwarding those ports from the internal router to the device you`re trying to access. Step 1 - Create your hostname Create your Dynamic DNS hostname or Standard DNS hostname (Standard DNS is for use with your own domain). If asked for an IP address when creating the hostname use the autodetected value or enter something like 192.0.2.1 - the IP address will be replaced by your update client later. Step 2 - Configure Updating If you have a dynamic IP address from your ISP, you have to make one basic decision - are you going to do your updating from your router, or from a PC? Running it from a PC (Windows, Linux or other) can mean that you get better logging and more control, but may result in more network traffic and greater delays in updating changed IP addresses (10 minutes rather than 1 minute). Using a non-approved router may mean that it is harder to get it working, or that you get blocked for updating your IP too often. If you are running your updater on Linux/*BSD or any other non-Windows platform it is generally best to install from a package (whether that be an RPM, a DEB or from ports/portage). That way you should get the required startup scripts and a sample configuration file. Step 3 - Configuring the Device You need to ensure that the device you forward traffic to has a static (aka fixed) IP address. If you don`t do this then at some point the IP could change, and you`ll be wondering why it`s suddenly broken. There are 2 ways of doing this. On the device itself - how you do this depends on the device or underlying operating system On the DHCP server (usually on the router) many offer the option of assigning a fixed IP address to any given device (usually by MAC address) If you go with option (1) make sure that you use an IP address outside of the range your DHCP server is allocating from. If you don`t do this you`ll end up with a duplicate IP on your network, and things won`t work. In the rest of this document I`ll use 192.168.0.1 to refer to this IP address. Step 4 - Initial Testing At this point you should be able to connect to the device, using the chosen IP address, from another computer on the LAN (it is important not to test from the device running the service). Until you get this to work there`s no point in going further. Step 5 Before Configuring the Router Your first step here is identifying what port(s) you need to forward. If you access the device with a web browser and a URL that looks like http ://192.168.0.1/ then you`ll want to forward port 80/TCP. If it looks like http ://192.168.0.1:3128/ then you`ll want to forward the number after the colon (:) - in this case port 3128/TCP. EMail (SMTP) uses 25/TCP for mail server to mail server communication. Other ports are used for other purposes: 587/TCP is a port for client to server (SMTP), 110/TCP for POP3, 143/TCP for IMAP. Other ports are also used for SSL versions of those services, though most modern software can use TLS instead. Other ports can usually be found easily by visiting Google, or consulting the appropriate guide (more in a moment). Now, before you configure your port forwarding there may be a problem. Some routers will not actually forward traffic on the same port as their administrative interface uses, even though they`ll happily let you set that up. If this applies to your router it`ll be easy to spot - instead of getting the device you expected to see you`ll get your router`s admin page (or a login prompt for the router). At this point you have 3 choices: If supported, move the admin page to a different port Forward a different port (and optionally use WebHop so that

people don`t have to add the port to the URL) Try a firmware upgrade, or alternative firmware (DD-WRT, OpenWRT etc) where supported Step 6 - Configuring the Router to Forward Traffic Now it`s time to configure the port forwarding. The manual that came with the router will detail how to do this, but if you`ve lost it (or don`t want to look for it) there`s a handy website with guides, and they even provide a program called PFConfig to do it for you. All you have to do is pick your router, pick the program you want to forward traffic to (or the protocol) and follow the instructions - complete with pictures. Be aware of problems with the Actiontec MI424WR (and probably other devices). If you configure the port forwarding using the hostname of the device to forward to then you may have problems. You have to use the IP address at all times. Step 6 - Testing You now need to test from outside your LAN with the DynDNS hostname. The reason for testing from outside your LAN is that not all routers support loopback connections. There are several ways to test this: Via a suitable online page. For web servers (or anything which uses a browser interface) there are various (limited functionality) online browsers (such as TCP Query from CentralOps). For email servers you can use the MX Toolbox service, which allows you to run some basic checks. From an external PC, online proxy or a VPN to a remote location. This will give you a proper test, allowing you to see what others would see. If you are using a computer ensure that you do your testing from another home user connection. Many public connections and work networks block ports and will give you an invalid result. The Open Port Tool allows you to check if portforwarding on your router is correctly configured, and your application is listening on the related port(s) Read more: How to set up port forwarding on dlink 2750u? - I want port foward to dvr for 3g ,normally i am usingmy dvr http port is 34567mobile is 34599how can i port foward above ports. I am using 2750u dlink dvr i want port foward to dvr , dvr their gave http pot 34567, mobile port is 34599 how can i port forward thank u pls