WRVS4400n port forwarding (SSH access)

I have a WRVS4400n and a CentOS server that I need to enable a SSH access to from WAN.
I created a single port forward rule to open port 22 and forward to server (which address is 192.168.41.3)
However ssh connect doesn't happen, the command "ssh user@{external_IP}" times out after 20 seconds.
Wondering why...
If I connect my server directly to modem through outside interface - I have no problems connecting to it. Once it's behind router - no luck.
I even added same rule for UDP, not sure if it's needed, but it definitely didn't hepl.
The router is on firmware version 2.0.1.3, version on a bottom is 2.
Any suggestions?

Hi Randy Manthey, Thanks for quick response. The server has 2 interfaces: eth0 (outside, WAN) currently down. When it was up it had a static IP, default gateway and mask assigned by ISP. It was plugged into the cable modem at that time, it was accessible. eth1 (inside, LAN), up, address 192.168.41.3, default gateway 192.168.41.1 (which is above mentioned Cisco router WRVS4400n). It can ping all machines on LAN, including gateway. It is accessible to all machines on LAN and can be pinged by the Cisco router. It CANNOT ping any IP address on WAN (I understand this is because eth0 is down). Let me know if you need any other info. Thank you.
Edit: I got home (the router is in one of my offices) and scanned the router with nmap:
nmap -v -sT -PN XXX.YYY.ZZZ.88
Starting Nmap 5.21 ( http://nmap.org ) at 2012-04-24 23:24 EDT
Initiating Parallel DNS resolution of 1 host. at 23:24
Completed Parallel DNS resolution of 1 host. at 23:24, 0.04s elapsed
Initiating Connect Scan at 23:24
Scanning wsip-XXX-YYY-ZZZ-88.nn.nn.nnn.net (XXX.YYY.ZZZ.88) [1000 ports]
Discovered open port 8080/tcp on XXX.YYY.ZZZ.88
Completed Connect Scan at 23:24, 6.06s elapsed (1000 total ports)
Nmap scan report for wsip-XXX-YYY-ZZZ-88.nn.nn.nnn.net (XXX.YYY.ZZZ.88)
Host is up (0.033s latency).
Not shown: 999 filtered ports
PORT STATE SERVICE
8080/tcp open http-proxy
Read data files from: /usr/share/nmap
Nmap done: 1 IP address (1 host up) scanned in 6.14 seconds
Port 8080 - is a port for remoute router administration.

Similar Messages

WRVS4400N port forwarding unresponsive

Router: WRVS4400N
Firmware: 2.0.2.1
Background:
Port forwarding external port 1234 to internal port 123 on a NAS appliance (ip 192.168.1.111)
Successfully accessed NAS like this:
https://11.22.33.44:1234/MyShare
Everything was working perfectly for several weeks
Last week I changed the subnet to 172.17.888.x
Problem:
Everything back to normal on the LAN except that port forwarding to the NAS no longer works.
Gerfingerpoken:
I opened another port (1235) and forwarded that to the NAS (in addition to the original port). No success.
I tried a port scanner. The port scanner reported that port 1234 was open on the router, but didn't mention 1235.
I repeated with yet another port. Same result: only port 1234 is reported open by the port scanner.
Software rebooted the router, same result
Hard reset (button) the router, still no change.
QUESTIONS:
1. How can I test if the router is actually forwarding new ports? (software tool?)
2. Any thoughts or suggestions?

Update.
Port forwarding was working, but the recipient device (NAS) was not accepting connections due to a misconfigured security certificate. It was necessary to regenerate the security certificate on the NAS device and all started working.
HOWEVER, it would be very nice to know if port forwarding was actually working. Knowing that would have eliminated half the possibilities and greatly simplified troubleshooting.

Port Forwarding and Accessing my Router

Well, I'm an idiot! I set up my router and now can't get back into it so I can open some ports for my PS3. I tried 192.168.1.1 but that takes me to my modem (Westell). I am in desperate need of some help and have also tried .0.1 to no luck. Does anyone know how I can access my router. Thanks if so.

Depending on your opertating system open start>run> type in CMD <enter>. That should take you to your DOS prompt and from there type in ipconfig /all <enter>. That will show you a few IP address's and there should be a Gateway IP. It may be 192.168.1.2 or something like that. That is your routers IP so when you try to access your router type in http://192.168.1.2 or the addy it lists as your gateway.
Richard Aichner (Ikester)

Port forwarding, NAT, SSH and Transmission.

A couple of days ago I decided to setup the Transmission daemon, along with automatization for my downloads. Recently, however, to put a layer of security around my laptop, I set up a wireless router I had lying around that is now connected with a wire to my laptop. The reason for this is that I have no idea how iptables work yet, and until then I decided this will suffice for the moment. One of the problems though (yes, problems seems to come in twenty-fold where my luck is concerned), is that when I rewire my laptop directly to the internet, without the router, NetworkManager or Archlinux doesn't reset the ip address, which for some reason jumps to 192.168.1.122, which it never uses otherwise. I haven't yet tried reinstalling networkmanager, but when I did turn it off, dhcpdcd assigned the same address... The problem here being that it shouldn't assign a LAN-address, I'm directly connected to the internet. Sidenote here though; my internet connection is just a plug in the wall, the operators here (I live on a kind of campus), probably only use a network-switch to relay the traffic to the socket.
That's that, my wired network doesn't work directly, only via the wireless router, wired or wireless. Because of this, I have to use port-forwarding for SSH (to test if the port forwarding works), and the Transmission daemon with an rcmp port of 9091., which was my intention in the first place. I have no idea if logging into my.ip.address.here:9091 in a browser would work, I just used localhost:9091.
Now for the results:
$ nmap -sT xx.xxx.xx.xx
Starting Nmap 5.21 ( http://nmap.org ) at 2010-06-14 19:42 CEST
Nmap scan report for xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Host is up (0.038s latency).
Not shown: 996 closed ports
PORT STATE SERVICE
22/tcp filtered ssh
53/tcp open domain
80/tcp open http
9091/tcp filtered unknown
Here it shows that the ports are actually not closed, but they're not exactly opened either, from what I gathered from the internet.
SSH shows the true problem:
$ ssh neal@xxxxxxxx
ssh: connect to host xxxxxxxx port 22: Connection timed out
SSH-ing to 192.168.0.102 (my internal ip) works, as does to localhost, same for Transmission webGUI. Before I used port-forwarding ssh would correctly say that it couldn't get traffic from the router.
My router is a cheap solution to another problem I had, but it should work like any router. It's a Sitecom WL-607. I disabled login authentication for the moment. Also, there is no filtering going on in the firewall. Like I said earlier, I don't get iptables, so that's not being used. The hosts file allows all and denies nothing.
TLDR version; I'm using port-forwarding on my Sitecom WL-607, but all ports except http and the 53 port are being blocked.
Is there something I'm missing here?
Thanks in advance,
Neal van Veen.

by default, all routers assign there clients an ip address from there internal pool of addresses, your wireless router is assigning you that address and then NAT's the connection with the WAN side, but even after directly plugging in to the wall socket you still dont get a new ip address, use dhcpcd <mydev> in terminal to reresh dhcp lease. if not then your campus/location/etc may also be using NAT on there own side.
as for the ports, iptables doesnt block any traffic by default, it allows everything. if there is filtering, it is from your wireless router.
on the above ssh and nmap scans, did u use your lan ip, or your public ip.

EA6400: Port forward two Netgear ReadyNAS FTP servers

I have a new EA6400 router with the latest May 2014 firmware. I also have two Netgear ReadyNAS network attached storage devices that are set up as FTP servers. With my old Netgear WNDR3700 with DD-WRT firmware (after the last thunderstorm, may she rest in peace), I could easily set up both with port forwarding and access them outside of my LAN by setting up 4321 and 4311 as ports that translate to 21 and 21 to two different addresses on my network. I have them set up the same way in the EA6400, going into Single Port Forwarding and forwarding 4321 to 21 at 192.168.1.144 and 4311 to 21 at 192.168.1.143, but the EA6400 tells me that I can't use the same port (21). Why not? They're going to different addresses. (Oh I wish I could get DD-WRT on this router!) Is there a way to set up two FTPs on a local network and make them accessible through the EA6400 to an address on the internet?
I have also attempted to disable one of the port forwards and attempted to access the remaining FTP server and have had no success. I have successfully forwarded a port on the EA6400 to my security camera system so I can monitor my home from the internet, so I know the basics of how this is done. I just can't get single port forwarding to work with my NAS FTP servers.
Any ideas?

I switched the settings around and now the other ReadyNAS is coming up, but the one that used to come up no longer does. I also tried replacing the 10001 with 2121 on both EA6400 and on that particular ReadyNAS because it seemed to be a little more common a number for an alternate FTP port.
So now I have access to the one I couldn't access before and the one I could access before I can no longer access. Of course I can switch them back around again, but I'd like both to work.
Of course one could potentially put the blame on the ReadyNAS as possibly not being able to work FTP off any other protocol than 21 but I have to place blame on the EA6400 router firmware. This worked well under DD-WRT.
Anyone have any more ideas? I appreciate the help.

Port Forwarding - don't ask

I posted a question about BT Blocking Port-Forwarding. This has been removed.
Did I upset somebody ?

It was moved http://community.bt.com/t5/Other-BB-Queries/Beware-BT-Infinity-Port-Forwarding-External-Access/m-p/8...
To say thanks for a helpful answer, please click the white star

Nginx client_ip in log file, with ssh -R Port forwarding

Hi, everyone!
First, I run a nginx server M1 (in my offce) behind a router R1 and M1's IP addr is 192.168.5.126. I set nginx's log format like this:
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
After that, I will get the correct client ip in the access log.
192.168.5.88 - - [21/Apr/2015:11:12:47 +0800] "GET /js/date.js HTTP/1.1" 200 403 "http://192.168.5.126/" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.118 Safari/537.36" "-"
Then, I want to visit M1 outside (in the campus) . Unfortunately, I can do nothing with the router R1. But I have a router R2 whose framework is OpenWrt and its IP 222.xx.xx.xx can be visited by anyone who has logged into the campus network.
Then I wrote a autossh service to do that:
[Unit]
Description=AutoSSH service for local port 80 forwarded to 222.xx.xx.xx:80
# place this in /etc/systemd/system/, than enable this.
After=network.target
Requires=nginx.service
After=nginx.service
[Service]
Environment="AUTOSSH_GATETIME=0" "AUTOSSH_POLL=60" "AUTOSSH_LOGFILE=/var/log/nginxssh.log"
ExecStart=/usr/bin/autossh -M 22000 -NR 222.xx.xx.xx:808:localhost:808 -NR 222.xx.xx.xx:80:localhost:80 -o TCPKeepAlive=yes -p xxxx [email protected] -i /home/username/.ssh/id_rsa
[Install]
WantedBy=multi-user.target
Yeah, It works! BUT BUT when someone visits 222.xx.xx.xx, I lost the the client ip in nginx log file. That would always be 127.0.0.1, why?
127.0.0.1 - - [27/Apr/2015:00:34:07 +0800] "GET /static/mathjax/MathJax.js?config=TeX-AMS_HTML HTTP/1.1" 304 0 "http://222.xx.xx.xx:808/url/jakevdp.github.com/downloads/notebooks/XKCD_plots.ipynb" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:37.0) Gecko/20100101 Firefox/37.0" "-"
After ``ssh -R Port forwarding``, client ip is lost?
If so, what should I use to replace ``ssh -R``?
Last edited by limser (2015-05-04 12:39:18)

It seems there is a port forwarding configuration trouble with you modem.
When you access from the WAN or from the LAN, you don't enter in you modem the same way, so the behavior is different.
It seems that the port 22 of your modem is not directly forwarded to your server. The modem itself asks you a login/password. The key-pair authentification is between laptop and server. The modem itself is not recognized during this authentification.
Don't touch your ssh-config. It's OK since it was working for monthes before you change your modem.

Combo unix ssh port forwarding + iChatAV + Bonjour question

I don't know which forum is best for this question, so thought I'd try here first.
I've been tossing around the idea of picking up a couple of iSights and running iChatAV. Problem is, if I understand this correctly, iChatAV uses a couple of ports for connections to third-party servers: AOL buddy server or Jabber server, a port for something called snatmap, a port for SIP, and some other stuff. Plus, it requires that you open up nearly 20 ports on your network for the AV traffic! (I get nervous just having my non-standard ports for smtp and ssh open, and my imaps port open (which is another issue -- anybody know how to change imaps port 993 to a non-standard port if running uw-imap server?) It doesn't look like iChatAV can, normally, operate by "calling up" an IP address or hostname...it always has to set up calls using AOL or Jabber...unless, perhaps, the destination iSight/iChatAV is on your own Bonjour-capable subnet.
So, I'm thinking, what if a calling party created a ssh tunnel and port-forwarded the dozens of UDP and couple of TCP ports over a ssh tunnel, as a lengthy list of port forward options like "-L 5297:localhost:5297 -L ...", (assuming that the forwarding host, to whom the caller ssh's, is the same computer that is running iChatAV, hence, the remote host specification in the "-L" option of "localhost"). Would the caller then be able to treat the connection like Bonjour networking and when he calls localhost on his end of the circuit, it "bonjours" to the called hostname's localhost and thus a peer-to-peer connection would be made?
Or perhaps a reverse port forward tunnel ("-R" options) could be set up in advance by the "to-be-called" party, and then the calling party initiates a iChatAV call as a "same-subnet-as-calling-computer-via-Bonjour" type of call?
I'm just kicking around some thoughts here; I don't know enough about the intricacies of iChatAV and Bonjour (and ssh) to really know all the "gotchas" and I'd like to get the planning done with a high degree of confidence of success before I plunk out $300 on two iSights.
If the general concensus of the group moderator and others on this forum is that this question should be posted in another forum, I apologize, and I'll move, but I thought that the ssh tunneling nature of my inquiry (and my unrelated side question about how to change 993 to a non-standard port) made this forum the obvious, and best, choice.
Thanks in advance for any thoughts on these issues!
2001 Quicksilver G4 Mac OS X (10.4.5)

