rdp fips problem

[Jon]

recently, i am not able to login into our server through my xp sp2 machine
via remote desktop.

event log shows the following error:

The RDP protocol component "DATA ENCRYPTION" detected an error in the
protocol stream and has disconnected the client.

i traced this back to the terminal services configuration snap-in and the
fips compliant, encryption level is selected and can not be changed. (greyed
out)

i tried deleting the connection and creating a new one, while making sure to
select client compatible encryption but the setting never stays and ends up
going right back to fips level.

this is the only server i have this problem with and it just randomly
started. however, i can piggy back off of another server to get to the
problem one but it will not work directly through remote desktop from any
workstations, only sp1 2k3 machines. all other servers are configured using
the client compatible option and all work fine except for this one.

[Vera Noest [MVP]]

Have you checked your Group Policy? Settings there override the
settings in TS configuration.

Check the info here:

Configuring authentication and encryption
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/lib
rary/ServerHelp/1b393752-f52d-46de-99e7-b39db35e5569.mspx

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

Post by Jon
recently, i am not able to login into our server through my xp
sp2 machine via remote desktop.
The RDP protocol component "DATA ENCRYPTION" detected an error
in the protocol stream and has disconnected the client.
i traced this back to the terminal services configuration
snap-in and the fips compliant, encryption level is selected and
can not be changed. (greyed out)
i tried deleting the connection and creating a new one, while
making sure to select client compatible encryption but the
setting never stays and ends up going right back to fips level.
this is the only server i have this problem with and it just
randomly started. however, i can piggy back off of another
server to get to the problem one but it will not work directly
through remote desktop from any workstations, only sp1 2k3
machines. all other servers are configured using the client
compatible option and all work fine except for this one.

[jon]

we dont have any group policy set up differently on any of our servers, other
than the base install's.

i checked just in case and the settings mirror the other servers that i can
connect to.

Post by Vera Noest [MVP]
Have you checked your Group Policy? Settings there override the
settings in TS configuration.
Configuring authentication and encryption
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/lib
rary/ServerHelp/1b393752-f52d-46de-99e7-b39db35e5569.mspx
--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

Post by Jon
recently, i am not able to login into our server through my xp
sp2 machine via remote desktop.
The RDP protocol component "DATA ENCRYPTION" detected an error
in the protocol stream and has disconnected the client.
i traced this back to the terminal services configuration
snap-in and the fips compliant, encryption level is selected and
can not be changed. (greyed out)
i tried deleting the connection and creating a new one, while
making sure to select client compatible encryption but the
setting never stays and ends up going right back to fips level.
this is the only server i have this problem with and it just
randomly started. however, i can piggy back off of another
server to get to the problem one but it will not work directly
through remote desktop from any workstations, only sp1 2k3
machines. all other servers are configured using the client
compatible option and all work fine except for this one.

[Vera Noest [MVP]]

Mmmm, strange.

You might want to look at this article, because it is about the
exact error that you receive at the client. But I'm not sure at all
if it will solve your problem, since the main problem seems to be
the FIPS encryption level.

323497 - Error Message: The RDP Protocol Component "DATA
ENCRYPTION" Detected an Error...
http://support.microsoft.com/?kbid=323497

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

Post by jon
we dont have any group policy set up differently on any of our
servers, other than the base install's.
i checked just in case and the settings mirror the other servers
that i can connect to.

Post by Vera Noest [MVP]
Have you checked your Group Policy? Settings there override the
settings in TS configuration.
Configuring authentication and encryption
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/l
ib rary/ServerHelp/1b393752-f52d-46de-99e7-b39db35e5569.mspx
--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

Post by Jon
recently, i am not able to login into our server through my
xp sp2 machine via remote desktop.
The RDP protocol component "DATA ENCRYPTION" detected an
error in the protocol stream and has disconnected the client.
i traced this back to the terminal services configuration
snap-in and the fips compliant, encryption level is selected
and can not be changed. (greyed out)
i tried deleting the connection and creating a new one, while
making sure to select client compatible encryption but the
setting never stays and ends up going right back to fips
level.
this is the only server i have this problem with and it just
randomly started. however, i can piggy back off of another
server to get to the problem one but it will not work
directly through remote desktop from any workstations, only
sp1 2k3 machines. all other servers are configured using the
client compatible option and all work fine except for this
one.

[jon]

i fixed it, turns out the fips encryption was set to enabled for whatever
reason under computer configuration.

Post by Vera Noest [MVP]
Mmmm, strange.
You might want to look at this article, because it is about the
exact error that you receive at the client. But I'm not sure at all
if it will solve your problem, since the main problem seems to be
the FIPS encryption level.
323497 - Error Message: The RDP Protocol Component "DATA
ENCRYPTION" Detected an Error...
http://support.microsoft.com/?kbid=323497
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

Post by jon
we dont have any group policy set up differently on any of our
servers, other than the base install's.
i checked just in case and the settings mirror the other servers
that i can connect to.

Post by Vera Noest [MVP]
Have you checked your Group Policy? Settings there override the
settings in TS configuration.
Configuring authentication and encryption
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/l
ib rary/ServerHelp/1b393752-f52d-46de-99e7-b39db35e5569.mspx
--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

Post by Jon
recently, i am not able to login into our server through my
xp sp2 machine via remote desktop.
The RDP protocol component "DATA ENCRYPTION" detected an
error in the protocol stream and has disconnected the client.
i traced this back to the terminal services configuration
snap-in and the fips compliant, encryption level is selected
and can not be changed. (greyed out)
i tried deleting the connection and creating a new one, while
making sure to select client compatible encryption but the
setting never stays and ends up going right back to fips
level.
this is the only server i have this problem with and it just
randomly started. however, i can piggy back off of another
server to get to the problem one but it will not work
directly through remote desktop from any workstations, only
sp1 2k3 machines. all other servers are configured using the
client compatible option and all work fine except for this
one.

[Vera Noest [MVP]]

In the GPO, you mean? OK, glad that it's solved.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

Post by jon
i fixed it, turns out the fips encryption was set to enabled for
whatever reason under computer configuration.

Post by Vera Noest [MVP]
Mmmm, strange.
You might want to look at this article, because it is about the
exact error that you receive at the client. But I'm not sure at
all if it will solve your problem, since the main problem seems
to be the FIPS encryption level.
323497 - Error Message: The RDP Protocol Component "DATA
ENCRYPTION" Detected an Error...
http://support.microsoft.com/?kbid=323497
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

Post by jon
we dont have any group policy set up differently on any of
our servers, other than the base install's.
i checked just in case and the settings mirror the other
servers that i can connect to.

Post by Vera Noest [MVP]
Have you checked your Group Policy? Settings there override
the settings in TS configuration.
Configuring authentication and encryption
http://www.microsoft.com/technet/prodtechnol/windowsserver200
3/l ib
rary/ServerHelp/1b393752-f52d-46de-99e7-b39db35e5569.mspx
--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

Post by Jon
recently, i am not able to login into our server through
my xp sp2 machine via remote desktop.
The RDP protocol component "DATA ENCRYPTION" detected an
error in the protocol stream and has disconnected the
client.
i traced this back to the terminal services configuration
snap-in and the fips compliant, encryption level is
selected and can not be changed. (greyed out)
i tried deleting the connection and creating a new one,
while making sure to select client compatible encryption
but the setting never stays and ends up going right back
to fips level.
this is the only server i have this problem with and it
just randomly started. however, i can piggy back off of
another server to get to the problem one but it will not
work directly through remote desktop from any
workstations, only sp1 2k3 machines. all other servers
are configured using the client compatible option and all
work fine except for this one.