Static IP adress vs DHCP

Hi

I've just updated a W7 machine to W10. The update has take all the settings from W7 and the machine was operating without problem before the update.

When running W7 the machine had a static IP address of 192.168.1.1 and all of the other machines could access the machine using the IP address or the name defined to the network.

After updating to W10 the machine continues to have a static IP address of 192.168.1.1 and the same machine name. Other machines can access it using the IP address but the machine name now resolves to 192.168.1.69 which is a DHCP address. The machine has not used this address, if ever, for at least a year.

I can't change the machine IP as some of the applications that run on it store the IP address which is why it was moved to a static one in the first place.

I'm assuming the problem is the router which allocates DHCP addresses. I've deleted the original entry in the devices table and it has been refreshed correctly but it hasn't made a difference. The router is a Technicolor TG582n

I've even tried adding an entry to the HOSTS file which hasn't made a difference.

Any ideas?

Thanks

Hi there
Go into router settings -- your router is assigning IP addresses - but you can "reserve" some and start DHCP addresses from a specific number.

In the network settings of your machine with fixed IP - disable DHCP in the networking panel (Windows) and put your IP address in. You might need gateway and DNS server ip address(es) to be set - that you can get from the router.

Cold boot ALL computers / phones etc etc on your network.

You might also need to change the IP of the router (normally 192.168.1.1 or similar addresses are for the router and gateway)

Should then work fine.

Cheers
jimbo

Does your router support specific IP address reservations? Any client in the Address Reservation table will always get the same IP address. The client gets set to DHCP but it always pulls the same IP address from the router. That way the router handles the DNS name lookup for the local network.



Also, is the network connection on the computer set as a private network?

Is Network Discovery turned on?

Thank you for your replies. The problem is still there this morning despite all of the other machines being closed down.

Yes the router supports a DHCP range, it's set for 65-253 so there is no clash of addresses.

I've cold booted everything all ready

The router is on 192.168.1.254

Network Discovery and File and Printer sharing are both on.

CompA can see and access everything else on the network without problem.

I had the same problem on another machine earlier in the week, but was able to cure it by switching to a DHCP address, unfortunately I can't easily do this with the current machine and having a DHCP address causes problems.