No, you can't do what you describe. You have to use port forwarding on the router for any incoming connections, and each port forward rule can only map to a single server/service.
However, SSH has the ability to tunnel other connections, so it may be possible to remove one or more of the existing port forwarding rules and replace them with a SSH rule, then use SSH tunneling to get to those services. Of course, this will only work for services that only you (or other authorized users) need to access, and not public services such as web/http traffic (assuming you're running a public web site).
The only other option would be to replace your router with one that doesn't have such a strict limit on the number of port forwarding rules.

Ssh Port Forwarding Stopped Working

I have used ssh port forwarding in the past, and it has come in handy.
I have recently upgraded to Mavericks, but it does appear that my ssh port forwarding stopped some time before this. The last time I know it worked was 5/14/14, and feel it has worked more recently as well.
Here's what I do, from my Mac I ssh to my work jump server (port 22, let's say its IP is 11.22.33.44), and my jump server has access to work PC (lets say IP of 10.1.2.3). My work PC has RDP running on it on the common port 3389. I have verified that I can set up a working RDP session at work from another box. Also, I know that my jump server can get to my PC at work as I can ping my work IP if I just ssh straight to my jump server. And I know that there is no firewall stopping me from the jump server as I can also open a telnet session to my work PC on port 3389, without errors.
So, here's how I have done it in the past and it has worked, but now recently stopped working in Terminal app:
ssh -f [email protected] -L 3388:10.1.2.3:3389 -Nnv
The verbose logging shows that it sets up connectivity. If I then look to see if my local port is listening I can type:
netstat -an | grep 127.0
I will note that port 3387 is in fact LISTENing and waiting for connection
I then start my RDP client app, and start a session to "localhost:3387" (I could also use "127.0.0.1:3387", and have, but it does not work either). My RDP client eventually times out. I have turned my firewall off and on, neither way works.
Does anyone know why this may have stopped working?
Your input is most appreciated.
The verbose log shows the following is setup appropriately (with noted modifications to server names and actual IPs):
debug1: Authentication succeeded (keyboard-interactive).
Authenticated to somewhere.net ([11.22.33.44]:22).
debug1: Local connections to localhost:3387 forwarded to remote address 10.1.2.3:3389
debug1: Local forwarding listening on 127.0.0.1 port 3387.

