1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

How do I tell if my connection is encrypted?

Discussion in 'Windows Home Server' started by ToddAndMargo, Oct 11, 2009.

  1. ToddAndMargo

    ToddAndMargo Guest

    Hi All,

    This seems too easy. Click on my icon and over the
    Internet I am connected to my remote Terminal Server.
    It seems too easy from a security standpoint. How
    do I tell if my connection is encrypted?

    Many thanks,
    -T
     
  2. ToddAndMargo <ToddAndMargo@invalid.com> wrote on 12 okt 2009:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hi All,
    >
    > This seems too easy. Click on my icon and over the
    > Internet I am connected to my remote Terminal Server.
    > It seems too easy from a security standpoint. How
    > do I tell if my connection is encrypted?
    >
    > Many thanks,
    > -T<!--colorc--><!--/colorc-->

    You can check (and set) the security level and the encryption on the
    server, in rdp-tcp properties, on the "General" tab.

    816594 - HOW TO: Secure Communication Between a Client and Server
    with Terminal Services


    _________________________________________________________
    Vera Noest
    MCSE, CCEA, Microsoft MVP - Terminal Server
    TS troubleshooting:

    *----------- Please reply in newsgroup -------------*
     
  3. ToddAndMargo

    ToddAndMargo Guest

    Vera Noest [MVP] wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > ToddAndMargo <ToddAndMargo@invalid.com> wrote on 12 okt 2009:
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    >> Hi All,
    >>
    >> This seems too easy. Click on my icon and over the
    >> Internet I am connected to my remote Terminal Server.
    >> It seems too easy from a security standpoint. How
    >> do I tell if my connection is encrypted?
    >>
    >> Many thanks,
    >> -T<!--colorc--><!--/colorc-->
    >
    > You can check (and set) the security level and the encryption on the
    > server, in rdp-tcp properties, on the "General" tab.
    >
    > 816594 - HOW TO: Secure Communication Between a Client and Server
    > with Terminal Services
    > <!--colorc--><!--/colorc-->

    Hi Vera,

    Thank you for the link.

    In my "General" tab:
    Security layer: Negotiate
    Encryption Level: Client Compatible

    Does this mean I am always encrypted?

    Many thanks,
    -T
     
  4. ToddAndMargo

    ToddAndMargo Guest

    ToddAndMargo wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Vera Noest [MVP] wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
    >> ToddAndMargo <ToddAndMargo@invalid.com> wrote on 12 okt 2009:
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> Hi All,
    >>>
    >>> This seems too easy. Click on my icon and over the
    >>> Internet I am connected to my remote Terminal Server.
    >>> It seems too easy from a security standpoint. How
    >>> do I tell if my connection is encrypted?
    >>>
    >>> Many thanks,
    >>> -T<!--colorc--><!--/colorc-->
    >>
    >> You can check (and set) the security level and the encryption on the
    >> server, in rdp-tcp properties, on the "General" tab.
    >>
    >> 816594 - HOW TO: Secure Communication Between a Client and Server with
    >> Terminal Services
    >> <!--colorc--><!--/colorc-->
    >
    > Hi Vera,
    >
    > Thank you for the link.
    >
    > In my "General" tab:
    > Security layer: Negotiate
    > Encryption Level: Client Compatible
    >
    > Does this mean I am always encrypted?
    >
    > Many thanks,
    > -T<!--colorc--><!--/colorc-->

    My concern is that with "Security layer: Negotiate", a client
    could negotiate "none".

    -T
     
  5. ToddAndMargo <ToddAndMargo@invalid.com> wrote on 13 okt 2009:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > ToddAndMargo wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
    >> Vera Noest [MVP] wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> ToddAndMargo <ToddAndMargo@invalid.com> wrote on 12 okt 2009:
    >>>
    >>>> Hi All,
    >>>>
    >>>> This seems too easy. Click on my icon and over the
    >>>> Internet I am connected to my remote Terminal Server.
    >>>> It seems too easy from a security standpoint. How
    >>>> do I tell if my connection is encrypted?
    >>>>
    >>>> Many thanks,
    >>>> -T
    >>>
    >>> You can check (and set) the security level and the encryption
    >>> on the server, in rdp-tcp properties, on the "General" tab.
    >>>
    >>> 816594 - HOW TO: Secure Communication Between a Client and
    >>> Server with Terminal Services
    >>> <!--colorc--><!--/colorc-->
    >>
    >> Hi Vera,
    >>
    >> Thank you for the link.
    >>
    >> In my "General" tab:
    >> Security layer: Negotiate
    >> Encryption Level: Client Compatible
    >>
    >> Does this mean I am always encrypted?
    >>
    >> Many thanks,
    >> -T<!--colorc--><!--/colorc-->
    >
    > My concern is that with "Security layer: Negotiate", a client
    > could negotiate "none".
    >
    > -T<!--colorc--><!--/colorc-->

    Yes. The only thing that is guaranteed to be encrypted with your
    settings is the password, and you're open for man-in-the-middle
    attacks. Did you click on the "More information" link in the window
    where the settings are made? It leads to this page:



    which explains what you can and should do to improve security.


    _________________________________________________________
    Vera Noest
    MCSE, CCEA, Microsoft MVP - Terminal Server
    TS troubleshooting:

    *----------- Please reply in newsgroup -------------*
     
  6. ToddAndMargo

    ToddAndMargo Guest

    Vera Noest [MVP] wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro--><!--coloro:green--><span style="color:green <!--/coloro-->
    >> My concern is that with "Security layer: Negotiate", a client
    >> could negotiate "none".
    >>
    >> -T<!--colorc--><!--/colorc-->
    >
    > Yes. The only thing that is guaranteed to be encrypted with your
    > settings is the password, and you're open for man-in-the-middle
    > attacks. Did you click on the "More information" link in the window
    > where the settings are made? It leads to this page:
    >
    >
    >
    > which explains what you can and should do to improve security.<!--colorc--><!--/colorc-->

    Reading over that article, I am not finding any reference
    to whether a "none" connection is possible. Just that
    some are higher than others. What am I missing?

    -T
     
  7. ToddAndMargo <ToddAndMargo@invalid.com> wrote on 13 okt 2009 in
    microsoft.public.windows.terminal_services:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Vera Noest [MVP] wrote:
    > <!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> My concern is that with "Security layer: Negotiate", a client
    >>> could negotiate "none".
    >>>
    >>> -T<!--colorc--><!--/colorc-->
    >>
    >> Yes. The only thing that is guaranteed to be encrypted with
    >> your settings is the password, and you're open for
    >> man-in-the-middle attacks. Did you click on the "More
    >> information" link in the window where the settings are made? It
    >> leads to this page:
    >>
    >>
    >>
    >> which explains what you can and should do to improve security.<!--colorc--><!--/colorc-->
    >
    > Reading over that article, I am not finding any reference
    > to whether a "none" connection is possible. Just that
    > some are higher than others. What am I missing?<!--colorc--><!--/colorc-->

    "None" is the default. From that article:
    "By default, Terminal Server uses native RDP encryption and does
    not authenticate the server."

    and:

    "Set the Security layer to Negotiate. If you use this
    configuration, TLS authentication is only enabled if the client
    supports it."

    _________________________________________________________
    Vera Noest
    MCSE, CCEA, Microsoft MVP - Terminal Services
    RDS troubleshooting:
     
  8. ToddAndMargo

    ToddAndMargo Guest

    Vera Noest [MVP] wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > "None" is the default. From that article:
    > "By default, Terminal Server uses native RDP encryption and does
    > not authenticate the server."
    >
    > and:
    >
    > "Set the Security layer to Negotiate. If you use this
    > configuration, TLS authentication is only enabled if the client
    > supports it."<!--colorc--><!--/colorc-->

    With mostly XP clients, which setting would you use if you
    wanted to guaranty at least some encryption?

    Many thanks,
    -T
     
  9. ToddAndMargo <ToddAndMargo@invalid.com> wrote on 14 okt 2009 in
    microsoft.public.windows.terminal_services:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Vera Noest [MVP] wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
    > > "None" is the default. From that article:
    >> "By default, Terminal Server uses native RDP encryption and does
    >> not authenticate the server."
    >>
    >> and:
    >>
    >> "Set the Security layer to Negotiate. If you use this
    >> configuration, TLS authentication is only enabled if the client
    >> supports it."<!--colorc--><!--/colorc-->
    >
    > With mostly XP clients, which setting would you use if you
    > wanted to guaranty at least some encryption?
    >
    > Many thanks,<!--colorc--><!--/colorc-->

    Authentication and encryption are 2 different things.
    I would set the encryption level to high.
    If you also want server authentication, you'll need a certificate.

    _________________________________________________________
    Vera Noest
    MCSE, CCEA, Microsoft MVP - Terminal Services
    RDS troubleshooting:
     

Share This Page