• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Remote Desktop vs PC Anywhere

Kelemvor

Lifer
Howdy,

I'm setting up a PC (XP Pro) in my basement that will run my Home Audio system. It will be set to automtically logon and start the needed app. However, I want to be able to access the system from my other computers.

I know that PC Anywhere can do this well since that's what it's made to do. But I'm not sure about exactly how remote desktop works. I do NOT want to access the other coputer and login as a new users to run new programs etc. I DO want to basically connect up, and see everything that is already running. Any error messages, pop ups, etc.

From what I know of Remote Desktop (which sin't much) it logs me on as a separate user from the one actually logged onto the machine which isn't what I want to do. Can RD be configured to work like PC Anywhere works or should I just use PC Anywhere and be done with it?
 
You should avoid PCAnywhere. It is a very poor product nowadays. From what you want, you'd be best off with some VNC product like Real/Tight/Ultra. Or my fav is RADmin. Terminal Services will not do for your needs.
 

RDP is much quicker than PCanywhere, and it will do everything that you need it to do. Use Event Viewer log to diagnose your system. As, Tennoh has mentioned that VNC & variants, and many other remote program are better than PCanywhere.
 
Are there any free products to do this? It's not something I'd be invoking very often so don't want to have to go pay for something. Since it just saves me the 30 seconds it takes to walk down to the basement. heh heh.
 

RDP is free that come with Windows, however you might have to download free RDP5 client for XP home from MS. VNC/TightVNC also are free.
 
RDP is MUCH faster than PCAnywhere. You actually *CAN* log into Session Zero on WinXP Pro ( Same DeskTop Session as though you were "hands on" at the box )

You need to start the RDP Client from the command shell though. Type in "mstsc /console" ( I suppose you could also save this as a text bat file and add an icon ) When you're done, open a shell on the remote machine and type in " tscon 0 /dest:console " to close the session. Again, you could prob create a bat file on the remote machine to make this easier.

I think Microsoft didn't want end users to be able to do this because they didn't want you to be able to use a WorkStation OS for server functions ( I run a WinXP Pro Email Server and remote manage this way ) Prob considered "Too much Value for the Money" and cheating them out of their "rightful revenue "
 
I tried the console thing but it didn't do what I need. I need to do exactly what PC Anywhere does where I take over the machine exactly as it is if I were sitting right in front of it. So I guess I'll have to look into VNC or something else like that.
 
Remote Desktop. Why not use it? It's right there in your programs list. Accessories>Communication>Remote Desktop Connection. Set the parameters. It does exactly what you need it to do.
 
Feel free to tell me how I can login to the actual desktop being displayed and not have to login as a separate user on a separate instance of the OS and I'd be happy to. That's the whole point of this thread...
 
Originally posted by: wlee
RDP is MUCH faster than PCAnywhere. You actually *CAN* log into Session Zero on WinXP Pro ( Same DeskTop Session as though you were "hands on" at the box )

You need to start the RDP Client from the command shell though. Type in "mstsc /console" ( I suppose you could also save this as a text bat file and add an icon ) When you're done, open a shell on the remote machine and type in " tscon 0 /dest:console " to close the session. Again, you could prob create a bat file on the remote machine to make this easier.

I think Microsoft didn't want end users to be able to do this because they didn't want you to be able to use a WorkStation OS for server functions ( I run a WinXP Pro Email Server and remote manage this way ) Prob considered "Too much Value for the Money" and cheating them out of their "rightful revenue "


If you already have a user logged in (and you said you did) you THOSE credentials when you connect with RDP (ignore all of the above, it's totally non needed)

You'll need pcA if you want to be able to connect and control the machine ACROSS the fast user screen. But with remote desktop if you just connect as the same user already logged in, you'll get their session...

Bill

 
OK, here's what I did.

1) Booted up the server (this one is running 2000 advanced server)
2) Logged in with my ID and password on the network.
3) Opened up a web browser and the printers window
4) Went to my laptop (running NT Pro)
5) Launched Remote Desktop
6) Entered my same User ID / Password in the connect window and clicked Connect
7) This brought me to a Logon window for Win 2k Adv Server. User my same information again and clicked OK to logon
8) This logged me in and brought up the session I used the last time I logged in with Remote Desktop. It did NOT bring up the IE Browser and such that I see whatn I look at the actua lserver itself. E.G. If I change things around while connected through Remote Desktop, then logout, then log back in with Remote Desktop, I will see what I had changed while connected through Remote Desktop. I do NOT see what is going on on the actual machine.

