WRT310N - Port forwarding problems.

Similar Questions

• On WRT54G port forwarding problem

  I have a strange problem with my WRT54G. I try then I go to the "port forward range" page to setup port forwarding. The "port range" is completely empty, so I start just enter my information in the first row:

  Application: NAS

  Start: 5000

  End: 5001

  Protocol: the two

  IP Addr: 192.168.1.50

  Activate: checked

  Then, I click on "save settings". The router says 'success' and I'm then routed to the page of "port forward range. To my surprise, the table is still empty! Where the hell is my settings? I tried several times with the same result. I tried to power off the router too. Without success.

  My router is rev HW 7.

  It has the latest firmware v7.00.4

  Before you make changes on your router, first you can delete your Internet Explorer browsing history and if there any firewall installed on your computer turn off, lower down your security IE, and after that try to make this change on your router.

• Port Forwarding problem through 2 routers RVS4000 2 subnets

  I modified a building network to be compliant (Visa) PABP where two router and two subnets are required.

  My original CD building network configuration was designed to allow remote access to a server terminal server via the port forwarding on a RVS4000 router. So cables / modems-> xx.xx.xx.xx wan ROUTER lan 192.168.1.1--> subnet 192.168.1.0 with TCP 3389 Port forwarding for 192.168.1.11 (terminal server).

  The new configuration of the network is composed of two routers RVS4000 on two subnets. So the Modem cable-> wan xx.xx.xx.xx ROUTER1 lan 192.168.2.2-> Subnet 192.168.2.0-> DMZ 192.168.2.14 and the second router wan ROUTER2 lan--> subnet 192.168.1.0 192.168.1.1 192.168.2.1.

  ROUTER1 is configured in Bridge mode and ROUTER2 is configured in router mode. Port forwarding on ROUTER1 to port TCP 3389 is 192.168.2.1 (on ROUTER2 wan port). Port forwarding on Router 2 for the TCP 3389 must 192.168.1.11 port (server address terminal server).

  With this new configuration of network I am able to connect to the Terminal Server remotely. No problem with access to the Internet and the 192.168.2.0 subnet from inside the 192.168.1.0 subnet.

  So I think my problem is through two RVS4000 routers port forwarding. Any help on this problem will be appreciated.

  Thank you.

  1. can you access the terminal server server from inside the subnet 192.168.2.0/24 using the IP WAN to Router 2, which is access 192.168.2.1:3389 from inside 192.168.2.0/24.

  2. turn on Router 2 router in Bridge mode. Try again. My guess is that this will make the work of transfer. I think that port forwarding is linked to the NAT/gateway mode. No NAT no transfer. Is not logical to use the transfer when you are able to access the IP directly without NAT. Of course, the web interface does not allow you to forward a port located outside the LAN subnet...

  3. are you sure that you can access internet through Router 2 in router mode on the LAN subnet router 2? Usually in the NAT their own LAN subnet routers only bridge mode but not others. If the RVS4000 not NAT a different subnet that would be good to know.

• VPN and port forwarding problem

  Hello

  I configured a VPN (IPSec) between 2 sites on Cisco 881 - K9.

  The server 'A', which the 192.168.0.X address must be accessible on port 80, 8080 and 90 of the public network.

  I have configured the ports of shipment with the command:

  IP nat inside source static TCP 192.168.0.X 90 interface fastethernet 4 90

  IP nat inside source static TCP 192.168.0.X 80 4 80 fastethernet interface

  IP nat inside source static TCP 8080 interface fastethernet 4 8080 192.168.0.X

  The server is accessible from the outside, the site in which it is located.

  But there is a problem with the second site:

  • I ping the server with its local address 192.168.0.X
  • But when I try to open a Web page that is using port 80 or 8080 or 90, the server appears inaccessible

  It seems that the problem is due to the translation of port because when I delete the configuration of port forwarding is no problem over on the second site.

  Thanks for your help

  Hello

  You need conditional NAT.
  When you want to Port Forwarding to work just for a part of traffic, e.g. when access to the server from the Internet
  but not for traffic entering via VPN, you can add a roadmap to the end.

  Thus,.
  IP nat inside source static TCP 192.168.0.X PUBLIC_IP 4 xx xx map route VPN

  The road map tells when it is NAT that will to spend.
  It will always happen, but when traffic is coming from the VPN.

  Now... the problem is that you can add a roadmap, when you have a rule of Port forwarding to an IP address (and not an interface).

  Anyway, give it a try and let us know.

  Federico.

