cancel
Showing results for 
Search instead for 
Did you mean: 

BT2700HGV - NAT fixed ip not working.

domcaz
Member

Hi,

 

We have  4 computers connected to our 2700HGV via wifi, and the DHCP server in the router is assigning the local IP addresses. So far so good...

 

One of the computers is regularly used for file sharing and we need to tie down its IP address so the others can easily find it.

 

In Settings/LAN/NAT & Address Allocation - I can select "Private Fixed:xxx.xxx.x.x" from the Address Assignment drop down menu, and after clicking save it says "Configuration Successful" in a nice green box....but the setting has reverted to "Private from pool: xxx.xxx.x.x".

 

No amount of restarting either the computer or the router seems to allow me to successfuly alter this setting.

 

Please help!

 

Dominic

2 REPLIES 2

gugaguga
Power User

First, you need to assign a static IP to your computer like 192.168.100.100.

 

At the NAT config. Do something like public IP:highport -->> 192.168.100.100:highport. Ex below.

 

2.2.2.2:51555 ---> 192.168.100.100:51555.

 

That is the idea, hope you find a way on how to set this up.

TimDurham75
Power User

I suspect the last poster has got the wrong end of the stick....

 

What you seem to be describing is something I have done for years so it absolutely should work and does for me.

 

I have the older 2700 though.

 

Model:BT2700HGV
Hardware Version:2701-100588-005
Firmware Version:6.3.9.63-plus.tm

 

If settings are not persisting properly then you possibly need at a minimum to reset the device list first but, otherwise to factory reset, then reconfigure as the devices are re-attached.  Having said that, as another point, I do not use the default NAT range for the device but am reconfigured to a completely separate IP range - I use a unique 10.x.x.x address with a 255.255.255.0 mask.  I have a number of hosts with statically allocated dhcp addresses.  The other difference is that I do not have the hub as the primary DNS - I have a static domain server which is primary DNS that has the hub as a forwarder as well as Google public DNS servers registered.

 

It really should work - if still not saving I suggest contact support as the hub may be faulty.