I have been been a vocal supporter of Microsoft, their ideas and their products for over 30 years and appreciate their product direction (with the possible exception of their recent guerrilla marketing tactics). Nevertheless, it was perhaps harsh for me to label this possibility as "typical" for the company. I know they are a huge corporation and have a lot of offerings, and obviously can't account for every combination of hardware, software and network environment, but sometimes the quality control is lacking. We've suffered through plenty of bad experiences with Microsoft, from blown updates/patches to rushed interface development to removal of popular feature sets. I don't know what it is yet, so I will continue on with Wireshark and other network scanning tools/logs until I locate the issue.Ĭliff - Per my "sleight" - I think the level of chastisement that I received in your last comment was unjustified. And Cliff, I think it is more along the lines of the firewall or network configuration as you originally suggested. So, there might be something with the update that corrected at least part of the issue, but I'm pretty sure there is still something wrong - there should be no hesitation. I went back and tried from the non-updated Windows 10 box to the same servers across the point-to-point VPN and still couldn't get the interface. It's not super-speedy like the Windows Server 2008 R2 remote desktop sessions and it hesitates, but the interface is at least accessible. The result, at least in my case, was that after Windows 10 Creator's Update was installed on my computer, I was able to access the desktop of all three Windows 2016 servers, both locally and across the VPN. I'm taking your advice and will Wireshark it to look at the flow, and will also scope the traffic and port access on the servers in question. I've been working with Windows remote desktop in multi-site environments ever since RDP first hit the scene, but I've never encountered this type of behavior. Like someone's pulling a shade over the desktop when I'm on a remote subnet. It's just that the screen is black and displaying a mouse pointer and I can't see what is going on. I can verify that after I remote in from the subnet. Another odd thing is that it does actually login. However, I'm thinking that it is something that I have misconfigured somewhere on the servers themselves - maybe some protection that doesn't like to pass or show the video from remote subnets. So, I agree with you that it is tied to our environment. Nice point about the Azure images - makes sense. And if the RDP protocols/ports haven't changed and I can manage all of the other non-2016 servers over those very same firewall/routers, then I don't know why 2016 won't work as well. Yep - when I mentioned no changes in the firewalls, I was referring to our group of Cisco and SonicWALL NSA units that support our point-to-point VPN tunnels and our SSL-VPN tunnels for traveling users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |