Remote Desktop is so awesome...

[archcommus]

Originally posted by: GeekDrew

Originally posted by: archcommus
Cool stuff, everyone. It's fun to learn about a whole new realm of computer things that you never even explorered or thought about before. I never gave RD a second thought and now I'm seeing all its possibilities!

I really only have two situations to use this: to connect to my computer from my girlfriend's house, and once I'm in school in the fall, to connect to my dad's computer at home from school (because I know he'll be needing help with things). All of these computers will be using XP Pro, so it seems RD is definitely the way to go for me.

So a VPN must be set up first? Is this something that's permanent or done every time prior to creating an RDC? What is the other way to do it besides IE, and is it better or worse?

Sorry for all the Qs.

No, a VPN is not needed... the way that most people connect to RDP is to go to <Start><RUN>mstsc<OK>, and then connecting to the computer they want to connect to (by typing in the appropriate computer name or IP). I personally prefer that way; I've found it works somewhat better / more reliable than IE.

What exactly is launching that app accomplishing? After doing that I could just enter my IP from the client in Start->Program->Accessories->Communications->Remote Desktop Connection?

Now some Qs from the article:

I can skip "Get Your Host Computer Ready" because the host is already XP Pro, is this correct?

From the "Configure Internet Information Services" section, I'm confused about what port I'm changing there exactly.

In the "Connect to Your Desktop" section, it is describing how to connect through IE. If I did it GeekDrew's way, what kind of window would it open in?

Finally, by creating a password for my account (since I do not use one now), will I have to enter it to get into Windows every time I boot the computer instead of it just going straight to the desktop itself? Whenever I connect to my computer remotely, it blacks out the host screen. Does it automatically restore itself after disconnecting or does it stay blacked out until someone comes back to it?

 

[GeekDrew]

Originally posted by: archcommus

Originally posted by: GeekDrew

Originally posted by: archcommus
Cool stuff, everyone. It's fun to learn about a whole new realm of computer things that you never even explorered or thought about before. I never gave RD a second thought and now I'm seeing all its possibilities!

I really only have two situations to use this: to connect to my computer from my girlfriend's house, and once I'm in school in the fall, to connect to my dad's computer at home from school (because I know he'll be needing help with things). All of these computers will be using XP Pro, so it seems RD is definitely the way to go for me.

So a VPN must be set up first? Is this something that's permanent or done every time prior to creating an RDC? What is the other way to do it besides IE, and is it better or worse?

Sorry for all the Qs.

No, a VPN is not needed... the way that most people connect to RDP is to go to <Start><RUN>mstsc<OK>, and then connecting to the computer they want to connect to (by typing in the appropriate computer name or IP). I personally prefer that way; I've found it works somewhat better / more reliable than IE.

What exactly is launching that app accomplishing? After doing that I could just enter my IP from the client in Start->Program->Accessories->Communications->Remote Desktop Connection?

Now some Qs from the article:

I can skip "Get Your Host Computer Ready" because the host is already XP Pro, is this correct?

From the "Configure Internet Information Services" section, I'm confused about what port I'm changing there exactly.

In the "Connect to Your Desktop" section, it is describing how to connect through IE. If I did it GeekDrew's way, what kind of window would it open in?

Finally, by creating a password for my account (since I do not use one now), will I have to enter it to get into Windows every time I boot the computer instead of it just going straight to the desktop itself? Whenever I connect to my computer remotely, it blacks out the host screen. Does it automatically restore itself after disconnecting or does it stay blacked out until someone comes back to it?

I've not got time to read the article and respond.... maybe later tonight.

Running MSTSC is the same thing as going thru the start ment to Remote Desktop Connection.

Connecting "my way" or thru the start menu opens a sizeable window in a dedicated program, instead of using ActiveX hooks in Internet Explorer. I believe that they look and work quite similarly.... wouldn't surprise me if IE actually just called the program I'm using. I just prefer to do it manually, I've had connection problems before when connecting thru IE.

 

[archcommus]

Thanks.

 

[ActuaryTm]

Originally posted by: archcommus
I can skip "Get Your Host Computer Ready" because the host is already XP Pro, is this correct?

No. Remote Desktop requires Xp Pro on the host side. If choosing to use the web client, follow the instructions as outlined in the article. If choosing to use the Remote Desktop client linked above (or using Xp Pro on the client side as well), follow those instructions.

From the "Configure Internet Information Services" section, I'm confused about what port I'm changing there exactly.

See above reply.

In the "Connect to Your Desktop" section, it is describing how to connect through IE. If I did it GeekDrew's way, what kind of window would it open in?

See above reply, again.

Finally, by creating a password for my account (since I do not use one now), will I have to enter it to get into Windows every time I boot the computer instead of it just going straight to the desktop itself?

