Unable to curl webservice inside container from host

Docker Desktop
1

Hello,

I’m unable to curl a webservice inside a windows container from the docker host (windows).
If I exec to the powershell inside the container i can curl the service (http://localhost:5000) and everything is fine.
I published the port in the docker-comopse file:
ports:

  • 5000:5000

I think my problem is the company network, the request is routed to the wrong location.

If I type ipconfig /all inside the container I see that there is a network adapter with DNS Suffix fritz.box, but this is my home network (at home it’s working fine). Have i change something, if i connect to the company network?

Windows IP Configuration

Host Name . . . . . . . . . . . . : e08ffce9fbc9
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : fritz.box

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : fritz.box
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-2D-F4-CB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b8:55ce:2046:540a%4(Preferred)
IPv4 Address. . . . . . . . . . . : 172.27.250.54(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . : 172.27.240.1
DHCPv6 IAID . . . . . . . . . . . : 67114333
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-F7-C8-5A-00-15-5D-2D-F4-CB
DNS Servers . . . . . . . . . . . : 172.27.240.1
192.168.178.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Can some network specialist help me?
How i can figure out the exact network problem and how to resolve it?

Thanks & Regards

2

I tested something… If I’m at home and not connected to the Company VPN everything is working fine.
But when I connect to the VPN (with Pulse Secure) a new Network Interface is created (Get-NetIPInterface) and I cannot curl the Container anymore.

3

Check the routes that VPN adds, then check if they match the container network.