Is there a way to use the Task Scheduler to auto start the host? I thought I saw a guide to do that somewhere & I can't find it now. I'm having problems with a client's host not starting now after a W10 upgrade. Tried reinstalling the latest host version & verifying service is set to auto on the admin account. Also sometimes when doing a simple upgrade the host fails to start afterwards & requires manually starting the host. If there was a way to Task Schedule host to automatically start if crashed that would help. I never upgrade a client now unless I'm connected on my other remote program in case I lose the host during upgrade.
I have a similar issue or perhaps the same one as Steven and Cristian. I only have one Viewer PC and no plans for any additional Viewers needed so my solution was to stop using the cloud address book feature altogether.
When I was using the cloud address book I needed to repeatedly sign back in to the server because it would sign me out very frequently and this made adding and removing clients very tedious or impossible. Eventually I couldn't even sign in at all and I just gave up on using the feature and exported my address book to the Viewer and disabled signing in to the server so now my Viewer launches much faster.
As a side note, I can only connect and see the online status of clients when I am on the same LAN as the server if my Viewer PC's network connection is routed through a VPN. For some reason it doesn't work from inside the network. When I'm using my cellular hotspot or another ISP or my VPN it works but I can't connect to the server domain address from inside the network.
A side note to the side note; the only way I am able to make clients I know are online appear online and connectable while my Viewer is on the same LAN as the server without using a VPN is if I edit the server address on each client on the Viewer address book and remove the domain name of the server and enter the server LAN IP address. Obviously this isn't going to work for when I'm on the road so I just use my VPN in the office instead.
It's not really a problem for me to use a VPN while in the office so I'm not complaining, I just think this is an interesting problem and if anyone else has dealt with it and has a fix I'm all ears.
I am having an issue with the Microsoft Malware Removal Tool version October 2018 detecting RU Host 6.9.4 files as threats and deleting them. Just thought I'd share in case anyone else was having this issue or plans to use MRT.exe on clients PC's. Luckily I use two different remote programs so I was able to reinstall RU through my other program and then re-ran MRT.exe to verify that it was in fact the source of the problem.
So this might have something to do with the resolution of your server's DNS name inside the same network where the server is. This brings us to the "loopback" problem when a service tries to resolve an external IP address from the inside.
I think you nailed it. I, as a test, went into my Viewer and renamed the server DNS address with the local IP of the server and my contact immediately appeared online. I can ping my server DNS name from the command prompt from within the network and get a response. It responds with my public IP address.
I just tried ipconfig /flushdns on Viewer and Server, nothing changed.
I'm really perplexed by this issue. It used to work fine on the old modem in network and out of network. I'm using noip.com for dynamic DNS and the app is running on the server keeping the IP address updated with the domain name.
I am able to ping my server PC. It is using a dynamic DNS and I can ping that address on my Viewer PC and receive a response. They are both on the same network.
The only thing that changed from when it was working to now was the router controlling DHCP. I was careful to assign the new router the same IP range, the same static IP's I had before and the same port forwarding parameters.
Yesterday Spectrum had to come do some work on the cable connection and upgraded the cable modem to Wave 2 router. I forwarded port 5655 to my dedicated server as it was before but now when I am connected to the same network on the Viewer the clients all appear offline. If I connect my Viewer PC to my cellular hotspot network the clients on the dedicated server appear online and are connectable.
I don't know what is wrong. Can someone please help me figure this out?
I just wanted to update everyone that I made a change to my network which seemed to clear up all of my issues that I was having before, the network cable wasn't it, I can now work wireless or wired with no noticeable difference.
I reconfigured my network to have only one DHCP server and one NAT enabled router (both the same device). Since making this change many things improved including faster more reliable Xbox live connections, and, more importantly, the strange unreliability and stuttering issues while working remotely through my self hosted server abruptly ended as soon as I made this change.
The connection to my RU server used to travel through an unmanaged switch, to a Netgear router 192.168.1.1 with DHCP enabled, NAT "Open", to the cable modem/router combo 192.168.0.1 (DHCP, NAT'd). I have two other routers and they are connected to the Netgear router which was previously 192.168.1.1 and their LAN IP's were ending in .3.1 and .4.1 respectively, both were DHCP enabled. Now everything is on the same 192.168.0.1 IP table and it's running great.
It's been a few months since I made this change, sorry for the late update. I hope this helps others who may be experiencing the same stuttering/dropping/unreliable connections on a self hosted server. Make sure your network isn't too "smart".
I ran a network cable to my laptop's workstation and that seems to have improved performance. Also setting color to 8bit and processor usage to FPS or High seems to help. I think the main problem may be WiFi interference. There are several hotspots in proximity to me here and although I never have issues with normal web browsing on WiFi, I noticed a substantial increase in performance with my remote work when I switched to wired.