RDP stopped working

[Frank]

For some reason, I can no longer connect to my domain controller using RDP. I
can do so to any other server.

From my workstation, if I attempt telnet <servername> 3389, I get no response.

From the domain controller, if I attempt telnet <localhost> 3389, I get the
response "...could not open connection to the host on port 3389. Connect
failed..."

Running netstat -a -o shows nothing using port 3389.

I've done nothing to cause this port to be blocked on 3389 on this server.

Anyone encounter this mystery?

Even better: anyone have a solution to the mystery?

Thanks!

 

[yifli]

Did you check the Windows Firewall?

Yifei

"Frank" wrote:

> For some reason, I can no longer connect to my domain controller using RDP. I
> can do so to any other server.
>
> From my workstation, if I attempt telnet <servername> 3389, I get no response.
>
> From the domain controller, if I attempt telnet <localhost> 3389, I get the
> response "...could not open connection to the host on port 3389. Connect
> failed..."
>
> Running netstat -a -o shows nothing using port 3389.
>
> I've done nothing to cause this port to be blocked on 3389 on this server.
>
> Anyone encounter this mystery?
>
> Even better: anyone have a solution to the mystery?
>
> Thanks!

 

[Frank]

Thanks for the quick response. Yes, Windows firewall is disabled on the
domain controller with the connection problem. It's also off on my
workstation.

"yifli" wrote:

>
> Did you check the Windows Firewall?
>
> Yifei
>
> "Frank" wrote:
>
> > For some reason, I can no longer connect to my domain controller using RDP. I
> > can do so to any other server.
> >
> > From my workstation, if I attempt telnet <servername> 3389, I get no response.
> >
> > From the domain controller, if I attempt telnet <localhost> 3389, I get the
> > response "...could not open connection to the host on port 3389. Connect
> > failed..."
> >
> > Running netstat -a -o shows nothing using port 3389.
> >
> > I've done nothing to cause this port to be blocked on 3389 on this server.
> >
> > Anyone encounter this mystery?
> >
> > Even better: anyone have a solution to the mystery?
> >
> > Thanks!

 

[yifli]

I think that's the problem. You can either open the Windows Firewall on
domain controllers and enable Remote Desktop in Exception List, or you can
run security configuration wizard on domain controllers to open the port 3389

Yifei

"Frank" wrote:

>
> Thanks for the quick response. Yes, Windows firewall is disabled on the
> domain controller with the connection problem. It's also off on my
> workstation.
>
> "yifli" wrote:
>
> >
> > Did you check the Windows Firewall?
> >
> > Yifei
> >
> > "Frank" wrote:
> >
> > > For some reason, I can no longer connect to my domain controller using RDP. I
> > > can do so to any other server.
> > >
> > > From my workstation, if I attempt telnet <servername> 3389, I get no response.
> > >
> > > From the domain controller, if I attempt telnet <localhost> 3389, I get the
> > > response "...could not open connection to the host on port 3389. Connect
> > > failed..."
> > >
> > > Running netstat -a -o shows nothing using port 3389.
> > >
> > > I've done nothing to cause this port to be blocked on 3389 on this server.
> > >
> > > Anyone encounter this mystery?
> > >
> > > Even better: anyone have a solution to the mystery?
> > >
> > > Thanks!

 

[Mathieu CHATEAU]

hello,
is HKLM\System\CCS\Control\Terminal Server\fDenyTSConnection
equal to 0 ?

that's strange the port is not even binded. Is the windows service started ?

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Frank" <Frank@discussions.microsoft.com> wrote in message
news:358751DD-A2F3-4630-A0FA-D5BFBCAAF5A3@microsoft.com...
>
> Thanks for the quick response. Yes, Windows firewall is disabled on the
> domain controller with the connection problem. It's also off on my
> workstation.
>
> "yifli" wrote:
>
>>
>> Did you check the Windows Firewall?
>>
>> Yifei
>>
>> "Frank" wrote:
>>
>> > For some reason, I can no longer connect to my domain controller using
>> > RDP. I
>> > can do so to any other server.
>> >
>> > From my workstation, if I attempt telnet <servername> 3389, I get no
>> > response.
>> >
>> > From the domain controller, if I attempt telnet <localhost> 3389, I get
>> > the
>> > response "...could not open connection to the host on port 3389.
>> > Connect
>> > failed..."
>> >
>> > Running netstat -a -o shows nothing using port 3389.
>> >
>> > I've done nothing to cause this port to be blocked on 3389 on this
>> > server.
>> >
>> > Anyone encounter this mystery?
>> >
>> > Even better: anyone have a solution to the mystery?
>> >
>> > Thanks!

 

