Re: Remote Desktop authentication



Well, I am using Remote Desktop Connection to connect to my Terminal Server.
When Opening Remote Desktop Connection, I write the FQDN
(pd03.projdev.skanska.se) in the Computer field, then I switch to the tab
Security in the Remote Desktop Connection (the last tab or configuration
window). There you can choose the Authentication mothod to use when
connecting to the remote computer (in this case the terminal server). If I
choose Require authentication I can't connect to the terminal server.
Attempt- and No authentication results in the following message, and I have
to enter the username and password again.

The message is:
The identity of the remote computer cannot be determined because the
remote computer is not configured to support authentication.
Remote computer: pd03.projdev.skanska.se
The connection cannot proceed because authentication of the remote
computer is required.

Any idea how to solve this?
Regards Magnus


"Jeff Pitsch [MVP]" <jeff@xxxxxxxxxxxxxxxxx> wrote in message
news:#60rh2YLGHA.720@xxxxxxxxxxxxxxxxxxxxxxx
I'm sorry, I'm not sure what your referring to. Would you be more
specific
please.

Jeff Pitsch
Microsoft MVP - Terminal Services
http://www.sbcgatekeeper.com
Your Terminal Services Security Website

"Magnus Blomberg" <magnus.blomberg@xxxxxxxxxx> wrote in message
news:OBJlxvYLGHA.1532@xxxxxxxxxxxxxxxxxxxxxxx
Hi!

In Remote Desktop there is a tab called Security where you can choose No
authentication, Attempt authentication, and Require authentication.
What is the purpose of these?

Regards Magnus

"Jeff Pitsch [MVP]" <jeff@xxxxxxxxxxxxxxxxx> wrote in message
news:eCHd9nXLGHA.4060@xxxxxxxxxxxxxxxxxxxxxxx
There is no single sign on solution for RDP. outside of 3rd party
products
or configuring a RDP file for the specific clients.

Jeff Pitsch
Microsoft MVP - Terminal Services
http://www.sbcgatekeeper.com
Your Terminal Services Security Website

"Magnus Blomberg" <magnus.blomberg@xxxxxxxxxx> wrote in message
news:uHahqKWLGHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
Hello!

I have installed Terminal Services at my 2003 server, and am using
Remote
Desktop to connect to it.
I can't figure out how to enable the ability to use Authentication to
logon
automatically to the server. All users have to enter their passwords,
and
I
don't want that.
I also want all users to click the same rdp-file, so Windows
Authentication
should be the solution.

How to do it?
Regards Magnus










.



Relevant Pages

  • Re: Authentication event id 5722
    ... Have you considered using RWW for this remote user? ... need either a local workstation or a Terminal Server for him to connect to. ... After changing the password, however, an authentication is ... of times that I try connecting the laptop through VPN connection), ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop Connection
    ... There's probably a disconnected session hanging around. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... via Remote Desktop connection? ...
    (microsoft.public.windows.terminal_services)
  • Re: Easiest way to share existing files saved on SBS server with remote users?
    ... on a SBS machine to a server-less remote office? ... The best method is Terminal Server, no matter what else, it's the only ... The key reason for terminal server is the savings in support, security, ...
    (microsoft.public.windows.server.sbs)
  • Re: Getting rid of old, obsolete kernels
    ... > to login via terminal server, enter user/password, hard reset the ... LILO and make the system unrecoverable without a boot disk. ... You need a remote serial concentrator to do this effectively. ... Some of the higher end ones support SSH now, ...
    (comp.os.linux.setup)
  • Re: Error messages for remote desktop connection attempt
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... also.....but heres my event log error message. ... The Terminal Services service depends on the Net Logon service ... In Control Panel - System - Remote? ...
    (microsoft.public.windows.terminal_services)