Can't see http://tower

[[email protected]]

With my PC booted, I boot the NAS and it boots cleanly. However, if I go into Chrome and type http://tower (albeit I have changed the name) it reports website not available.

 

If I go into the router's DHCP table the name and IP address are there but the NAS is setup to obtain the DNS address automatically.

 

If I type in the IP address I get the main web page and if I play about flushing DNS etc. and ipconfig i will eventually resolve the name.

 

I just wondered if anyone could help resolve the minor niggle.

 

TIA

RJJ

 

 

[trurl]

Settings, SMB, Workgroup Settings, Local master: Yes

[[email protected]]

Local Master has been set to yes from the start.

 

Rich J

[mad taurus]

Give it a static IP on your LAN (either outside of DHCP pool, or force a reserved DHCP IP address through the router) , and it should update pretty quickly. You could also add an entry to it in your hosts file since it is now a static IP.

[Frank1940]

If you set an static IP Address, it is best to set it at the upper end of the DHCP pool.  Many of the less expensive or older routers have limited capability of dealing with static IP addresses.  (Mine of mine is set at 192.168.1.245.  The DHCP process always assigns addresses from the bottom end of the pool starting with 192.168.1.2  I would have to have more than 200 devices before the router would be assigning addresses that high!)  You can than always simply use  http://192.168.1.245  to access the server.  The IP address will always work since that is what is actually used when you enter http://Tower!

[JonathanM]

If you set an static IP Address, it is best to set it at the upper end of the DHCP pool.

That advice is valid if the DHCP pool is not changeable and encompasses the entire block. Otherwise assign the address outside the DHCP pool but inside the block, for example DHCP is 192.168.1.2-192.168.1.100, so start your statics at 192.168.1.101 and work up from there. Most routers will allow you to change the DHCP range. Occasionally I've seen routers smart enough to detect fixed IP devices and manage them without user intervention, but most won't.