TeamViewer Forum

General Category => Teamviewer for Windows => Topic started by: FourCandles on August 06, 2015, 06:29:05 AM

Title: Windows Server 2012 R2 Essentials - TV can't get internet connection
Post by: FourCandles on August 06, 2015, 06:29:05 AM
Hi,

I installed TV on a fresh install of Windows Server 2012 R2 Essentials and it was working fine. Took the server to a client and the server can connect to the internet and ping various TV sites but TV won't connect. Tried re-installing TVH, tried TV QS, tried rebooting the server, tried turning off all firewalls, tried putting the server into the DMZ, tried a different IP address, tried turning off UTP. But still the same issue.

The office has a bunch of other servers and PCs running TVH without any problems at all.

Help!
Title: Re: Windows Server 2012 R2 Essentials - TV can't get internet connection
Post by: FourCandles on August 06, 2015, 06:31:13 AM
And here's some log file:

2015/08/06 14:26:42.562  3144   736 S0   Updateing Keys on Login
2015/08/06 14:26:42.562  3144   736 S0   Resource-Language:en
2015/08/06 14:26:51.237  3144   736 S0!! S191 NC.ReadHttp.SendRequest.12002, Errorcode=12002
2015/08/06 14:26:51.237  3144   736 S0!! HttpQueryInfoNum(19) failed with error 12019, Errorcode=12019
2015/08/06 14:26:51.237  3144   736 S0!! HttpQueryInfo(20) size failed with error 12019, Errorcode=12019
2015/08/06 14:26:51.237  3144   736 S0!! S191 NC.ReadHttp: Could not establish a connection: 0 , Errorcode=12019
2015/08/06 14:26:51.237  3144   736 S0!! S191 NC.ReadHttp.Failed1.12019
2015/08/06 14:26:51.237  3144   736 S0!  S191 NC.ReadHttp.Retry
2015/08/06 14:26:59.733  3144   736 S0!! S191 NC.ReadHttp.SendRequest.12017, Errorcode=12017
2015/08/06 14:26:59.733  3144   736 S0!! S191 NC.CHttp.Conn.Failed
2015/08/06 14:26:59.733  3144   736 S0!! CT191 CT.ConnectFailed: -1
2015/08/06 14:26:59.733  3144   736 S0   CT191 CT.Disconnect
2015/08/06 14:26:59.733  3144   736 S0!!!Connect to Master master8.teamviewer.com / 178.77.120.104 failed!
2015/08/06 14:26:59.733  3144   736 S0!! MC.Connect.Failed
2015/08/06 14:26:59.733  3144   736 S0!! MC.L addonchannels=0&ckaportsenabled=0&client=TVH&commercial=1&f=Login&gw=0&gwlevel=430&hideonlinestatus=0&httpout=1&iguid={5f56e8d1-0140-4769-8da1-88609191b293}&keepalive=1&language=en&licensetype=10000&midf=1&midhistory=0x308d99fc58ce_1ce9f3c9365c7ab_1105107012|u3936373731375a433235323932313259308d99fc58d1fcc7e29e43ea811e5502e6c54a3145d8&noofactivekeepalive=0&os=Win_6.2.9200_S&port443out=0&rhash={adc84b11-d198-a8ab-50a9-1ecdae4d07df}&runtime=2838&smidv=1&sro=0&supportedfeatures=867171292&tcpout=0&v=9.0.41110 H&windowsserveruser=System - 10
2015/08/06 14:27:11.254  3144   736 S0!! NetWatchdog: Port 443 proxy search failed! No working setting found.
2015/08/06 14:27:19.356  3144   736 S0!! NetWatchdog: Port 80 proxy search failed! No working setting found.
2015/08/06 14:27:39.428  3144   736 S0!! NetWatchdog: Port 443 proxy search failed! No working setting found.
2015/08/06 14:27:46.685  3144  2840 S0!  CWaitAtGatewayThread::Reconnect() Reconnect started. noWait = 0
2015/08/06 14:27:47.569  3144   736 S0!! NetWatchdog: Port 80 proxy search failed! No working setting found.
2015/08/06 14:27:47.569  3144   736 S0   Resource-Language:en
2015/08/06 14:27:56.627  3144   736 S0!! HttpQueryInfo(66) size failed with error 12150, Errorcode=12150
2015/08/06 14:27:56.627  3144   736 S0   S198 NC.CHttp.Conned
2015/08/06 14:27:56.627  3144   736 S0   CT198 CT.Send.CMD_MASTERCOMMAND From=285411724 To=0 L=663
2015/08/06 14:28:14.734  3144   736 S0   CT198 CT.Receive.CMD_MASTERRESPONSE From=0 To=285411724 L=263
2015/08/06 14:28:14.734  3144   736 S0   CT198 CT.Disconnect
2015/08/06 14:28:14.734  3144   736 S0   MC.L addonchannels=0&ckaportsenabled=0&client=TVH&commercial=1&f=Login&gw=0&gwlevel=430&hideonlinestatus=0&httpout=1&ic=2004549173&id=285411724&iguid={5f56e8d1-0140-4769-8da1-88609191b293}&keepalive=1&language=en&licensetype=10000&logging=1&mid=u3936373731375a433235323932313259308d99fc58d1fcc7e29e43ea811e5502e6c54a3145d8&midf=1&midhistory=0x308d99fc58ce_1ce9f3c9365c7ab_1105107012|u3936373731375a433235323932313259308d99fc58d1fcc7e29e43ea811e5502e6c54a3145d8&midv=1&noofactivekeepalive=0&os=Win_6.2.9200_S&port443out=0&rhash={adc84b11-d198-a8ab-50a9-1ecdae4d07df}&runtime=2903&smidv=1&sro=0&supportedfeatures=867171292&tcpout=0&v=9.0.41110 H&windowsserveruser=System - 0#OK_10000_-_2__37.252.253.2:80_33282_1_-1_0.0.0.0__178.77.120.101_178.77.120.100_0_285411724_1_0_0_0_31195001__37.252.253.2,92.51.156.70,178.162.204.224,37.252.227.3,37.252.225.3,178.255.154.12,178.255.156.102,159.8.191.4,217.146.1.45,88.198.136.208,37.252.224.5
2015/08/06 14:28:14.734  3144   736 S0   CT199 CT.TM_WaitAtGateway.37.252.253.2:80 - CT199 - S199
2015/08/06 14:28:14.734  3144   736 S0   CT199 CT.Connect to TeamViewer Router 37.252.253.2:80
2015/08/06 14:28:22.584  5036  4964 G1   CMainWindow::TrackIdleTime(): System goes idle. (IdleTime=307218)
2015/08/06 14:28:22.584  5036  4964 G1   TVUpdate::CheckForAutoUpdates(): AutoUpdateMode=1, LastAutoUpdate=0, AdminRights=1
2015/08/06 14:28:22.897  3144   736 S0!! S199 NC.ReadHttp.SendRequest.12017, Errorcode=12017
2015/08/06 14:28:22.897  3144   736 S0!! S199 NC.CHttp.Conn.Failed
2015/08/06 14:28:22.897  3144   736 S0!! S199 NC.Connect.RetryHttp, Err=0
2015/08/06 14:28:30.930  3144   736 S0!! S199 NC.ReadHttp.SendRequest.12017, Errorcode=12017
2015/08/06 14:28:30.930  3144   736 S0!! S199 NC.CHttp.Conn.Failed
2015/08/06 14:28:30.930  3144   736 S0!! CT199 CT.ConnectFailed: -1
2015/08/06 14:28:30.930  3144   736 S0   CT199 CT.Disconnect
2015/08/06 14:28:30.930  3144   736 S0   CT.Disconnect.TM_WaitAtGateway finished
2015/08/06 14:28:30.930  3144   736 S0   CT199 CT.Term.TM_WaitAtGateway: SendQueueThread stopped
2015/08/06 14:28:30.930  3144   736 S0   CT199 CT.Term.TM_WaitAtGateway: Terminated
2015/08/06 14:28:39.979  3144   736 S0   S200 NC.CHttp.Conned
2015/08/06 14:28:39.979  3144   736 S0   CT200 CT.Send.CMD_MASTERCOMMAND From=285411724 To=0 L=184
2015/08/06 14:28:41.924  3144  2840 S0!  CWaitAtGatewayThread::Reconnect() Reconnect started. noWait = 0
2015/08/06 14:28:58.096  3144   736 S0   CT200 CT.Receive.CMD_MASTERRESPONSE From=0 To=285411724 L=4
2015/08/06 14:28:58.096  3144   736 S0   CT200 CT.Disconnect
2015/08/06 14:28:58.096  3144   736 S0   Resource-Language:en
2015/08/06 14:29:07.151  3144   736 S0   S201 NC.CHttp.Conned
2015/08/06 14:29:07.151  3144   736 S0   CT201 CT.Send.CMD_MASTERCOMMAND From=285411724 To=0 L=663
Title: Re: Windows Server 2012 R2 Essentials - TV can't get internet connection
Post by: matt on August 08, 2015, 02:28:30 AM
What are the DNS settings for this machine?
Is IPv6 enabled?
Title: Re: Windows Server 2012 R2 Essentials - TV can't get internet connection
Post by: hslfni on August 18, 2015, 09:50:35 AM
We are experiencing the same problem with two Windows Server 2012 R2 machines. Same errors in the log file.

