Date   

Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

John Gleason
 

I have been using the Teamviewer free version for about 3 years with few disconnection problems.  That's remote from California to Australia. Where in Australia we have a less than optimal connections via satellite. (A possum once chewed though a connection). TV hardly ever drops out compared to Logmein which wants to drop about every 2 to 3 hours or so.  Sometimes LMI drops frequently. I will fine TV fully functional in those cases. We are sometimes limited by bandpass, so if I run at maximum screen resolutions to look at fine data, both TV and LMI will kick out pretty quickly. Mainly just monitor at lowest color res after initial setup. 


 No experience with the others, but much I think depends on the connection and the service at the remote PC in my personal experience.  Neither TV or LMI has any problem when managing the PC at the telescope in my backyard.


   


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Joe Zeglinski
 

Thanks Mike –
 
    Does “SPLASHTOP PERSONAL” ...  keep both local and remote screens etc., fully and simultaneously displayed ?
Microsoft Remote Desktop (RDP) always required the user to log back into the running session on Windows Pro and higher. It acts as if a “Switch User” command has been initiated, with the initial session then moved to running in background, but hidden and inaccessible until switching back with a login. You would think Microsoft, with all its in-house smarts, would have fixed that, decades ago.
 
    I need to be able to get to the session screen without the delays of fumbling in the dark, logging in again, just to see the active session screen, when there is a panic situation with my AP mount about to collide.
 
Joe


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Michael
 

I will offer a different suggestion to try - I use Splashtop Personal. It's free and has worked well for me for years. I can control my observatory computer from the house with my office PC, iPad, or iPhone. I don't leave it running all night, but just pop on and off as needed to see how the observatory computer is doing. It doesn't log off the observatory computer so it purrs happily, but I can control the computer if needed.


Mike


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Joe Zeglinski
 

Thanks Mike,
 
    I may have to eventually go with VNC,  if this TeamViewer connection “randomness” doesn’t get resolved.
VNC is probably the second most common remote support package out there, and indeed the TeamViewer website “compares itself (briefly) to VNC – claiming only that TV doesn’t have the need for “port forwarding”, so it is easier to configure.
 
    I also thank Ray, for suggesting RADMIN. Can’t beat the $49 (version) lifetime license, compared to over $800 for a Commercial (non-timeout plagued version) of TeamViewer.  As I recall from RADMIN website, the standard version is for 3 client connections, which should suffice the average telescope setup from a couple of PC’s. Besides, can’t get better recommendation,  than its being used by Ray Gralak. I may dedicate RADMIN for astronomy, and continue wit TeamViewer for more mundane family PC remote support.
 
    I would prefer that TeamViewer would not have the “randomness” – I could just about live with the 3-hour cut-off, for the free version. TV is nice for quick and easy support of remote family and friend computers, since they can download and install it themselves, without any technical “port forwarding” expertise. It is probably why many or most,  large computer software companies use it and have customers download TV to solve a problem, with them on-line. Of course, these software companies will have their own TV name  “rebranded” versions for the download, but it is still TeamViewer inside, something every user can become comfortable using themselves. It is also easy to download at say, a friend’s house, and immediately log into one’s,  already running telescope session, just to check up on CCD imaging progress,  while away on a dinner visit, for example.
 
*******
BTW:
    For those using TeamViewer, (in EXTRAS->log files)  the “Connections_incoming.txt” log file is interesting – a log listing the  incoming host PC name, its TV ID-number, and Session connect/disconnect times.
Unfortunately this log seems to use UT-Time, while the other, far more detailed and complex,  “TeamViewer11.log”  activity file uses Local Time, so beware of the difference. They should have just used a single time standard for all logs to sync up the activities reports. The connections log is helpful in examining, perhaps by importing into a spreadsheet and its graphing,  to see just how long a session lasted, before being shut down or lost, over weeks or months of telescope use.
********
    Last night – strictly JUST for “fun” – while debugging my TeamViewer system, I wanted to see  how many client connections could be “CASCADED” to each other,  connecting sessions to the Scope PC. So, I connected as client from one home (client) laptop to my Scope (host) PC. Then I went to a second PC, and connected to the first “client PC” which was already operating the scope remotely. I was surprised that I now saw the Scope window inside the first client window, on my (second) client PC window – “a picture, in a picture, in a picture”, if you like.
 
    Next,  I wondered if this client -  remoting the former two - could actually still “CONTROL” the Scope PC (via the initial client). Sure enough, my mouse controlled the Scope PC mouse position – I still had control, two client PC’s down the lane. In fact, I was even more surprised, that this second client’s Windows clipboard was also connected to the Scope PC clipboard. I could copy something saved to my distant client clipboard, and paste it directly, on the remote Scope PC screen (file name, text into a WordPad doc.  etc). Wow !
 