Unfortunately I don't have another device to test if RDP is working on my LAN, however, when I check out my network connections and this is what I see after setting up the ssh tunnel and prior to attempting the RDP connection (again names protected):
my-rmbp:~ me2$ netstat -an | grep 127.0
tcp4       0      0 127.0.0.1.3387         *.*                    LISTEN
Then, as it is difficult to catch in the middle of TCP 3-way handshaking, here's what happens after an attempt with the RDP client while it sits and spins:
my-rmbp:~ me2$ netstat -an | grep 127.0
tcp4       0      0 127.0.0.1.3387         127.0.0.1.50323        FIN_WAIT_2
tcp4       0      0 127.0.0.1.50323        127.0.0.1.3387         CLOSE_WAIT
tcp4       0      0 127.0.0.1.3387         *.*                    LISTEN
You can clearly see it's attempting to make a connection over the tunnel via my RDP client, but it's being shut down right away. I will obtain a WireShark packet capture and see exactly what's happening. Oh, and if I tried to RDP to a port other than the one I set up the port forwarding tunnel with, RDP would disconnect right away.
What I'm most interested in is why, without any known changes, other than OS updates, did this work a few months ago, and now it does not?
I have also tried other test ssh port forwarding, such as to www.apple.com forwarding 8080 on localhost to 80, and others, and none of those work either with web browsers, I assume this is something Apple has done to disable ssh port forwarding/tunneling. Perhaps someone else has bumped into this and found a fix? Please share!
Also, I have heard that you have to be root in order to set up port forwarding, but clearly this is not accurate, as it worked before, and also as you can see above it worked without root. But I tried both ways, and sadly neither worked.
Could it by my jump server? Possibly, but others at work do this and it works just fine for them from their Windoze PCs. So can't be that either.
Perhaps my capture will tell me, I'll report back here with what I discover. Thanks in advance!

