Hello, first time poster so be gentle lol. We are using TeamViewer 12 inside our network to manage servers since our office is a block away from the actual location, we have a dedicated fiber connection and run two DC's.

The main DC will not allow a TeamViewer connection after about 12 hours or so. I have to reboot the Dc and then it will work just fine for a about a day. I have uninstalled and reinstalled TeamViewer, scoured the event logs and do not see anything that indicates the service is stopping. I have even restarted the service and that does not work but a full reboot will fix the problem. Any suggestions on how to troubleshoot this or fix the problem wold be greatly appreciated.ThanksEdited Jan 22, 2018 at 16:20 UTC. Starg33ker wrote:Lakecoit wrote:RDP will also work when TeamViewer will not.I'd stick with that. It's native to Windows.

Less overhead!Lakecoit wrote:it drives me nuts when something should work but is notI get it.when you log in via RDP when TeamViewer isn't working, do you see anything wonky with the application? Fail to load? Can you upgrade to 13?Nothing strange at all, honestly would not have noticed it's an issue as everything else is works fine. I don't think upgrading to 13 would help as it works without issue on all our other servers. Lakecoit wrote:Toby, we do use RSAT generally but noticed that this was not working, and it drives me nuts when something should work but is not, the DC is also a virtual machine. RDP will also work when TeamViewer will not.If you cant connect to a DC with RSAT tools (even sometimes) there is a bigger/wider network issue. I would start investigating this rather than trying to fix Teamviewer.For day to day stuff my team probably use ADUC, DHCP, DNS, ADSI Edit and Powershell.

Select TeamViewer from the list then click OK. If TeamViewer is not listed, click Browse, navigate to the installation folder of TeamViewer, select the main executable (for example, TeamViewer.exe), click Open, and then OK all through out. Run TeamViewer and see if this fixes the problem. If it doesn’t, run TeamViewer as administrator. No Connection To Teamviewer Server. I live in a rural area at live chat channel on the. Are you sure you're answer helpful? The software, designed to conduct PC screen sharing & control activities Teamviewer 11 Not Ready Please Check Your Connection meeting idHi, i just bought a samsung note with android 2.3.6.

We RDP to the DC once a week to verify operational settings, patch verification etc. If you get to the stage where a tool isnt working its time to break out the usual toys and log files to diagnose where the issue is and fix that. Check DNS and System time. I agree with Toby. There is something up with the Network that isn’t allowing RSAT tools to function regularly.Also run dcdiag on the server to make sure everything looks ok. I’ve seen issues with stale records from a removed Domain Controller.As for the original question with TeamViewer, DNS or firewall inspection is most likely the issue.

Connection

Teamviewer No Connection To Teamviewer Server Download

Make sure to whitelist the connection URL. If you are using country blocking on your Firewall this could block the system status connection.Hope this helps.

I apologize for the confusion, I have no issues with RSAT tools, or RPD working when trying to connect with this server. I just stumbled accross the fact that TeamViewer does not work on this particular DC. We use TeamViewer to support remote users for the most part. It was a fluke that i tried it on this server and noticed an issue, I have tried to duplicate it on other servers and there are no problems. I will look at DNS and see if i notice anything strange there thanks for the suggestion. I have run several tools and the DC is working properly and not giving us any issues, not even any replication errors to DC2.

I guess more then anything I was wondering if anyone has had this issue before and could point me in the direction of a resolution.

Last week I decided to use TeamViewer VPN to administer software on a server behind a firewall using RemoteDesktop. It was easy to configure to start-up with the system and make VPN available on the other side but now it fails to connect at the step shown below:The remote machine is running Windows Server 2008 R2.Is there a native way to circumvent the external firewall using a server role or feature to make Windows Server do the VPN work?Do people have better / more reliable experiences with other products such as Hamachi?The requirements are as follows:. Start at remote system start-up time. Make VPN connections to the remote machine possible.

Comments are closed.