*****
    Going for broke ... I clicked on the TeamViewer icon on that Scope window and made yet a THIRD connection ... “Right back to myself”,  the second client – a Closed Loop connection. Talk about “Screen Art” – there was suddenly a cascade of hundreds of copies of  ALL the client screens, ever decreasing in size into a “naked singularity”. The effect was like viewing an object set between two mirrors facing each other – infinite number of  projections. At first I thought I really broke my PC graphics card this time, and would need to Shutdown Windows – but the effect was easy to close, by simply clicking the red-X on the “outermost” TV session window, to disconnect from the first client PC session.
 
    As I said ... just for fun – and to see just how tolerant TeamViewer software could be.  ... Very Powerful program !
Normally I might “DIRECTLY” log into the Scope control PC, from a second client – but I wonder how the APCC would know where commands are coming from, the first or second client simultaneous session, and would the AP Mount’s CPx controller get muddled by two dual access sources. But that is for another day.
******
 
    So ... Right now I am still desperately trying to resolve the simple host/client connection problem. Possibilities include:
-----
  1. Bug in TeamViewer – connection code ... (perhaps less likely).
  2. The Linksys WRT-610N “Simultaneous Dual Band Router ... may have a varying signal quality, and may sometimes, be “HUNTING for the best Frequency Band in the middle of a session. So, the TV app quickly (and impatiently), sends out its own Session Disconnect,  when it first sees some momentary dropouts. A direct cable connection to both Scope and Client PC’s should disprove the “wobbly wireless LAN” possibility.
  3. Perhaps my ISP was overly busy, heavy cable traffic, Modem signal momentarily dropping out, before most of their customers logged out and went to bed. The PC’s win-10 never even flickered, so Windows may be more tolerant.
  4. WIN-10 doing too many “Self Diagnostics and System Clean-ups”. There was a flurry of disconnects last night, (as usual), just before midnight. TV would not accept a reconnect that lasted longer than just a few seconds at a time. After midnight, it seemed to last for over one hour. Unlike Win-7, these MICROSOFT diagnostics schedules, Defrag, Memory Test, File & Security, etc. and others  of various kinds are now encoded as  “CUSTOM” , and can’t be rescheduled by the user,  to more appropriate ...  Daytime hours.
  5. Differences in operating system activity – I can retest later,  using Win-7 on the same client PC.
    I have learned a lot about choosing and using a remote app, during these conversations.
Sorry if this thread has lasted longer than perhaps some expected. Thanks for your patience with this OT posting.
But, I feel the choice of an easy to use, common, reliable and inexpensive Remote session application program,  is important to operating our Astro-Physics mounts, safely.
 
My thanks to Joel, Mike, and Ray, for your added information and advice thus far.
Back to debugging.
Joe Z.
 


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out

Michael Buxton
 

I use TightVNC and it is free.  TV is my backup.  It is a good alternative and it does not timeout.  It requires some knowledge with port forwarding if you have a firewall though.

Mike


Sent from my Verizon Wireless 4G LTE smartphone


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Ray Gralak
 

Hi Joe,

To prove it does work, just this minute, I pulled the Modem’s power plug, so only
my (Linksys) router and my two PC’s on my local wireless LAN were
communicating through it. No ISP connection of any kind.
Ok, I believe you! :-) I think they might have added that capability in one of the versions since V8, for which I had purchased a Business license.

Can TeamViewer also take advantage of Intel AMT (boot PC if is off, remotely enter BIOS screen, etc.)?

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma


-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Saturday, April 30, 2016 4:29 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
Times out & Disconnects



Ray,

To prove it does work, just this minute, I pulled the Modem’s power plug, so only
my (Linksys) router and my two PC’s on my local wireless LAN were
communicating through it. No ISP connection of any kind.

I launched PemPro on the remote (in-house Host laptop, which would be the
scope computer for example) to prove it still works. Of course, if you have one of
those modems with a “built-in wireless router” – nowadays more common perhaps
– then doing that trick would lose the local wireless LAN link as well. I use a
separate Router, and I prefer it this way, for now. In any case, it is perhaps wiser –
for local scope use - to choose “Accept Exclusively”, so that the modem doesn’t
even try to leap out over the internet to the TV website server.

RAY - Please don’t tell TeamViewer – or they might change it to the way you
describe :-)

