greg_gorrell Posted September 30, 2016 Share Posted September 30, 2016 I reverted back to unRAID 6.1.9 and got my Windows VMs installed again and now I have run into a frustrating issue. I cannot get RDP access on the Windows 10 VM. When I install Windows 7, RDP works right out of the box. I also had it working previously with Windows 10 when I upgraded using the Upgrade Assistant through the VM. This is a clean iso install of Windows 10 Pro. Running netstat, I can see the port is not listed at all. Here's all I have done so far: -Restarted the service, verified it is running -Imported registry files from working Windows 7 install (RPD-tcp or whatever) -Turned off firewall completely -Made sure it is turned on in system properties -Created a local only user account None of this has helped. When I try to connect from any clients (laptop, ipad, phone) I get the error that Remote desktop cannot connect to the computer for the following reasons: 1. Remote access not enabled 2. Remote computer is turned off 3. Remote computer not available on the network Note that I can access all of the other computers on the network, it is connected to the right domain and I even connected to the homegroup. Has anyone came across this before or have any other suggestions? Thanks in advance! Link to comment
johnodon Posted September 30, 2016 Share Posted September 30, 2016 Did you verify that the WIN10 VM is actually getting a valid IP (not a private 169.x.x.x one)? If so, did you try RDP'ing to the IP instead of the hostname? Link to comment
itimpi Posted September 30, 2016 Share Posted September 30, 2016 You certainly do not need to turn off the firewall - in fact doing so is dangerous. Have you unticked the box that requires the highest level of authentication? This will not work with most RDP clients. Link to comment
CHBMB Posted September 30, 2016 Share Posted September 30, 2016 You need to have Win10 professional for it to have a RDP server Link to comment
greg_gorrell Posted September 30, 2016 Author Share Posted September 30, 2016 Windows 10 is the pro version CHBMB (mentioned in the first post), and I am using the same key that I had previously used with Windows 7 Ultimate to do the upgrade assistant. It does have a valid IP (10.0.0.105) that I set statically and that is what I use to connect to it rather than the computer name. I only have the firewall turned off for troubleshooting, and this VM is only used to RPD into my network, but I do normally leave the firewall on. I will also note that I have the network set to private, as I have come across some threads on various forums where people have had issues with that. I went through all the basic common sense stuff and tried to let you all know what I did in the original post in case someone notices something I may have missed, but I think there is something else going on here. I can't see how the port is not listening if the service is turned on. Link to comment
CHBMB Posted September 30, 2016 Share Posted September 30, 2016 Sorry missed that, my bad... Link to comment
greg_gorrell Posted September 30, 2016 Author Share Posted September 30, 2016 You're fine, I don't understand what may be different between the two. Is it possible that I have a corrupt install? Sent from my SM-N910V using Tapatalk Link to comment
CHBMB Posted October 1, 2016 Share Posted October 1, 2016 Corrupt install unlikely. Tried turning off NLA? Link to comment
greg_gorrell Posted October 1, 2016 Author Share Posted October 1, 2016 Corrupt install unlikely. Tried turning off NLA? NLA is off as well. I am going to just update my Windows 7 VM to 10 so I have the RDP access again, but I am super stumped at what this could be.. I know there were issues with Windows Server 2012 and the remote desktop driver or some sort, but this driver isn't on Windows 10. Link to comment
landS Posted October 1, 2016 Share Posted October 1, 2016 We had the same issue with some bare metal windows 10 work computers after a clean install. The 'solution' was to use TeamViewer instead.... Link to comment
greg_gorrell Posted October 1, 2016 Author Share Posted October 1, 2016 I was waiting for that suggestion haha. I have used TeamViewer in the past but it definitely doesn't perform as well as RDP. I actually would rather upgrade Windows 7 again and go through that hassle than use anything but RDP. Plus I have access to RDP from my computer at work and I cannot add additional software. I would just prefer to know why this is acting up then to take the easy route. There's only so many things it could be one would think. Link to comment
GHunter Posted October 1, 2016 Share Posted October 1, 2016 My guess would be that the network type changed from private to public which would not allow your RDP connection. This can happen with a Windows or driver update. If you can get into it somehow either local or VNC, check your network type. Link to comment
f3dora Posted October 1, 2016 Share Posted October 1, 2016 Open "allow an app through Windows Firewall" and allow "Remote Desktop" (private and public networks) http://i.imgur.com/vJ3W2rr.png. Also open "Allow remote access to your computer" and enable RDP http://i.imgur.com/0msIWNL.png. With these settings it shouldn't matter if the network is public or private, if it still doesn't work try reinstalling the VirtIO drivers. Link to comment
johnodon Posted October 1, 2016 Share Posted October 1, 2016 Open "allow an app through Windows Firewall" and allow "Remote Desktop" (private and public networks) http://i.imgur.com/vJ3W2rr.png. Also open "Allow remote access to your computer" and enable RDP http://i.imgur.com/0msIWNL.png. With these settings it shouldn't matter if the network is public or private, if it still doesn't work try reinstalling the VirtIO drivers. He has the firewall completely disabled. Link to comment
f3dora Posted October 1, 2016 Share Posted October 1, 2016 Open "allow an app through Windows Firewall" and allow "Remote Desktop" (private and public networks) http://i.imgur.com/vJ3W2rr.png. Also open "Allow remote access to your computer" and enable RDP http://i.imgur.com/0msIWNL.png. With these settings it shouldn't matter if the network is public or private, if it still doesn't work try reinstalling the VirtIO drivers. He has the firewall completely disabled. I just wanted to make sure that he definitely tried with these settings, if this does not work its definitely a problem with the network connection. I am 99% sure that the VirtIO network driver is not installed correctly, OP please install the newest VirtIO drivers again to make sure that all of them work correctly. Link to comment
greg_gorrell Posted October 1, 2016 Author Share Posted October 1, 2016 I will reinstall the virtIO drivers right now f3dora. Just to be clear, this is set on a private network. It has not worked at all since it was a fresh install three days ago so no settings have changed due to updates. Like I said before, the port does not show up as listening so I am lead to believe it is something deeper than basic network settings. Link to comment
greg_gorrell Posted October 2, 2016 Author Share Posted October 2, 2016 The Fedora site has VirtIO drivers at release 0.1.126 and unRAID is only showing 0.1.102. I am going to download the 126 manually and try those as the highest the 102 version goes is Windows 8.1, which most people have been using with no issue. Link to comment
CHBMB Posted October 2, 2016 Share Posted October 2, 2016 The Fedora site has VirtIO drivers at release 0.1.126 and unRAID is only showing 0.1.102. I am going to download the 126 manually and try those as the highest the 102 version goes is Windows 8.1, which most people have been using with no issue. Something isn't right there.... Link to comment
greg_gorrell Posted October 2, 2016 Author Share Posted October 2, 2016 I had to downgrade to 6.1.9 again so the VM settings page does have the latest version listed automatically but I didnt have the option for 118-2 when I was on 6.2. So regardless, I just updated the VirtIO Ethernet Driver to the 126 version from the Fedora site and it site doesn't show up as listening after a restart even. Something must be corrupt with the RDP service. I have had Windows installs act up with weird bugs and glitches in the past like this so thats the main reason I am leaning towards that. Link to comment
f3dora Posted October 2, 2016 Share Posted October 2, 2016 The Fedora site has VirtIO drivers at release 0.1.126 and unRAID is only showing 0.1.102. I am going to download the 126 manually and try those as the highest the 102 version goes is Windows 8.1, which most people have been using with no issue. Something isn't right there.... OP is it possible that for some reason your browser doesn't display the VirtIO iso list correctly, i think the list should be integrated into unRAID? I have version 6.2 as well and this is my VirtIO iso list: I had to downgrade to 6.1.9 again so the VM settings page does have the latest version listed automatically but I didnt have the option for 118-2 when I was on 6.2. So regardless, I just updated the VirtIO Ethernet Driver to the 126 version from the Fedora site and it site doesn't show up as listening after a restart even. Something must be corrupt with the RDP service. I have had Windows installs act up with weird bugs and glitches in the past like this so thats the main reason I am leaning towards that. Did you move the virtual harddisk after creating it and if you run chkdsk and sfc /scannow do you get any errors? Also is the windows activation status displayed correctly and do you get any errors when running slmgr commands? Link to comment
greg_gorrell Posted October 2, 2016 Author Share Posted October 2, 2016 I created both VM's after the downgrade as I had some disk errors prior to and unrelated to the 6.2 upgrade. These are both fresh installs with no errors when running slmrg in either of them. The VM settings page displays the same thing in both Edge and Chrome, see attachment. Link to comment
f3dora Posted October 2, 2016 Share Posted October 2, 2016 I created both VM's after the downgrade as I had some disk errors prior to and unrelated to the 6.2 upgrade. These are both fresh installs with no errors when running slmrg in either of them. The VM settings page displays the same thing in both Edge and Chrome, see attachment. WTF? Ok something is definitely not right here... Picture is my server (6.2), compare the Libvirt and QEMU versions. Link to comment
saarg Posted October 2, 2016 Share Posted October 2, 2016 I created both VM's after the downgrade as I had some disk errors prior to and unrelated to the 6.2 upgrade. These are both fresh installs with no errors when running slmrg in either of them. The VM settings page displays the same thing in both Edge and Chrome, see attachment. WTF? Ok something is definitely not right here... Picture is my server (6.2), compare the Libvirt and QEMU versions. He downgraded to 6.1.9, so no wonder it's old versions of libvirt and qemu. Link to comment
saarg Posted October 2, 2016 Share Posted October 2, 2016 You said earlier that you set the IP statically, but I wonder if you have set the network in the VM template to br0 also? If it's set to virbr0 and you set the IP manually, it will not work. Setting the IP to dhcp and check what you get is also an easy way of seeing which bridge you are connected to. Link to comment
f3dora Posted October 2, 2016 Share Posted October 2, 2016 I created both VM's after the downgrade as I had some disk errors prior to and unrelated to the 6.2 upgrade. These are both fresh installs with no errors when running slmrg in either of them. The VM settings page displays the same thing in both Edge and Chrome, see attachment. WTF? Ok something is definitely not right here... Picture is my server (6.2), compare the Libvirt and QEMU versions. He downgraded to 6.1.9, so no wonder it's old versions of libvirt and qemu. OP please upgrade back to 6.2 and check if your VM settings look like in my screenshot. You said earlier that you set the IP statically, but I wonder if you have set the network in the VM template to br0 also? If it's set to virbr0 and you set the IP manually, it will not work. Setting the IP to dhcp and check what you get is also an easy way of seeing which bridge you are connected to. IMO its easier to just use DHCP and set the ip and dns servers in the router. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.