Wireless-N 300 ADSL modem router help

[pappaG]

Hi Guys,

I need help with the Wireless-N 300 ADSL modem router. I need to change the local IP address that the router allocates to the local network outside the range of the private IP address range.
By default it is configured as in the 192.168.0.* range. I need to change this to say for instance in the 13.0.0.* range.
I need to do this to connect to my work via VPN, and this is their requirement.
Can anyone help me urgently please.

Thanks in advance.

[jmizoguchi]

read manual
http://kbserver.netgear.com/downloads_support.asp

this basic 101 states usually in manual

login router and go to lan setup.. simply ... make sure you do it with pc to the router with wired for changing

[pappaG]

I'm sorry, I still needed to add that I know how to do this. The problem is that I lose my internet connection when I change the local LAN ip range to 13.0.0.* But when I change it back to the 192.168.* range, then the internet works again.

[jmizoguchi]

Originally Posted by pappaG

I'm sorry, I still needed to add that I know how to do this. The problem is that I lose my internet connection when I change the local LAN ip range to 13.0.0.* But when I change it back to the 192.168.* range, then the internet works again.

contact support if changing the to desire IP does not work

try 192.168.99.x and if that takes it

[pappaG]

192.168.99.x is still in the private IP range.
the following is in the private IP range:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

I need an IP range in the local network to something out of the private IP range

[Mars Mug]

Originally Posted by pappaG

I'm sorry, I still needed to add that I know how to do this. The problem is that I lose my internet connection when I change the local LAN ip range to 13.0.0.* But when I change it back to the 192.168.* range, then the internet works again.

I’m guessing you don’t simply mean the computer stops talking to the router, but just in case, you need to refresh the connection.

Otherwise, that subnet is not one of the private IP ranges so the router firmware may be partially rejecting it (NAT may not work) for that reason

[pappaG]

in both cases the subnet is 255.255.255.0
do i need to change this to something else when i change the ip range to 13.0.0.*

[Mars Mug]

Given the way many Netgear routers react automatically to seeing a private IP on the WAN side, by changing the LAN subnet to another private range e.g. 10.x.y.z. I would not be surprised in the LAN subnet for NAT purposes is hard coded to expect one of the three private subnets and nothing else. I think that by setting a public IP on the LAN side you are stopping the thing from performing NAT and it’s just operating as a DHCP server/switch/access point.

That is all something of a guess.

[jmizoguchi]

Originally Posted by pappaG

192.168.99.x is still in the private IP range.
the following is in the private IP range:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

I need an IP range in the local network to something out of the private IP range

why needs to be out side of private IP range

[pappaG]

So that I can connect to my work via VPN, it is setup in such a way that your IP address needs to be outside the private IP range for the VPN to connect.
I have phoned technical support for Netgear as well, and they've told me to register at dyndns.com, setup this info in the router and... This seemed even to me not like the right option and sounded like they didn't really understand my problem, so it was back to square one again. Then I've changed this to 11.0.0.* and all of a sudden this works. I don't know why but it just does. Thanks for all the help.