Re: Unable to successfully setu p and use .Remote Desktop Connection.

From: Rick \ (rick_at_mvps.org)
Date: 12/26/04 

Date: Sun, 26 Dec 2004 12:04:41 -0500

Hi Dale,

Your post was a bit confusing, but let's see...

>I haveWinXP PRO and WinXP SE OS's with Remote desktop installed

I am assuming from the rest of your pos that you really meant "I haveWinXP
PRO and Win98SE [there is no WinXP SE] OS's with Remote desktop installed
[on the Win98SE system]"

> Does Domain = Workgroup??? Does it need to be Addressed

No, they are two different things. A domain is generally used in a corporate
environment and allows for a network administrator to control the user
systems. A Workgroup is generally what a home user has when they have
several machines connected together, but each machine is individually
controlled.

> Does it require a password? I have not been using one
> is it the computer's passwords or one created for the program?

With the RD, you should only need the password for the user account that you
are logging into on the WinXP Pro machine. Keep in mind that you can install
the access files onto virtually any modern Windows system, but you can only
access a system with WinXP Pro installed with accounts properly activated
for remote access. To access Windows installations remotely on other
versions of Windows, you would need something like pcanywhere.

> Is the user name for the computer the one for the computer or the one it
> is logging onto?

It should be the username and password for the account on the WinXP Pro
machine that you are trying to remotely access. You may find that it helps
to leave that account logged on all the time, as I have run into trouble
when the account is logged off, including the error messages you are seeing.

> When I logged on to the Win XP PC, The message " The client could not
> connect to the remote computer. Remote connections might not be enabled or
> the computer might be too busy to accept new accept connections. It is
> also that network problems are preventing your connecting. Please try
> connecting again later. If the problem continues to occur, contact your
> administrator."

It could be several things. If the access is on your home LAN or workgroup,
then you may need to do as I stated above and leave that account logged on.
If you are outside of your local systems, such as accessing from a work
location, then you may need to have port 3389 opened for you at that
location - this is the port that RD uses. Same thing applies if the system
is behind a router, you may need to configure the router for port
forwarding. Some work locations may have this function blocked entirely, so
access from there may not be possible.

Hope some of this helps. Please feel free to clarify and ask folllow-up
questions. 

-- 
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org
"Dale" <Dale@discussions.microsoft.com> wrote in message 
news:5F7EFDAB-2DF6-4ACB-92AD-BB7B4AC64365@microsoft.com...
>I haveWinXP PRO and WinXP SE OS's with Remote desktop installed. I have yet
> to successfully log on to the RDC. When I complete the option section on 
> the
> Win 98 pc that supplies the desktop, I receive the message
> "The system could not log you on. Make sure your User Name and Domain are
> correct, then type your password again. Letters in Passwords must be typed
> using the correct case".
>
> When I logged on to the Win XP PC, The message " The client could not
> connect to the remote computer.
> Remote connections might not be enabled or the computer might be too busy 
> to
> accept new accept connections. It is also that network problems are
> preventing your connecting. Please try connecting again later. If the 
> problem
> continues to occur, contact your administrator.
> I went back and added passwords under users as administrator. I still had 
> no
> luck.
> My system has a Inspirion P4 laptop with win xp pro and a dlink card, as
> well as a pIII win98se with a nic both using a dling wireless router.
> Everything there works fine in terms of connections.
> I have reviewed numerous sites/printouts from various sources and as near 
> as
> I can tell, I cant find anything I am leaving out.
> A few additional questions I have that appear somewhat unclear to me:
> Does Domain = Workgroup??? Does it need to be Addressed
> Does it require a password? I have not been using one
> is it the computer's passwords or one created for the program?
> Is the user name for the computer the one for the computer or the one it 
> is
> logging onto?
> Thanks so much
> -- 
> Dale C.

Relevant Pages

  • Unable to successfully setu p and use .Remote Desktop Connection.
    ... I haveWinXP PRO and WinXP SE OS's with Remote desktop installed. ... to successfully log on to the RDC. ... Remote connections might not be enabled or the computer might be too busy to ... I went back and added passwords under users as administrator. ...
    (microsoft.public.windowsxp.help_and_support)
  • Remote Connection problem
    ... My machine at the office is Win XP Pro SP 1, and my machine at home is Win XP ... I went to control panel - System - Remote tab, ... "The client could not connect to the remote computer. ... Remote connections might not be enabled or the computer might be too busy to ...
    (microsoft.public.windowsxp.general)
  • Remote Desktop Connection on WinXP home - updated
    ... >or Pro and try to connect to my terminal server (which ... Remote connections might not be enabled at the remote ...
    (microsoft.public.windowsxp.work_remotely)
  • Remote Desktop Connection on new machines
    ... or Pro and try to connect to my terminal server (which ... The client could not establish a connection to the remote ... Remote connections might not be enabled at the remote ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Rmote Access problem
    ... The client could not connect to the remote computer. ... Remote connections ... Re-running CEICW on SBS server: ...
    (microsoft.public.windows.server.sbs)