Port Forwarding Netgear 834G V2 / V5

Lourens

Well-Known Member
Joined
Jun 18, 2004
Messages
450
Reaction score
0
Location
South Africa.
Hi,

Can anyone help me with the Port Forwarding on a Netgear 834G V2 or V5 or both of them

I need to run an app on a pc that is accessible from the web or specific ip address to send information that need to be processed on the machine and then return the results to the web or specific ip address.

Everything I tried so far has failed and setting up a DMZ on a machine also did not work - Remote Management can also not be reached with ip address on port 8080

The Netgear authenticate at the exchange

The pc use win xp pro with sp3 and the machine run avg free edtion.

Tnx,

Lourens
 
Last edited:
  1. If you want to test it, you'll have to test from another Internet connection, because the cheap/poor ADSL modems doesn't support NAT loopback, which means that you cannot make use of the port forward from the internal network.
  2. I'd suggest that you disable the firewall completely on the PC.
  3. Make sure that you're connecting the the correct Internet IP address. To ensure that it's correct, go to www.whatsmyip.co.za on the PC that you enabled the port forwarding for.
  4. Make sure that the internal/LAN IP address of the PC that you've forwarded to matches the port forward entry on the ADSL modem
  5. Lastly, make sure that you're forwarding the correct port and protocol (TCP/UDP). DMZ pretty much just forwards every port and protocol to that specific LAN IP address

The remote management thing is usually disabled to prevent attacks from the Internet.
 
1. First try accessing the application on the target PC, using only your local network. So get a 2nd PC on your network to test with. The application running on your PC will need to be accessed via an IP address and port number. Eg. 192.168.0.2:7890. You will need to unblock this port (7890 in my example) in the Windows Firewall settings, else the connection will be rejected. Check your application settings to see which port it is accepting requests on. Only proceed to the next step if you can get it working on your local network, from a 2nd PC.
2. Next, you need to enable remote management on your router, and try to access your router web interface from the internet, from a PC not connected to your local network (else NAT loopback will screw you). Try a 3G connection from your phone tethered to your PC, or simply use the web browser built into your phone. Type in the public IP address of your ADSL connection (get it from your router web interface, or even your ADSL provider's client zone login) into the web browser, and don't forget the specific port number for remote management if you have enabled this option: e.g. http://196.123.123.123:8080.
3. Once you have that working, then start with the port forwarding. You will want to set up a port forward from a public facing port on your router, to a local IP address and port combo. E.g. 196.123.123.123:456 --> 192.168.0.2:7890. You have to make use of 2 port numbers, one on either side of the connection, unless you set your PC as a DMZ, in which case all incoming traffic from the outside will be forwarded to your PC (not recommended, unless you have a good firewall setup, and you know what you are doing, which I don't think you do, no offense).
4. Lastly, when you have all that working, you'll want to set up a DynDNS account for your router, so you don't have to remember IP addresses, or continuously check for your latest public IP address of your ADSL connection (it changes every 24 hours or so). Head on over to http://www.dyndns.com, and register for a free account. You will be able to register your own free domain name. eg: lourens.dyndnds.info. Then you can access your application on your PC via the hostname and not the IP address, e.g. http://lourens.dyndns.info:456. You will need to configure your Netgear router with your DynDNS username and password, in order to allow your router to tell the DynDNS service what it's latest IP address is, so that DynDNS can associate it with your hostname.

Hope this helps. If not, tell us where you get stuck, and we'll try to assist.
 
  1. If you want to test it, you'll have to test from another Internet connection, because the cheap/poor ADSL modems doesn't support NAT loopback, which means that you cannot make use of the port forward from the internal network.
  2. I'd suggest that you disable the firewall completely on the PC.
  3. Make sure that you're connecting the the correct Internet IP address. To ensure that it's correct, go to www.whatsmyip.co.za on the PC that you enabled the port forwarding for.
  4. Make sure that the internal/LAN IP address of the PC that you've forwarded to matches the port forward entry on the ADSL modem
  5. Lastly, make sure that you're forwarding the correct port and protocol (TCP/UDP). DMZ pretty much just forwards every port and protocol to that specific LAN IP address

The remote management thing is usually disabled to prevent attacks from the Internet.

Pada,

Appreciate your reply;

1 - Know this and done it from several other networks.
2 - Done so on Win Xp, AVG and Netgear
3 - Know this and done it and checked with Vnc using the ip of the machine.
4 - Know this and done it and checked at www.whatsmyip.org - did not know www.whatsmyip.co.za exits
5 - Know this and done it and verified correct port - the app does not work on any other port

Unfortunately none of these work for me.

I'll keep on tying until I either get it right or when the Netgear suddenly stop working for doing a flying connection with the opposite wall of this room!

Thank you,

Lourens
 
@ToxicWazte,

I'll be back, let me first try and calm myself down and try this again step by step before this thing really end up in bit and pieces.

Thank you,

Lourens
 
The only thing that I can think of now is that the application is binding on an internal IP address and not on 0.0.0.0.

Run 'netstat -na' and ensure that it says something like:
Code:
  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING

Then do as ToxicWazte said and see if you can connect to the service from your internal network.
 
Hi,

I appreciate your responses - I should have made threats to smash this Neatgear a long time ago, it just decided to work after I went through the process for the umpteenth time.

The only thing that I can think of doing differently was the Firewall rules – I cannot remember that I have clicked previously on the Apply button after setting up the Inbound and Outbound Service.

Anyway, it work now and that is all the count for me at this point.

Ok, it's now several hours later. Tested a different port and had the same issues - went for supper and on return found the port is working fine when I tested. It seems that for some reason or the other, it takes a while for my set up to recognise the changes - weird but wonderful!

Just for future reference for someone else - this is on the Netgear DG834Gv5 with Firmware Version V6.00.25

Awe,

Lourens
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X