IPv4 address changed from Static to DHCP

Topic

New Reply

I manage about 40 PC remotely  using Remote Desktop Connection Manager. Therefore I have all the PC set to a static IPv4 address. I am now finding that many of the PC have been changed to use DHCP. I believe this happened after a windows update. I also noticed that the PCs that are still static change to DHCP after a reboot.  If I set the address back to static with the IP address of my choice (eg 192.168.1.95) the address gets set to a 169 address after reboot and will no longer communicate.

I found KB5029244 update breaks remote desktop connections and I wonder is this is related. Does anyone have experience with this problem?

Reply | Quote

Replies

A 169 address means that DHCP is enabled but the NIC can’t find a DHCP server, so it self assigns.

Is it possible to leave DHCP on and connect via DNS name?

cheers, Paul

Reply | Quote

Thanks Paul. When I re-enable DHCP in the properties for the NIC everything is fine and it gets a DHCP address so I know a DHCP server is running. But the point is that when I select Static and assign my own address, the NIC will not retain the address and therefore I cannot communicate with it remotely.

Reply | Quote

I assume the Router is the DHCP server. Can you reserve/assign the IP address for the computer in the Router and have it remain static?

Reply | Quote

The DHCP server is on a SonicWALL firewall. Your suggestion is a good one and I will try that.

Reply | Quote

I found KB5029244 update breaks remote desktop connections and I wonder is this is related. Does anyone have experience with this problem?

@R Dance

the KB5029244 update is an old update from August 2023 and the remote desktop connection problems should already have been fixed in most newer updates after that one.

so the answer to your 1st question might be a no as it may not be related

Reply | Quote