Re: Unable to connect to 2K3 Server with RDP 6

Tech-Archive recommends: Fix windows errors by optimizing your registry

Okay, first off, assuming what you typed below is not a typo, you are using the wrong slash marking. It should be:
Domain\Username
not
Domain/Username

Second, I'm assuming that this is not the administrator account for the domain, just the machine you are logging into. RDP 6.0 assumes the domain is the same as the client machine's unless specified otherwise. Thus, when you give a user ID of administrator, that is interpreted as:

DomainOfClient\administrator

as opposed to the more likely option:

ShortNameOfRemoteComputer\administrator

For example, lets say I'm on the Foo domain, connecting to a machine named Bar, using the local Administrator account. If I just enter Administrator, it will try to connect as Foo\Administrator, which doesn't exist. I'd need to specifically type Bar\Administrator in the username field.

You don't actually need the fully qualified domain name, but the fully qualified machine name as the connection target is a good idea.

So instead of:
Computer: bar
User name: administrator

I'd do:
Computer: bar.foo.mycompany.com (or whatever the full name of your computer is)
User name: bar\Administrator

Try using the correct domain syntax and see if that fixes the problem.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"Eric T." <EricT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:A8769419-6BDC-4231-8D85-9C0B67CBDA82@xxxxxxxxxxxxxxxx
Thanks Josh, here's the info:
The client and the server are on the same domain. This is a single domain
shop.
The client is XP w/sp2 and the server is Win2k3 w/sp1, both 32-bit.
I have been using just a short domain name not the FQDN. But, I did just
try that and still no dice.
For my credentials, I have been using "administrator". I also tried
domain/username and it did not work either.

Thank you!

--
Eric Townsend
Spokane Public Libraries
IT Specialist


"Josh Rosenberg [MSFT]" wrote:

Can you give me some additional information to help pin down the source of
your problem?

Specifically:
1. Which client OS are you using? Win2000, WinXP, or WS03 and are you using
a 32 bit or 64 OS?
2. What domain or workgroup is your machine joined to?
3. What domain or workgroup is the server joined to?
4. Are you providing the fully qualified domain name (FQDN) for the server,
or an abbreviated name? (FQDN would be "mymachine.mybranch.mycompany.com",
vs. just "mymachine")
5. How are you entering your credentials? The exact format if possible,
though you can use "myusername" in place of your real user name to avoid
posting your credentials in a public forum.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"Eric T." <EricT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C69BA08F-A81E-4008-8DE1-2BD0A11B3727@xxxxxxxxxxxxxxxx
> Using RDP 5, I was able to connect just fine to our Windows 2003 > Servers
> (SP1), now, with RDP 6, I can no longer connect. I am prompted to > enter
> my
> login, but am met with the message:
> "Remote Desktop Disconnected.
> This computer can't connect to the remote computer. Try connecting > again.
> If the problem continues, contact the owner of the remote computer or > your
> network administrator".
>
> If I revert to RDP 5, I am back in business. Upgrade to 6 and unable > to
> connect again.
> Any help would be appreciated.
> Thanks!
> -- > Eric


.

Relevant Pages

  • Re: RDP limited but RWW just fine
    ... administrative access to the server for the purpose of server management, ... RDP client) to get to session 0. ... admin rights, 1 with poweruser, and the rest ... I use a domain administrator account to log into the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: RDP
    ... the server through sbs vpn and attempts to connect to his desktop ... can you RDP to his desktop from your own? ... The Client could not establis a connection to the remote computer. ...
    (microsoft.public.windows.server.sbs)
  • Sometimes I cannot access through RDP
    ... Sometimes I cannot access a Windows Server 2003 computer through RDP ... "This computer can't connect to the remote computer ... The only thing I can do is reboot the server using a command line program ...
    (microsoft.public.windows.terminal_services)
  • Sometimes I cannot access through RDP
    ... Sometimes I cannot access a Windows Server 2003 computer through RDP ... "This computer can't connect to the remote computer ... The only thing I can do is reboot the server using a command line program ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Best Practices for securing RDC???
    ... Personally if I use RDP to access remote server over internet I use regular ... Once I am on server I use RDP to connect to internal servers using ... to administrator to remove any access tools using group or local policy... ...
    (microsoft.public.windowsxp.security_admin)