Have you found a solution for this problem?



Quote from: FourCandles on August 06, 2015, 06:29:05 AM
Hi,

I installed TV on a fresh install of Windows Server 2012 R2 Essentials and it was working fine. Took the server to a client and the server can connect to the internet and ping various TV sites but TV won't connect. Tried re-installing TVH, tried TV QS, tried rebooting the server, tried turning off all firewalls, tried putting the server into the DMZ, tried a different IP address, tried turning off UTP. But still the same issue.

The office has a bunch of other servers and PCs running TVH without any problems at all.

Help!
Title: Re: Windows Server 2012 R2 Essentials - TV can't get internet connection
Post by: FourCandles on August 19, 2015, 01:23:09 AM
Hi,

I contacted support and they came back with this:

***********************

Explicit Congestion Notification (ECN) is an extension to the Internet Protocol and to the Transmission Control Protocol and is defined in RFC 3168 (2001). ECN allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that may be used between two ECN-enabled endpoints when the underlying network infrastructure also supports it.

Conventionally, TCP/IP networks signal congestion by dropping packets. When ECN is successfully negotiated, an ECN-aware router may set a mark in the IP header instead of dropping a packet in order to signal impending congestion. The receiver of the packet echoes the congestion indication to the sender, which reduces its transmission rate as though it detected a dropped packet.

Rather than responding properly or ignoring the bits, some outdated or faulty network equipment drop packets that have ECN bits set.

ECN support can be disabled with the following shell command run as administrator:

netsh interface tcp set global ecncapability=disabled

ECN is activated by Default since Windows 2012, network infrastructure is not always ready for this feature and this is why we would suggest this.

***********************

I ran that command to disable ECN and Teamviewer was able to connect.

I have other clients with Windows Server 2012 and have no problem with TV connections without having to disable ECN, so I'm assuming it's something specific to this client's ISP provided fibre router or ISP infrastructure that's causing the issue.

I haven't picked up on any issues due to disabling ECN on that server.