I am trying to setup port forwarding

I am trying to setup port forwarding for a mfi 5510l hotspot. I have made the changes on the hotspot but the hotspot doen't respond when tested. Can anyone help?

If you examine the About section of the Jetpack’s web style user interface, you should find that it has a reserved IP4 IP address. That means your Jetpack doesn’t connect directly to the public internet, your Jetpack is connected to Verizon’s private network. Your port forwarding has no affect on Verizon’s private network.
The standard recommendation is:
Purchase a public facing static IP address from Verizon for a one time fee of $500.
Use a VPN to go around the issue. 
Use another ISP that provides a static IP address.

Similar Messages

  • How can I setup port forwarding for RDP (3389) using MHS291LVW?

    Hi,
    I went into my MHS291LVW and I enabled port forwarding.  I didn't see an option for Remote Desktop (RDP) so I added a custom application called RDP and I set "Global Port" and "Private Port" to port number 3389 and I set it as TCP/UDP and then entered the local IP (192.168.1.135) of the PC I want to connect to.  I made my local PC use a static IP so this 192.168.1.135 will never change.
    Then when I go under "About Jetpack" I see that there is a WAN IP address listed; so I wrote this down and then I tried to connect remotely to this PC from outside the Verizon Jetpack network but it didn't work.
    Then the strange thing is when I go to Google and type "what's my IP", Google shows me a different external WAN IP address that Verizon Jetpack showed me in the admin web interface.  Anyway, I tried this WAN IP address that Google gave me but it still didn't connect to my local PC.
    Can someone please help me in figuring out why this is not working?
    I've setup port forwarding on plenty of other routers (Linksys, Netgear, etc.), but I never tried it on a Verizon Jetpack MHS291LVW but it should work the same so I'm not sure why this is not working for me.
    Thank you!

    > If I can't use the "Microsoft Windows RDP" service because of the private IP; would I be able to use a software like "TeamViewer" to gain access to my PC?
    Yes.  This is how a VPN server works around the private IP address restrictions of the VZW network.  It will work and you will be able to access anything that is centrally connected to a VPN server. 
    > Also, if I were to take the VPN option and setup a VPN server on the PC
    Not on the remote PC silly guy.  Hosting a VPN from within the VZW network wont do you any good as its IP will be masked by the NAT firewall.  You must setup a VPN server off of the VZW network for it to work.  That way when you remote into the VPN server it is already outside of the VZW NAT that is restricting you in the first place.  There are many VPN vendors that you can test out and pay access for if you don't have any interest in setting up one on your own.  Some are free where others charge more money for more bandwidth and customization features.
    > If I were to try to connect to this PC on the JetPack side from an external PC on a different network I don't know how I would be able to access it since the JetPack IP address is private.
    The idea is that everything rests on the VPN server when remote connections are made.  The Jetpack PC, VPN Server and your current local PC all connect to the VPN server so everything is then local communication.  The VPN will make it appear as though everything is virtually connected to the same appliance even though they are physically separated by whatever distance you want.

  • How do I setup "port forwarding" on a Time Capsule on Mountain Lion?

    I am trying to set up a Foscam FI8910W so that I can access it remotely.  I have some tutorials about how to do it, but most seem to involve using an old OS and I'm getting hung up at the step that involves setting up port forwarding.  I have never done this before and I'm flummoxed.

    Tap AirPort Utility
    Tap the AirPort Extreme icon
    Tap Edit
    Tap Advanced
    Tap Port Settings
    Tap New Entry
    Enter the port type and values provided by the manufacturer

  • 2 WTR54GX2, trying to do port forwarding

    Hey all, So heres the thing, I have two WRT54GX2's in my network. One is the gateway router (192.168.1.1) and the other is quite a distance away and is the secondary (192.168.100.1). I want to set up a SlingBox on port 80 so basically a webserver. But due to restrictions of cabling and what not I have to attach it to 100.1 the secondary router. My question is how do I make this work with port forwarding? Because I can set the slingbox up with 192.168.110.12 and then port forward it on the secondary router and make it work, how do i do it on the gateway router, as I understand it, in order to port forward the device has to be on the same subnet as the router, but two routers on the same subnet is a PAIN. And the both routers have hardwired devices and wireless devices. Any help would be appreciated. Cheers! _KN

    brickmonkey, i really aprecieate the help. I have one more question tho (i know this whole thing must be getting annoyin, sorry :/), when i do the static IP i tried setting the "Internet IP" as 192.168.1.34 but it gave me an error along the lines of "Internet IP cannot be on the same subnet as the gateway", so what IP do i give the second router? As I understand it, in order for the 1st (gateway) router to portforward correctly, the port its forwarding has to be on the same subnet. Any advice?

  • HELP!! Cisco RV180 Port Forwarding

    Someone please advise as to this is the first time I've tried to setup port forwarding using the Cisco RV180 Router. I have a Cisco RV180 Router, a Ruckus 7055 access point and a power distribution unit. I'd like to be able to access the router remotely and also the devices behind the router (the ruckus access point and the power distribution unit). I'm assuming that I'll need to assign the Cisco RV180 router a static IP address and I'm assuing that this static address should be assigned to the WAN port? I'd also like to configure port forwarding so that I can access the ruckus and the PDU remotely also. I've tried assigning a static IP address to the WAN port of the RV180 but I cannot ping this device remotely. Anyone have any advice on accessing the RV180 remotely? I've populated all of the correct fields for the WAN settings (ip, gateway, subnet, etc.) , and my static ip address is valid.Thank you in advance.

    Hello sirflex,
    As you have mentioned you need to configure a static nat for the devices which you have done when you configure a port forwarding.
    Have you configured access rules under firewall>access Rules. Add the access rules for the ping and the Http and Https services.
    Can you capture the packets at the WAN port while you are pinging the WAN port and the firmware version on the device.
    Which mode are you running the device gateway or router. You can check it under Netwroking>Routing>Routing Mode.
    Thanks,
    Prithvi
    Please mark answered and rate for helpful posts.

  • Help with port forwarding for the WRT54G

    I need assistance please!
    I am having issues trying to setup port forwarding for a ftp. I already have set this up for a SQL Server port and it works remotely. When I setup another rule for ftp using port range 20-21 it does not work.
    I have confirmed that I have saved my settings, have the correct IP address, etc. I have firmware version 4.21.1 and not sure how to troubleshoot this. Any help would be great.
    Thanks,
    John

    Yes you do need to have the port already forwarded for port 20~21 with both TCP/IP and UDP enabled unless you know for sure your ftp only uses just one of them.  That is why I asked what port your SGL was set to.  Follow the link that other guy posted and open port 20 and 21 (I only use 21 with no problems) and make sure it is directed to the IP of the ftp host.  Also that PC needs to have the FTP enabled in windows.  To do that go to your control panel > add/remove software > and on the left side go to add/remove windows components.  Then check the box for the ftp and add it.  It should ask for your windows CD do have it handy when you add the ftp component to your PC.
    Richard Aichner (Ikester)

  • Home Hub 3 Port Forwarding (NOT)

    Hello World
    Ok recived the New Home Hub 3 today, ahead of my Infinity install.
    I thought ok lets replace Trusty Home Hub 2 with the 3 as it works both on Std ADSL and Infinity
    Super Quick UI and love the GIG port BUT and its a BIGGY (well for ME) !
    THe hub is running 4.7.5.1.83.8.48 (TypeA) lastest and greatest, Upnp does work so Xbox works no prob and it can be seen in the FW Log being setup 
    BUT if you configure port forwarding by hand ie HTTP to 192.168.0.2 DOESNT WORK !!!
    I tried using a connected device to forward to and just the IP address BOTH FAIL !
    roll back in trusty Hub2 and all work again !
    Phoned in and was told after a few minutes on hold (No Problem) to roll back to Home Hub 2 and there should be a Firmware upgrade for the 3 soon to fix this issue.
    So now you know if you try it and it doesnt work
    Giz
    Solved!
    Go to Solution.

    Similar situation here.
    I received HomeHub 3 this week. Overall, I am pretty satisfied with the new router. The local networking feels quicker due to the gigabit port (connected to gigabit switch). And the wifi reception is better probably due to the intelligent channel selection.
    Similarly, I tried to replicate settings from my old HomeHub 2. I wasn't able to setup port forwarding.
    The problem is the router in inaccessible using the external IP address.
    I contacted BT Broadband Help desk. I spoke to 2 operators. First told me he would investigate and call me back. Never did. Second told me they were untrained to deal with this sort of queries and suggested speaking to the BT Subscription help line.
    So, now I know thanks to you. Waiting anxiously for the patch. Hope it will be out soon.
    Slava

  • Port-forwarding or UPnP on VERIZON FIOS modem/router

    I'm trying to help someone access his home network remotely from another location. he just got the new Verizon FIOS network.
    i'm new to the world of port-forwarding and UPnP forwarding, but have learned a lot in a short period of time.
    I can easily setup port-forwarding and UPnP forwarding (necessary to setup the afp file sharing, screen sharing, etc) on Linksys routers that have those capabilities.
    My friend just got the new Verizon FIOS network installed. It is smoking fast both up and down. We figured out that the box Verizon provided him (it's a fairly huge thing) is an internet modem, a router, and a wireless router all in one.
    And once we accessed its control panel, I definitely saw places where we could configure port-forwarding........
    but it's not quite as straightforward as it is on a Linksys router in that, on a Linksys, if I want to open a specific port, like 5900, for screen sharing, I can easily type in the numbers 5900 and type the IP address of the computer on my LAN that I wish to forward port 5900 traffic to.......or I can do this with UPnP forwarding....either way it is simply and fully controllable.
    But on this Verizon box, it seems to have most standard ports and protocols stored in presets that you must choose from. For example, if I wanted to setup port forwarding for FTP traffic, I would choose FTP from the dropdown menu and then the router would automatically know to forward port 21 to the computer of my choice.
    but we specifically want to turn on AFP for apple file sharing, which is port 548. On the Linksys, i could simply type port 548. But this Verizon router does not show a service called AFP. It has a nice LONG menu of many different pre-set options, but AFP is not one of them. Would it be called something else on a device like this that is obviously not specifically designed to know Apple's file sharing protocol?
    So would anyone know what kind of service I should look for that opens port 548 for file sharing?
    Anyone have experience with these new Verizon routers/modems yet? I'd really love to find a way to type everything in manually, but I dunno if that's possible on this unit.
    i know there's a lot here. thank you to anyone who knows about this and can shed some light

    That doesn't work because applications that initiate outbound connections are given randomly assigned 5-digit port numbers (e.g., 49144) through which the CLIENT communicates. The "well known" port numbers like 548 for afp, 22 for ssh, 80 for web servers, etc., are for the SERVER function to which the server daemon listens. Example: you don't send the request to download your email from your pop 110 (or 995 when using SSL), or from your imap 143 (or 993 when using SSL); that's the port number at the DESTINATION server to where your traffic is delivered, i.e., the port to which that SERVER is listening for incoming traffic. Same for when you send mail, you send from some randomly assigned five-digit port number TO the smtp server's port 25. You can see this by launching Terminal.app from an admin-privileged account and typing sudo tcpdump -i en1 (use en1 for airport, en0 for wired ethernet) and looking at the packet transmissions' headers.

  • Port Mapping / port forwarding - help please...again...

    Hi,
    I am trying to use port forwarding/port mapping but after numerous failures to access my computer from an Internat connection, I am seeking advice or guidance. 
    I have a 2011 Apple Time Capsule, and under the Advanced tab on Airport utilities, Port mapping I have chosen +
    it then comes up with a box in which I have entered the following:
    Service - drop down menu (number of options...but have been advised on other threads to leave as is)
    It then has 5 boxes:
    Public UDP port(s)  - 9080
    Public TCP ports(s) - 9080
    Private IP adress    - 10.0.1.x
    Private UDP Port(s)  - 9080
    Private TCP Port(s)   -9080
    note I have enabled NAT port mapping protocall. My ISP has advised that I cant use port 80 for some reason...but all others should be ok
    note also the 10.0.1.x is a static address i have assigned to teh camera.
    I have a dns provider, and when I use the URL on my LAN - I can access the camera....but as soon as I tryu to access via the WAN - it is unable to reach the server.
    Other points - the TC is in normal mode (i.e. not Bridge)
    Does anyone have any idea if I have set port mapping up correctly; any way i can test, any ideas how i can fix this??
    I have tried this on a number of forums thus far - but no success to date.
    Welcome all and any help!!!

    LaPastenague wrote:
    Have you reset the camera web page to use 9080?
    i have checked again and in teh advances settings of my camera - it asks for HTTP port, HTTPS port, and for Nata Traversal it asks for an alternative HTTP port.   I have entered 9080 against all of these.
    The TC is in normal mode ie as a router.. what modem do you have in front of it? Is it in bridge? Does the TC get the public IP or does the modem route the address as well? You will have no success via double NAT.
    not sure what brand the modem is - but i can confirm it is set up as a modem only with both the router and wireless functions turned off.
    The Modem is not in Bridge mode - neither is my ATC.  The ATC gets the public IP address via the adsl modem.  so double NAT should not be an issue
    When you say you can access the camera using URL on lan, is that using the new port 9080? Please give explicitly what address you use.. (you can hide the full public address) and port.. and AFAIK this should NOT work as the TC would have to handle NAT Loopback which would amaze me if it does. According to all the info around the web the TC has no NAT Loopback and therefore should not be able to handle the address. I need to know therefore the exact address you use
    this is actually using the url that my dns provider provides to me as i do not have a static ip address.   albeit this appears temperamental as to when it works sometimes from my LAN. after which it requests user name and password and I can then see the live stream.
    one problem I have just noted is that when checking teh DNS setup - it still appears to default to port 80 which my isp has advised i can not use) so i am checking with teh dns provider how i change this.
    The good news is port mapping must work on my ATC, as I have just set up my slingbox using their automatic port mapping assistant and it seemed to set up with no issues...i have also just confirmed that the stream can be viewed on the internet.  

  • Cant get port forwarding working, please help :(

    I bought an airport extreme yesterday, and since then ive been trying to get port forwarding to work. I've set it up before on other routers, and while its always been a hassle, this is the first time where I might just give up and take the router back. I've been searching the boards for solutions, and ive implemented several of them without success, and a call to apple's tech support got me nowhere. Im sure im just using the wrong number or setting somewhere, but I just cant seem to find it.
    One suggestion i read was to set up the routers connection to my modem manually, instead of through dhcp. When I switched from dhcp to manual, i noticed all the prior numbers except dns servers stayed entered, so i wrote down the ones from when it was set for dhcp and typed them in. My manual setup is:
    I.P.: 68.197.191.59
    subnet: 255.255.224.0
    router: 68.197.160.1
    dns: 167.206.245.68
    167.206.245.69
    every other setting i left on the default.
    the dhcp range is 10.0.1.2 - 200
    One entry recommended a static ip. I originally set one up with the dhcp reservation feature, but then another post said your ip should be outside the dhcp range. Not sure if either method is better, but ive set my system with the following static ip:
    i.p: 10.0.1.201
    subnet: 255.255.254.0 (i was unsure what to enter here, so i chose the same as the routers)
    gateway: 10.0.1.1
    in port forwarding i made an entry with 60000 for the 4 public/private tcp/udp and an ip of 10.0.1.201 (i have tried many other port numbers in the odd chance that the one i picked at random might have already been in use)
    I left every other setting on the defaults. The nat settings (a setting im not familier with) is current set for enabled with the default host box above it empty.
    I should mention, my pc is wired to the router. I am using utorrents port checking site, as well as canyouseeme.org. Neither can ever see my port, one simply says not open, the other says connection refused.
    I hope someone out there can help me with this, as the router is great with this one exception, and I'd rather not return it.

    For starters, it's probably not a bad idea to "factory reset" your device since it sounds like you've had a lot of people giving you different advice. This isn't to say that you've been given *bad advice* but, it may make things easier for a trouble-shooter if you start over from a "known" state.
    That said:
    You need to setup manual port mapping. The problem is, when somebody from the outside tries to access your computer, the Aiport (for lack of a better analogy) isn't expecting any visitors; so it turns them away. ---That matches what you are seeing from canyouseeme.org etc...
    Your error was when you "made an entry with 60000 for the 4 public/private tcp/udp and an ip of 10.0.1.201" Essentially all that will do is make a mapping for one port. Port "60,000" which to my knowledge, isn't used by anything.
    You have to tell the Airport specifically what "outside" ports (each and every one) that you want routed to what "inside" ip address.
    I use:
    Public TCP: 22,80,443,27900,13405
    Public UDP: 123,7777-7783, 13405,6881-6999
    Private IP Address: 10.0.1.201
    Private TCP: 22,80,443,27900,13405
    Private UDP: 123,7777-7783, 13405,6881-6999
    This enables: telnet, http, ssh, bittorrent and unreal tournament from the outside and routes ANY AND ALL TRAFFIC from those ports to my PC at 10.0.1.201 on the inside.
    If I ran AIM, or ICQ or one of those things, then you need to add the ports that that system uses to the list also.

  • Port Forwarding Question - Detailed

    Hi,
    I hate wasting people's time, so I will give you very detailed information.
    So here's an overview of the network. I have a WRT54G with V4.21 firmware on it. I also have a WRE54G Range Expander. Both are secured. We have 3 desktops, 2 laptops, and some game consoles hooked up to the wireless internet, with nothing connected with an ethernet cable (all wireless).
    A friend and myself want to play an online game, which requires one person to be a server, and one to be a client. He doesn't have access to his network configurations, so I will end up being the server.
    I have setup port forwarding, and the program gives me a Socket Error of 10061 - Connection was refused forcefully.
    The port is 1001 that we need open.
    I have checked with my ISP, and have found that they are not blocking any ports, so I know that is not an issue.
    If I hook the computer up directly to the modem, it works fine, so it is definitely a forwarding issue.
    I have DHCP turned off on the computer, my local IP address is 192.168.1.106
    My port forwarding settings look like this.
    Application: (Blank... but I have used other names during tests)
    Start: 1001
    End: 1001
    Protocol: Both (I have also tried TCP and UDP individually)
    IP Address: 192.168.1.106 (my static IP address)
    Enabled: True
    I have also tried turning the SPI Firewall Protection off, as well as Block Anonymous Internet Requests.
    The IP address that the person is using to connect to the computer with is my router's IP address (which is propagated directly from the modem). With the port 1001. This is the same combination used when the computer is hooked up directly to the modem, however with it behind the router, the forwarding just doesn't seem to handle the forward.
    I have tried it with Windows Firewall turned off, as well as my Norton AV.
    I have also created exceptions and completely opened port 1001 in Windows Firewall just in case.
    I've also tried just simply restarting the computer.
    I'm tapped out of ideas... can anyone else suggest anything?
    Message Edited by Joker_69 on 05-13-2008 01:53 AM

    Alright, I went through the checklist, and every single step in the checklist checked out, except for connecting from outside the LAN. I can connect to the server through 192.168.1.150:1001, but not through xxx.xxx.96.215:1001.
    Here are all settings that have been changed (everything else should be assumed to be default values):
    Wireless/Security:
    Security Mode: WEP
    Default Transmit Key: 1
    WEP Encryption: 128 bits 26 hex digits
    Passphrase: Have been set
    Key 1, 2, 3, 4: Have been set
    Security/Firewall:
    Firewall Protection: Disable
    Block Anonymous Internet Requests: False
    Filter Multicast: True
    Filter Internet NAT Redirection: False
    Filter IDENT(Port 113): True
    Applications & Gaming/Port Range Forward:
    Application: (no name given)
    Start: 1001
    End: 1001
    Protocol: Both (TCP & UDP)
    IP Address: 192.168.1.150
    Enable: True
    Now, here is the Status Page of the Router:
    Firmware Version: v4.21.1, Nov. 6, 2006
    Current Time: Tue, 13 May 2008 23:47:26
    MAC Address: xx:xx:xx:02:11:F5
    Router Name: WRT54G
    Host Name:
    Domain Name:
    Login Type: Automatic Configuration - DHCP
    IP Address: xxx.xxx.96.215
    Subnet Mask: 255.255.192.0
    Default Gateway: xxx.xxx.64.254
    DNS 1: xxx.xxx.133.68
    DNS 2: xxx.xxx.133.100
    DNS 3:
    MTU: 1500
    Here is the copy from ipconfig /all (with IP's blocked out):
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : xxxxx-xxxxxxxxx
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter Wireless Network Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Wireless-B PCI Adapter
    Physical Address. . . . . . . . . : xx-xx-xx-0D-39-EC
    Dhcp Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.1.150
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : xxx.xx.133.68
    xxx.xxx.133.100
    Here is my netstat -an:
    Active Connections
    Proto Local Address Foreign Address State
    TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:1001 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:5051 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:5101 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:7501 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:21159 0.0.0.0:0 LISTENING
    TCP 127.0.0.1:1026 0.0.0.0:0 LISTENING
    TCP 127.0.0.1:1045 0.0.0.0:0 LISTENING
    TCP 127.0.0.1:3668 127.0.0.1:3669 ESTABLISHED
    TCP 127.0.0.1:3669 127.0.0.1:3668 ESTABLISHED
    TCP 127.0.0.1:3670 127.0.0.1:3671 ESTABLISHED
    TCP 127.0.0.1:3671 127.0.0.1:3670 ESTABLISHED
    TCP 192.168.1.150:139 0.0.0.0:0 LISTENING
    TCP 192.168.1.150:4153 xxx.xxx.193.131:119 ESTABLISHED
    TCP 192.168.1.150:4156 xxx.xxx.233.145:5050 ESTABLISHED
    TCP 192.168.1.150:4170 xxx.xxx.107.81:1863 ESTABLISHED
    TCP 192.168.1.150:4949 xxx.xxx.207.191:80 CLOSE_WAIT
    TCP 192.168.1.150:4950 xxx.xxx.223.191:80 CLOSE_WAIT
    TCP 192.168.1.150:4951 xxx.xxx.139.166:80 CLOSE_WAIT
    TCP 192.168.1.150:4952 xxx.xxx.139.166:80 CLOSE_WAIT
    TCP 192.168.1.150:4953 xxx.xxx.255.103:80 CLOSE_WAIT
    UDP 0.0.0.0:445 *:*
    UDP 0.0.0.0:500 *:*
    UDP 0.0.0.0:1048 *:*
    UDP 0.0.0.0:1050 *:*
    UDP 0.0.0.0:1166 *:*
    UDP 0.0.0.0:1178 *:*
    UDP 0.0.0.0:1802 *:*
    UDP 0.0.0.0:1803 *:*
    UDP 0.0.0.0:1804 *:*
    UDP 0.0.0.0:1805 *:*
    UDP 0.0.0.0:1806 *:*
    UDP 0.0.0.0:3456 *:*
    UDP 0.0.0.0:4500 *:*
    UDP 0.0.0.0:5051 *:*
    UDP 127.0.0.1:123 *:*
    UDP 127.0.0.1:1900 *:*
    UDP 127.0.0.1:2089 *:*
    UDP 127.0.0.1:2111 *:*
    UDP 127.0.0.1:3459 *:*
    UDP 192.168.1.150:9 *:*
    UDP 192.168.1.150:123 *:*
    UDP 192.168.1.150:137 *:*
    UDP 192.168.1.150:138 *:*
    UDP 192.168.1.150:1900 *:*
    UDP 192.168.1.150:4160 *:*
    UDP 192.168.1.150:4161 *:*
    UDP 192.168.1.150:4163 *:*
    UDP 192.168.1.150:4164 *:*
    UDP 192.168.1.150:8163 *:*
    UDP 192.168.1.150:39358 *:*
    The sixth one down from the top looks like it is working properly.
    Let me know what you think .
    Message Edited by Joker_69 on 05-14-2008 12:01 AM

  • Port forwarding problems with WRT610N v2 + WAG54GS v1.0

    Background:
    I have a WAG54GS v1.0 (Annex A) which I was using to handle my home network and my ADSL connection. I bought a WRT610N v2 (which I'll refer to as the router) with the intention that it would replace the networking duties of the WAG54GS (which I'll call the modem), which would be relegated to just handling the Internet connection. Both are running their latest firmware.
    I've gotten this configuration to work, but with one problem: I've lost a lot of flexibility in regard to port forwarding. The problem is that the only way I've managed to get the Internet to work is by having the router on 192.168.0.1, and the modem on 192.168.1.1. If I try and have both on 192.168.0.x or 192.168.1.x then connecting to the Internet no longer works under any configuration of options I've tried.
    What this means is that when I go to setup port forwarding in the modem, I can only forwards to clients on 192.168.1.x, but the router can only forward to 192.168.0.x. The only things I can get to work are situations where port range triggering can be applied, so only when a connection is made on the relevant port to an external IP, and then that external IP also communicates back on that port. As you may guess this doesn't nearly cover all cases.
    Question:
    Should it be be possible to have both router and modem on either 192.168.0.x or 192.168.1.x, which would allow port forwarding to work as expected. That should have in theory been possible with the modem's bridge mode except that it's then impossible to configure the PPPoA settings necessary to connect to my ISP.
    Or am I going to have to rethink the network layout (i.e. buy a dedicated ADSL modem and fully retire my WAG54GS?)
    Solved!
    Go to Solution.

    Actually in the end what I figured out was that as far as my WRT610N was concerned my WAG54GS was my ISP, and that was all it needed to know about the Internet connection. So I set it to connect to the WAG54GS with a static IP, stuck that IP into the WAG54GS's DMZ, and left the WRT610N to handle port forwarding as all devices that connect will do so through that. (Yes, I've disabled the wireless features of the WAG54GS)
    I'm reasonably sure I tried the combination of settings you've suggested (including moving the WAG54GS off the Internet port of the WRT610N, which I would have wanted to avoid anyway as I have four permanently connected devices anyway) and found it still wouldn't work. And I wasn't trying to set both to 192.168.1.1 at any point, my self-obscured point was that changing only the last block of the IP address failed to work for accessing the Internet.

  • 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 not working on new Home Hub 4

    Hi all,
    I'm trying to get port forwarding going on a new Home Hub 4, specifically so I can access my Netgear Stora through its web interface on my LAN.
    I've set the rules in port forwarding for the following ports:
    Port 80 is HTTP Server
    Port 443 is HTTPS Server
    Port 21 is FTP Server
    Port 22 is SSH Server
    All these are now open and connect to Stora, which has an address supplied by DHCP.
    However, when I check with various online port checkers, none of the ports are open and checking the trouble shooting logs of the BT Home Hub shows that the connection is being rejected. This is a sample of the message that is shown:
    IN: ACCEPT [57] Connection closed (Port Forwarding: TCP 192.168.1.69:22 <-->86.141.184.236:22 [184.72.89.72:42894] CLOSED/TIME_WAIT ppp1 NAPT)
    What can I do to make port forwarding work? I can't change the IP address of the Stora as I need to get into it via its web interface to do that.
    I can navigate directly through Explorer to the files on the Netgear Stora NAS but not through the web interface.
    Can anyone help?
    Thanks.

    i think by applying a static DNS i got it working, not 100% sure yet. edit: yep that worked, everyone can connect once again.
    Message Edited by briantoxicity on 01-01-2008 04:59 PM

  • Port Forwarding BEfW11s4 linkstation

    I am a newbie with networking.  I set up a home network a few years ago and it has worked ok.  I have to unplug the router from time to time though.  Anyway, I just bought a Buffalo Tech linkstation live and would like to use the web access features.  I tried doing the port forwarding but my router must not be plug and play compatible with the drive.  I tried to do it manually from a website Buffalo suggested but no luck.  Is this something I shouldn't even try being that I have very limited knowledge when it comes to networking?
    Any help would be apprecitated!
    Tom

    What are the different ports you tried to forward on the router let me know,,,

Maybe you are looking for