Re: Cannot connect to domain controller via Terminal Services

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks again for your help Vera

I took a look at the registry, however there were no entries in there for
the X509 certificate or the X509 Certificate ID. The values that were
present were:

Certificate
fInternetConnector
UserLicenseServer

I thought that before I tried deleting the Certificate value I would post
here again and make sure it would still be the correct course of action.
Could this entry still be contributing to the problem even if the X509
certificate and certificate id values are not present?

thanks


"Vera Noest [MVP]" wrote:

OK, you'll have to delete some certificates from the server.
Documented here:

323497 - The RDP Protocol Component "DATA ENCRYPTION" Detected an
Error..." error message
http://support.microsoft.com/?kbid=323497
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?REI1NTE4NQ==?= <DB55185@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 18 jun 2007 in microsoft.public.windows.terminal_services:

Hi Vera,

The only error message that shows up in the Eventlog is EventID
50

http://www.eventid.net/display.asp?eventid=50&eventno=606&source=
TermDD&phase=1

Protocol Component name is DATA ENCRYPTION.

Thanks so much :)



"Vera Noest [MVP]" wrote:

Any errors or warnings in the eventLog of the server when you
try to connect?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?REI1NTE4NQ==?= <DB55185@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 14 jun 2007 in
microsoft.public.windows.terminal_services:

It used to work, but n for some reason we are unable to
connect to our WIndows2000 domain controller via Remote
Desktop or Terminal Services manager. Happens wether we are
inside or outside of our network. DNS is fine, and I even
tried typing in the server IP address instead of the server
name. Remote Desktop and TS Manager in our overall
environment is working fine and
I can connect to all other servers in our network. Except
for this one
particular server.

When trying to connect, I get an error message saying that:

1) Remote Connections may not be enabled on the server-they
are, I checked

2) Maximum connections have been established- I even
restarted the DC to clear connections.

3) A network error may have occured-Server is up and running
and connected to the network. Again, I restarted it over the
weekend.


Iv'e tried everything but reinstalling TS. I can ping the
server, but when trying to telnet on 3389 all I get is a
hanging cursor. I even checked the registry value
TSEnabled=1 and it was in fact set correctly.

Any help or new ideas would be appreciated. I have been
stumped on this one for weeks now.

thanks

.

Relevant Pages

  • RE: SSL for Exchange stops WSUS
    ... detect your current network configuration settings or you never run CEICW ... configuring ISA Server 2000 as a gateway server, firewall, and web caching ... This newsgroup only focuses on SBS technical issues. ... How you added a certificate to the default web site? ...
    (microsoft.public.windows.server.sbs)
  • Re: Huge problem; new to this job
    ... our entire network went down. ... We have 2 offices and 1 server. ... over IPSec require the installation of a machine certificate, ... connection to provide connectivity between the two offices (across the ...
    (microsoft.public.windows.server.networking)
  • RPC over HTTP, Microsoft solution
    ... Exchange Server 2003 RPC over HTTP Deployment Scenarios ... Place a check in the box next to 'Certificate Services' and click 'Yes' ...
    (microsoft.public.exchange.setup)
  • Re: OWA 2003 w/ Smart Card Authentication.
    ... Exchange 2003 server via ActivSync. ... the IIS certificate. ... Whether or not authentication will succeed is completely dictated by ... Server's SSL certificate must be configured on root of v-server via ...
    (microsoft.public.exchange.connectivity)
  • RE: Two domains question
    ... internal network resources in your home network. ... On the SBS 2003 Server open the Server Management console. ... Click the "Connect to the Internet" link. ... On the "Web Server Certificate" page, choose to create a new Web server ...
    (microsoft.public.windows.server.sbs)