• XPS 8500 USB 3.0 Port forward problems

  Ports USB 3.0 on the XPS 8500 give me bad, and from what I can tell, it comes from a physical problem with the port hardware.

  I can acquire and maintain a 3.0 connection when I plug my WD Passport drive or a Rocketfish hub propelled into the ports on the back. Connected to the front, however, I can sometimes 3.0, sometimes only 2.0 and rarely even get no connection at all. Connection I get to the front, if I move to sentence (like touch), the cable or the plug connection can change back from 2.0 to 3.0. Writing on a drive that will prevent mobile 3.0 to the front.

  I noticed that the physical connection of USB plug on the port is more solid at the back than the front. A cable plugged into the rear port 3.0 is able to travel further and the rubber around the contacts of plug of cable on the back of the computer. On the front ports, the connector does not travel in too far, and the rubber of the USB connector is about 1-2 mm of front cover of the computer. A 3.0 cable on the front can move much more than a through the rear hole. I should mention that I have no problem with the USB 2.0 cables or devices in these front ports.

  This isn't a driver problem, it is a problem of the plug 3.0 doesn't not not solid contact in the port. Dell must cease to use the current material in front port and to find a more appropriate part. Then, they can replace all the front ports on the XPS already shipped 8500.

  My problem with USB 3.0 before XPS 8500 ports seems to have been resolved by the new cables. However, my initial assessment of ports before being too loose, making it difficult to get good 3.0 connections still holds upward. To save their customers and themselves from many headaches, Dell needs to find a replacement part for these ports before issues.

  Everything that I had to test this with a WD Passport 3.0 years was HARD and a new Rocketfish powered 3.0 disc hub. Using the cables of original, these devices connected to ports at the back, but not the front. If I held the plug and stuck firmly in a front port, I couldn't sometimes 3.0 connection - although as soon as I let go of the plug I would lose the connection 3.0 and it would immediately reconnect as a 2.0 device.

  I bought a 3.0 a mini-B cable for direct use with the WD drive and a 3.0 extension cable A-male to female for general use. These cables make very positive connections and seem to contribute to compensate ports before release. I can use them in any combination on the front (or back, of course).

  You think that the problem was simply the cables and had nothing to do with the front ports. However, if I plugged the new extension to the front cable, I could then connect the WD drive to that using the original cable that would not connect directly on the front. Which tells me that the strength of the connection of two front port and the original cable was low. Trying to connect these two weaknesses directly was problematic. Solid connectors of the new cable used between two weak points allowed a good connection. This and the fact that the original WD and Rocketfish cables connected to the rear ports 3.0 without problem, points directly to the ports before being part of the problem.

