- #Remote sharing server alternative to teamviewer install#
- #Remote sharing server alternative to teamviewer android#
- #Remote sharing server alternative to teamviewer windows#
I may end up using AWS (Amazon Web Services) again as Google Compute Srvs. The AWS instance used to work fine with LogMe In at the time. DWS Remote Control is one of the lesser-known services for remote support but is a very simple and useful tool. Hopefully I can find someone knowing about this issue. It doesn't seem TeamViewer has a setting to change the port it connects with etc. I enabled those ports also to work for RDP in the Google Compute Instance interface, but still it made no difference.
#Remote sharing server alternative to teamviewer android#
Display and control your PC and Android devices. I don't know if it's either because the new port was being used or there is a policy somewhere directing it always to the original port again. Open source virtual / remote desktop infrastructure for everyone The open source TeamViewer alternative. So it changes it but on rebooting it goes back to be on the same port again. (of course to connect I had to do it through the original port). I noticed it goes back to be on the same port again. when I changed it and then rebooted the Win Server 2008 VM, and checked to see if it made the change. I tried changing the listening port to different numbers.
#Remote sharing server alternative to teamviewer windows#
as in the place where I am located (my desktop computer) the firewall blocks Windows RDP but does not block TeamViewer's. In order for TeamViewer do it's job and take its place. My main problem is having TeamViewer work without having to initiate the native Windows RDP. Or perhaps a setting were since it's a VM the screen is de-activated when the "Windows Remote Desktop" program is off or minimized etc.? Hopefully someone out there can help me! I don't know if it may be part of the Google Compute Services Instance settings so as to limit the remote desktop only to the native "Windows Remote Desktop" program. I did a complete version installation of TeamViewer as administrator, running on a Windows Server on google compute VM. This is probably due to fast user switching or a disconnected/minimized Remote Desktop Session." "The screen cannot be captured at the moment. (4G internet outside the firewall -of desktop trying to access the VM Instace through Team Viewer-).Įven if I minimize the "Windows Remote Desktop"on my laptop it will cut the connection through TeamViewer between the VM cloud instance and my Desktop computer.Īny help or ideas in there? It seems that either Team Viewer isn't able to start or somehow either the VM Windows Server screen only runs when the "Windows Remote Desktop" is running. The funny thing is that I can access that VM instance through Team Viewer Only, as long as it is connected through "Windows Remote Desktop" to a separate 3rd computer. Reason of why I installed Team Viewer on that VM instance.
#Remote sharing server alternative to teamviewer install#
I could install Team Viewer on the instance.īecause of Firewall issues I cannot run "Windows Remote Desktop" from my desktop to access that VM (google compute) Instance. I can access the instace via the "Windows Remote Desktop" no problem. I am running a Windows Server VM Instace on Google Compute Services. Supremo Remote Desktop Assistant A rather new entrant in the desktop sharing market, Supremo Remote Desktop Assistant is an excellent alternative to TeamViewer.
0 kommentar(er)