What I need is for it to work just like PC Anywhere where I would be controlling the actual PC I'm connecting to and not using it as another user.

I'll try VNC later (downlaoded from www.vnc.com, hope that's the right one) and see what happens. At home I will be doign this betwene two PCs both running WIn XP Pro if that makes a difference.
 
OK, here's what I did.

Irrelevant steps deleted.

I wish you would simply read my response and TRY IT. This works differently on XP pro (the OS you said you were using downstairs) vs 2000 advanced server (sheesh). XP only allows one logged in session, period. If you log in wit the same credentials you get the same session.

For gods sake, it just works. I'm sending this message from my home pc, I'm RDP'd in to my existing session (just like I do every day)

Bill
 
Some people just don't want to hear the answers. They struggle and struggle with it. Anyway, good luck with the quest, since even when you have accomplished it you still go on trying to accomplish it. Life must be hard. 😀
 
All you had to say was that it works differently on XP than 2k server.

OK, I'm at home now.
Logged onto my PC (Media-pc) and logged in with the default user (media) which is set to automatically login with no password.
Went into the Sys Properties and turned on Remote Access. Said I could add users but that user Media already has access.
Went to my other XP PC and launched the remote desktop connection tool
Typed the computer name (media-pc) and used the same username (media) as is logged in on the PC I want to connect to.

That brought up a Windows XP Login Screen like I was logging into the PC from scratch.
I again typed in the username (media) that was already in use and then I got the error window that says:

Unable to log you on because of an accoutn restriction.

Did I miss something?

EDIT: Well, per Microsoft I guess I can't have a null password so I guess I'll put a password on there.
 
That's OK, I just don't have passwords on my home computers. Turned one on and it's working like a charm.

Thanks all.
 
I use both. I prefer ultra vnc for quit connects over my 200 plus network at work. 1 password for most everything and the user can watch me while I work. For connections to my desktop over a vpn i use RDS. It seems quicker and eliminates mouse lag. I know this thread was done but had to throwin my 2 cents.
 
Whether to use Win Remote Desktop (RTP) or a regular remote program might depend in the way you are using it, and who, or what is on the other side. RDT is more like an OS thing rather than an application.

I use RDT between spots that I need to Connect to Repetitively for long periods of time and when on the other side there is someone who understands how it works. I would set it up, and insist that No one would touch the settings.

Otherwise I use Ultr@VNC (free program). Its provides: Remote Control, File Transfer, and Chat between LAN computers or over the Internet. It takes only few minutes to set it.

For security purpose, and to avoid System's load on the system resources I want the remote application out of the picture once the session is terminated. Ultra@VNC and few other VNC variants provide this capacity.

In most cases, even if some one "played" with the system I still will be able to connect with VNC.

You will find every thing you need in order to set it here: Ultr@VNC - Installation, and Settings

If you decide to go the RDT way, here you have two links with help for Win Remote Desktop (RDT).

Link to: Set Up Remote Desktop Web Connection with Windows XP.

Link to: How to use remote Desktop Access in Windows XP.

:sun:
 
Just go out and at least TRY a VNC variant! It's about as idiot proof as you can get and you get the added benefit of being able to use the standard client or connect via your web browser (on port 5800).

While I like Ultra VNC and think it is going to be THE vnc of the future, it's been buggy (service crashed occasionally) on a couple of machines that I've put it on... reverted back to TightVNC on these machines and everything is fine. Other machines have been running Ultra just fine, but since I'm in a commercial environment, the stability is MUCH more important to me than the added features. I must reiterate though that I anticipate moving all my machines over to Ultra once they release a version that isn't buggy on some machines.

Joe
 
Back
Top