Netgear 834PN routing problems!

IAmATeaf

IAmATeaf

IAmATeaf

Soldato
Joined
3 Apr 2007
Posts
7,266
Location
South of the Watford Gap!
I've replaced my Netgear 834G wireless modem/router with a Netgear 834PN, have made sure all the settings are the same between the 2 but with the 834PN it refuses to let me access the internet from the second subnet. If I do nothing but change the 834PN over for the 834G it all springs into life.

I know the obvious answer is to keep on using the 834G but the reason I got the PN was cause the wireless kept on randomly dropping out. The wireless on the PN also has better coverage but the failure to let traffic from the second LAN onto the internet is peeving me off.

From the second network I can ping the router itself, I can also use it as a DNS server to say resolve www.google.com to an IP address, the 1 thing it just won't do is let network traffic through. I've tried the various firmwares and have reset to defaults but still no joy.

Anybody have any ideas? Is there some sort of secret setting that I need to set/unset?
 
Sorry should have explained more.

I've got the wireless/modem/router on the 192.168.0.0 subnetwork with a few desktops wired in and laptops that gain access wirelessly. I'm running DHCP on the router but have reserved most of the IP addresses via MAC reservations for both wired and wireless to make sure they always get the same IP address.

I then have a Windows Server 2003 machine with 2 network cards, I on the 192.168.0.0 and the other on a separate 192.168.1.0 subnet. I run Routing and Remote Access services on this server to route between the 2 nets. I've also added a static route on the 834G/834PN to route data back to the 192.168.1.0 subnet via the W2K3 server.

With the 834G in place from the 192.168.1.0 subnet devices can both ping the router and access the internet, with the 834PN in place devices can ping the router (confirming that the static route and routing and remote access on the server are running) but can't access the internet.

Leaving nothing changed, if I swap back to the 834G the 192.168.1.0 subnets gets internet access back.

I've checked and rechecked all my settings, to me it looks like there's a problem with the firmware in the router is not allowing LAN data from another subnet onto the WAN, in the static route I've added on the router I've tried ticking and unticking the Private box but the results are the same for the 834PN.

Have since found out that the Private option stops the route being replicated to other routers via RIP so it's not that that's causing the problem, this is doing my head in.
 
Ah, that makes more sense now. Do you actually need the static route on the router? Doesn't RRAS effectively provide NAT for 192.168.1.0 so anything to/from that sub-net should have the server's address on 192.168.0.0 as far as the router is concerned?
 
Snapshot said:
Ah, that makes more sense now. Do you actually need the static route on the router? Doesn't RRAS effectively provide NAT for 192.168.1.0 so anything to/from that sub-net should have the server's address on 192.168.0.0 as far as the router is concerned?
Click to expand...

Now your replies got me thinking, I don't run the NAT service, just IP routing in the W2K3 server, think I might give NAT a go and see what happens.

Without NAT the static route needs to be there else the 834G/834PN won't know how to get to the 192.168.1.0 subnet and I assume will then try and send any received packets for 192.168.1.0 back out through the WAN.
 
It might also be worth looking at the RIP settings under Advanced/LAN IP Setup on the router, if you haven't already, as it looks like RIP-2B might be useful.
 
HOO-RAH :)

Fixed the problem by enabling NAT on the W2K3 server acting as a router.

No idea why the DG834G doesn't require this and the DG834PN does but who cares. :)
 
Well HOO-RAH but not for too long, installing NAT on the server allows comms from the 192.168.1.0 to the 192.168.0.0 network and the internet but any devices on the 192.168.0.0 network can't access devices on the 192.168.1.0 network as NAT gets in the way.

Classic case of NAT in an internal server from what I've read, anybody have any advice before I punch a hole through the blue lights on 834PN :)
 
You must log in or register to reply here.
Back
Top Bottom