|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
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:
|
|
|
|
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
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
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:
|
|
|
|
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
From: mailto:ap-gto@...
Sent: Saturday, April 30, 2016 6:48 PM
To: ap-gto@...
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
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:
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
Hi Joe,
toggle quoted messageShow quoted text
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-----
|
|
|
|
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
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
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
Hi Mark,
toggle quoted messageShow quoted text
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-----
|
|
|
|
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:
|
|
|
|
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
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
Mark Striebeck
Thanks guys, I'll try TeamViewer - let's see if that works better. For file transfer, I started to use Google Drive a year ago. All files are automatically uploaded to Drive and then my "local" machine gets them from there. But best is that they are backed up almost immediately in the cloud. Mark
On Sat, Apr 30, 2016 at 1:29 PM, Jim Jones albiero@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
Jim Jones
I run my observatory which is about 100 feet from the house with metal shop building in the wifi path with Team Viewer. It does a very good job for me with very few instances of slow response. I connect in evening and stay connected until the connection times out (several hours). The newer versions of Team Viewer time out and disconnect with no way that I have found to over ride the time out. I wish they hadn't done that.
toggle quoted messageShow quoted text
I have experienced the VNC behavior you describe and have never had that happen with TV. I depend on Tv file transfer capability to transfer my files in the morning and have never had it fail. I have used VNC and Windows Remote Desktop and find TV much more capable. I've been using it for several years now. It is easy to find out for yourself. Just download (free) it and try it out. Hope this helps. Jim Jones
On 4/30/2016 11:18 AM, Mark Striebeck mark.striebeck@... [ap-gto] wrote:
Funny, I am just trying to debug issues with my remote software (VNC or
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
BigE Astro
It is available with different limitations with the different packages. I always purchase professional or the package that has the full versions of Windows with two way RD provided. It does depend on which version of windows you use. You are correct that the basic versions don't provide it or at least the same functionality. The cost to upgrade to the pro is very small and I think Win 10 only comes with it offered with full functionality. Not sure. Anyways, I think it is a good idea to not include separate packages for RD because it is just another vender and supporting other software.
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
Correct me if I'm wrong, but I thought that Windows Remote Desktop was not available to "home" users, just "professional" or "ultimate"? That's the reason I never pursued it when on Windows 7. I don't know about Win10 though. joel
On Sat, Apr 30, 2016 at 2:35 PM, bigeastro@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
BigE Astro
Why not just use Window's remote desktop? What do other software packages offer that Windows remote desktop does not? I use remote desktop to access all of my computers and servers at four different locations, office, homes, observatory. The machines are set up to shut down and turn on automatically at prescribed times. Routers have wake on LAN functionality so I can pretty much turn on any machine that is not already awake. Power failure fault tolerance is met with batteries and graceful shutdowns and then the system powers on when it detects power again. Displays are spanned if I need multiple display outputs. This seems to work well whether you have static IP or are using dydns. Why would you go outside of what is already offered in windows? This would add an extra level of complexity? Just curious.
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
It's probably been at least 4 years since I looked into remote software. At that time I tried VNC and much preferred Teamviewer, but I would guess it's a lot better now. I never tried WRD, but dealing with Windows is not my idea of a good time. joel
On Sat, Apr 30, 2016 at 1:18 PM, Mark Striebeck mark.striebeck@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
Mark Striebeck
Funny, I am just trying to debug issues with my remote software (VNC or Windows Remote desktop). Every now and then the remote control SLOWS down like crazy (takes up to several minutes to just refresh the screen...) How does TeamViewer compare in general to VNC or Windows Remote Desktop? Mark
On Sat, Apr 30, 2016 at 11:12 AM, Joel Short buckeyestargazer@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: OFF TOPIC - remote PC & TeamViewer Home Use version - Times out & Disconnects
Joe, I forgot to say thanks for the information. I didn't know that was a "bug" or limitation in the free license, so it does explain some thing to me. joel
On Sat, Apr 30, 2016 at 1:11 PM, Joel Short <buckeyestargazer@...> wrote:
|
|
|