Of course, if the observatory is truly remote – off site – then there is no option
other than The TeamViewer server’s host site, or your own network server,
somewhere. Doing that, involves lags and possible other causes of session drop
outs, including weather, satellites, transmission lines, ISP quality, and traffic, etc.
etc. – no way around that.

The other nice thing is that by default, TeamViewer is set to start in background
on Windows boot. That can be changed. But, it also means that I don’t actually
have to have my scope PC logged in – TV (after using your TV password), can log
into the Win-10 “LOCK SCREEN” – if that is how the scope PC is currently sitting -
which you can then then choose to login to a specific Account via another
account Windows password. You can also Reboot the host, wait for it to complete,
and log back on. Very flexible.

For newbies to TeamViewer use, I should state that the random or expected 3
hour session log out ... changes nothing on the Host side. If the scope (host) PC
was in the middle of a GOTO or displaying images from a CCD, that PC continues
like nothing happened. It is the client that is very temporarily made blind. If you log
right back in to the scope (host) PC, the (client) session just resumes as if nothing
had changed in the link.

So, if you were going to pull an all night remote session, plus the added up front
time to set things up on the remote host PC, you will need to answer the Login
screen every 3 hours (free version only), or after loss of connection in between.
Once everything is going, and you normally use an “unattended observatory
control system” on the scope side, you can come back in the morning, and log
right back into the session again, to see the night’s results. The host PC continued
to operate on its own, whether your client side was active or not.

Joe

From: mailto:ap-gto@yahoogroups.com
Sent: Saturday, April 30, 2016 6:48 PM
To: ap-gto@yahoogroups.com
Subject: RE: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
Times out & Disconnects

Hi Joe,

Yes, that's true but I thought that was only to *use* local IP addresses as the
"connect to" address. I thought that the free version of TV requires an internet
connection because it passes the connection through one of TV's servers. I
thought only the full version allowed direct connects without internet.

That would be nice if the free version of TV does not require an internet
connection because that's the way I was told that it worked.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-
physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma


-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Saturday, April 30, 2016 3:37 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
Times out & Disconnects


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Ray Gralak
 

Hi Joel,

OK, that's good to know. Thanks for confirming no internet is required!

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Saturday, April 30, 2016 4:01 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
Times out & Disconnects



Free Teamviewer does not require an internet connection. I use this all the time
out in the field with a headless miniPC at the mount controlled by my tablet or
laptop via TV. I create an adhoc wifi network on the miniPC and connect to it with
the tablet. Then enter the miniPC IP address in TV and it connects. The only
catch of course is that I need to know the IP address of the miniPC, which does
not have a screen.

joel

On Sat, Apr 30, 2016 at 5:48 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-
gto] <ap-gto@yahoogroups.com> wrote:





Hi Joe,

Yes, that's true but I thought that was only to *use* local IP addresses as the
"connect to" address. I thought that the free version of TV requires an internet
connection because it passes the connection through one of TV's servers. I
thought only the full version allowed direct connects without internet.

That would be nice if the free version of TV does not require an internet
connection because that's the way I was told that it worked.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-
physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma



> -----Original Message-----
> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
> Sent: Saturday, April 30, 2016 3:37 PM
> To: ap-gto@yahoogroups.com
> Subject: Re: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use
version -
> Times out & Disconnects
>
>
>
> Ray,
>
> That is true only if you select the TeamViewer EXTRAS –>GENERAL
option ...
> to ACCEPT (incoming LAN connections), rather than “ACCEPT
EXCLUSIVELY” (
> which limits connection to the house LAN acting as the server). The
former
> decides whether it will be the TV ISP server (possibly, stronger outdoor
signal), or
> limit itself to the house LAN signal.
>
> Joe
>
> From: mailto:ap-gto@yahoogroups.com
> Sent: Saturday, April 30, 2016 5:43 PM
> To: ap-gto@yahoogroups.com
> Subject: RE: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use
version -
> Times out & Disconnects
>
> Hi Mark,
>
> I think it makes connections through a remote server controlled by
TeamViewer.
>
> IMO, a good alternative, though not free, is Radmin ($49 license for each
server,
> clients are free). It is lightweight and high performance, and has most of
the same
> features as TV (except no automatic disconnect!!!). I've used this for over
10 years
> for connections to New Mexico Skies.
>
> https://www.radmin.com/radmin/features.php
>
> -Ray Gralak
> Author of APCC (Astro-Physics Command Center): http://www.astro-
> physics.com/index.htm?products/accessories/software/apcc/apcc
> Author of PEMPro: http://www.ccdware.com
> Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
> Author of PulseGuide: http://www.pulseguide.com
> Author of Sigma: http://www.gralak.com/sigma
>
>
>
>







Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Mark Striebeck
 

