Remote Desktop - pitfalls, shortcomings

pmrid (Peter) · #1 07-10-2009, 03:43 PM

I've managed to get this working with the computers in my Obs. It's 200 metres away from the house so I've put up a couple of grid-type dishes linked to the wireless router in the house and to a bridge and a 5-port switch in the Obs so I have both scopes (there are 2 piers in the obs and a scope on each) now accessible via Remote Desktop. But the weather hasn't been kind so I've yet to give it an 'under-the-sky- test.
So while I wait, I thought I might poll others with more experience in these areas than I (won't be hard) to see what the pitfalls are and identify any 'things-I wish-I knew-before-I-started'.
Peter

rogerg (Roger) · #2 07-10-2009, 05:00 PM

Providing you could already use your telescope(s) via computer while sitting in the observatory, controlling them via Remote Desktop shouldn't present any problems at all. I haven't had any problems relating to remote usage of my observatory, or Remote Desktop in work applications.

You do very occasionally find some software will not install correctly when installing that software under the control of Remote Desktop, but that is the only thing I can think of.

Remote Desktop tends to "just work", as if you were sitting at the remote computer.

If this is also your first shot at running entirely from computer then you might have other things to consider like programming in horizons and slew limits to your starchart/control software, ensuring no cables can snag, having a procedure in place to sufficiently monitor the weather conditions, understanding your pointing accuracy limitations (if any), etc.

Roger.

Quote:

Originally Posted by pmrid

I've managed to get this working with the computers in my Obs. It's 200 metres away from the house so I've put up a couple of grid-type dishes linked to the wireless router in the house and to a bridge and a 5-port switch in the Obs so I have both scopes (there are 2 piers in the obs and a scope on each) now accessible via Remote Desktop. But the weather hasn't been kind so I've yet to give it an 'under-the-sky- test.
So while I wait, I thought I might poll others with more experience in these areas than I (won't be hard) to see what the pitfalls are and identify any 'things-I wish-I knew-before-I-started'.
Peter

acropolite (Phil) · #3 07-10-2009, 05:09 PM

Peter, in my experience, there are no pitfalls with remote desktop, you're essentially on the desktop of the machine you're remotely connected to. I use RD every day for work, we have RD set up from the outside world via the net and port mapping, using alternate ports to the standard (which is 3389) and with user accounts that lockout after 3 incorrect login attempts. I use this when I'm on holidays for support purposes.

Works a treat for everything we do, every app works including some that use an outgoing ISDN modem to dial in to PABX's.

BTW grid dishes are overkill for the distance you're using (grids will work at distances over 10Km) and may even give problems as they're prone to picking up interference from the rear.
If you get interference problems a better option are the 12db panels which, although directional, don't pick up from behind. You can even print remotely if you have the same driver on both the remote and host machine. Given that you're using wireless make sure you have encryption set up and it wouldn't be a bad idea to change the default RD port (I use something in the 32000 and upwards range, a simple registry hack, just google for it) and set up some login restrictions just in case someone does manage to hack your network.

To put an account login restriction (you need to have first applied a password to the host machine user account) go to Control Panel, Admin Tools,Local Security Policy, Account policies, Account lockout policy. You'll find settings for the number of login attempts, a time period for those attempts and a lockout period if you number of unsuccesful attempts has been reached.

Octane (Humayun) · #4 07-10-2009, 05:22 PM

The only problem I've ever found whilst using Remote Desktop is that when I go back to work on the remote machine, my Wacom Intuos 3 stylus fails to register clicks and taps. So far, rebooting the machine has been the only fix.

Regards,
Humayun

mithrandir (Andrew) · #5 07-10-2009, 05:45 PM

Depending on the version of Windows, RDP may or may not give you the real console. Windows 2000 certainly doesn't and there is no workaround. Windows 2003 Server you have to specify the /console option to get it.
XP and Vista I couldn't be sure about.

Some things you might want to do require the real console, so you could find yourself wandering outside occasionally.

AlexN · #6 07-10-2009, 06:11 PM

Peter, I've been using RDP for exactly what you're talking about now for maybe 8 months... I've not once needed to walk outside to access the computer directly... My only outdoor ventures are to re-focus (soon to be solved) and to pack up...

Its a dream...

This message sent to you via RDP... Notebook, outside, in a deck chair in the sun with a corona, using my desktop to access the net..

pmrid (Peter) · #7 08-10-2009, 12:01 PM

Corona - a very suitable libation in the circumstances

I think I may have gone overboard with my grid dishes but it's too late now.
But it does make it a bit more important to get some encryption going. Up till now, my isolation was my excuse - the nearest warm body was/is a kilometre away but these dishes can push a signal several kilometres in open country. Although the dishes are directional, I should still do the sensible thing.
I haven't installed encryption before so I might just put that job aside 'till you get here and you can guide me through it.
cheers.
Peter

AlexN · #8 08-10-2009, 01:04 PM

running encryption is easy enough.. We'll do that next friday arvo once i've set up that can be task one. Then once i'm drift aligned and imaging we'll hit that rc and get that humming, then onto the qhy8... We'll have all your gadgetry singing a sweet song don't you worry!

kinetic (Steve) · #9 08-10-2009, 05:16 PM

Quote:

Originally Posted by AlexN

Peter, I've been using RDP for exactly what you're talking about now for maybe 8 months... I've not once needed to walk outside to access the computer directly... My only outdoor ventures are to re-focus (soon to be solved)

Its a dream...

+1

This message sent to you via RDP... Notebook, outside, feet up
having a Guinness and not remotely interested in observing atm

Steve

JohnH · #10 08-10-2009, 05:25 PM

Remote desktop does have some limitations - that is the session on the target machine will be logged off and your new session logged on. You therefore cannot control the target machine from its keyboard again until the remote control session is shut down. I have also seen issues with USB devices not recognised if the control program is started remotely as opposed to locally (seen with AA4).

Having said that it works very well for me and it is a boon in the winter to be able to control the scope from the lounge.

Tandum (Robin) · #11 08-10-2009, 08:23 PM

Quote:

Originally Posted by JohnH

Remote desktop does have some limitations - that is the session on the target machine will be logged off and your new session logged on.

Do a google for sala source terminal server patch. It enables 3 sessions on windows xp so you can be at the console and have 2 or 3 remote sessions all going at once. Not sure if you can have the same user logged in 4 times though

pmrid (Peter) · #12 09-10-2009, 12:07 AM

Quote:

Originally Posted by kinetic

+1

This message sent to you via RDP... Notebook, outside, feet up
having a Guinness and not remotely interested in observing atm

Steve

Good lad. You have to have priorities.
Peter

AstroJunk (Jonathan) · #13 09-10-2009, 12:53 AM

Quote:

Originally Posted by JohnH

Remote desktop does have some limitations - that is the session on the target machine will be logged off and your new session logged on. You therefore cannot control the target machine from its keyboard again until the remote control session is shut down.

If you log on remotely as the same user that doesn't happen - when you go back to the observatory it just kills the remote link and takes over the session (well it does that for me!)

As a video astronomer, I have issues. Not just with the refresh rate, which isn't such an issue, but with video capture programs which seem to have some problems with every bit of remoting software I have tried.

I'm going to have a try with two win7 machines to see if they work better as so far my main win7 box has been superb.

g__day (Matthew) · #14 09-10-2009, 09:10 AM

I find VNC runs (and re-freshes) a tad faster and with better remote screen colour fidelity than Remote Desktop.

Still in Winter - its great to remote control things!

kustard (Simon) · #15 09-10-2009, 11:27 AM

Quote:

Originally Posted by g__day

I find VNC runs (and re-freshes) a tad faster and with better remote screen colour fidelity than Remote Desktop.

Still in Winter - its great to remote control things!

I was just about to mention VNC. I use it here at work for all our windows based servers so I can access each server without the hassle of trying to set up Remote Desktop.

acropolite (Phil) · #16 09-10-2009, 01:04 PM

Robin's on the money on the Terminal server patch, turns out microsofts beta version of XP pro allowed access for more than one user, then nobbled it in the final release. The patch is basically some replacement DLL's from memory.

I have the same patch running at work, saves me inadvertantly logging out another user when I connect in from the outside world.

FWIW the patch allows concurrent logins for different users, no the same user.

pmrid (Peter) · #17 09-10-2009, 02:08 PM

Quote:

Originally Posted by acropolite

Robin's on the money on the Terminal server patch, turns out microsofts beta version of XP pro allowed access for more than one user, then nobbled it in the final release. The patch is basically some replacement DLL's from memory.

I have the same patch running at work, saves me inadvertantly logging out another user when I connect in from the outside world.

FWIW the patch allows concurrent logins for different users, no the same user.

I am hesitating on this patch only because on the DL site, it says the patch is not for machines that are in a domain. I'm not sure what that means to be honest but hestiate because I run a WAN at home.

White Rabbit · #18 09-10-2009, 05:18 PM

I had problems using aplications that used open GL when using RDP, I solved the problem with VNC though. Although VNC is still quite slow.

acropolite (Phil) · #19 11-10-2009, 01:00 PM

Quote:

I am hesitating on this patch only because on the DL site, it says the patch is not for machines that are in a domain.

No need to worry, you'll only be running in workgroup mode at home.

In a domain, terminals get their profiles, e.g. permissions etc, from a domain controller, usually a seperate server.