VNC without access to set up port forwarding

I just bought the VNC Viewer app for my iPhone 4 and got it to work over 3G and wifi with my macbook pro connected to my home network. I know very little about networking but I knew enough to be able to set up port forwarding to my ip on my router at home. The problem is that I am a student in college right now, so my computer will be hooked up to the schools network when winter break is over. I have no access to set anything up on the network at school, so how will I get this to work? I made a host name at no-ip (does that allow me to connect to my computer even when my ip changes?), and I read something about being able to set up an ssh tunnel to make it work...maybe? I now have no idea what to do and the other forums I've read about this topic are using language that I am not familiar with. I need some network education! Again, the problem is setting up my MacBook Pro to allow a VNC connection on a network I have no control over. Thanks!
Message was edited by: drummer914

My suggestion is using TeamViewer.com (they have both a Mac and an iPhone app) and it is free for personal use.
Team viewer has the ability to work across routers and corporate firewalls.
The problem with ssh is that it also needs port forwarding the same as VNC. You could have your Mac at college ssh to a Mac at home, setting up a reverse tunnel (ssh -R). You then VNC to the Mac at home, and instead of attaching to a VNC server at home, you connect to the ssh tunnel listening for connections. You would have to always have the tunnel established from your college Mac to a home Mac (or it could be a Linux box at home). And at home you would also need to port forward port 22 so your college Mac and ssh into your home Mac.
It might be an interesting exercise, but I think you would be happier using TeamViewer.com

