Port Forwarding from TimeCapsule to QNAP NAS

Hi there,
I just read the posing under
https://discussions.apple.com/message/12003510?messageID=12003510
but it does not solve my problem. I have opened all the ports on my time capsule that are required fro my QNAP NAS, but everytime I enter the WAN IP of my internet router (ATT DSL modem) I only get to the modem admin page. I have entered the IP address of my NAS as the PRIVATE IP ADDRESS in the time capsule settings and also have followed all other steps. not sure what I am doing wrong. would be great if someone could point e in the right direction.
thanks

Hi Arvind,
We can do redirection oURL from HTTP to HTTPS by adding some parameter in instance profile.
But, in earlier reply you said you are going to block port 80, in such case you can't do redirection from HTTP to HTTPS from port 80 to 443
for e.g
user is giving URL :- http://www.test.com and you want to redirect it to https as :- https://www.test.com
Above example can only work when port 80 is open.
if you are using http port as 8080 in this case redirection can work as below
user is giving URL as :- http://www.test.com:8080 , it will get redirect to http://www.test.com
so redirection of HTTP without port in URL will redirect to https in scenario where port 80 is open.
any query pls reply.
Thanks
Anil

Similar Messages

How to do port forwarding from wla2-g54l Buffalo bridge to mac mini

Hi,
I am trying to get Azurus to remove the "firewall block" message and I think I have narrowed it down to port forwarding.
I have set up port forwarding from my X modem to the Airport Xpress base station. I have then set up the port forwarding from the base station to the buffalo.
The problem I have had is setting up the wla2-g54l to forward the same port to the mac mini....
any Ideas? Not much luck on the Buffalo website.. and I have RTFM. Many times!
Cheers
Mac Mini G4 1.2Gz Mac OS X (10.4.8)

It sounds like your set-up is in a horrible mess with 3 levels of NAT going on.
What you should really have is the X-Modem configured in it's default mode "Modem Mode" where there will be no need to do any port forwarding as the modem is acting as a pure modem without having any influence over ports.
Then the Airport express should be configured to "Distribute IP addresses" so that the Airport is acting as a router. I presume that you use the Buffalo unit as a repeater for the AIrport so you should set-up WDS so that both are on the same network. Then your computers will all be using IP addresses in the 10.0.1.x range as issued by the Airport. You can then configure the Airport to directly forward ports to the IP address of your computer. Therefore only one instance of NAT and only one set of port forwarding rules.

Rv320 - port forwarding from a specific WAN IP

Hi, i just received and configuring the rv320 router. I can successfully set the port forwarding from WAN to specific LAN IP address. I would like to know is it possible for this device to set the port forwarding from a specific WAN IP address? Thank you for the help.

I have the same problem, and have already tried creating a Access Rule without success. I need to forward Remote Desktop Port 3389 from a specific public IP address to a internal server. I do this with other lower-level Cisco Small Business routers all the time, but cannot get this to work with the RV320. Here's what I've tried:
1) Create new Access Rule
2) Create new Service called TS for TCP port 3389-3389
3) Set new Access Rule to Allow
4) Set Source Interface to Any (I've also tried WAN1, etc.)
5) Set Source IP to the only single public IP that will be allowed
6) Set Destination IP to the single internal IP address
7) Set Scheduling to Always
When I use any standard RDP app from the outside, the router blocks 3389 access.
What am I missing? Can anyone help resolve this, or do I need to call in to Cisco Support?

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.

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.

Port forwarding in Solaris 8

Hi,
I am new to Solaris and am trying to set up a simple port forwarding from port 80 to 8080.
I know how to do this in Linux:
iptables -t nat -I PREROUTING -p tcp dport 80 -j REDIRECT to-port 8080
but cannot find a way to do this in Solaris. I have installed SunScreen, but am not sure whether this is the right thing to use.
This is a simple server in a hosting centre.
Can anyone help?

In solaris you can do port forwarding with ssh . You have to install SSH from soalris 2 of 2 CD .
see man pages of ssh
Regards

Help: Port forward in Cisco SOHO 97