Ha! If course, sorry Joe!!!

On Apr 30, 2016 5:40 PM, "Joel Short buckeyestargazer@... [ap-gto]" <ap-gto@...> wrote:
 

I'm glad to help Mark, but "Joe" is the one who provided most of the good info in this thread.
joel

On Sat, Apr 30, 2016 at 7:36 PM, Mark Striebeck mark.striebeck@... [ap-gto] <ap-gto@...> wrote:
 

Thanks for all the info Joel. That's pretty much exactly the setup that I am looking for.

      Mark

On Apr 30, 2016 5:11 PM, "Joel Short buckeyestargazer@... [ap-gto]" <ap-gto@...> wrote:
 

Yeah Joe, that's essentially what I did and I know the miniPC IP address when not connected to the home network and the miniPC is just broadcasting an ad hoc wifi network.  This IP address does not change so I know that I can log in to it even when it is not connected to the home wifi network.  I hope that all made sense.
Teamviewer I think really is about the best free solution out there.  
joel

On Sat, Apr 30, 2016 at 6:54 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
 

Joel,
 
    You should be able to find its IP from the router, or on Windows “Network Settings.
Otherwise, if you can log into your “MiniPC” Windows during its setup (with keyboard and screen), click on TeamViewer as if logging in, and go into EXTRAS Options General tab – and switch the “ Incoming LAN connection to ... Accept Exclusively”. The  TV login screen screen will switch from displaying your remote host machine’s ID to your machine’s actual IP address (plus randomized  password) every time. Once you see this IP and record it, you can switch back to just “Accept” for both local and internet connection, if you like, and log in.
 
Joe




Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joel Short
 

I'm glad to help Mark, but "Joe" is the one who provided most of the good info in this thread.
joel

On Sat, Apr 30, 2016 at 7:36 PM, Mark Striebeck mark.striebeck@... [ap-gto] <ap-gto@...> wrote:
 

Thanks for all the info Joel. That's pretty much exactly the setup that I am looking for.

      Mark

On Apr 30, 2016 5:11 PM, "Joel Short buckeyestargazer@... [ap-gto]" <ap-gto@...> wrote:
 

Yeah Joe, that's essentially what I did and I know the miniPC IP address when not connected to the home network and the miniPC is just broadcasting an ad hoc wifi network.  This IP address does not change so I know that I can log in to it even when it is not connected to the home wifi network.  I hope that all made sense.
Teamviewer I think really is about the best free solution out there.  
joel

On Sat, Apr 30, 2016 at 6:54 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
 

Joel,
 
    You should be able to find its IP from the router, or on Windows “Network Settings.
Otherwise, if you can log into your “MiniPC” Windows during its setup (with keyboard and screen), click on TeamViewer as if logging in, and go into EXTRAS Options General tab – and switch the “ Incoming LAN connection to ... Accept Exclusively”. The  TV login screen screen will switch from displaying your remote host machine’s ID to your machine’s actual IP address (plus randomized  password) every time. Once you see this IP and record it, you can switch back to just “Accept” for both local and internet connection, if you like, and log in.
 
Joe




Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Mark Striebeck
 

Thanks for all the info Joel. That's pretty much exactly the setup that I am looking for.

      Mark

On Apr 30, 2016 5:11 PM, "Joel Short buckeyestargazer@... [ap-gto]" <ap-gto@...> wrote:
 

Yeah Joe, that's essentially what I did and I know the miniPC IP address when not connected to the home network and the miniPC is just broadcasting an ad hoc wifi network.  This IP address does not change so I know that I can log in to it even when it is not connected to the home wifi network.  I hope that all made sense.
Teamviewer I think really is about the best free solution out there.  
joel

On Sat, Apr 30, 2016 at 6:54 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
 

Joel,
 
    You should be able to find its IP from the router, or on Windows “Network Settings.
Otherwise, if you can log into your “MiniPC” Windows during its setup (with keyboard and screen), click on TeamViewer as if logging in, and go into EXTRAS Options General tab – and switch the “ Incoming LAN connection to ... Accept Exclusively”. The  TV login screen screen will switch from displaying your remote host machine’s ID to your machine’s actual IP address (plus randomized  password) every time. Once you see this IP and record it, you can switch back to just “Accept” for both local and internet connection, if you like, and log in.
 
Joe



Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joel Short
 