[Frank]

Yes, Thanks. That key is set to 0. I saw that mentioned in earlier posts.
The terminal services on the domain controller are started.

"Mathieu CHATEAU" wrote:

> hello,
> is HKLM\System\CCS\Control\Terminal Server\fDenyTSConnection
> equal to 0 ?
>
> that's strange the port is not even binded. Is the windows service started ?
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "Frank" <Frank@discussions.microsoft.com> wrote in message
> news:358751DD-A2F3-4630-A0FA-D5BFBCAAF5A3@microsoft.com...
> >
> > Thanks for the quick response. Yes, Windows firewall is disabled on the
> > domain controller with the connection problem. It's also off on my
> > workstation.
> >
> > "yifli" wrote:
> >
> >>
> >> Did you check the Windows Firewall?
> >>
> >> Yifei
> >>
> >> "Frank" wrote:
> >>
> >> > For some reason, I can no longer connect to my domain controller using
> >> > RDP. I
> >> > can do so to any other server.
> >> >
> >> > From my workstation, if I attempt telnet <servername> 3389, I get no
> >> > response.
> >> >
> >> > From the domain controller, if I attempt telnet <localhost> 3389, I get
> >> > the
> >> > response "...could not open connection to the host on port 3389.
> >> > Connect
> >> > failed..."
> >> >
> >> > Running netstat -a -o shows nothing using port 3389.
> >> >
> >> > I've done nothing to cause this port to be blocked on 3389 on this
> >> > server.
> >> >
> >> > Anyone encounter this mystery?
> >> >
> >> > Even better: anyone have a solution to the mystery?
> >> >
> >> > Thanks!
>
>

 

[Mathieu CHATEAU]

does telnet mydc 3389 works (black screen) ?

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Frank" <Frank@discussions.microsoft.com> wrote in message
news:F695045A-9C7F-47D4-9C81-E42706E8021A@microsoft.com...
>
> Yes, Thanks. That key is set to 0. I saw that mentioned in earlier posts.
> The terminal services on the domain controller are started.
>
> "Mathieu CHATEAU" wrote:
>
>> hello,
>> is HKLM\System\CCS\Control\Terminal Server\fDenyTSConnection
>> equal to 0 ?
>>
>> that's strange the port is not even binded. Is the windows service
>> started ?
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>>
>>
>> "Frank" <Frank@discussions.microsoft.com> wrote in message
>> news:358751DD-A2F3-4630-A0FA-D5BFBCAAF5A3@microsoft.com...
>> >
>> > Thanks for the quick response. Yes, Windows firewall is disabled on the
>> > domain controller with the connection problem. It's also off on my
>> > workstation.
>> >
>> > "yifli" wrote:
>> >
>> >>
>> >> Did you check the Windows Firewall?
>> >>
>> >> Yifei
>> >>
>> >> "Frank" wrote:
>> >>
>> >> > For some reason, I can no longer connect to my domain controller
>> >> > using
>> >> > RDP. I
>> >> > can do so to any other server.
>> >> >
>> >> > From my workstation, if I attempt telnet <servername> 3389, I get no
>> >> > response.
>> >> >
>> >> > From the domain controller, if I attempt telnet <localhost> 3389, I
>> >> > get
>> >> > the
>> >> > response "...could not open connection to the host on port 3389.
>> >> > Connect
>> >> > failed..."
>> >> >
>> >> > Running netstat -a -o shows nothing using port 3389.
>> >> >
>> >> > I've done nothing to cause this port to be blocked on 3389 on this
>> >> > server.
>> >> >
>> >> > Anyone encounter this mystery?
>> >> >
>> >> > Even better: anyone have a solution to the mystery?
>> >> >
>> >> > Thanks!
>>
>>