Remote Desktop problem

PAUL SHILLAM · 13th January 2002

Problem with XP Proffesional Remote Desktop.
I am new to Networking and have XP running on my laptop and ME on my desktop with wireless Lan cards. If I go into My Network Places on both machines they can see each other but only SharedDocs and Printers they can't see the disk drives.
If I access Remote Desktop from my Me PC I get the logon screen but it asks me for a password which I don't know as I have not set any passwords up.
I I activate Remote Destop from my XP laptop it says I haven't got permission to access the ME PC.
Any help would be welcome.
Paul

**Bursley** · 13th January 2002

You won't be able to see the entire hard drive of your other system across the network unless you access the c$ share on the remote PC.
Also, you need to grant permissions to remote desktop to a user on the local system. Once that is done, you can use your terminal services client to connect to your remote desktop with that user account.
The username and password would be those provided on the local PC. If you didn't provide a password, then the password is blank.
If you are not sure what user you are logged in as, press <winkey> L

PAUL SHILLAM · 13th January 2002

Thanks Eric I can now access my drives over the network.

However I stll can't use Remote Desktop.

If I try to connect from the laptop running Xp I grt thr Loging screen and now it comes up with 'The client could not connect , remote connection might not be enabled'

If I try to connect from my ME PC I get the login screen but then I get ' Unable to logi in becaues of account restrictions'

PAUL SHILLAM · 13th January 2002

In ME I have 'access Control' set to 'Share level access'
And in Passwords 'Remote Amin' I have 'Enable remote admnistration on this server' checked.

In XP System profiles , Remote I have 'Remote Desktop' checked to allow user to connect remoteley too this computer.

Thomas · 14th January 2002

Hi,

I read your message this after noon.

Follw the steps-

Step 1-
Install Remote Desktop(RD) on ME with the help of your XP installation CD.

Note:
There should be a user name and password in the ME machine that you use to log in.

Step 2-

On the XP machine create a user account exactly with the same name and password as that in Me.

Note-This is essential for the XP to know which users can connect and access resources on it. XP will not allow any users not in the local SAM database in a workgroup mode.This is the normal/default behaviour of XP.

Step 3
On the XP pro check if the RD is enabled by going to My computer-Right click -Properties-Remote- check the second box.

You will encounter a pop up message.

Click OK.

In the next box that appears - click ADD.
Note- basically this is where you are authorizing the remote users to connect to your computer.

Click on Advanced-
A list of existing names appear- select the user name you just created(also resident in Me)

Step 4

Log as that user in XP and share some files and folders. Normally the shares are as Admin share ie C$ and will be hidden. While sharing, click on New share, and give the share a name.

Step 5
Log with identical username and password in Me.

Step 6
Configure the RD by clicking on the Options button.

Step 7
Click connect.

Your RD should work fine now and you should be able to access all your files and folders created under that user.

NOTE
RD will not work under the following conditions-
Blank password
User name and password do not match that in the SAM database.
If the terminal services are stopped for some reason

You can get the XP on Me - but the other way is not possible because an essential service called terminal services that are responsible for sending the data accross are not available on Me.

Also note that all members of Administrators group will be able to access all the files and folders.

Tell us if this helped you.

Regards
Thomas MCSE MCT

**Scott Smith** · 14th January 2002

I didn't know Remote Desktop could be used on any machines other than XP machines. Hmmm... I have to go try this.. Maybe I can retire PC anywhere? I use RD to access my win2k server and honestly I dont remember how I set it up.
I have some win2k pro machines I access over the net with PC anywhere that I would like to use RD.
What port does RD use? I have to do some port fowarding to get through some firewalls.

Thomas · 14th January 2002

hi,

The RDP port is 3389.

You can RD XP Pro with XP Home
W2KP
Me
98/SE
95

It would be better if you uninstalled PC Anywhere.

If you want to RD over the web, my suggestion to you would be to use Remote Asistance and NOT Remote Desktop. The prime function of RD to my understanding is to be able to access the info on your computer sitting at a remote location. RD WILL NOT permit simutaneous usage by 2 people. When you RD the host will returnto welcome screen-if another user trys log in at this point on the host- your Remote connection will be cut off and the host will return to local mode. This is NOT a bug- but done by design to protect data security.

RA allows simultaneous connections. But RA can only be on XP machines. RA works like PCAnywhere.

Let us know if this worked.

have fun
Thomas MCSE MCT

**Scott Smith** · 15th January 2002

RD is what I want to use to admin some machines in other citys. I use PC anywhere now so Im just kicking tires at this time.
These remote machines run a dialer program called Spitfire. These machines have anywhere for 8 to 24 port modems to do telemarketing. (yea one of those things ugh!) I have to set these machines up daily and transfer files across the net.

Newt · 15th January 2002

One caution if you are accustomed to a remote control program like PCAW or NetOp. With them, you are seeing a shot of the same screen that is running on the remote PC. Do a thing to the remote pc and it is just like you did it from the kbd at the remote pc.

Terminal Services Client (which I understand RD and RA use) is not that way. Most times, no problems but you can occasionally get bitten. A couple of examples.

We run an app on several servers to monitor production - how many made, how much waste, etc. The servers controlling the monitoring aren't real close so we need to remote control them. New servers and my company hates to spend money so they said "no way we buy more NetOp licenses when you have a free program that will do the same". So I merrily went about doing this and that.

Got a message on first connect asking what screen resolution/size I wanted. Easier to work in a window so I choose 800x600 rather than the normal resolution at the server monitor. Oops, it reset the program there and wasn't nice about letting it get fixed later.

Did some work on the server and relaunched the monitoring app. Assumed it would display on the remote screen as well as on mine. Nope. User at the console tried to start it (not knowing already had and it was running in the background like it was a service). Boom. Program was unhappy and server gave the user one of those "I'm already running that program, Stupid" errors. User was way confused.

Also, as has been the case with every app Microsoft has added when there were already a bunch of commercial products available, it works but has a limited set of features. Won't compare to PCAW/NetOp/etc. If you only need the features available with RD/RA, it works great. Otherwise, you may still have to pay some $$, ££, €€.

Last point. I have used both PCAW and NetOp extensively. NetOp winds hands down. Faster, can do more stuff, etc.

PAUL SHILLAM · 15th January 2002

Thank-you for your very clear instruction Thomas, RD is working fine now pity you can't use it from XP to ME though as I will have to but another copy of XP Pro to do that, and it's not cheep.