Windows need TRACERT to solve local names

[jurendes]

Hi, i've an issue that i think is with my Windows System when using openvpn.

Once connected the OpenVpn Client it only solve the local net names after using the TRACERT command to any device (except the one where the OpenVpn Server is running)

After using TRACERT, e.g. To the remote router: TRACERT 192.168.0.1 (The IP of my router in the Openvpn Server net, the remote one), it begins to work properly solving remote names as expected, like if you where working locally.

But it only last for a while, aprox. 15min., and then i need to do the same again and again.

i,ve checked the ROUTE PRINT result before using TRACERT and after, and nothing changes.

Hope some can help.

[TinCanTech]

I assume you are relying on Windows to resolve network names ?

[jurendes]

Sorry, i'm not an expert, I thougth solving routes was happening in the router, but no idea. In my net i have a Debian Server with SAMBA, a NAS with Linux system where is running then OpenVPN Server, and some Personal Computers runnig Windows 10.

This Issue is happening just with one Laptop runnig Windows 10, and thats why i think it may be something wrong with then Windows 10 configuration that could be happening to more people.

[TinCanTech]

In order to help others, you need to identify your problem first,