Believe so. However, you can change the Logon behavior by using Tweak UI Powertoy. Check the Logon>Autologon option.

Whenever I connect to my computer remotely, it blacks out the host screen. Does it automatically restore itself after disconnecting or does it stay blacked out until someone comes back to it?

Yes. One added benefit of using a VNC derivative over Remote Desktop is that it does not black out the host screen during a remote session. Nice for showing a remote user how to accomplish a task. The same can be done with Remote Assistance, I believe, which should not be confused with Remote Desktop.

 

[archcommus]

Thanks.

So the host computer needs no work expect for having "Allow etc. etc." checked in System Properties as long as it's XP Pro and you're using the client and not IE.

The client just needs the IP and name and pw.

Just tried it with my buddy and it was very easy. Not quite as fast as I was hoping, though, which is odd considering we both have 4 Mbps cable.

Whenever I logged in to his computer, though, it did not black out his screen, it took him to the log on screen. And he had no way of knowing when I was logged on or not. But as soon as HE would log back on, it would kick me.

 

[GeekDrew]

Originally posted by: archcommus
Thanks.

So the host computer needs no work expect for having "Allow etc. etc." checked in System Properties as long as it's XP Pro and you're using the client and not IE.

The client just needs the IP and name and pw.

Just tried it with my buddy and it was very easy. Not quite as fast as I was hoping, though, which is odd considering we both have 4 Mbps cable.

Whenever I logged in to his computer, though, it did not black out his screen, it took him to the log on screen. And he had no way of knowing when I was logged on or not. But as soon as HE would log back on, it would kick me.

Yeah, now that I think about it, it does normally go to a login screen instead of a blank screen... maybe it depends on whether it detects the console is in use? I'm fairly certain I've seen it both ways.

I'm surprised you mentioned a speed issue... I've used RDP over a 1.5 mb DSL connection... and I've streamed MP3s across that connection, while browsing... in real time... :-\

 

[archcommus]

Great, and now I have other problems. No way could it be related to this. See my thread in General Hardware.

 

[Philippine Mango]

remote desktop is nice for speed but pcanywhere will let you run games... So you can't play CivIII on a system with only remote desktop but you could with a system with pcanywhere. It's pretty cool, the reason I like remote desktop though over pcanywhere in some cases is that I'm able to listen to music from my home computer.
Remote desktop Pros: Faster loading, audio playing, no extra software required
Remote desktop cons: Will not run any program that requires direct anything like draw etc.. Very difficult if not impossible to send files from the host computer to your computer

PC anywhere pros: will run directX programs, easy to send files from host to your computer, you can host from older machines (windows 95, 3.1 etc..), more control of the system (easier to restart)
PC anywhere cons: slower loading, does not play audio, extra software required (buy it)

 

[ActuaryTm]

Originally posted by: GeekDrew
Yeah, now that I think about it, it does normally go to a login screen instead of a blank screen... maybe it depends on whether it detects the console is in use? I'm fairly certain I've seen it both ways.

Agreed. Have seen it both ways as well, now that you mention it. My aging memory isn't what it used to be, unfortunately.

As should be rather evident, I am much more familiar with the operations of VNC than Remote Desktop, and can sternly attest that the host machine shows precisely the same as the client (no blank/black/logon/etc).

As soon as I have a spare moment, will look at your thread in GH.

 

[Philippine Mango]

Originally posted by: GeekDrew

Originally posted by: archcommus
Thanks.

So the host computer needs no work expect for having "Allow etc. etc." checked in System Properties as long as it's XP Pro and you're using the client and not IE.

The client just needs the IP and name and pw.

Just tried it with my buddy and it was very easy. Not quite as fast as I was hoping, though, which is odd considering we both have 4 Mbps cable.

Whenever I logged in to his computer, though, it did not black out his screen, it took him to the log on screen. And he had no way of knowing when I was logged on or not. But as soon as HE would log back on, it would kick me.

Yeah, now that I think about it, it does normally go to a login screen instead of a blank screen... maybe it depends on whether it detects the console is in use? I'm fairly certain I've seen it both ways.

I'm surprised you mentioned a speed issue... I've used RDP over a 1.5 mb DSL connection... and I've streamed MP3s across that connection, while browsing... in real time... :-\

were you browsing on the remote computer or on your computer? I listened to music on the remote computer but could not have any moving objects on the remote system otherwise it would skip.

 

[GeekDrew]

Originally posted by: Philippine Mango
were you browsing on the remote computer or on your computer? I listened to music on the remote computer but could not have any moving objects on the remote system otherwise it would skip.

I was doing everything remotely... listening to music, browsing, etc. My local computer was doing nothing besides providing my connection to the remote system (and for that matter, the remote system was only doing what I was telling it to do, remotely).

 

