When connected to VPN, host name still resolves to WiFi IP address

I recently received a new laptop and went through our company's IT process to install the base Windows image (Windows 11 Pro 24H2). I connect to my WiFi router fine and receive an IP address (for example, 192.168.1.xxx). When I ping my host name (ping %COMPUTERNAME%), I can see in the results that the %COMPUTERNAME% environment variable resolves to my host name, which resolves to the IP address 192.168.1.xxx. And the ping is successful.

I then connect to our Cisco AnyConnect VPN, which assigns me a new IP address (for example, 10.43.105.xxx). Now when I ping my host name (ping %COMPUTERNAME%), it still resolves to the 192.168.1.xxx IP address, instead of to the VPN-assigned IP address of 10.43.105.xxx. And the ping fails with the error "General failure".

This failure to be able to address my host by name when connected to the VPN is causing problems with some of the applications I have to use.

I have an older machine that is set up in a similar way that does not have this issue. The ipconfig /all command shows the WiFi and VPN IP addresses and other attributes, but I don't see any issues there. Is there a way to determine why the host name is resolving to the WiFi IP instead of to the VPN IP?

A search turned up this link on this forum, but it looks like the VPN interface already has the lowest Interface metric (which I believe means it has the highest priority). Thanks.

It's going to depend a lot upon how the VPN is configured, split tunneling configuration and what's allowed or enabled to go through the VPN tunnel interface. In short, talk to your IT team.

Thanks nemobeer. Yes, I've had a ticket open with our IT team for over a week now, but no resolution.
It looks like our Cisco AnyConnect VPN is using an IPv4 Tunnel Mode of "Split Exclude".

If you're on your home network, as far as the home network is concerned your address is the 192... address. The VPN address comes from a VPN pool from the VPN server and nothing on your home network would be aware of that address. It's literally a virtual interface solely existing on that computer. If you're trying to connect to that computer from that computer I would recommend using the loop back for that purpose.