After seeing that I seem to get access back after a reboot, I wondered is something starting up on my local machine could be causing this issue. As it turns out, yes!
When Tailscale started up, it was blocking access to local ports. As I run Tailscale on most of my machines with automatic start, this was affecting multiple machines a minute or so after startup. Only realised this was an issue when I suddenly had access to IPs after a Windows update and reboot (and noticed that an "Error - connection change" was booting me off again). Partly caused by the Tailscale connection on my server (which enables access to subnets) not starting automatically.
			When Tailscale started up, it was blocking access to local ports. As I run Tailscale on most of my machines with automatic start, this was affecting multiple machines a minute or so after startup. Only realised this was an issue when I suddenly had access to IPs after a Windows update and reboot (and noticed that an "Error - connection change" was booting me off again). Partly caused by the Tailscale connection on my server (which enables access to subnets) not starting automatically.
"