I'm having problem getting the port forwarding to work. When testing my home router (851w) at work, using VNC, Telnet, SSH, nothing gets through. Cannot connect, so it's not an authentication issue, as I don't reach the username/password stage.
Please take a look at my config and see what the mistakes might be. Also, what is the command to mask the passwords in my configuration? The <password> I've typed in were original just plain text.
I tried to set most of the stuff up with the CLI, and some were helped by SDM.
You have configured IP address on the VLAN interface (SVI). To telnet or SSH your SVI should be up.
To bring up this SVI you require atleast one port in vlan 1.
Check by configuring an IP address on the etherner interface and do a telnet. Though you will able to do SSH too, you should look at configuring this way
I don't quite understand how to execute this. If I am to create a SVI interface on the router, I'm not seeing that as a choice under the commands.
Also, is there a way to go about this w/o an IP for VLAN1? I only put that address there because it was the only way to assign an IP to the router itself I could see.
for one, you will need to move all the vlan1 config to bvi1 and configure no ip address and bridge-group 1 under vlan1. Else, you will never be able to use your wireless.
Then yes of course you need and IP for BVI1. It's your PC's default gateway address
The port forward seems correct and you should be able to connect from outside, but please remap 23 to something else if you still want to be able to telnet into the router. Finally, you don't need this:
ip nat pool nat1 192.168.1.1 192.168.1.254 netmask 255.255.255.0
Hope this helps, please rate post if it does!
Hmm, well, the wireless is working, but I'm still unable to VNC, telnet, or SSH into my home router from work.
If I PuTTY through telnet the black screen comes up with a "(inactive)" in the title bar.
If I SSH, I get PuTTY Fatal Error, "Network error: Connection refused".
For VNC, which is the 192.168.1.130 forward, "Failed to connect to server".
Strange, can you at least telnet into the router ?(require removing the port 23 forward).
Also pls send again the router config now.
I have to wait until I get home to send the router config again, unless I find time during lunch break.
Instead of using 23, i used 2300. I'm able
to telnet from inside the network, but not from outside.
I will also need to double-check and make sure dyndns.org is working so I know I'm not using the wrong IP address.
Apparently I don't know how to designate a different port to telnet yet, so I reverted the port forward lines back to port 23.
And sorry, I forgot to verify if the ddns is working properly or not.
The odd thing is, the 1811w at work I can telnet/SSH to with no problems, and that one doesn't even have the static tcp lines.
ip nat inside source static tcp 192.168.1.1 23 interface Dialer0 23
ip nat inside source static tcp 192.168.1.1 22 interface Dialer0 22
and you should be able to telnet/ssh into router. Regarding the forwards, these should work as configured, not sure why they don't.
That is, you can telnet and ssh to the router, but no forward to hosts behind the router works ? Can you try something else than VNC for a test? Eg web server to an host behing the router, like port 8000 "outside" mepped to 80 "inside".
Sorry, currently working on upgrading the computer, and the only quick thing I could think of was to run an FTP server. However, the FileZilla Server kept saying it couldn't connect to the local server.
I'll see what else I can try.
OK, when trying this with the LAN at work, I'm able to get FTP to work, but not VNC. Cisco routers just don't like to pass through VNC data?
Using online ShieldUp service, all the ports I opened, are indeed open, so the problem appears to be that they aren't being directed to the internal PC's properly.
Still stuck on this. Would this provide any leads?
tcp 22.214.171.124:3724 192.168.1.130:3724 --- ---
tcp 126.96.36.199:5900 192.168.1.130:5900 --- ---
tcp 188.8.131.52:6112 192.168.1.130:6112 --- ---
tcp 184.108.40.206:14147 192.168.1.130:14147 --- ---
tcp 220.127.116.11:49306 192.168.1.130:49306 18.104.22.168:5050 22.214.171.124:5050
tcp 126.96.36.199:49307 192.168.1.130:49307 188.8.131.52:1863 184.108.40.206:1863
tcp 220.127.116.11:49308 192.168.1.130:49308 18.104.22.168:1863 22.214.171.124:1863
tcp 126.96.36.199:49309 192.168.1.130:49309 188.8.131.52:443 184.108.40.206:443
tcp 220.127.116.11:49310 192.168.1.130:49310 18.104.22.168:5191 22.214.171.124:5191
tcp 126.96.36.199:49311 192.168.1.130:49311 188.8.131.52:5191 184.108.40.206:5191
tcp 220.127.116.11:49312 192.168.1.130:49312 18.104.22.168:5191 22.214.171.124:5191
tcp 126.96.36.199:49313 192.168.1.130:49313 188.8.131.52:80 184.108.40.206:80
tcp 220.127.116.11:49314 192.168.1.130:49314 18.104.22.168:80 22.214.171.124:80
tcp 126.96.36.199:49315 192.168.1.130:49315 188.8.131.52:80 184.108.40.206:80
tcp 220.127.116.11:49317 192.168.1.130:49317 18.104.22.168:80 22.214.171.124:80
It seems the config is correct. I have an 851w and I can forward ports without any problem. I use 12.4(11)XJ4, perhaps you may want to try that image as well.
In fact you can't. You will need a support contract, aka smartnet, in order to access the downloads. This should be available from your cisco reseller and the simpler level should be well below $100 forone year, that beside the download include hardware warranty and access to TAC support.
Correction, the IOS the I use is 12.4(11)T2.