• [WRT120N] Port forwarding problem

  Hello world

  I am running server in my Ubuntu computer in port 8000.

  When I go to http://192.168.1.104:8000 in another computer on my local network site works very well.

  but when I transfer the port and you're trying to enter my public IP address he never stops loading.

  Here is a screenshot of my router settings:

  

  What telnet says:

  Martin@Martin-desktop:~/dropbox/mysite$ telnet 190.189.59.90 80
  190.189.59.90 by train...
  ^ C

  Martin@Martin-desktop:~/dropbox/mysite$ telnet 192.168.1.104 8000
  192.168.1.104 by train...
  Connected to 192.168.1.104.
  [Escape character is ' ^]'.

  Thanks in advance

  It seems you are trying to access the remote server then.  In so that you can access this computer remotely, assign a static ip address for this computer. Open this port on the router with this static ip address. Uncheck "filter internet requests annonymous" w/c are under the Security tab of the router check the router's WAN ip address and see if you can ping the ip address (if you use a brand of modem DSL of course she is in Bridge mode). Try to access this remote port by using http://WAN_IP:8000. You can also see the links below to check if the port has been opened.

  http://ping.EU/port-chk/

  http://canyouseeme.org/

• Problems with WRT610N v2 + WAG54GS v1.0 of port forwarding

  Background:

  I have a WAG54GS v1.0 (Appendix A) that I use to manage my home network and my ADSL connection. I bought a WRT610N v2 (which I will refer to as the router) with the intention that he would replace the functions of networking of the WAG54GS (which I will call the modem), who could be relegated to handling just the Internet connection. Both are running their latest firmware.

  I got this configuration to work, but with a problem: I lost a lot of flexibility with regard to port forwarding. The problem is the only way I managed to get the Internet to work with the 192.168.0.1 router and the modem to 192.168.1.1. If I try and that you have both 192.168.0.x or 192.168.1.x then connect to Internet no longer works under any configuration options, I've tried.

  What wants to say that when I go to port forwarding of installation in the modem, I can only forward to clients on 192.168.1.x, but the router can only transmit to 192.168.0.x. The only things that I can go to work are situations where triggering serial port can be applied, so that when a connection is made to the relevant port to an external IP address, and then this external IP address to communicate on this port. As you can guess this covers almost all cases.

  Question:

  Would it not be possible to have the router and the modem on 192.168.0.x or 192.168.1.x, allowing port translation work as expected. Which should in principle be possible with the modem bridge mode except that it is impossible to configure the PPPoA settings needed to connect to my ISP.

  Or I'll have to rethink the configuration of the network (i.e. buy a dedicated ADSL modem and remove entirely my WAG54GS?)

  In fact in the end what I figured out was that according to my WRT610N concerned my WAG54GS is my ISP and that was all he needed to know on the Internet connection. So I had to connect to the WAG54GS with an IP address static, stuck that IP in the DMZ of the WAG54GS and left the WRT610N to manage port forwarding like all devices that connect will make it through that. (Yes, I've disabled features wireless of the WAG54GS)

  I'm reasonably sure that I tried the combination of settings you suggested (including moving the WAG54GS off the Internet port on the WRT610N, which I wanted to avoid in any case as I have four devices permanently connected in any case) and found that it still does not. And I wasn't saying two to 192.168.1.1 set at any point, my darkened auto focus was that change only the last block of the IP address doesn't have to work for Internet access.

• Problem with Port Forwarding (When PPTP is upward) in the WRT-160N

  Hello world!

  I'm looking for more help with Port Forwarding in my new Linksys router. I bought the daysago afew router and was pretty surprised when I discovered that there is no DD - WRT firmware is installed in it (the router was 100% NEW when I bought it). I downloaded latest firmware original and flashed Linksys file successfully.

  But I still have the problem (even that I was on DD - WRT firmware too) with the port forwarding for my DC ++ and Vuze (app from torrents): I wrote port forward for ports 49151 (for Vuze) and 4000 (for DC ++) to pass on to my desktop computer (IP 192.168.1.201) - I saw a post on this forum, that there could be a problem If you transfer to an IP address, which is within the local area of DHCP, so I forwarded to IP.201 (my local DHCPzone is 192.168.1.100-. 149) But does not forwardind (())

  What's wrong?

  My configuration:

  Router IP: 192.168.1.1

  PPTP (I my ISP)

  IP address: 192.168.226.127

  Default gateway: 192.168.226.2

  DNS 1: 192.168.1.1

  2 & 3 DNS: 0.0.0.0

  The IP address of the PPTP server: 192.168.226.2

  User name: *.

  Password: *.

  _____________________

  Simple Port Forwarding:

  Name of the external port application port internal protocol for IP address Enabled

  Vuze 49151 49151 times checked 192.168.1.201

  DC 4000 4000 checked two 192.168.1.201

  As you mentioned in your post that your ISP has provided you with a PPTP connection with an IP address: 192.x.x.x. The IP address that is provided by your ISP is in a private beach, and if you try to transfer all the ports on your router, it will not work, as long as your ISP modem is blocking this port. If you need get a public IP address from your ISP.

  As you get Private IP of your ISP, if this connection is called as NAT behind NAT and your Modem behaves like a router.

  So now you have 2 options, get the public IP address from your ISP or change the type of connection.

• Problem setting up Port Forwarding with two routers.

  I can't set up by Linksys RT31P2 and routers port forwarding WRT160Nv3.

  My setup is Webstar Modem = RT31P2 = WRT160N = Mac OS 10.6.5. (No configurable modem and ISP do not prevent port forwarding. It comes with two Linksys routers).

  I had a Monty Python-going around with the support of Cisco cat; and follow up with telephone assistance in which the agent knew nothing about port forwarding and his supervisor expressed the view that it was not possible with two routers. Sigh.

  If anyone can help me with step by step specific and simple instructions to configure routers. I know that the basic procedures. I'm not clear, what exactly changes on routers.

  I read that portforward.com has to say and it does not work so I must be misunderstanding something.

  The ip address of my computer is 192.168.1.103.  Are the last three digits of this speech concluded the two routers in the area on the port forwarding page? What other changes should be done what router?

  I know the port numbers that I use are OK because I can implement successfully if I connect to one or other of the routers (but not both), and my software of p2p shows port are open.

  Any help and suggestions most welcome.

  If you set up as I have suggested that you have only a single LAN that will be using in your addresses * 192.168.15 case. So in your case:

  1. change the address LAN IP of 192.168.1.1 to 192.168.15.2 WRT.
  2 disable the DHCP server.
  3. connect the LAN of the WRT port to port LAN of the RT.

  That's all. Disable the DHCP server will not affect whatever it is that you're connected LAN - LAN and DHCP server on the RT is still operational.

  After the change, previously the WRT computers may require a reboot to get a new address 192.168.15. *.

  Your computer to which you are transferring must have an IP static and not dynamic (or variable). Check the current IP information on this computer. It must have an IP address like 192.168.15.103, mask 255.255.255.0, gateway 192.168.15.1 subnet and DNS 192.168.15.1 server or maybe two other IP addresses instead. Note DNS servers if you do not 192.168.15.1.

  Then configure a static IP address on the computer. Use something like 192.168.15.10, 255.255.255.0 gateway 192.168.15.1 and the DNS servers you found before.

  After this implement 192.168.15.10 port forwarding.

• Problems with static IP setting for the port forward through 2 routers

  I currently have cable internet connected to a router (Linksys E2000 w / v1.0.03 firmware). This router is connected to another router, a Linksys E3200 with firmware v1.0.02. In order to correctly forward ports through the E3200, I understand that I need to set up a static IP address on the router.

  I almost followed the steps in this video, but when I enter all the IP addresses for the static IP address settings, it allows me to access the router configuration page. I try to get the new IP address that I gave (which he tries to move automatically once I have save settings) and the connection times out. I am able to access internet otherwise, however. From here, I have to do a factory reset on the router and start from square one.

  Anyone have any ideas? I'm quite frustrated and would like to get ports forwarded so I can get my server properly set in place.

  1. If it has connected LAN - LAN you will need to disable the DHCP server on the E3200.

  2. the best option would be to use the 'bridge' on the E3200 mode (in the latest firmware) and connect the internet port to the main router.

  3. If connected LAN - LAN (or in Bridge mode) all internet related functions on the E3200, including ports are not relevant. There is no need to set up the port on the E3200 redirects. All shipping is done only on the E2000 and nowhere else.

  4. What is the address LAN IP of the E3200? What is the address LAN IP of the E2000?

• Airport of Port Forwarding is more?

  So I'm pretty new to this network thing. I don't know the technical network terms then please do not use (or at least their simplification). So I managed to set up my ASUS RT - something something router. I also put in some rules to sink my Xbox One anywhere port forwarding. However, I had problems with port forwarding, so I just used the dmz for her service. However, given that I had to move my Xbox to another part of my house with worst network connection, set up a time capsule for the network. After a long time, I managed to do the work, but now I can listen to is no longer my Xbox. My guess is that the port forwarding rules are not carriers, as it connected via ethernet time capsule and the capsule is connected to another time capsule via radio and this time capsule is connected to my ASUS router via ethernet. So my question is: how to transfer the required ports to my Xbox?

  If both of your time Capsules are configured as bridges, the Asus router is the one that needs to be set up on port mapping. The port mapping is used only when a router is configured for routing. In other words, the NAT and DHCP services are enabled. This is the default value for any router.

  Just to make sure that I understand your current network configuration, the following is correct?

  • ASUS > Time Capsule > > > Time Capsule > Xbox, where ' > ' represents a wired connection, and ' > > > ' represents a wireless.

• How do I port forward on apple airport? (READ ALL)

  I have an airport express from apple connected to an asus router via wifi and I need to know how I can portforward by airport to the router because my pc is connected by ethernet to the airport. Help, please.

  The express should be none not routing at all and therefore no port forwarding.

  The only way this can work is the express installation to the wireless bridge... Apple called client mode... There is no routing.

  BUT it can also have port problems... It is really unsuitable if you operate in questions.

  In any case all the transfer is possible on the Asus.

• Port forwarding rules missing WNR1000V3

  I read a few posts here that may be similar, but they are so old, that threads are blocked. I'm trying to help out a local company add some rules to redirect to their server port WNR1000V3 more.

  They must have some configuration of port forwarding already because they are able to access an existing via RDP server so there is a rule somewhere for port 3389. However, it is has nothing listed in respect of port forwarding.

  My view on it after scratching my head for several hours, it's that there is either a port forwarding rules defined and running, but they are not displayed in the user interface, OR there is some screen that I have not found (was all!) where port forwarding is also configured.

  I think it's the first because there is no rule for the listed FTP, but if I try to add a new FTP rule, it displays a "conflict of Port with other services".

  Firmware is V1.0.2.62_60.0.87 although the router points out that there is an update.

  There is a known issue like this with this model? It seems a few years old.

  Thank you, Rob.

  Sorry, I would have given an update on that. I am aware of what means the error and it was probably that a rule on this port unless it was not displayed. I hoped that export Netgear configuration could be a human readable script (found on the Cisco routers), but it's not.

  After discussion about ServerFault and checking some of the suggestions there, it became clear that something was broken enough with the router. An update does not solve so I have taken note of all the settings and did a reset.

  That solved the problem. My theory is that some bugs in an earlier version of the firmware caused a bad record in order to be there for port forwarding. One that actually worked, but could not be displayed.

  Cheers, Rob.

• NETGEAR ProSafe VPN Firewall SRXN3205 and port forwarding?

  Hi, this is a long shot, but I'm pulling my hair out at this point and can be a bit over my head, as I am new on network

  Small short story, I have two servers, one is the NAS box (IE if I connect via the internet to the site via public IP network from home, I get it that site says 'my actions' I insert login and pass and get access to them.)
  That is, everything is peachy.
  The problem is when I try to connect to my FileMaker Server I'm not and instead, he takes me to the login NAS box. So I think ok, I need to port forward (5003 for filemaker) to go to different PC local LAN(192. etc)

  Security > firewall > Add Service entering:
  Service: fmserver
  Action: Always leave
  Send to LAN Server: unique address 192. etc is filemaker installed on (and different on a NAS)
  Definition of Port number: 5003<-- is="" this="" right?="" how="" else="" would="" you="" indicate="" you="" want="" all="" connections="" on="" this="" port="" to="" go="" to="" this="" specific="" lan="" machine="" from="" internet="" instead="" of="" default="" which="" seems="" to="" be="">
  rest is default, I click on apply.

  Here's what I don't understand. In the table of incoming Services, (security > firewall) I have two local IP in the list, a SIN, the other for Filemaker. But only the top works and can be connected to. I can move every top position and it will work, but they will not work at the same time, just the one that sits on the top of the sad Smiley page

  and yes I read the manual again and again and don't know how I'm screwing up the port forwarding on this point, even if I am brand new to probably something stupid Smiley Happy (our work IT guy is gone so tried to get involved through this somehow)

  Any help would be appreciated.

  Hello sinieq,

  There is a hierarchy on incoming service table, which is normal. I see 4 services added using "ANY" (ALL use any port number) you will need to remove/disable these because of the rule of the hierarchy on the table, all other services will be ignored when EVERYTHING is used. What is the port number used by the NAS Server? I don't see a port defined to access NAS. Try disabling services by using "ANY" and try again by adding the translation to the port number of the NAS.

  Let us know what happens.

  Thank you

• port forwarding issues

  I played with port forwarding with my two cams of linksys and other 3 g wireless network web pages on my local network I want to access from the outside world.  I have one to configure them to use other port 8081, but after a few experiments see it as useless.

  I have a router linksys WRT54GL running dd - wrt V23 SP2 firmware and ports 80,81 and 443 (all in the field "port of") transmitted to cam1, cam2 and Western Digital NAS drive respectively. I found that because I'm port forwarding in any case, the two cams can continue to use port 80 and I 80 and 81 in the ' port of "or side defined WAN port 8080 bothers me to my router gui.

  There's the rub for me, it is, I cannot use 80,81 and 443 of the side ports WAN routers forward my port, if I use a different port, I can't access anything whatsoever that is served as a web page. I discovered this when I installed the Transmission torrent client on my NAS drive, it has a web interface as well and uses the port 9091, however when I port transfer it via my router I can't web interface from outside my local network. If I change the WAN or 'port' 80 or 81 and let the 'port' to 9091 I get fine, but I need to disable the port front of webcam that uses this port.

  I was going to get a 3rd and 4th IP Cam but will have the same problem, because it seems that only I can use ports 80, 81 and 443, and they are already exhausted. (I use 443 for secure access to my NAS drive) Change the port number in settings/options to 1024 or anything else works that if I leave it on the side of port forwarding LAN, WAN-side must always be 80 or 81.

  The only way I can see around this is to create a page that will reside on my router or my drive NAS I can show more out of a camera on it - something, I want to do in any case.

  PS. I do not use TZO, but I use dyndns so my dns is myname.dyndns.org.

  Finally understood that there is a problem with blocked ports from my place of work, which is where I tried to connect from. When I connected to the internet with my laptop computer and aircard, I was able to get to ok. My solution when I want to check on the torrents of the work is to connect to my router GUI work, changing the port 80 or 81 and disable the webcam on this address.