Connecting to TC with Teamviewer by IP Address

curtswanson · Post by **curtswanson** » Mon Sep 14, 2009 3:44 pm

I am unable to connect to my TC via Teamviewer using the TC's IP address. I have the "Allow LAN Connections" setting checked but I do not have the "LAN Connections Only" setting checked. I have read what seems to be the definitive post on this topic:

http://www.phoneservicesupport.com/team ... t4038.html

But the apparent solution in that post does not seem to fit my situation as my TC's System Properties are already set to accept remote connections.

I have a laptop that I use as an HTPC. I can connect to it using Teamviewer with its IP address regardless of the "LAN Connections Only" setting. Since access by IP address is not working on my TC with "LAN Connections Only" off, I am hesitating to try it with "LAN Connections Only" on because, then, if I cannot connect, I will have to cart my monitor, keyboard and mouse to the basement (I know I am lazy).

I am not running any firewall on my TC. The firewall on my desktop, free ZoneAlarm, has my entire LAN as a trusted zone. I can ping my TC's IP address from my desktop. I can also ping my desktop from my TC.

Has anyone else had this issue and resolved it?

STxFarmer · Post by **STxFarmer** » Tue Sep 15, 2009 9:16 am

Didn't think Teamviewer had anything to do with the IP address of the machine you are trying to connect to. Teamviewer assigns a unique address number used by any other Teamviewer computer to connect to another. Once you have that unique number of the TC you are good to go.

curtswanson · Post by **curtswanson** » Tue Sep 15, 2009 10:36 am

When you use the ID number that Teamviewer provides, you connect using the Teamviewer servers over the internet. When you connect using the IP address of the device, the data only travels through your LAN. This should make for a faster and more secure, I think, connection.

Based on the Teamviewer manual, in the Options General tab, you select "Accept Incoming LAN Connections" which should allow you to use either method. On the Options Advanced tab, selecting "LAN Connections Only" should limit you to the IP address option.

This works flawlessly when I connect from my desktop to my HTPC by IP address regardless of the "LAN Connections Only" setting. However, I cannot connect to my TC using IP address at all with "LAN Connections Only" turned off. I have not tried it yet with "LAN Connections Only" turned on.

I have not yet tried turning it on because I will have to hook my TC up to a monitor, keyboard and mouse if it still does not work because I will have eliminated the option to use the Teamviewer ID.

VaHam · Post by **VaHam** » Tue Sep 15, 2009 7:26 pm

curtswanson wrote:When you use the ID number that Teamviewer provides, you connect using the Teamviewer servers over the internet. When you connect using the IP address of the device, the data only travels through your LAN. This should make for a faster and more secure, I think, connection.

Based on the Teamviewer manual, in the Options General tab, you select "Accept Incoming LAN Connections" which should allow you to use either method. On the Options Advanced tab, selecting "LAN Connections Only" should limit you to the IP address option.

This works flawlessly when I connect from my desktop to my HTPC by IP address regardless of the "LAN Connections Only" setting. However, I cannot connect to my TC using IP address at all with "LAN Connections Only" turned off. I have not tried it yet with "LAN Connections Only" turned on.

I have not yet tried turning it on because I will have to hook my TC up to a monitor, keyboard and mouse if it still does not work because I will have eliminated the option to use the Teamviewer ID.

Just a thought is your HTPC set to allow windows logins in TV and your TC set not to allow windows logins? I actually did not have that shown correctly when I went back and reviewed the info I posted in that other thread so I changed it to show allowing windows logins for administrators only. See the pic below which is the changed version and what I actually run:

Try that setting and see if it makes a difference.

curtswanson · Post by **curtswanson** » Wed Sep 16, 2009 3:28 pm

Thanks VaHam for the suggestion. I tried that change and I still could not connect with the IP address. the response continues to be an error pop-up window that says "A connection could not be established. Reason unknown."

VaHam · Post by **VaHam** » Thu Sep 17, 2009 2:01 am

curtswanson wrote:Thanks VaHam for the suggestion. I tried that change and I still could not connect with the IP address. the response continues to be an error pop-up window that says "A connection could not be established. Reason unknown."

Hummm usually when something like this happens to me it is something simple I over looked.

Can you confirm you have the "Accept incoming LAN connections" checked in the General tab of the TC's TV and the proxy selection of "No proxy"?

curtswanson · Post by **curtswanson** » Thu Sep 17, 2009 10:08 am

"Accept incoming LAN connections" checked in the General tab of the TC's TV and the proxy selection of "No proxy" - Check.

I am sure you are right that it is something simple. I realized the TC was not joining my network workgroup. It was joining the default WORKGROUP but my workgroup has a different name. I made that change but it still does not work.