Hi there!
I have a Cisco SOHO 97.
The IP is: 10.0.0.1/24
Gw: 0.0.0.0
*Default route via DIALER1
I also have a RV042 configured as VPN Server (PPTP and IPSec).
The IP is: 10.0.0.2/24
I need help to configure the router to I be able to connect to VPN server from OUTSIDE-WORLD.
I imagine I need Port forwarding from Cisco SOHO to RV042.
I hope for possibles answers!
Thanks!

Sorry i found the issue.
The problem was that, i wanted to redirect port 443 (https) to an private address.
But by default port 443 is reserved to access ASA via https for management.
I just reserved another port 888 for https management access and now i can redirect port 443 normaly as i wanted.
Using this command: http server enable 888
Germain

RV220W port forwarding an 99% CPU usage

Hi,
I made a custom port forward using tcp ports 2121-2130 to a private IP address on my network (192.168.1.8). Whenever I do this, RV220W CPU usage spikes to 98-99% and my Internet connection starts lagging a lot. Just disabling the port forward from the administation console fixes this. I'm running the latest firmware.

Taneli,
There is a problem with port forwarding in RV220W please read the release notes for 1.0.3.5 for work arounds
Jasbryan

WAG320N port forwarding to wireless client/bridge client

Hi,
My network looks like the above diagram:
1. Wireless bridge connections.
ADSL Line ==> WAG320N (192.168.1.1) == bridge client mode ==> TP-Link WR941ND (192.168.1.4) ==> Client (192.168.1.11)
2. Lan connections.
ADSL Line ==> WAG320N (192.168.1.1) == cable connection ==> Client (192.168.1.100)
3. Wireless AP conenctions.
ADSL Line ==> WAG320N (192.168.1.1) == wireless connection ==> Client (192.168.1.106)
Port forwarding from WAN to LAN (scenario 2) clients works great, but I have problem with wireless clients (scenario 1 and 3). Accessing the wireless destination from LAN is possible. Also pings from WAG320N to the wireless destination looks OK.
PING 192.168.1.11 (192.168.1.11) 60 bytes of data.
60 bytes from 192.168.1.11: icmp_seq=1 ttl=63 time=1.69 ms
60 bytes from 192.168.1.11: icmp_seq=2 ttl=63 time=1.62 ms
60 bytes from 192.168.1.11: icmp_seq=3 ttl=63 time=2.23 ms
60 bytes from 192.168.1.11: icmp_seq=4 ttl=63 time=1.60 ms
60 bytes from 192.168.1.11: icmp_seq=5 ttl=63 time=2.12 ms
60 bytes from 192.168.1.11: icmp_seq=6 ttl=63 time=3.78 ms
60 bytes from 192.168.1.11: icmp_seq=7 ttl=63 time=1.61 ms
60 bytes from 192.168.1.11: icmp_seq=8 ttl=63 time=1.56 ms
60 bytes from 192.168.1.11: icmp_seq=9 ttl=63 time=2.08 ms
60 bytes from 192.168.1.11: icmp_seq=10 ttl=63 time=3.37 ms
--- 192.168.1.11 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9002ms
rount-trip min/avg/max/mdev = 1.569/2.172/3.788/0.748
Forwarding external port 9090 to wireless client (192.168.1.11:80) is not working. I am thinking of resetting to default settings. What do you think?

nicebilal_007 wrote:
Hope ! You are fine.I am using LINKSYS WAG320N since 10 days.I am facing no. of issues.If wifi is on & i connect "LAN PORT OF MY PC" to LINKSYS WAG320N or with ADSL Modem.My LAN doesn't work.
When i am using wifi,it frequently disconnects or doesn't work.
There is no fault from my ISP Provider.
Anyone can address my issues...Thanks a lot....
From:Bilal Ali-Pakistan
[email protected]
0092-344-7127679
Reset the WAG320N then check if you are getting a valid ip address to know if it is still assigning an ip address to the network. To reset, press and hold the reset button for 30 seconds while the power on. After that, release the button and power off the WAG. Leave it off for 30 seconds then power it back on. Wait for the power light to stop blinking then check if you have a valid ip address with the computer. You may click the link below on how to check the ip address of the computer:
Title: Checking your computer’s IP address
Article ID: 3996
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=d02ed3aa3e704caea42f5c007b8c6472_3996.xml&pid=80&r...

How to Port Forward on Cisco 1900 Router?