Yeah Joe, that's essentially what I did and I know the miniPC IP address when not connected to the home network and the miniPC is just broadcasting an ad hoc wifi network.  This IP address does not change so I know that I can log in to it even when it is not connected to the home wifi network.  I hope that all made sense.
Teamviewer I think really is about the best free solution out there.  
joel

On Sat, Apr 30, 2016 at 6:54 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
 

Joel,
 
    You should be able to find its IP from the router, or on Windows “Network Settings.
Otherwise, if you can log into your “MiniPC” Windows during its setup (with keyboard and screen), click on TeamViewer as if logging in, and go into EXTRAS Options General tab – and switch the “ Incoming LAN connection to ... Accept Exclusively”. The  TV login screen screen will switch from displaying your remote host machine’s ID to your machine’s actual IP address (plus randomized  password) every time. Once you see this IP and record it, you can switch back to just “Accept” for both local and internet connection, if you like, and log in.
 
Joe



Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joe Zeglinski
 

Joel,
 
    You should be able to find its IP from the router, or on Windows “Network Settings.
Otherwise, if you can log into your “MiniPC” Windows during its setup (with keyboard and screen), click on TeamViewer as if logging in, and go into EXTRAS Options General tab – and switch the “ Incoming LAN connection to ... Accept Exclusively”. The  TV login screen screen will switch from displaying your remote host machine’s ID to your machine’s actual IP address (plus randomized  password) every time. Once you see this IP and record it, you can switch back to just “Accept” for both local and internet connection, if you like, and log in.
 
Joe


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joe Zeglinski
 

Ray,
 
    To prove it does work, just this minute, I  pulled the Modem’s power plug, so only my (Linksys) router and my two  PC’s on my local wireless LAN were communicating through it. No ISP connection of any kind.
   
    I launched PemPro on the remote (in-house Host laptop, which would be the scope computer for example) to prove it still works. Of course, if you have one of those modems with a “built-in wireless router” – nowadays more common perhaps – then doing that trick would lose the local wireless LAN link as well. I use a separate Router, and I prefer it this way, for now. In any case, it is perhaps wiser – for local scope use -  to choose “Accept Exclusively”, so that the modem doesn’t even try to leap out over the internet to the TV website server.
 
    RAY -   Please don’t tell TeamViewer – or they might change it to the way you describe :-)
 
     Of course, if the observatory is truly remote – off site – then there is no option other than The TeamViewer server’s host site, or your own network server, somewhere. Doing that, involves lags and possible other causes of session drop outs, including weather, satellites, transmission lines, ISP quality, and traffic, etc. etc. – no way around that.
 
    The other nice thing is that by default, TeamViewer is set to start in background on Windows boot. That can be changed. But, it also means that I don’t actually have to have my scope PC logged in – TV (after using your TV password), can  log into the Win-10 “LOCK SCREEN” – if that is how the scope PC is currently sitting - which you can then then choose to  login to a specific Account  via another account Windows password. You can also Reboot the host, wait for it to complete, and log back on. Very flexible.
 
    For newbies to TeamViewer use, I should state that the random or expected 3 hour session log out ... changes nothing on the Host side. If the scope (host) PC was in the middle of a GOTO or displaying images from a CCD, that PC continues like nothing happened. It is the client that is very temporarily made blind. If you log right back in to the scope (host) PC, the (client) session just resumes as if nothing had changed in the link.
 
    So, if you were going to pull an all night remote session, plus the added up front time to set things up on the remote host PC, you will need to answer the Login screen every 3 hours (free version only), or after loss of connection in between. Once everything is going, and you normally use an “unattended observatory control system” on the scope side, you can come back in the morning, and log right back into the session again, to see the night’s results. The host PC continued to operate on its own, whether your client side was active or not.
 
Joe
 

Sent: Saturday, April 30, 2016 6:48 PM
Subject: RE: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
 
Hi Joe,

Yes, that's true but I thought that was only to *use* local IP addresses as the "connect to" address. I thought that the free version of TV requires an internet connection because it passes the connection through one of TV's servers. I thought only the full version allowed direct connects without internet.

That would be nice if the free version of TV does not require an internet connection because that's the way I was told that it worked.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro:  http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma


> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Saturday, April 30, 2016 3:37 PM
> To: ap-gto@...
> Subject: Re: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
> Times out & Disconnects


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joel Short
 

Free Teamviewer does not require an internet connection.  I use this all the time out in the field with a headless miniPC at the mount controlled by my tablet or laptop via TV.  I create an adhoc wifi network on the miniPC and connect to it with the tablet.  Then enter the miniPC IP address in TV and it connects.  The only catch of course is that I need to know the IP address of the miniPC, which does not have a screen.

