Unreachable Private HTTP resource - Windows Client

### Describe the Bug

Hi, this was raised under Private HTTP resource - Windows Client
#3083 but was closed down. This issue still persists even when i have updated the client so that it is now using v0.11.0

When using pangolin client V 0.11.0 (GUI version) the windows machine cannot reach private resources when on a LAN. Other devcies on lan such as MAC laptop and phone are able to access the private resouece.

### Environment

OS Type & Version: Ubuntu 24.04.3 LTS
Pangolin Version: V1.19.2 --> running on a IONOS VPS
Gerbil Version:1.4.2
Traefik Version: v3.7.5
Newt Version: v1.13.0
Badger version: 1.4.4

### To Reproduce

When i do a nslookup on windows pc it shows the following:

server:unknown
Address:IP of my internal DNS server

Non authoritive answer:
name:[domain name of resource]
address:public ip of my VPS where pangolin is running

When i do a curl from my windows PC i get 404 page not found - same error message if i try to browse to the resource via the domain

### Expected Behavior

i should be able to access the private resource when the Pangolin client is running.

Start by reproducing the failure on the Windows GUI client using the reported LAN setup, nslookup result, and curl or browser request. Compare access from the Windows machine with the working Mac and phone paths; done means the Windows client can reach the private resource while running.

Written by the indexing model from the issue text.