>>You don't have to. Before you connect, run "nslookup myub" in a CMD window, which will show the ultrabook's current IP address.
>
>That's the part which is automated. I do this dozens of times a day. I only click on a .rdp icon and it goes into the connection right away. So, I have updated the .rdp file to use the fix IP. But, now that I have a fix IP, when I go on the road, this will cause a conflict. So, I guess I am better off to keep using the DNS name and find what has started to cause those problems since a while.
>
>It is Windows 8.1. So, I am assuming a bad Windows update could have been in effect at a certain point causing this.
>
>>Just to confirm, you've tried connecting to your ultrabook via its IP address, and you still have the problem?
>
>Yes, even with the IP address, the problem remains, and without a VPN.

OK, so the problem has nothing to do with VPN.

The last Patch Tuesday was February 11th. You could go into your Windows Update history on the ultrabook and uninstall the updates that were applied on that date, see if that fixes the issue.

BUT today is also Patch Tuesday. You might want to wait until today's patches are applied, maybe they include a fix. If they don't you could uninstall patches applied today and in February.

Here is an article from last November - you may have the patches/updates already but it shows what to check: http://windowsitpro.com/windows-7/windows-7-sp1-can-now-connect-remotely-windows-81-and-windows-server-2012-r2