greg_gorrell

Yes, I can ping the VM, access the public shares on it, and all other network functions. I changed the port in the registry even, and no matter what port I change it to it still does not come up as listening when running netstat.

Sorry that was my bad. The router is set to 10.0.0.1, my DCHP server issues IPs from 10.0.0.110-10.0.0.200 My unRAID server is 10.0.0.100 ubuntu server - 10.0.0.102 Windows 10 - 10.0.0.105 Windows 7 - 10.0.0.106 Like I said, all network functionality is okay. It is just the RDP port on the 10.0.0.105 Windows 10 VM.

As far is I know,KVM/QEMU has to use an image, either img or qcow files. There is no way to have it use the whole drive like you are asking.

It is set statically because I have 5 clients on my network that I need to always be at the same IPs (Ubuntu Server, this VM for RDP access, unRAID host, etc). I reserve the first 5 IPs on my subnet for this purpose., starting with 10.0.0.1 10.0.0.100 for the unRAID server. This VM is set to br0, and all network functions work other than the RDP port not listening. I have internet, network share access, and I can connect to that VM's shares from anywhere else. Also, I cannot upgrade to 6.2 as it does not work with my hardware (AMD FX series), and breaks my Windows VMs. That is the reason I had to go through the hassle of downgrading, reloading my VMs, and ultimately the reason I have this problem currently.

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.

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.

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.

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.

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.

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.

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

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.

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!

Sweet! Can you recommend a make+model I should look at? There seems to be so many options with very mixed reviews! Thanks!! https://www.amazon.com/Portta-PET30DP-10-Inch-Extender-Cables/dp/B003LZA95W/ref=sr_1_3?ie=UTF8&qid=1473357287&sr=8-3&keywords=cat5+hdmi

I had the same issues with 6.2. I am very disappointed in Lime Tech releasing this version without proper testing. But have a read at this link to see which config files you may want to save: https://lime-technology.com/wiki/index.php/Files_on_v6_boot_drive I learned a lot from using unRAID that past year as well, so I started fresh but I kept all of my shares. Its nice to have a copy of the flash drive so you can pick and choose the config files that are not going to change. They say you can just change the bzroot and bzimage files but that I have found causes more headaches then a clean wipe.

Please post your network configuration for unraid. Are you running a network bridge?

I had this happen to me as well. Format the USB drive, add the UnRAID files and run the make bootable script again. Something got corrupt in my case and you have to rule this out before wasting a whole lot of time investigating other causes.

OpenELEC Windows 7 - will not boot at all past splash screen, even when trying to install. It does seem to be running though as it is consuming a good chunk of memory. Windows 10 same as above. I installed and it ran fine with cpumode=host-passthrough, then quit after a day with the same errors as above. It is booting with the xml change Eric suggested, but I feel like performance is taking a hit. I don;t get why OpenELEC will work sometimes and then generate the earlier mentioned Execution Error.

Can anyone help me figure out why the limetech-plex docker would keep crashing and filling up my RAM until the server becomes unresponsive? In the course of 5 minutes, this docker will fill up 10% of my available memory, completely maxing it out in less than a half hour. Here's the log file: Note that is just a small sample of the whole log file. Here's the run command: The attached picture shows the top 20 processes in RAM after about 20 minutes. Just a little bit longer and my whole server will become unresponsive.

When I check for the crash report in the directory given, there are no .dmp files. The directory is empty. What is going on? This only started happening with the latest update. i'm unable to reproduce locally on my 6.2 final unraid box. can you please provide the output obtained by following this post. http://lime-technology.com/forum/index.php?topic=40937.msg481150#msg481150 root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="PlexMediaServer" --net="host" --privileged="true" -e TZ="America/New_York" -e HOST_OS="unRAID" -v "/mnt/cache/appdata/plexmediaserver/":"/config":rw -v "/mnt/user/Media/Movies/":"/Movies":rw -v "/mnt/user/Media/Music/":"/Music":rw -v "/mnt/user/Media/TV/":"/TV":rw limetech/plex 7935be23a4ccf35f3eb8839ea52d3f61fb8f689fb716c8055963c901fbb16039

Can anyone help me figure out why Plex keeps crashing, and filling up my RAM until the whole server becomes unresponsive? Over 5 minutes, these Plex processes fill up 10% of my RAM and keeps opening new processes until the RAM is depleted. Here is the log: When I check for the crash report in the directory given, there are no .dmp files. The directory is empty. What is going on? This only started happening with the latest update.

So you're saying that the only thing stored in the config/plugins/dockerMan/templates-user directory on the flash drive are the volume mappings? I can just download my dockers again and they will load the appdata currently on my cache drive?

Okay thanks Squid, I must have posted my initial question in a misunderstanding way because this is just the answer I am looking for. Maybe we should add those files to the page on v6 files, in the section about starting over. Some users may want to keep their Plex configurations when starting over.

You might need another XML change for your VM, look for: <topology sockets='1' cores='2' threads='2'/> and replace it with: <topology sockets='1' cores='4' threads='1'/> I went ahead and updated to the newest 6.2. That line breaks the Windows VM: When I change the number of cores back to one, all the VMs all boot up. OpenELEC and Ubuntu logs show the following:

Nope, not there. I have nothing showing up under user defined templates, or on the previous apps section of CA.