• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

OT: I need help getting my wireless router to forward ports to my SETI Q! Problem sorta solved.

S

Swanny

Diamond Member
Hello all,

I have myself a little problem. I just got a new Netgear MR814 wireless router. I have all my wired comps in my room (3 of them) plugged into it and my laptop on the wireless. The way my house is set up the router for the internet is in the basement along with one other computer. Naturally I don't want to put my wireless in a hole in the ground, so it's up in my room. I figured I'd use the internet port on it just as an uplink going to the router in the basement. Well, it turns out that that won't work, it has to be a routed port. That's fine with me, because the only consequence is that the comp in the basement and comps upstairs can't see eachother in network neighborhood and such. Anyway, my problem is that my computer with the SETI Q server is upstairs. I figured I could just forward the port twice and have it work, but that's not been the case so far. My queue uses ports 5517~5519. I changed the forwarding of the basement router (Dlink) to the IP addy of my upstairs router. Then I set up the upstairs router to forward those same ports to my server machine. Problem is, it doesn't work! I'm pretty sure the problem has to be in my new wireless router since all was working fine when I just had the basement one. This is all I have done one the wireless one for forwarding:

# Service Name Start Port End Port Server IP Address
1 SETI Queue 5517 5519 192.168.0.3


I can ping the wireless router from computers on the downstairs router, but I can't ping the SETI Q server.


All help is apprecieted. If I lost you, say so and I'll try to fix it.




Thanks,
Swan
 
You said you have a Netgear MR814. I didn't see that model in the netgear site. Could you describe this router? What port/feature does it provide?
 
MR314 is a Netgear Wireless Router with rj45 ports.

Usually it's best to use the Wireless Router as the internet router and just use a switch for the additional ports needed for your wired system.









 
I know I don't want to be using 2 routers, but due to location it would really degrade wireless LAN performance if I put my wireless router in the basement.

Here is a link to the MR814.
 
I just reread your first post.

First off, are you either using a crossover cable between the two routers, or do the routers have a crossover port? This could be the problem, though I doubt it if the compouters connected to the wireless router upstairs can access the internet through the router in the basement.

Secondly, there's something wrong with the computers on the two routers not being able to see each other at all. If you're just using the wireless router as a switch then all of the computers on your LAN should be on the same subnet (probably 192.168.0.X). Turn off ALL of the routing type features on your wireless router (since you aren't using it as a router) including DHCP, NAT, port forwarding, etc. See if that fixes the problem.
 
Originally posted by: Sukhoi
I just reread your first post.

First off, are you either using a crossover cable between the two routers, or do the routers have a crossover port? This could be the problem, though I doubt it if the compouters connected to the wireless router upstairs can access the internet through the router in the basement.

Secondly, there's something wrong with the computers on the two routers not being able to see each other at all. If you're just using the wireless router as a switch then all of the computers on your LAN should be on the same subnet (probably 192.168.0.X). Turn off ALL of the routing type features on your wireless router (since you aren't using it as a router) including DHCP, NAT, port forwarding, etc. See if that fixes the problem.
Click to expand...


No, the cable is a regular cable. There is only one upstream port on the wireless router, that being the WAN port. With the way it is set up now the upstairs computers CAN access the internet fine.

Also, I don't see anywhere where I can turn off NAT. That means that turning off DHCP wouldn't help (I don't think).
 
Ok, I've got my problem solved, sort of.

To test if the new wireless router was forwarding correctly I had been using my browser pointed to it's internal address with the specified port. Well, today, when looking at the server's logs I noticed that some traffic had gotten in from outside my house. I thought this was strange, so I went to the computer I've been testing from and tried to get the the server via the wireless router's IP and still no dice. So on a whim I tried doing the same thing, only with the internet router's IP. To my amazement, the web page came right up like it was supposed to.

So here is what I don't understand: When a request goes to the first router (via it's external IP), it is forwarded to the second router, then forwarded to my server like it is supposed to. But when the request goes straight to the second router, it is not forwarded and does not work. Does anyone know the reason for this?
 
Right now it sounds like you have your internet line plugged into the WAN port of your basement router, then a cable is running from a LAN port on the basement router to the WAN port on the wireless router. You don't want to be doing this as currently trying to run NAT on a private IP, which is most likely causing all these problems. There's no need to run NAT on a private IP since you can have as many private IPs as you want. Also, you're going to get some weird problems if both routers start assigning the same private IPs via DHCP. I.E. if your basement router assigns the wireless router 192.168.0.1, and then your wireless router assigns a computer 192.168.0.1 you're going to have two computers on the same LAN using the same IP, which is not good.

You don't want any wires going into the WAN port on the wireless router.

You want a cable going from a LAN port on the basement router to a LAN port on the wireless router. This way the wireless router is just acting like a wireless switch, which is what you want it to do. Then your basement router will be doing all the NAT, DHCP, etc.

You can't do a straight LAN->LAN port connection. So you need to see if either router has uplink ports (some automatically change regular ports to uplink when they sense the need), or use a crossover cable.
 
So I can plug a cross over cable into a LAN port on the basement router and into a LAN port of the wireless router and it will work just like an uplink?
 
Yes, a crossover cable does the same thing as an uplink port.

First try and see if it'll work with a regular cable. It's possible that the ports on one of your routers is an auto-sensing uplink port (it'll switch to uplink if it needs to).
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top