joel

On Sat, Apr 30, 2016 at 5:48 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...> wrote:
 

Hi Joe,

Yes, that's true but I thought that was only to *use* local IP addresses as the "connect to" address. I thought that the free version of TV requires an internet connection because it passes the connection through one of TV's servers. I thought only the full version allowed direct connects without internet.

That would be nice if the free version of TV does not require an internet connection because that's the way I was told that it worked.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma

> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Saturday, April 30, 2016 3:37 PM
> To: ap-gto@...
> Subject: Re: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
> Times out & Disconnects
>
>
>
> Ray,
>
> That is true only if you select the TeamViewer EXTRAS –>GENERAL option ...
> to ACCEPT (incoming LAN connections), rather than “ACCEPT EXCLUSIVELY” (
> which limits connection to the house LAN acting as the server). The former
> decides whether it will be the TV ISP server (possibly, stronger outdoor signal), or
> limit itself to the house LAN signal.
>
> Joe
>
> From: mailto:ap-gto@...
> Sent: Saturday, April 30, 2016 5:43 PM
> To: ap-gto@...
> Subject: RE: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
> Times out & Disconnects
>
> Hi Mark,
>
> I think it makes connections through a remote server controlled by TeamViewer.
>
> IMO, a good alternative, though not free, is Radmin ($49 license for each server,
> clients are free). It is lightweight and high performance, and has most of the same
> features as TV (except no automatic disconnect!!!). I've used this for over 10 years
> for connections to New Mexico Skies.
>
> https://www.radmin.com/radmin/features.php
>
> -Ray Gralak
> Author of APCC (Astro-Physics Command Center): http://www.astro-
> physics.com/index.htm?products/accessories/software/apcc/apcc
> Author of PEMPro: http://www.ccdware.com
> Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
> Author of PulseGuide: http://www.pulseguide.com
> Author of Sigma: http://www.gralak.com/sigma
>
>
>
>



Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Ray Gralak
 

Hi Joe,

Yes, that's true but I thought that was only to *use* local IP addresses as the "connect to" address. I thought that the free version of TV requires an internet connection because it passes the connection through one of TV's servers. I thought only the full version allowed direct connects without internet.

That would be nice if the free version of TV does not require an internet connection because that's the way I was told that it worked.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Saturday, April 30, 2016 3:37 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
Times out & Disconnects



Ray,

That is true only if you select the TeamViewer EXTRAS –>GENERAL option ...
to ACCEPT (incoming LAN connections), rather than “ACCEPT EXCLUSIVELY” (
which limits connection to the house LAN acting as the server). The former
decides whether it will be the TV ISP server (possibly, stronger outdoor signal), or
limit itself to the house LAN signal.

Joe

From: mailto:ap-gto@yahoogroups.com
Sent: Saturday, April 30, 2016 5:43 PM
To: ap-gto@yahoogroups.com
Subject: RE: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
Times out & Disconnects

Hi Mark,

I think it makes connections through a remote server controlled by TeamViewer.

IMO, a good alternative, though not free, is Radmin ($49 license for each server,
clients are free). It is lightweight and high performance, and has most of the same
features as TV (except no automatic disconnect!!!). I've used this for over 10 years
for connections to New Mexico Skies.

https://www.radmin.com/radmin/features.php

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-
physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma




Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joe Zeglinski
 

Ray,
 
    That is true only if you select the TeamViewer EXTRAS –>GENERAL option ... to ACCEPT (incoming LAN connections), rather than “ACCEPT EXCLUSIVELY” ( which limits connection to the house LAN acting as the server). The former decides whether it will be the TV ISP server (possibly, stronger outdoor signal), or limit itself to the house LAN signal.
 
Joe
 

Sent: Saturday, April 30, 2016 5:43 PM
Subject: RE: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
 
Hi Mark,

I think it makes connections through a remote server controlled by TeamViewer.

IMO, a good alternative, though not free, is Radmin ($49 license for each server, clients are free). It is lightweight and high performance, and has most of the same features as TV (except no automatic disconnect!!!). I've used this for over 10 years for connections to New Mexico Skies.

https://www.radmin.com/radmin/features.php

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro:  http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joe Zeglinski
 

Mark,
 
    Open TV, click on “EXTRAS” then “ADVANCED” option. There is a box to click OFF labeled ... “ Start Remote Control automatically when connected to a MOBILE device”.  This is ON by default.
