>One thing that seems to be not widely known is that when you connect to a VPN, your local computer's DNS servers are changed to the DNS servers of the remote network. You can see this by running ipconfig /all in a CMD window before you connect to the VPN, and again while you're connected.
>
>If you connect to your ultrabook via its hostname (e.g. "MyUB") then your system is using DNS to look up and convert that name into an IP address. Suppose you then connect to the VPN. If for any reason your system has to use DNS to look up the "MyUB" host name again, it will almost certainly fail because the VPN's DNS has no idea what "MyUB" is. You may be OK for a while if the result for "MyUB" remains in your local DNS resolver cache but if/when that value drops out DNS lookup will fail.
>
>To see if that's your issue you could try connecting to the ultrabook's IP address rather than its hostname, which would take DNS out of the picture.

If I assign a fix IP address to my ultrabook, this means it won't work when I will be on the road.

Also, even with a remote desktop IP connectivity, this does not help. This used to work ok before. Only since a few weeks, it started to act completely crazy with those disconnects.