[imthebadguy]

yeahhh its awesome

 

[kyparrish]

OMG this rocks...

I've never set it up before I'm enjoying running my main rig off of my wireless lappy

 

[Pepsi90919]

had it going for a while now. actually using it to control foobar on the other computer from my laptop, to play mp3s on my good speakers in the other room.

*however*, i have had issues trying to connect from school... i talked to a CCNA geek i have classes with and he thinks everything above port 1024 is blocked. however possible it was to reassign the port, i didn't think it was worth it.

oh and that terminal services web client isn't network-specific...i could use any of the web clients to connect to any remote desktop connection.

 

[iamwiz82]

Originally posted by: Philippine Mango
remote desktop is nice for speed but pcanywhere will let you run games... So you can't play CivIII on a system with only remote desktop but you could with a system with pcanywhere. It's pretty cool, the reason I like remote desktop though over pcanywhere in some cases is that I'm able to listen to music from my home computer.
Remote desktop Pros: Faster loading, audio playing, no extra software required
Remote desktop cons: Will not run any program that requires direct anything like draw etc.. Very difficult if not impossible to send files from the host computer to your computer

PC anywhere pros: will run directX programs, easy to send files from host to your computer, you can host from older machines (windows 95, 3.1 etc..), more control of the system (easier to restart)
PC anywhere cons: slower loading, does not play audio, extra software required (buy it)

PCAnywhere is on the bottom of the totem pole when it comes to speed between RDC, VNC, and PCAnywhere.

 

[Amused]

I remote desktop within my own network all the time (laptop to main system or server, usually).

But I haven't figured out how to do it from another network. You all make it sound easy. I guess I'll have to figure it out.

If I forward a port, wont my network be much less secure?

 

[PlatinumGold]

Originally posted by: Amused
I remote desktop within my own network all the time (laptop to main system or server, usually).

But I haven't figured out how to do it from another network. You all make it sound easy. I guess I'll have to figure it out.

If I forward a port, wont my network be much less secure?

yes. anyone that knows the login / password of that machine would have access to it.

 

[Amused]

Originally posted by: PlatinumGold

Originally posted by: Amused
I remote desktop within my own network all the time (laptop to main system or server, usually).

But I haven't figured out how to do it from another network. You all make it sound easy. I guess I'll have to figure it out.

If I forward a port, wont my network be much less secure?

yes. anyone that knows the login / password of that machine would have access to it.

Is that easily hackable?

 

[archcommus]

My friend connected to me no problem (I don't have a router). When I connected to my friend, it was slow and I kept getting data encryption errors. I think it was just because he didn't forward his ports properly.

 

[Viper GTS]

Originally posted by: Amused

Originally posted by: PlatinumGold

Originally posted by: Amused
I remote desktop within my own network all the time (laptop to main system or server, usually).

But I haven't figured out how to do it from another network. You all make it sound easy. I guess I'll have to figure it out.

If I forward a port, wont my network be much less secure?

yes. anyone that knows the login / password of that machine would have access to it.

Is that easily hackable?

No more so than someone sitting down at your machine & trying to figure out your username & password.

Port 3389 TCP is what you need (as others have said).

Viper GTS

 

[kyparrish]

wanna add one more thing to this....

I was mainly interested in RD so that I could listen to my iTunes music from my desktop on my laptop. It sounded decent with RD, but sounds twice as good just using iTunes music sharing

 

[Valhalla1]

by the way, if any of you guys run linux or a BSD as your firewall, you might consider instead of forwarding port 3389 to your windows box, instead only leave port 22 open and foward this to a secured linux machine.
Then use SSH2 tunneling on the remote end to port forward localhost:3389 to 192.168.0.x(windows machine at home)

advantages -
leaves only port 22 open on firewall, instead of having an obvious windows box with a listening port exposed on your exterior
encrpytion over encryption - RDP is encrypted, but so is ssh. I use tunnels a lot and think of it as a quick and easy ghetto vpn. RDP on windows hasn't been cracked yet, but with MS you never know.


and if you are using VNC (windows 2000 for example) I would certainly use SSH tunneling and not leave that exposed

 

[nageov3t]

I use it all the time at work, and frequently at home within my local network... it's nice to be in bed on my laptop and be able to change the away message on my desktop without getting up

I've never figured out how to get into my computer at home through my computer at work, though. no static ip on my home pc kills it for me.

 

[Amol1]

i wanna run this on my desktop (xp pro) while using my laptop (xp home)

that'd be awesome, especially away from the house, i could set up a webcam and see what all is happening

 

[Goosemaster]

heh...jsut wait till you discoverthe RDP Active X control....lol...you people will go nuts