We have a cisco 1900 router. I m new to cisco routers commands, recently started learning. I need to forward all requests coming from port 1723 from outside to inside server ip. I check "show running-config" and I see already forwarded ports and ip like below,
ip nat pool onlyone xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx netmask 255.255.255.252
ip nat inside source list 1 pool onlyone overload
ip nat inside source static tcp 192.168.0.xx 22 xxx.xxx.xxx.xxx 22 extendable
ip nat inside source static tcp 192.168.0.xx 80 xxx.xxx.xxx.xxx 80 extendable
ip nat inside source static tcp 192.168.0.xx 80 xxx.xxx.xxx.xxx 96 extendable
ip nat inside source static tcp 192.168.0.xx 443 xxx.xxx.xxx.xxx 443 extendable
ip route 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is public facing IP.
so what is the command to add "ip nat inside source static tcp 192.168.1.xx 1723 <public-ip> 1723 extendable" to currnetly working settings?
I am currently reading below but no luck so far...
http://www.cisco.com/en/US/docs/routers/access/1900/software/configuration/guide/software_configuration.pdf
I have found this
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094e77.shtml#topic7
interface ethernet 0
ip address 172.16.10.1 255.255.255.0
ip nat inside
!--- Defines Ethernet 0 with an IP address and as a NAT inside interface.
interface serial 0
ip address 200.200.200.5 255.255.255.252
ip nat outside
!--- Defines serial 0 with an IP address and as a NAT outside interface.
ip nat inside source static tcp 172.16.10.8 8080 172.16.10.8 80
!--- Static NAT command that states any packet received in the inside
!--- interface with a source IP address of 172.16.10.8:8080 is
!--- translated to 172.16.10.8:80.
How do I know if "interface ethernet 0" and "interface serial 0" will work for me?

the router is already setup and working for 2 years. all i need to do add a simple port forward from public ip to internal server. Following make sense to accomplish what i m trying to do. Lets assume 1.2.3.4 is my office public static ip and 192.168.0.10 is my internal server. All requests will come from some Ip lets say 25.24.23.22:1723 to 1.2.3.4:1723 and router will forward this request to 192.168.0.10:1723. This is all i m trying to accomplish. I m not setting up a new router. Some rules are already there. Therefore below seem to be what i need. All I need is how to identify "interface ethernet 0" & "interface serial 0". I understand the inside and outside details. All i have to find is how to replace ethernet 0 and serial 0 with what i have in my router setup.
interface ethernet 0
ip address 172.16.10.1 255.255.255.0
ip nat inside
!--- Defines Ethernet 0 with an IP address and as a NAT inside interface.
interface serial 0
ip address 200.200.200.5 255.255.255.252
ip nat outside
!--- Defines serial 0 with an IP address and as a NAT outside interface.
ip nat inside source static tcp 172.16.10.8 8080 172.16.10.8 80
!--- Static NAT command that states any packet received in the inside
!--- interface with a source IP address of 172.16.10.8:8080 is
!--- translated to 172.16.10.8:80.

Actiontec Rev. F port forwarding - is filtering by IP possible?

I would like to know if Actiontect Rev. F router allows filtering by IP address for port forwarding (similar to Windows 7 firewall, Advanced Settings, "Scope" tab). That is I want only requests from specific external IP address to be allowed through.

Points to your other thread at
http://www.dslreports.com/forum/r26265890-Windows-7-firewall-and-port-forwarding-from-FIOS-router
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Actiontec MI424WR rev I port forwarding issue.

Within the last month, all of my wireless security cameras as well as my Directv DVR have stopped responding to remote access. All of the cameras work fine when directly connected to an e-net cable. I have checked all the settings on the router and they have not changed. I then tried to check the ports assigned to the cameras and found that they are all reported as CLOSED by two different internet port checkers. However, these same port checkers report eveything closed on this router., but my browser, email, remote desktop all work ok. Before I tear any more hair out, can some one have pity on an old fart and tell me what I have overlooked????
KentM
Solved!
Go to Solution.