Port forwarding for external access to VNC server on multiple machines

I will have 10 PCs connected to the WRT54GL wireless AP. I am testing with 1. It has a static addresses 10.155.22.51. It is running a VNC server at port 5951.
If I set my VNC client up to access 10.155.22.51:5951 it works through the WRT54GL wireless AP.
I set the WRT54GL port forwarding to 5951 - 5951, set the IP address to 10.155.22.51 and enable. The external address of the AP is 10.155.0.29 on the company LAN.
So I set the VNC client to access the AP address with the VNC port, i.e. 10.155.0.29:5951. I expect the AP to change the address to 10.155.22.51:5951. This does not work.
Note: the problem could be that the AP is going through NATting because I can also access it at 10.155.22.9 along with all the other PCs on that LAN, i.e. I can access the LAN directly from elsewhere on the company net.

You can try changing the IP of the AP manually ... connect it to the Computer ..... access the setup page using http://192.168.1.245 .... use password as admin ....
Configure the IP settings first ...
Again login with new IP address .... configure wireless settings .....
Power down the AP & then the router ....
Wait for few minutes .... then power on the router ...first then the AP ...

Port forwarding for clientless SSL VPN access

Hello,
I am currently trying to set up clientless SSL VPN access for some remote sites that our company does business with. Since their machines are not owned by my company, we don't want to install/support a VPN client. Therefore, SSL is a great option.
However, I'm running into an issue. I'm trying to set up port forwarding for a few remote servers. These remote servers are different and have distinct IP addresses. They are attempting to connect with two different servers here.
But my issue is that both servers are trying to use the same TCP port. The ASDM is not letting me use two different port forwarding rules for the same TCP port. The rules can exist side-by-side, but they cannot be used at the same time.
Why? It's not trying to access the same TCP port on a server when it's already in use. Is there anyway I can get around this?
If this doesn't make sense, please let me know and I'll do my best to explain it better.

