WRV200 Port forwarding internal/external

Hi,
Is there any way I can set up a port forwarding with a different tcp port externally than the one internally ? (for example: wan tcp port 8080 -> lan 192.168.1.1 tcp port 80)
Thanks.

I have this same issue with the same firmware.
I have UPnP turned on but there is not a screen to configure it like there is on so many other Linksys Routing products.
Is it just a hidden page that we can go to if we typed the url in?

Similar Messages

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 externally but not internally

I've got an AExtremeBS at home and at work. I've been port forwarding http for a while with no problems internally or externally. I've recently configured a new web server which internally is hosted on port 80. I've enabled port forwarding from 8080 to 80 on the AEBS and it works fine externally. However, if I try to browse the site internally using the FQDN:8080 of my AEBS, it does not work.
I can check both external and internal and the external is still working while the internal is not.
Any ideas?
One idea would be to move my internal listener to 8080 and just port forward 8080 to 8080 (I would just redirect 8080 to the internalIP:8080 rather than map 8080 to internal:80).
Thanks,
sid.

You might be onto something....but it's probably not what you think, but then again, I just confused myself again.
To get OD working I had to add my Leopard Server to my DNS settings. The Leopard Server required that it resolves the FQDN of the AEBS to itself (the internal IP address). However, everything else on the network resolves the FQDN to the external IP address.
If I nslookup on my FQDN, from my mac (which has the Leopard Server as it's DNS server) I get the internal IP address of the Leopard Server. However, if I go to another machine inside my network which does not query DNS from the Leopard Server, I get my external IP and when I browse to extneral:8080 it port forwards correctly. So it wasn't the AEBS, it was my particular mac and freaking Leopard Server.
So, it's settled, Leopard Server strikes again. I can't believe that Apple released this POS. I had a much easier time with Ubuntu 6.06 on my old 300 MHz blueberry iMac.

Port Forwarding on OSX 10.5 Server using Dynamic External IP Address

I have been able to get Port Forwarding to work properly on OSX Server by following the documentation and following discussion:
http://discussions.apple.com/thread.jspa?messageID=6700460
The problem however, is that you specify a static ip address on the natd.plist file.
I do not have a static ip address, and sometimes it changes. When this happens, of course all the port forwarding configuration will not work, and I need to replace the old external ip with the new external ip address.
This is an easy task to be accomplished, however having the internal network down just for the change of ip address is a hassle.
Is there any way the string entry can be updated with the ip address of the external interface (en0), instead of applying an ip address?
<key>aliasIP</key>
<string>17.128.128.128</string>
I would like to have the ip address (ex: 17.128.128.128) to be updated automatically from my interface ip address. So if my external ip address changes to 17.128.30.30, the natd.plist file will be automatically updated with correct values.
If I could do the following would be great but doesn't work
<key>aliasIP</key>
<string>en0</string>
Any ideas on how to get this accomplished?
Or better yet, can it be accomplished as of now?
I know I can use IPNetRouterX (www.sustworks.com) and that will work just fine. Have tested using the trial and it works, however I do not want to spend $100 for the software either, and I bet there should be a way this can be done on OSX 10.5 Server.
Thanks a lot!!!

This would be best reposted in the appropriate Leopard server forum
http://discussions.apple.com/category.jspa?categoryID=96

NAT / Port Forwarding WRV200

Hi, I would like to access a Digital Video Recorder (192.168.3.200 port 12088) from the internet (Telenet/Belgium). I'm using a Cisco/Linksys WRV200 (192.168.3.254) to access the internet. I can access the WRV200 remotely (from Internet) and I've created following port forwards: Port 8016-8016 >>> 192.168.3.200 Port 12088-12088 >>> 192.168.3.200 Connecting to the DVR internally is working fine but accessing the DVR from the outside doesn't work for some reason. Any suggestions?
Solved!
Go to Solution.

These products are being handled by the Cisco Small Business Support Community. (URL: https://supportforums.cisco.com/community/netpro/small-business )

WRT160Nv2-Problem with Single Port forward to multiple servers with same internal port numbers.

On my network I have 3 systems that I've set up as RDP hosts. And need to get to all three of them externally. So I'm trying to do the following single port forwarding.
RDP 1   Forward 4000 to port 3389 for 192.168.1.11
RDP 2   Forward 4001 to port 3389 for 192.168.1.12
RDP 3   Forward 4002 to port 3389 for 192.168.1.14
When I hit "Save Changes" I get the error "Port range already exists". So it's good that it won't let me overlap ports generally, but at the same time, I'm trying to send them to different IP address. There should be no overlap in this case. Please advise
I'm trying this on the WRT160Nv2 with firmware 2.0.02, which I had just bought this weekend.

kevj,
Thanks for your suggestion. I have now upgraded the firmware to 2.0.03 build 7. But I am still seeing the error message
As I mentioned previously, I'm trying to single port forward to multiple machines in the following way:
Machine 1:   Forward 4000 to port 3389 for 192.168.1.11
Machine 2:   Forward 4001 to port 3389 for 192.168.1.12
Machine 3:   Forward 4002 to port 3389 for 192.168.1.14
The error appears to be generated by the fact that 3389 is selected for multiple external port numbers, but the same internal port number. The router I believe isn't taking into account that the similar internal port numbers aren't taking into account the different internal ip address I'm trying to send this to.
This would be a standard sort of practice for running a live HTTP server on one machine, and a new beta HTTP server behind the router on a secondary machine on the same internal port, but different external port numbers for test purposes from the outside.
Please advise
Thank you.

Port forwarding with airport & external router

Hi,
I'm happy with port forwarding normally, but I've just made my network entirely wireless and can't figure out the answer to this problem. I have a non wired netgear router as my internet access point, an airport express is connected to this getting its address via DHCP, another airport is joined to this network, and 2 macs are connected to the airports again getting addresses via DHCP. How do I port forward to the macs using this setup? I can't figure it out. Obviously I'll need to configure manually, but if I open the port on my router and open the same port on the AX will they go throught to the mac ok. Do I map the router to forward to the AX manual IP then map the AX to a specific mac IP? Any tips appreciated before I go ahead and break my network
Emma

Emma,
Ok, here are my thoughts. Have you tried assigning static IPs via DHCP, not manual config, based on client MAC addresses? Meaning when the router sees an ethernet MAC address it always assigns the same IP to that machine. This should enable the handing out of IPs while retaining port forwarding to the same machine each time and still preserve the routing that DHCP seems to enable more betterer . I'm not familiar with the netgear setup and I couldn't get my AX performing satisfactorily for my needs either so I have returned it however this is a 'somewhat' common option when setting up DHCP on different routers and I have found it works better when daisy chaining through routers.
HTH,
Steve

ASA 5505 how to create a port forwarding rule

ASA 5505 IOS ver 9.2.3
I need to create a firewall rule that will allow internal services to be accessed externally, but using port forwarding. For example I'd like to enable access to our NAS via ftp external on port 1545 and then have the ASA forward the request to the NAS internally on port 21.
I tried these commands but they didn't work:
object network NAS
host 192.168.2.8
nat (inside,outside) static interface service tcp 21 1545
access-list NASFTP-in permit tcp any object NAS eq 1545
conf t
int vlan 2
access-group NASFTP-in permit tcp any object NAS eq 1545
I really appreciate the help everyone.

try this, it worked for me, here is an example of adding a webserver with a ip of 10.10.50.60 and naming it with a object named www-server and forwarding port 80 , the way it works is you need to do three things, u need to "nat it" "foward it" and allow it in "acl"
object network obj-10.10.50.60-1
host 10.10.50.60
nat (inside,outside) static interface service tcp 80 80
object network INSIDE
nat (inside,outside) dynamic interface
object network WWW-SERVER
nat (inside,outside) static interface service tcp 80 80
access-list Outside_access_in extended permit tcp any object WWW-SERVER eq 80
access-group Outside_access_in in interface Outside

SRP547W, How to use multiple WAN IPs for port forwarding?

Hi folks,
We've run into some difficulty trying to take advantage of multiple WAN IPs in conjunction with the SRP547, and I'm hoping someone here can help out or at least tell us that we're going to need to buy a different router...
What we're trying to acheive is the ability to port forward from our distinct public IPs to different internal servers. Looking at the options under Port Forwarding it looks like we can only configure forwards at the "WAN interface" level, but our problem is that we can't work out how to set up separate interfaces for each of our Public IPs...
Our ISP provides us with a fully managed NTU/router with a single "Internet" ethernet port, which we can use by statically configuring IPs on our end. For this configuration this port has been directly patched to the WAN ethernet port on the SRP547W.
We have been allocated a 255.255.255.248 (/29) subnet, giving us 5 usable IPs after the ISP's gateway address is taken into account, like so:
a.b.c.208     Network Address (/29 subnet)
a.b.c.209     ISP Gateway
a.b.c.210     IP1
a.b.c.211     IP2
a.b.c.212     IP3
a.b.c.213     IP4
a.b.c.214     IP5
a.b.c.215     Broadcast Address
On the SRP we've set up the default "Ethernet WAN2" sub-interface with the following details for IP1
VLAN ID:               4088 (Uneditable)
Connection Type:       Static IP
Internet IP Address:   a.b.c.210
Subnet Mask:           255.255.255.248
Default Gateway:       a.b.c.209
The next step (I would have thought) would be to add a second sub-interface, using similar info for IP2
VLAN ID:               4000 (Chosen arbitrarily)
Connection Type:       Static IP
Internet IP Address:   a.b.c.211
Subnet Mask:           255.255.255.248
Default Gateway:       a.b.c.209
When we try to do so however we get:
Fail!
Conflict with Ether_WAN2 interface address type
I should mention at this point that we're running on firmware version 1.02.01 (023).
Any suggestions on how we can proceed?
Is there a CLI or other method of configuration that might work if the web interface won't?
Thanks,
Tim.

OK, I've seen reference to this solution before but not much in the way of details. Perhaps you can spell out how this ought to work, as the Software DMZ doesn't behave as I'd expected it to.
As before, on the SRP we've set up the default "Ethernet WAN2" sub-interface with the details for IP1 with a /29 subnet.
VLAN ID:               4088 (Uneditable)
Connection Type:       Static IP
Internet IP Address:   a.b.c.210
Subnet Mask:           255.255.255.248
Default Gateway:       a.b.c.209
We'd now like to expose a server function on IP2, let's say LAN details for this server are:
VLAN:                  3000
VLAN IP Range:         192.168.1.1/24
Server IP:             192.168.1.10
Server Port:           80
So first we turn on Software DMZ:
Status:                Enabled
Public IP:             a.b.c.211
Private IP:            192.168.1.10
WAN Interface:         Ether_WAN2
My understanding, based on what you've said, is that this should expose the whole server to external access via IP2. Unfortunately, it doesn't seem to work this way - we don't seem to have any access at all. Perhaps there's a default deny rule on the firewall?
Just to be sure, I tried creating a rule to allow HTTP traffic to the server in the Advanced Firewall page.
In Interface (WAN):    All
Out Interface (LAN):   VLAN.3000
Source IP:             0.0.0.0
Source Subnet:         0.0.0.0
Destination IP:        192.168.1.10
Destination Subnet:    255.255.255.255
Protocol:              TCP
Source Port:           Any
Destination Port:      Single:80
Action:                Permit
Schedule:              Everyday
Times:                 24 Hours
Still no dice. What am I missing?
Cheers,
Tim.

Time Capsule disconnects internet when using web server through port forwarding

My current config is: 2TB Time Capsule running 7.6.3, Mac Pro running Lion (10.7.5), MacBook Pro running Mountain Lion (10.8.3), and a couple of MacBook Pro Retinas running Mountain Lion. My current ISP is Comcast.
I have the Time Capsule set up to port forward port 80 to the Mac Pro for the purpose of running a web server. Most of the traffic is shuttling fairly large m4v files back and forth to work (work product from video editing work). I can reach the webserver on the Mac Pro just fine from the outside world, and can list files in the directory just fine. When I initiate a download (via right click on a link, "Save As..." or whatever), the Time Capsule reports that the Internet has been disconnected, and all machines inside my network lose access to the outside world. I have to either power cycle the Time Capsule, or disconnect/reconnect the Cat-6 cable between the cable modem and the Time Capsule to re-establish the connection. Interestingly, the download continues and completes on the other end without issue (so, the connection is actually still there!).
Before switching to Comcast, I was on AT&T Uverse - Uverse includes a router, so I had the TIme Capsule set up in Bridge Mode. That worked fine. I also have an older 500GB 1st generation Time Capsule. I set it up with the same config as my 2TB TC, and it shows the exact same behavior - internet disconnects upon initiating a file download through a forwarded port. I then hooked the Mac Pro up directly to the cable modem. I can initiate a download without issue, and I continue to stay connected to the Internet without problem. Called Comcast anyway - they report no errors on the line, but reset the whole device chain anyway. No change in behaviors.
I tried downgrading the Time Capsule software to 7.6.2 (the earliest version that came on it). No dice, same behavior.
So... I called Apple. Complete and utter FAIL. Apple Support reports that they have no training in the port forwarding features of the Time Capule or Airport products, and cannot help me resolve the issue because of that. So, I have a $300 router that apparently cannot perform a simple routing function (download through a forwarded port), that I cannot troubleshoot (because Airport software v7 is an epic fail in that regard), made by a company who cannot support it - and everything this $300 device is doing can be done by a $50 device with a $100 external hard drive?
Do I understand this situation correctly? What have I missed in trying to troubleshoot this thing?

Apple Support reports that they have no training in the port forwarding features of the Time Capule or Airport products, and cannot help me resolve the issue because of that. So, I have a $300 router that apparently cannot perform a simple routing function (download through a forwarded port), that I cannot troubleshoot (because Airport software v7 is an epic fail in that regard), made by a company who cannot support it - and everything this $300 device is doing can be done by a $50 device with a $100 external hard drive?
Do I understand this situation correctly? What have I missed in trying to troubleshoot this thing?
Excellent summary.. I think you have covered all the salient points most thoroughly.
Port forwarding on the TC I would put into the category of "epic fail"
I have a nasty feeling it just doesn't work in many cases. Clearly from your situation the port is forwarded correctly.. it is the actual download that is causing the device to crash.. which is probably not the port forwarding itself that is at fault but rather the external link and opening another port for the download to happen.
Many of the issues were caused by using icloud and btmm.. which would work a lot better btw. Although the hassle there is needing to offer that as a service to any Tom Dick or Harry.
Let me suggest a work around or other things to try.
I also have an older 500GB 1st generation Time Capsule. I set it up with the same config as my 2TB TC, and it shows the exact same behavior - internet disconnects upon initiating a file download through a forwarded port.
Use 5.6 utility.. more info below. And take the firmware of this unit (Gen1) back to 7.5.2 (before icloud mess ups in 7.6).
You can go back to 7.5 firmware also in Gen4 TC if it is more than about 14months old.. Simply hold down the option key when you select firmware and the old versions will show up. If your TC came with 7.6.1 (the 7.6.2 was withdrawn as it was even bigger failure than 7.6.3). then you cannot go back.
You might also find downloading via http is not as reliable as using FTP.. FTP is a better and more efficient protocol. It should be no problem to setup ftp server on the mac pro to allow download via ftp even with a browser.
But in the end.. your $50 router suggestion.. well perhaps a little more than that.. $80-100 will work very well.. also this router can be setup with a Hard Disk and offer the files to the internet via FTP.. without needing full network access to your internal network.
How to load 5.6 into ML.
1. Download 5.6 for Lion.
http://support.apple.com/kb/DL1482
Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.
2. Download and install unpkg.
http://www.timdoug.com/unpkg/
Run unpkg on the desktop.. it is very simple.. drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. drill down.. applications utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.
You cannot uninstall 6.1 (now 6.2 if you updated) so don't try.. and you cannot or should not run them both at the same time.. so just ignore the toyland version.. the plastic hammer.. and start using 5.6.. a real tool.
For screen shots see this post.
https://discussions.apple.com/thread/4668746?tstart=0

Port Forwarding for L2TP/IPSec VPN Behind Verizon Actiontec MI424WR-GEN2 Rev. E v20.21.0.2

I've got a NAS setup with various services running on custom ports to help minimize exposure (especially to script kiddies). I've tested everything both internally and externally to confirm they all work, and even had someone at a remote location confirm accessibility as well. Port forward configurations performed on the Actiontec are working well.
I installed an L2TP/IPSec VPN server, tested internally and it connected successfully. So for all intents & purposes, this validates that the VPN server is correctly configured to accept inbound connections and functioning correctly.
I logged into the Verizon Actiontec MI424WR router, setup port forwarding for UDP ports 500, 1701 & 4500.
Note: I added the AH & ESP protocols based on what I saw on the built-in L2TP/IPSec rules
With the port forwarding in place, I tested VPN externally but it didn't connect.
I've done the following so far to no avail:
Double & triple checked the port forwards, deleted & recreated the rules a few times to be sure
There are no other pre-existing L2RP/IPSec port forward rules or otherwise conflicting port forward rules (e.g.: another rule for ports 500, 1701 or 4500)
There was an L2TP port triggering rule enabled, that I toggled on and off with no change
Verified the firewall on VPN server had an exclusion for L2TP, or that the firewall is off. (Firewall is off to reduce a layer of complexity, but it worked internally to begin with so I doubt that's the issue.)
Since it works internally, and there are no entries in the logs on the device indicating inbound connections, I'm convinced its an issue with the Verizon Actiontec router. But unfortunately, I'm not sure what else to try or where else to look to troubleshoot this. For instance, is there a log on the router that I can view in real time (e.g.: tail) that would show me whether or not the inbound connection attempt is reaching the device, and whether or not the device allowed or blocked it?
My router details:
Verizon Actiontec
MI424WR-GEN2
Revision E
Firmware 20.21.0.2
Verizon Actiontec built-in L2TP/IPSec rule templates. They're not currently in use, but are baked into the firmware for easy configuration/selection from a drop down menu.
Solved!
Go to Solution.

normally a vpn on that router, will have a GRE tunneling protocol as well.
two ways to build the PF rules,
Manually
Preconfigured
I know the preconfigured VPN rules will do the GRE protocol as well, but if you do it by hand you can't get it.

Port Forwarding for Minecraft - Port not recognized as open

I am trying to set up Port Forwarding to host a Minecraft server on a local machine. I am able to connect to Minecraft from within the network, but when I try to use my external IP, it fails. I have port forwarding (supposedly) set up on my Airport Extreme base station, for TCP/UDP port 25565. When I check on canyouseeme.com , it says that the port is not open. Do I have some configuration wrong in Airport Utility? I'm pretty sure it's not something wrong with my Ubuntu box (the one hosting the server) because I am able to connect to it without any problem using it's Internal IP.
Any help is greatly appreciated.

I am having this same problem. My AirPort Utility is v6.2. I have followed a tutorial labeled for v6. I cannot open my ports.
I have a static IP address with the following:
Router Mode: DHCP and NAT
I increased the DHCP Range so it would include the static IP address I selected.
DHCP Reservations
Description: Minecraft
Reserve Address By: MAC Address and entered my MAC address
IPv4 Address: the static IP address that I created in System Preferences- Network
Port Settings
Description: Minecraft
Public UDP Ports: 25565
Public TCP Ports: 25565
Private IP Address: same as above which is the same as the statis IP address
Private UDP Ports: 25565
Private TCP Ports: 25565
I also checked with Comcast, my internet provider, to make sure they were not blocking port 25565. The person on the chat said that that port was open.
I have been using yougetsignal.com to check if my ports are open and so far nothing.
Does anyone have any suggestions?

WRT54G2 - Port Forwarding is not working properly?

I have a WRT54G2 model #1 with firmware Version 1.0.00 setup as a static IP address connection from my data provider. The router provides service to an Internal IP network of 10.50.6.___. The connection is working properly and I am able to access external IP's from all internal computers. I am attempting to have all inbound traffic on port 9100 forwarded to 10.50.6.49 (a network printer). I set up port forwarding and enabled it according to previous posts in this forum, and I see the inbound traffic in the log, but nothing appears to be getting to the printer. I am able to ping the printer from the router, and print to it from internal PC's. I am fairly new at this process but know enough to be dangerous. How can I tell if the traffic is actually being routed to the printer or is getting lost in the router?
Thank you!

Hey try resetting the router reset button in such a way that power light is blinking on the router & then do a complete network power cycle i.e., unplug the power cables from the modem & from the router & then plug in the power cable to the modem first once all the lights are solid green you could plug in the power cable to the router & check out it will definately work!!

Port forwarding doesn't appear to be working.

I'm trying to port forward my RDP ports on my Airport extreme so I can access my Windows machine from outside my local network.
I've forwarded port 3389 to the correct IP but I can't connect. I can connect from inside my network by using my internal IP address but if i try to connect with my external ip address it will not connect.
I've disabled the windows firewall but this was all working on my netgear router that I had before I got the airport extreme.
I've also tried port scanning the router from my mac mini and it does not detect that port 3389 is open.

I was able to get it working by making my main machine the default host but I would prefer to not expose my main machine to the internet like this. Any idea why it's not working?

Port forwarding

wondering if anyone could walk me through port forwarding on a westell e90 610015-06 router. I am trying to set up TCP and UDP for a P2P program(e-mule). After several attempts i can't seem to set it up. Thanks!

Here is what I have set up
Services:
1. imapssl_993t_in all 993
2. imapssl_993t_out 993 all
Exceptions
1. imapssl_993t_in Public Any Public PUBLIC_IP_OF_BM_SERVER (I only want it coming in on this address)
2. imapssl_993t_out Public PUBLIC_IP_OF_BM_SERVER Public Any
Proxy - Generic TCP
original (internal_ip_of_imap_server) port:993 Proxy address: PUBLIC_IP_OF_BM_SERVER port:993
Access rule
Very generic, just allow original port with value of 993.
>>> akeaveney<[email protected]> 1/9/2013 11:46 AM >>>
JackCunha;2122118 Wrote:
> BM 3.8, fully patched; NW 6.5.8. An internet backup service says I need
> to forward external port 443 to the internal backup server's port 4282.
> I have a stateful filter exception for port 443 on my BM server, with
> the destination being the public address of the BM public NIC. Can i
> accomplish what want to do. If so, how?
I am trying to setup this at the moment, yet for IMAP access from
outside to internally. I don't want to hijack the thread, yet someone
might be able to help us both.
I have setup the generic tcp proxy under the BM Server in Imanager and
setup the private address and public proxy address with the port numbers
I want. I also allowed a filter exception from all interfaces to public
and allow the destination as the BM public address, but this still won't
work for me,
Is there something I am missing? I have tried it with the filters down,
but it doesn't seem to be doing the mapping.
Many thanks,
Anthony
akeaveney
akeaveney's Profile: http://forums.novell.com/member.php?userid=6365
View this thread: http://forums.novell.com/showthread.php?t=442041

WRV200 Port forwarding internal/external

Similar Messages

Maybe you are looking for