|
Re: Remote Desktop PC access on Ad Hoc Network
Joe Zeglinski
Hi Greg,
Just the simple decimal separated number.
e.g. ... 192.168.1.xxx ... as any of your
printers or devices are shown on your router wireless table list. No spaces,
just decimals and digits.
Joe
From: Astronutcase astronutcase@... [ap-gto]
Sent: Saturday, March 17, 2018 9:47 PM
To: ap-gto@...
Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc
Network What is the IP form of address? Just the IP value or does it need some
keyword or special format? I normally use Radmin when the TV site is down or I
need bandwidth but if this avoids that access then I’ll use it.
Greg
On Mar 17, 2018, at 9:33 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Micah Smith <micahlsmith@...>
This is what I'm working on
On Sat, Mar 17, 2018, 5:19 PM Wayne Hixson wayneh9026@yahoo.com [ap-gto] < ap-gto@yahoogroups.com> wrote:
[Non-text portions of this message have been removed]
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
What is the IP form of address? Just the IP value or does it need some keyword or special format? I normally use Radmin when the TV site is down or I need bandwidth but if this avoids that access then I’ll use it. Greg
On Mar 17, 2018, at 9:33 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Joe Zeglinski
Glad you found the problem, and are back on TV.
BTW:
if you are logging into a “nearby” Remote like the
backyard scope – definitely do NOT use the 9-digit ID for login.
Use the target PC “IP address” form of login, instead.
Otherwise, your connection to the backyard, goes out on the internet via
New York continental head office , or to the main Germany host computer,
becomes MUCH slower than the direct internal wireless link, and liable to
random disconnect with ISP blips, fades, or frequency hopping trying to find a
“better user ISP connection”, etc.
Only use the 9-digit ID address if trying to reach a
remote PC which is way beyond house wireless LAN range.
Might also want to disable the option in EXTRAS->Advanced-> section
Advanced setting for connections to other computers:
“Start remote control automatically when connected to a MOBILE
device”.
... so someone with a Smartphone doesn’t hack in – Unless you are using
something like SkiSafari as your local mount control pad, at the same time
I suppose.
Joe
From: 'Greg Salyer' astronutcase@... [ap-gto]
Sent: Saturday, March 17, 2018 9:04 PM
To: ap-gto@...
Subject: RE: [ap-gto] Re: Remote Desktop PC access on Ad Hoc
Network Ok, problem solved. After deleted my copy of TeamViewer I download a version labeled "TeamViewer 13 Spring Release". I did a basic installation specifing personal/non-commercial. The screen I get before making the remote connection is now quite different than I was getting with my old version 13. No problem - just different. Now when I make the remote connection I get what looks like the same as version 12 with all the functions that were missing. Happy days are here again! Thanks everyone. I wouldn't have known I had a broken version 13 without your help.
Greg
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Joe Zeglinski
Hi Stuart,
What I meant by “target names”, is not the PC name AFTER
reaching the remote destination, but rather the pop down list of 9-digit ID’s
(down-arrow), as you launch TV to select a formerly used login ID. I have
to keep a desktop file handy, with a list of ID’s and PC or people names.
Otherwise, how would you distinguish one ID from another in order to try a login
number? Guessing a formerly used PC ID would be embarrassing, or scare the other
person, that someone is attacking their PC – when it was just an error.
I think TV offers the user the option to REGISTER your
(perhaps customer) target machines, with an further identification ... at their
company website in GmBH ???
First, I don’t like such ID info on some other PC or Cloud, somewhere else
in the world. Second, I mostly use TV on my house LAN to connect to the
telescope or other internal laptop, so I don’t want to access the internet just
to double check an ID versus person name or other identifier. Besides, some
people don’t change their PC Name from the MS default of “MY PC” –
most of my relatives or non computer savvy friends.
Tonight I tried “fooling TV” by giving it
the “correct 9-digit ID”, but tacked on a space and some extra defining
alpha letters, hoping that TV would simply accept the first 9 characters as the
ID, and then also record the remaining identifying characters into its
“previously-logged-into” list of ID’s – expecting it would otherwise ignore
anything after my leading 9 digits.
That would be a nice way of maintaining this list. Unfortunately, its
numeric entry is very format specific – No foolin’ it. In fact, it doesn’t even
permit a space separating a group of 3 digits, for clarity.
But, all that is trivial – great product anyway.
Joe
From: Stuart Heggie stuart.j.heggie@...
[ap-gto]
Sent: Saturday, March 17, 2018 8:36 PM
To: ap-gto@...
Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc
Network Joe, not to take away from this being Greg's thread but why aren't
all your computers showing up by their names? I name all mine. Easy to tell
which is which in TV.
Stuart
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Ok, problem solved. After deleted my copy of TeamViewer I download a version labeled "TeamViewer 13 Spring Release". I did a basic installation specifing personal/non-commercial. The screen I get before making the remote connection is now quite different than I was getting with my old version 13. No problem - just different. Now when I make the remote connection I get what looks like the same as version 12 with all the functions that were missing. Happy days are here again! Thanks everyone. I wouldn't have known I had a broken version 13 without your help.
Greg
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, March 17, 2018 8:36 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Greg,
EXACTLY, the same “menu/function bar” as in all previous versions. Checked its function bar contents & options, a few minutes ago, and there are no differences.
By any chance did you click the “Up-Arrow” at the top of the logged in (host PC, telescope) screen button, on it to “HIDE, roll up, the function bar” ? If so, click it again.
Joe
From: 'Greg Salyer' astronutcase@... [ap-gto] Sent: Saturday, March 17, 2018 8:29 PM To: ap-gto@... Subject: RE: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Ok, I've now got version 13 on both ends, however, I still don't get the "missing" functions. Are you getting the same screen as version 12 when you connect? I get a brand new line at top with almost no function.
Greg
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Joe Zeglinski
Greg,
I can’t quite remember, but I think the TWO kinds of
install, it asks you for, after download, during install, is whether you want
“UNATTENDED ACCESS” type of use.
My present setup, like previous versions, was OF COURSE, I want that
one. Perhaps the alternative one, you may have accidentally selected, was one
for visitors to your remote, who were NOT given any of the extra “Privileges”,
such as we discussed here.
BTW: Fun Thing to see:
Once you get it all checked out, a weird and fun way of
using TeamViewer is to use “your own” client TV ID number as the remote target
address. TV tries to login sequentially, in quick succession. producing a new
screen “within” every new login screen. Nice art, but be ready to find the red
x-button to close the first opened session window – or power off. This
produces “Fine Art” – a mirror image in a succession of rapid fire mirrors.
Effectively, a circus ... House Of Mirrors !
Probably a bug they should fix, but you can open a
remote PC, and use THAT ... PC’s TeamViewer to login to a deeper,
other remote (from the first remote), ad infinitum. It is only interesting to
show how flexible and darned powerful TeamViewer is.
Seems to have been harmless for years.
Joe
From: 'Greg Salyer' astronutcase@... [ap-gto]
Sent: Saturday, March 17, 2018 8:38 PM
To: ap-gto@...
Subject: RE: [ap-gto] Re: Remote Desktop PC access on Ad Hoc
Network I didn't know there were two kinds of install. I did a fresh install. I was installing on a brand new computer. Looks like I've got some experiments to try. I'll totally remove the program then either install 12 followed by an upgrade to 13 or a fresh 13 this time looking for that two kinds of install option. Thanks for info. I'll give it a try tomorrow and tell you guys what happened.
Greg
From:
ap-gto@... [mailto:ap-gto@...]
Greg,
Perhaps you answered the INSTALLER with some non-control option – or what ever the alternate was. I forget what it was, but there were TWO kinds of user install.
Yes – I did a File Transfer, the same old way I have for years, this afternoon – and I double checked – I am now running version 13.1.1548 build Mar 9, 2018.
The File Transfer, and all the other command menu bar options are EXACTLY the same as they always were, including File Transfer and Remote Print – and I assume Clipboard still works as it used to do. I too was surprised by the “slightly new” GUI screen – I didn’t use their new fangled advanced one, offered as a beta test option back in version 12. I like this simpler, old one.
Only one thing would improve it – a NAME tag beside its remembered list connect ID numbers. Hard to distinguish between helped family and friends’ 9-digit numbers.
So, there is something different in your own install of version 13. Mind you, I didn’t install version 13 ... all over again. It updated itself at some point, when I wasn’t looking. So, my old install is NOT a “fresh” install. Maybe that is where they changed things.
Greg - Did you perhaps install version 13 from scratch, that got you in the current mess ? Maybe download and re-install, or install version 12 and click the CHECK for new Version button in HELP, rather than a fresh download/install. That’s in case there is a inconsistency between Installer, and Updater. It really is worthwhile pursuing.
Good luck Greg. Just curious – hope your situation isn’t something new at TV. Joe Z.
From: 'Greg Salyer' astronutcase@... [ap-gto] Sent: Saturday, March 17, 2018 7:48 PM To: ap-gto@... Subject: RE: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
No, as far as I know disconnect is not one of the problems with version 13. Of course as soon as I found fie transfers weren't supported yet I dropped it and went back to version 12 so I don't have a lot of experience with it. I then went on the web and found a lot of people went back to 12 because of missing functions such as file transfer, remote print and clipboard transfer. If your using such functions then I can't understand what's going on. The look and feel is totally different than version 12. The basic stuff seemed to work just fine but if the missing functions are hidden somewhere I didn't see where. Are you sure your on version 13?
Greg
From: ap-gto@...
[mailto:ap-gto@...]
Hi Wayne,
Is this disconnect something new in version 13?
Like you, I used TV for probably 10 years, hassle free. Used version 13 today, for most of the afternoon, never got disconnected, no warnings, just a “polite Thank You” for using TeamViewer .... AFTER I logged out.
It didn’t disconnect me in the 4 hours I was using it, so I don’t know why you are having a problem. That’s weird. Did you somehow download a trial “commercial user” version”. I think TV Corp is pretty wary and checks if you are suspected of using it for business. Don’t know what they may “snoop” for, in the transactions – if they actually do that. Perhaps there are “terms of service” that you acknowledge their right to do that – probably.
I have heard of cases where so-called “home users” got caught and cancelled.
Anyway, so far, the latest TV version is behaving no different from years of the older ones. I would curious what you or anyone else discovers about your TV situation. I don’t think TV changed the rules for eligibility.
Joe
From: Wayne wayneh9026@... [ap-gto] Sent: Saturday, March 17, 2018 5:44 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Waynr
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
I didn't know there were two kinds of install. I did a fresh install. I was installing on a brand new computer. Looks like I've got some experiments to try. I'll totally remove the program then either install 12 followed by an upgrade to 13 or a fresh 13 this time looking for that two kinds of install option. Thanks for info. I'll give it a try tomorrow and tell you guys what happened.
Greg
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, March 17, 2018 8:24 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Greg,
Perhaps you answered the INSTALLER with some non-control option – or what ever the alternate was. I forget what it was, but there were TWO kinds of user install.
Yes – I did a File Transfer, the same old way I have for years, this afternoon – and I double checked – I am now running version 13.1.1548 build Mar 9, 2018.
The File Transfer, and all the other command menu bar options are EXACTLY the same as they always were, including File Transfer and Remote Print – and I assume Clipboard still works as it used to do. I too was surprised by the “slightly new” GUI screen – I didn’t use their new fangled advanced one, offered as a beta test option back in version 12. I like this simpler, old one.
Only one thing would improve it – a NAME tag beside its remembered list connect ID numbers. Hard to distinguish between helped family and friends’ 9-digit numbers.
So, there is something different in your own install of version 13. Mind you, I didn’t install version 13 ... all over again. It updated itself at some point, when I wasn’t looking. So, my old install is NOT a “fresh” install. Maybe that is where they changed things.
Greg - Did you perhaps install version 13 from scratch, that got you in the current mess ? Maybe download and re-install, or install version 12 and click the CHECK for new Version button in HELP, rather than a fresh download/install. That’s in case there is a inconsistency between Installer, and Updater. It really is worthwhile pursuing.
Good luck Greg. Just curious – hope your situation isn’t something new at TV. Joe Z.
From: 'Greg Salyer' astronutcase@... [ap-gto] Sent: Saturday, March 17, 2018 7:48 PM To: ap-gto@... Subject: RE: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
No, as far as I know disconnect is not one of the problems with version 13. Of course as soon as I found fie transfers weren't supported yet I dropped it and went back to version 12 so I don't have a lot of experience with it. I then went on the web and found a lot of people went back to 12 because of missing functions such as file transfer, remote print and clipboard transfer. If your using such functions then I can't understand what's going on. The look and feel is totally different than version 12. The basic stuff seemed to work just fine but if the missing functions are hidden somewhere I didn't see where. Are you sure your on version 13?
Greg
From: ap-gto@... [mailto:ap-gto@...]
Hi Wayne,
Is this disconnect something new in version 13?
Like you, I used TV for probably 10 years, hassle free. Used version 13 today, for most of the afternoon, never got disconnected, no warnings, just a “polite Thank You” for using TeamViewer .... AFTER I logged out.
It didn’t disconnect me in the 4 hours I was using it, so I don’t know why you are having a problem. That’s weird. Did you somehow download a trial “commercial user” version”. I think TV Corp is pretty wary and checks if you are suspected of using it for business. Don’t know what they may “snoop” for, in the transactions – if they actually do that. Perhaps there are “terms of service” that you acknowledge their right to do that – probably.
I have heard of cases where so-called “home users” got caught and cancelled.
Anyway, so far, the latest TV version is behaving no different from years of the older ones. I would curious what you or anyone else discovers about your TV situation. I don’t think TV changed the rules for eligibility.
Joe
From: Wayne wayneh9026@... [ap-gto] Sent: Saturday, March 17, 2018 5:44 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Waynr
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Stuart Heggie <stuart.j.heggie@...>
Joe, not to take away from this being Greg's thread but why aren't all your computers showing up by their names? I name all mine. Easy to tell which is which in TV. Stuart
On Sat, Mar 17, 2018 at 8:23 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
--
Stuart Heggie
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Joe Zeglinski
Greg,
EXACTLY, the same “menu/function bar” as in all previous
versions.
Checked its function bar contents & options, a few minutes ago,
and there are no differences.
By any chance did you click the “Up-Arrow” at the top of the logged in
(host PC, telescope) screen button, on it to “HIDE, roll up, the function
bar” ? If so, click it again.
Joe
From: 'Greg Salyer' astronutcase@... [ap-gto]
Sent: Saturday, March 17, 2018 8:29 PM
To: ap-gto@...
Subject: RE: [ap-gto] Re: Remote Desktop PC access on Ad Hoc
Network Ok, I've now got version 13 on both ends, however, I still don't get the "missing" functions. Are you getting the same screen as version 12 when you connect? I get a brand new line at top with almost no function.
Greg
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Ok, I've now got version 13 on both ends, however, I still don't get the "missing" functions. Are you getting the same screen as version 12 when you connect? I get a brand new line at top with almost no function.
Greg
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, March 17, 2018 8:05 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
That might be it. Any time I get that warning about one of my computers being behind I just update. It is a small program and reloads really fast.
Stuart
On Sat, Mar 17, 2018 at 8:00 PM, 'Greg Salyer' astronutcase@... [ap-gto] <ap-gto@...> wrote:
Perhaps I can explain what's going on. I installed version 13 without also installing version 13 on the remote computer. This has never been a problem before but maybe I was missing the functions because of the version difference. When I have a chance I'll try using version 13 on both ends. I do like the high dpi behavior of the new version better.
Greg
From: ap-gto@... [mailto:ap-gto@...]
I've been using v 13 since it came out. It totally does file transfers.
Stuart
On Sat, Mar 17, 2018 at 7:48 PM, buckeyestargazer@... [ap-gto] <ap-gto@...> wrote:
I've been using Teamviewer also for years, including now on version 13. There was a short time when 13 came out that is was giving annoying warnings and promotions, but those have ceased for a while now.
I never get disconnected as long as there is a stable network. Quite often I forget to exit TV before I go to bed and wake up the next morning and TV is still connected to the remote PC.
I've never quite understood why people like Windows RD when much better options like TV are available for free. joel
-- Stuart Heggie
-- Stuart Heggie
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Joe Zeglinski
Greg,
Perhaps you answered the INSTALLER with some non-control
option – or what ever the alternate was. I forget what it was, but there were
TWO kinds of user install.
Yes – I did a File Transfer, the same old way I have for
years, this afternoon – and I double checked – I am now running version
13.1.1548 build Mar 9, 2018.
The File Transfer, and all the other command menu bar
options are EXACTLY the same as they always were, including File Transfer
and Remote Print – and I assume Clipboard still works as it used to do.
I too was surprised by the “slightly new” GUI screen – I didn’t use
their new fangled advanced one, offered as a beta test option back in
version 12. I like this simpler, old one.
Only one thing would improve it – a NAME tag
beside its remembered list connect ID numbers. Hard to distinguish between
helped family and friends’ 9-digit numbers.
So, there is something different in your own install of
version 13.
Mind you, I didn’t install version 13 ... all over again. It updated itself
at some point, when I wasn’t looking. So, my old install is NOT a “fresh”
install. Maybe that is where they changed things.
Greg - Did you perhaps install version 13 from scratch,
that got you in the current mess ?
Maybe download and re-install, or install version 12 and click the CHECK
for new Version button in HELP, rather than a fresh download/install.
That’s in case there is a inconsistency between Installer, and Updater. It
really is worthwhile pursuing.
Good luck Greg. Just curious – hope your situation isn’t something new at
TV.
Joe Z.
From: 'Greg Salyer' astronutcase@... [ap-gto]
Sent: Saturday, March 17, 2018 7:48 PM
To: ap-gto@...
Subject: RE: [ap-gto] Re: Remote Desktop PC access on Ad Hoc
Network No, as far as I know disconnect is not one of the problems with version 13. Of course as soon as I found fie transfers weren't supported yet I dropped it and went back to version 12 so I don't have a lot of experience with it. I then went on the web and found a lot of people went back to 12 because of missing functions such as file transfer, remote print and clipboard transfer. If your using such functions then I can't understand what's going on. The look and feel is totally different than version 12. The basic stuff seemed to work just fine but if the missing functions are hidden somewhere I didn't see where. Are you sure your on version 13?
Greg
From:
ap-gto@... [mailto:ap-gto@...]
Hi Wayne,
Is this disconnect something new in version 13?
Like you, I used TV for probably 10 years, hassle free. Used version 13 today, for most of the afternoon, never got disconnected, no warnings, just a “polite Thank You” for using TeamViewer .... AFTER I logged out.
It didn’t disconnect me in the 4 hours I was using it, so I don’t know why you are having a problem. That’s weird. Did you somehow download a trial “commercial user” version”. I think TV Corp is pretty wary and checks if you are suspected of using it for business. Don’t know what they may “snoop” for, in the transactions – if they actually do that. Perhaps there are “terms of service” that you acknowledge their right to do that – probably.
I have heard of cases where so-called “home users” got caught and cancelled.
Anyway, so far, the latest TV version is behaving no different from years of the older ones. I would curious what you or anyone else discovers about your TV situation. I don’t think TV changed the rules for eligibility.
Joe
From: Wayne wayneh9026@... [ap-gto] Sent: Saturday, March 17, 2018 5:44 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Waynr
Sent from my iPhone
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Stuart Heggie <stuart.j.heggie@...>
That might be it. Any time I get that warning about one of my computers being behind I just update. It is a small program and reloads really fast. Stuart
On Sat, Mar 17, 2018 at 8:00 PM, 'Greg Salyer' astronutcase@... [ap-gto] <ap-gto@...> wrote:
--
Stuart Heggie
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Perhaps I can explain what's going on. I installed version 13 without also installing version 13 on the remote computer. This has never been a problem before but maybe I was missing the functions because of the version difference. When I have a chance I'll try using version 13 on both ends. I do like the high dpi behavior of the new version better.
Greg
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, March 17, 2018 7:52 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
I've been using v 13 since it came out. It totally does file transfers.
Stuart
On Sat, Mar 17, 2018 at 7:48 PM, buckeyestargazer@... [ap-gto] <ap-gto@...> wrote:
I've been using Teamviewer also for years, including now on version 13. There was a short time when 13 came out that is was giving annoying warnings and promotions, but those have ceased for a while now.
I never get disconnected as long as there is a stable network. Quite often I forget to exit TV before I go to bed and wake up the next morning and TV is still connected to the remote PC.
I've never quite understood why people like Windows RD when much better options like TV are available for free. joel
-- Stuart Heggie
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Stuart Heggie <stuart.j.heggie@...>
I've been using v 13 since it came out. It totally does file transfers. Stuart
On Sat, Mar 17, 2018 at 7:48 PM, buckeyestargazer@... [ap-gto] <ap-gto@...> wrote:
--
Stuart Heggie
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
No, as far as I know disconnect is not one of the problems with version 13. Of course as soon as I found fie transfers weren't supported yet I dropped it and went back to version 12 so I don't have a lot of experience with it. I then went on the web and found a lot of people went back to 12 because of missing functions such as file transfer, remote print and clipboard transfer. If your using such functions then I can't understand what's going on. The look and feel is totally different than version 12. The basic stuff seemed to work just fine but if the missing functions are hidden somewhere I didn't see where. Are you sure your on version 13?
Greg
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, March 17, 2018 7:19 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Hi Wayne,
Is this disconnect something new in version 13?
Like you, I used TV for probably 10 years, hassle free. Used version 13 today, for most of the afternoon, never got disconnected, no warnings, just a “polite Thank You” for using TeamViewer .... AFTER I logged out.
It didn’t disconnect me in the 4 hours I was using it, so I don’t know why you are having a problem. That’s weird. Did you somehow download a trial “commercial user” version”. I think TV Corp is pretty wary and checks if you are suspected of using it for business. Don’t know what they may “snoop” for, in the transactions – if they actually do that. Perhaps there are “terms of service” that you acknowledge their right to do that – probably.
I have heard of cases where so-called “home users” got caught and cancelled.
Anyway, so far, the latest TV version is behaving no different from years of the older ones. I would curious what you or anyone else discovers about your TV situation. I don’t think TV changed the rules for eligibility.
Joe
From: Wayne wayneh9026@... [ap-gto] Sent: Saturday, March 17, 2018 5:44 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Waynr
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
I've been using Teamviewer also for years, including now on version 13. There was a short time when 13 came out that is was giving annoying warnings and promotions, but those have ceased for a while now.
I never get disconnected as long as there is a stable network. Quite often I forget to exit TV before I go to bed and wake up the next morning and TV is still connected to the remote PC. I've never quite understood why people like Windows RD when much better options like TV are available for free. joel
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Joe Zeglinski
Greg,
Are you saying that TV does NOT have “File Transfer”, in
the free personal use version ?
I used it an hour ago, on TV version 13, and on past versions for years.
Unfortunately, it isn’t File “Drag-n-Drop”, but does quite well, once you set up
the from/to (left/right) pointers on its File Transfer screen.
I mostly use it for my backyard remote scope, so yes,
you have to “Accept Incoming LAN connections” – obviously, which isn’t a problem
for an internal - home LAN. In past years, I did get random disconnects,
and was going to eventually give TV a hard time on that issue. Of course,
turning on the microwave oven for rewarming my coffee, will always disconnect
after about 30 seconds – that’s just the nature of 2G (2.4 GHZ)communications,
and I should switch to 5G frequencies on my next Router. But, to my utter
surprise, the problem FINALLY disappeared on its own, about half a year ago, and
I never got a disconnect since. Hopefully, the recent version 13, doesn’t,
as you suggest screw that up again.
If TV ever gets nasty, which I doubt, then I will have
to find some other “Remote app” – but definitely NOT Microsoft’s lame Remote
Desktop version, as it has been from day one. I think the reason why Microsoft
didn’t make a “decent” Remote, is because they were forced to comply with their
third party software companies – not to compete with their better commercial
versions. Microsoft treats commercial customers and probably developers well,
and Home Users customers as cannon fodder.
I think the folks at TeamViewer are doing a great job on
their commercial product support product – with my hardiest gratitude and
thanks, as a “personal use only” customer – and hope their quality
service and performance continues as it has been.
Joe Z.
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
Joe Zeglinski
Hi Wayne,
Is this disconnect something new in version 13?
Like you, I used TV for probably 10 years, hassle free.
Used version 13 today, for most of the afternoon, never got disconnected, no
warnings, just a “polite Thank You” for using TeamViewer ... AFTER I logged out.
It didn’t disconnect me in the 4 hours I was using it,
so I don’t know why you are having a problem. That’s weird. Did you somehow
download a trial “commercial user” version”. I think TV Corp is pretty wary and
checks if you are suspected of using it for business. Don’t know what they may
“snoop” for, in the transactions – if they actually do that. Perhaps there are
“terms of service” that you acknowledge their right to do that – probably.
I have heard of cases where so-called “home users” got
caught and cancelled.
Anyway, so far, the latest TV version is behaving no
different from years of the older ones.
I would curious what you or anyone else discovers about your TV situation.
I don’t think TV changed the rules for eligibility.
Joe
From: Wayne wayneh9026@... [ap-gto]
Sent: Saturday, March 17, 2018 5:44 PM
To: ap-gto@...
Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc
Network Joe, I used the freeware version of TeamViewer for quite a while but I got tired of it frequently reminding me that I was used my a free version and making me reconnect. Does it still do that? Waynr
On Mar 17, 2018, at 2:37 PM, 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: Remote Desktop PC access on Ad Hoc Network
I totally agree, but don't use version 13. It has better high dpi support but currently lacks many features (like file transfer). It should have been released only as a Beta. They do provide back versions. Get version 12. Also, to avoid disconnects you must "accept" "Incoming LAN connections" under Extras/Options/General. Teamviewer also allows control from an iPhone or iPad (and I suspect Android as well).
Greg PS: I also like and use Radmin
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, March 17, 2018 5:38 PM To: ap-gto@... Subject: Re: [ap-gto] Re: Remote Desktop PC access on Ad Hoc Network
Hi Micah,
While Microsoft’s “Remote Desktop” is OK when starting out ... consider using a free (for non-commercial users) copy of TEAMVIEWER.
The big advantage of the latter, besides not needing a PRO version of Windows on each computer – is that BOTH PC screens & mice remain LIVE – you can operate the mount or control your imaging program, from indoors or outdoors. The outdoor PC does NOT logout and its screen doesn’t go black, when you go indoors, and you don’t have to login again, on either side, as you do in “MS Remote Desktop”. You can also have friends login, or login from other computers in the house, into your outdoor remote scope computer, to share the experience, even using their own mouse, if you let them participate fully.
It is far more convenient, with added benefits like File Transfer – in both directions. There are of course other (subscription based) remote control programs. – Microsoft has always been a rather chincy, “bare bones” Remote, and forces you to install a more expensive Windows OS. Also, you can’t operate your scope computer for a “show-n-tell”, with that MS version, from anywhere else, like a friend’s place, unless they also have the PRO version installed.
Joe Z.
|
|
|