Unless of course, you really want to control a session while at an internet cafe, just to show off to friends.
 
    You may also prefer to limit telescope connection just to your in-house LAN.
The default under the “GENERAL” tab in Extras, is (for your Host side PC ...  INCOMING LAN CONNECTION) to  “Accept” – which includes connections  from both your local LAN as well as from your ISP via TeamView head office and back home.
    When I first started using TV, I found that TV would sometimes find a stronger signal in the backyard, and connected to the house via the internet –  the ISP connection was intermittent, so that is another reason it might have been disconnecting, besides the random or 3-hour timeouts.
 
    Unless the remote PC and telescope were “miles” away, I prefer to change the TV  option to “Accept Exclusively” for backyard use. This way TeamViewer only connects to my own wireless LAN (or perhaps also a neighbours – don’t know). I presume there is less chance of flakey wireless or internet connection during a session. I originally blamed the Accept default for the lost connections, before I found out the latest news about the 3 hour timeout.
    Maybe it was communicating with my backyard host scope PC via the TeamViewer website, somewhere, and it was busy with blogs and other customer activity, besides my accidental worldwide jump through that site. Just another possible cause.
 
    However, with the ACCEPT EXCLUSIVELY option, you CANNOT log in via the internet, and the TeamViewer website (somewhere on the planet) acting as an ISP pass through.
 
    You can also use ACCEPT, and then specify the IP address of your host (telescope) PC, rather than its (default) Partner ID as provided by TV and  displayed on its login screen. That is my preferred local session use.
    You might also use the option to define a “permanent Personal Login Password” (under the Security tab), rather than the hassle of the generated one, which changes on every session.
 
    TeamViewer is a very powerful app. When I was testing its “multi-session” capability, I even connected to another PC from the Login icon on the Host PC – sort of a cascaded session, just to see if it would break.
 
Enjoy it,
Joe


Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Ray Gralak
 

Hi Mark,

I think it makes connections through a remote server controlled by TeamViewer.

IMO, a good alternative, though not free, is Radmin ($49 license for each server, clients are free). It is lightweight and high performance, and has most of the same features as TV (except no automatic disconnect!!!). I've used this for over 10 years for connections to New Mexico Skies.

https://www.radmin.com/radmin/features.php

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Saturday, April 30, 2016 2:25 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] OFF TOPIC - remote PC & TeamViewer Home Use version -
Times out & Disconnects



OK, sorry for not hijacking this thread further to ask about TeamViewer:

I installed it (telescope computer, laptop, Android tablet) - works really well. Great!!!

But now, I'm sitting at Starbucks and my tablet just reconnected to the telescope
computer! And I know that I didn't make any changes to our firewall. How is it
doing that? Or better: how can I turn that off (I don't want any incoming
connections to our network)?

Mark

On Sat, Apr 30, 2016 at 2:16 PM, 'Joseph Zeglinski' J.Zeglinski@rogers.com [ap-
gto] <ap-gto@yahoogroups.com> wrote:







Hi,

I used Win RD years ago, with XP, and had to be the PRO version for all
my PC’s for that reason alone. However, unlike TeamViewer, RD logs you out at
one end of the link or the other.

I too use TV to control my backyard scope – I carry a laptop out to it on a
drinks table – quick and easy one cable plug in . The nice thing is that once the
indoor and outdoor PC’s are connected by wireless, you can control the telescope
at either end, and you don’t get logged out, as RD does (or did). That is important
if you happen to run into a “situation” while you are currently outdoors. You might
have started a slow GOTO from indoors, walked to the scope and came across an
“ahhhh-Sh*t situation, as the scope heads for the pier. With RD you have to log
back in at the remote in a panic, making sure your fingers do things right. But, with
TeamViewer, the remote screen, keyboard and mouse, is always active.

TeamViewer in my opinion is the best remote control software there is,
even with its connection drop outs. It even allows you to start and join “multiple
sessions” to the same remote session, so you can control the scope from more
than one PC, even share it with a remote friend, or run multiple scopes from the
same client screen on different sessions – no limit to how many. Likewise, when I
have a PC problem, I give the techie the current TeamViewer session password,
and we can do the debug together. For long distance help, I usually open a
WORDPAD document screen into which we type back and forth. This is much
easier than the annoying sound and time lag on the IP Phone call link
conversations through TV.

The other thing I did, back in Win-8 days, was to search through the
Schedule Task list in Windows, MICROSOFT folder, and vet every single one, to
change its run run from evening hours or early morning, to mid day. You would be
amazed how much Microsoft does for us after regular hours. That way, Win
Updates, Diagnostics, Performance Report generation and uploads, or virus
scans, etc. etc. ..... don’t needlessly slow down the PC in the middle of astronomy
sessions.
Microsoft assumes everybody has left the office and gone to bed, so it uses
the night shift to clean things up.
Astronomers ... work nights :-)