Hi Caleb,
if you mean clientless webvpn port-forwarding lists, then you should be able to get your requirments. even the same port of the same server can be mapped to different ports bound to the loopback IP.
CLI:
ciscoasa(config) webvpn
ciscoasa(config-webvpn)# port-forward PF 2323 192.168.1.100 23
ciscoasa(config-webvpn)# port-forward PF 2300 192.168.1.200 23
then you apply the port-forwarder list under a group-policy
Hope this helps
Mashal
Mashal Alshboul

Remote TC access via port forwarding

I have been trying to setup my network for remote TC access via port forwarding. Here's my setup:
Verizon FiOS router (main router, dhcp & nat) -> connected to TC set in bridge mode with a static IP
I can remotely access the TC using Back to my Mac with no problems, and of course locally on the home network via Wifi.
Since the TC has to connect in bridge mode, port forwarding is done on the FiOS router.
If I set a port forwarding rule in the FiOS router TCP,UDP (any) to port 548, it works. However I want to use a specific connection port
so others can't connect unless they know the forwarded port. BTW, I have remote disk sharing set with Use Device Password.
So here's what works:
FiOS Router (TCP any -> 548, UDP any ->548)
What doesn't work:
FiOS router (TCP 8990 -> 548, UDP 8990 -> 548).
Is there any additional setting required for specific port forwarding to work?

You're my hero!
I also have my TC in Bridge Mode to my Verizon FIOS Router. I used to be able to access my TC remotely, but since I upgraded my router (MI424WR GigE), I had forgotten some port forwarding rules I must have established in my old router. Once I re-created these two port forwarding rules (just like yours), I can remote access my TC (with TC password) again.
In addition, I have a static host name aliased to my dynamic IP address through dyndns.org (I have the free version, which I don't think is available anymore, but there are other free providers out there) for easier remote access.
Regarding, Secure Share Disks: with TC password vs a disk password. Is one more secure than the other?
Thanks!

Application And Gaming / Port Forwarding || HELP NEEDED || Can Only Access Via LAN

Hi.
I have just bought a Wireless Router, Model Number: WGKPC354G-UK. With the intention of setting up a small server. This server will run from my PC (directly wired into router), running a game called "Counter Strike" - I had to download a dedicated-server tool for this and i successfuly installed this and followed the tutorial to set it all up..
So I thought i had done it, but I could only access my server with my internal IP 192.168.1.64 (LAN).
I then found out that i needed to "Port-Forward" I followed a tutorial on www.portforward.com - This showed me how to open the ports, and which ones to open.
I did all this and i still encounter the same problem !
So i then opened all my router ports "DNZ" and it still doesnt work !!!
Any help will be greatly aprreciated !
PS. Below Are The Required Ports.
http://portforward.com/english/routers/port_forwarding/Linksys/WAG354G/Counter_Strike.htm

Keep in mind your ISP could be blocking the ports needed. DMZ almost ALWAYS works and if it doesnt, most likely your ISP blocks the ports.
another test is to make sure you can connect to the game server from another CS machine on the inside of your network. If this works, that means your server is up and running properly and its probably your ISP blocking certain ports needed for the CS Server.
You should also check you have the Windows firewall disabled, and any other software firewall on your server disabled.

EA2700 port forwarding issues for DVR access

So start this off I searched these forums for answers and new here but not to the router world, I have been having issues lately I set up a DVR and need to view remotely, ports are 7000 and 8080, I setup DVR on a static IP and it can access the internet and I can ping the DVR internally than I go into router and port forward those ports on DVR's IP address disabled upnp I setup dhcp reservation on DVR's IP but when I check can you see me.org it shows those ports are closed for my external than I check port 80 and shows closed looks like all my ports are close is there some firewall in this router that would do this please help

If the ISP modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems: Link>http://www.practicallynetworked.com/networking/fixing_double_nat.htm and http://cognitiveanomalies.com/cisco-nat-how-nat-works/. If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.
Glad you got it working. Enjoy.
loginix wrote:
So start this off I searched these forums for answers and new here but not to the router world, I have been having issues lately I set up a DVR and need to view remotely, ports are 7000 and 8080, I setup DVR on a static IP and it can access the internet and I can ping the DVR internally than I go into router and port forward those ports on DVR's IP address disabled upnp I setup dhcp reservation on DVR's IP but when I check can you see me.org it shows those ports are closed for my external than I check port 80 and shows closed looks like all my ports are close is there some firewall in this router that would do this please help

WRVS4400n port forwarding (SSH access)

Similar Messages

Maybe you are looking for