Reply

Re: Portforwarding horror

DJR
Aspirant
Aspirant

Portforwarding horror

Hi, I checked on the numerous portforwarding issues but none of them seem to help my case.

This is the story:

- Cisco 3212 modem, connected to
- WNDR3700 firmware V1.0.16.98NA

I fail to open every port, E.g. port 445,21,9000) all tried and none is detected open by portchecker tools from the internet.

The ONLY port who is correctly opened is when I enable "Remote Management", which opens port 8080 succesfully!

My internal WNDR3700 ip adres is 192.168.1.1
My internet WNDR3700 ip adres, shown in router status page is public 62.195.x.x
My internal NAS server is at 192.168.1.100
My DHCP server is activated: 192.168.1.10 - x.x.x.50

I've checked "NAT secured/open" with no success
I've checked "Upnp off/on" with no success
I've disabled firewall functions under WAN sections with no success

Any help is deeply appreciated.
DJR.
Message 1 of 6
Tank_Killer
Tutor

Re: Portforwarding horror

Is your CISCO modem modem in bridged mode? Call your isp, you are probably running a double NAT. Your ISP can change the modem to bridged.
Message 2 of 6
DJR
Aspirant
Aspirant

Re: Portforwarding horror

Hi, I checked with my ISP and they said my modem is already in Bridge mode.

Please note that enabling Remote Management (8080) is working without a problem. Any other suggestions?
Message 3 of 6
jmizoguchi
Virtuoso

Re: Portforwarding horror

you have 62., public IP so should been working with it unless ISP blocks certain ports etc that fits what you are doing
VPN Case Study

VPNCASESTUDY.COM

"Our Second To None VPN Related Setup Case Study[/COLOR][/URL]

"One Stop Solution To Your Netgear VPN Connectivity"

*Visit the site for Non-VPN related Doc & Links* [Windows & Mac user/support]





June Mizoguchi-
Message 4 of 6
csewell
Aspirant

Re: Portforwarding horror

Do you have anything listening for incoming connections on the ports you forwarded? Otherwise they will show as closed. If you do have software listening for and accepting incoming connections, your ISP may be blocking certain ports. Enabling remote management doesn't actually forward anything; the connection is handled by the router itself.
Message 5 of 6
jlewter
Guide

Re: Portforwarding horror

I am with csewell here, If you do not have listening software running then it doesnt show the ports open. Try to connect to the local IP (192.168.1.xx:9000) and see if it is listening. Also make sure that your firewall is set to accept connections from local and internet.

On a side note, you should not open port 445 to the world. Samba shares are local shares and trying to force it to the interwibble would be a bad move (if the SMB software allows it).

Also (worth noting), some ISP's may block ports 80 (web server), 45 (ftp server), and port 25 (SMTP Relay).
Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 2148 views
  • 0 kudos
  • 5 in conversation
Announcements