Joe






Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Mark Striebeck
 

OK, sorry for not hijacking this thread further to ask about TeamViewer:

I installed it (telescope computer, laptop, Android tablet) - works really well. Great!!!

But now, I'm sitting at Starbucks and my tablet just reconnected to the telescope computer! And I know that I didn't make any changes to our firewall. How is it doing that? Or better: how can I turn that off (I don't want any incoming connections to our network)?

    Mark

On Sat, Apr 30, 2016 at 2:16 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
 

Hi,
 
    I used Win RD years ago, with XP, and had to be the PRO version for all my PC’s for that reason alone. However, unlike TeamViewer, RD logs you out at one end of the link or the other.
 
    I too use TV to control my backyard scope – I carry a laptop out to it on a drinks table – quick and easy one cable plug in . The nice thing is that once the indoor and outdoor PC’s are connected by wireless, you can control the telescope at either end, and you don’t get logged out, as RD does (or did).  That is important if you happen to run into a “situation” while you are currently outdoors. You might have started a slow GOTO from indoors, walked to the scope and came across an “ahhhh-Sh*t situation, as the scope heads for the pier. With RD you have to log back in at the remote in a panic, making sure your fingers do things right. But, with TeamViewer, the remote screen, keyboard and mouse,  is always active.
 
    TeamViewer in my opinion is the best remote control software there is, even with its connection drop outs. It even allows you to start and join “multiple sessions” to the same remote session, so you can control the scope from more than one PC, even share it with a remote friend, or run multiple scopes from the same client screen on different sessions – no limit to how many. Likewise, when I have a PC problem, I give the techie the current TeamViewer session password, and we can do the debug together. For long distance help, I usually open a WORDPAD document screen into which we type back and forth. This is much easier than the annoying sound and time lag on the IP Phone call link conversations through TV.
 
    The other thing I did, back in Win-8 days, was to search through the Schedule Task list in Windows, MICROSOFT folder, and vet every single one, to change its run run from evening hours or early morning, to mid day. You would be amazed how much Microsoft does for us after regular hours. That way, Win Updates, Diagnostics, Performance Report generation and uploads, or virus scans, etc. etc. .....  don’t needlessly slow down the PC in the middle of astronomy sessions.
Microsoft assumes everybody has left the office and gone to bed, so it uses the night shift to clean things up.
Astronomers ... work nights :-)
 
Joe



Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects

Joe Zeglinski
 

Hi,
 
    I used Win RD years ago, with XP, and had to be the PRO version for all my PC’s for that reason alone. However, unlike TeamViewer, RD logs you out at one end of the link or the other.
 
    I too use TV to control my backyard scope – I carry a laptop out to it on a drinks table – quick and easy one cable plug in . The nice thing is that once the indoor and outdoor PC’s are connected by wireless, you can control the telescope at either end, and you don’t get logged out, as RD does (or did).  That is important if you happen to run into a “situation” while you are currently outdoors. You might have started a slow GOTO from indoors, walked to the scope and came across an “ahhhh-Sh*t situation, as the scope heads for the pier. With RD you have to log back in at the remote in a panic, making sure your fingers do things right. But, with TeamViewer, the remote screen, keyboard and mouse,  is always active.
 
    TeamViewer in my opinion is the best remote control software there is, even with its connection drop outs. It even allows you to start and join “multiple sessions” to the same remote session, so you can control the scope from more than one PC, even share it with a remote friend, or run multiple scopes from the same client screen on different sessions – no limit to how many. Likewise, when I have a PC problem, I give the techie the current TeamViewer session password, and we can do the debug together. For long distance help, I usually open a WORDPAD document screen into which we type back and forth. This is much easier than the annoying sound and time lag on the IP Phone call link conversations through TV.
 
    The other thing I did, back in Win-8 days, was to search through the Schedule Task list in Windows, MICROSOFT folder, and vet every single one, to change its run run from evening hours or early morning, to mid day. You would be amazed how much Microsoft does for us after regular hours. That way, Win Updates, Diagnostics, Performance Report generation and uploads, or virus scans, etc. etc. .....  don’t needlessly slow down the PC in the middle of astronomy sessions.
Microsoft assumes everybody has left the office and gone to bed, so it uses the night shift to clean things up.
Astronomers ... work nights :-)
 
Joe