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

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


Date: Mon, 27 Dec 2004 18:09:49 -0500

Hi,

If I'm reading you correctly, then it sounds like you are trying to access
the Win98SE machine remotely - if so then you cannot do this. The machine
being accessed remotely must be the machine running WinXP Pro. The machine
doing the accessing can be any recent version of Windows.

-- 
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:EAE793FA-EE4F-4B33-8928-4CDA9A4767CC@microsoft.com...
> Thanks for your quick response. I'm still unable to get anything going. 
> You
> were indeed correct - I was referring to WIN98 SE, but my fingers refuse 
> pre
> 2k data.
> Scenario: Home PC =WIN98SE, to be left on and accessed. Lets call it
> "desktop". The laptop is the one that will be accessing the home "desktop"
> pc. Lets call it "notebook". They are part of a workgroup at home called
> "home".
> The computer name that goes in the desktop RDC box would be??? I have 
> tried
> both names. The drop down box shows the + home group but will not break 
> down
> any further. The "notebook" pc would contain the name ??? I tried the drop
> down box, a box opened and error message to the effect "it does not 
> contain
> any terminal servers". All that is essential to be typed in, then, is the
> computer and user name???  As one might not be part of a domain or have a
> logon password. Incidently, I am using a DLINK 624 wireless router. I have
> never had any problem with firewalls. I continue to avoid installing SPII. 
> I
> did once and it really wasnt pleasant.
> I could not see how to uninstall this program, though I didnt dig. I found
> one reference that advised to use the New Connection Wizard to set up a 
> VPN.
> I hadnt seen anything anywhere else, and my address is dynamic, so that 
> might
> be a problem.
> If this is Rick, I read your home page and you are very funny man.
> I'd appreciate any help or insight you provide. As Deniro said, " I know a
> thing or two about a thing or two" but this aint that.
>
> Thanks
>
> Dale
>
>
> "Rick "Nutcase" Rogers" wrote:
>
>> 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

  • Re: Down the MPD road
    ... Trying to get remote Windows users through securely to the Inside. ... >> Apparently PPTP actually puts the remote machine IN the target network. ... >> connections to the rest of the Internet are now coming from behind the ...
    (FreeBSD-Security)
  • Re: PPTP vpn- cant connect to printer.
    ... Check your network protocols.. ... Windows XP does not support NetBEUI ... over Remote Access connections, ... Remote Networking Technology Support Site - ...
    (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)
  • Re: Best solution for remote GUI access from Windows/Linux to Linux
    ... On Tue, 2005-10-11 at 15:52, Arthur Pemberton wrote: ... > easier done on Windows (which I may need when I am on a foriegn ... connections and have the least overhead on the server ... (probably not an issue unless you have a lot of remote ...
    (Fedora)
  • Re: /remote desktop control suddenly broken - critical
    ... The client computer may not be turned on. ... Remote Desktop connections may not be enabled on the client ... Verify that Remote Desktop is enabled on the computer you are ... connection from another computer on the Windows Small Business Server ...
    (microsoft.public.windows.server.sbs)