I had a session with a VZW tech who in turn brought an Actiontec tech on the line. What we did was to delete all of the current camera rules and reinstall them. Everything now works. ?????
THe one remaining issue regards the port checkers that show all the well known ports closed. We never came up with an answer to that. But they are not stopping anything from working. One other item regarding the camera ports. If the camera is not on for some reason, then the port will show that it is closed...
CaptainSTX wrote:
Not that I have an answer for your question but misery always loves company.
The prior firmware update for the Actiontec knocked out the automatic update using DynamicDNS.
The 10/31 update fixed the problem of updating DynamicDNS however it seems to have done something to port forwarding.
Prior to the last two updates of the Actiontec's firmware I used to be able to run an FTP server on a USB drive connected to a router double NATed behind the Actiontec. I was also able to remotely access certain devices using port forwarding from the Actiontec. Not working anymore.
Based on your problem I think it is a firmware issue with the Actiontec and there may be nothing that can be done until the next firmware update.

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 to multiple computers

Hello,
I am port forwarding from my AirPort Express to my tower so that I can connect via sftp. This uses port 22. If I wanted to connect to another one of my macs at home with sftp can I simply give it any port I want and opn that port in the firewall? Or is there a way to port forward on the same port to multiple machines (which seems weird).
Thanks for your any help.

You would use a different public port but the same local port on that Mac.
So your port mapping rule would be:
Public port: 222 (or whatever)
IP address: IPAddressOfYourMac
Private port: 22
In this example, the device on the Internet would need to use port 222 to access that Mac.

Lync Edge and Proxy server public DNS records port forwarding rules

Hi All
I have question in regards to port forwarding rules for port 443 of simple url.
I have 4 public ip addresses.
1 edge server (4 nics , 3 running with different ip for sip, meet and dialin in DMZ network, 1 connected to internal local network).
1 proxy server (2 nics, 1 running with an ip which is in DMZ same as edge, and 1 connected to internal local network)
1 front end (lync 2013 standard installed.) connected to internal local network
1 office web apps . connected to internal local network
The question is that I am using 3 public ip addresses respectively on public DNS records for sip, meet and dialin(av) and using port 443 which has been set on edge server. So , I can use 3 DMZ network ip address on edge for sip, meet
and dialin (av) port forwarding from 3 public ip addresses as per in Microsoft document.
However, I also have a reverse proxy .Hence, my understanding is all public DNS records except SIP and port 443 should be pointed and port forwarded to reverse proxy ip address which is in DMZ network as it would redirect 443 and 80 to 4443 and 8080 to front
end.
Now the question has been clear, if simple URLs public DNS record and port forwarding rules for port 443 should be pointed to reverse proxy server, why they need to be set on each ip address and port number in Front end server topology to edge server?
If anyone knows, please give a help how to set it correct and what is supposed to be a correct configuration for a topology lync 2013

Hi George
Thanks for your reply. Attached is my topology which could make my it bit clear. You may see the public dns host record from the image. I set sip, meet, dialin , and owa 4 host records. The first 3 records are pointed to lync edge by doing a NAT with port
443 which is the same as per you said. However my understanding is they should be pointed to reverse proxy instead as for instance, I need meet.xxx.com with port 443 to be redirected to port 4443 through reverse proxy server to the front end. So when the external
customers who do not have lync client installed to their machine then we can shoot a lync meeting and send to them via outlook and they just need to click on join lync meeting link in the email to join in such a meeting based on IE. (Is my understanding correct?)
If lync web meeting works like so , then the question is why I need to set three SAME addresses in front end topology builder for edge and make them point to edge server instead?　
１. Access Edge service (SIP.XXX.COM) ---> I understand that it is used for external login lync front end.
2. Webconf edge server(Can I set to meet.xxx.com which is the same as simple URL that points to reverse proxy?) ----> If I can set this address to be the same as simple url address that points to reverse proxy, why should it need to be NATed to edge
instead? TO BE HONEST, if I HAVE tested, if I set this url as sip.xxx.com which means to use a single FQDN and ip address with port 444 and points simple url meet.xxx.com to reverse proxy, it will still work to join lync meeting sent by
outlook.I DO NOT REALLY UNDERSTAND WHAT this URL used for at this stage.
3. AV edge --- same as webconf
Regards
Wen Fei Cao

Port Forwarding from TimeCapsule to QNAP NAS

Similar Messages

Maybe you are looking for