Windows
IP address conflict kept the host unreachable over RDP/VPN
The host could not be reached over RDP while on the VPN because it was using an IP address that was also being seen as a printer. The IP was changed to the reserved address and remote access came back.
Killed once by someone from XL.net, on 2026-01-28.
What you see
- RDP over VPN fails to reach the host.
- Remote access/agent could not connect to the machine.
- A network scan showed the IP being tagged as a printer.
Why it happens
Likely Likely duplicate/static IP conflict on the network; the host needed to be moved to its reserved IP address.
When it shows up
A Windows machine is reachable by VPN/network scan but RDP stops working, and the same IP is also identified as a printer or other device.
You are in this case if:
- Network scan identifies the address as a printer.
- DHCP shows a reservation for the host's IP.
- Remote agent cannot connect until the IP is changed.
1 fix below
The steps that killed it
The steps are behind a quick check
There are two ways in and both take a few seconds. Signing in opens the steps on every bug page; so does reading the picture.
Or answer this
Drawing a picture for you.
Can't read it? Sign in instead.
Keeping it away
- Keep static IP addresses outside the DHCP scope to avoid address conflicts.
Someone from XL.net killed this on a Windows computer on 2026-01-28. It is written up from that one repair, so it cites no outside page.