Remote Desktop Service not behaving properly but no error

Yes I can telnet and so does portquery and telnet show connectivity is ok.
As a matter of fact as stated previously, after a reboot I am able to use
RDC, but it seems after a while the services is not behaving properly.

"Robert L. (MS-MVP)" wrote:

> Can you telnet port 3389?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> news:F12518CE-EA70-431D-AFF5-58C376613B42@microsoft.com...

> > Hi.
> > I have 2 XP SP2 clients trying to connect using RDP.
> > Connecting Client uses RDC v6 and/or 5.1
> > Serving client uses the default TermServices (5.1)
> >
> > RDC is enabled on serving client
> > Ports are open and listening, communication is ok
> >
> > When trying to remotely log in into serving client, nothing happens.
> > Hitting
> > connect does nothing and return to RDC connexion dialog without error
> > messages (nor visual or in the event log)
> >
> > I have checked settings for RDC and nothing seems wrong...
> >
> > fdenytsconnections is 0
> > TSEnabled is 0
> > TCP port 3389 (unknown service): LISTENING
> > portqry.exe -n servingclient -e 3389 -p TCP exits with return code
> > 0x00000000
> >
> > I have read that it maybe due to .NET 3 or SP3 but none of those are
> > installed...
> >
> > This said, rebooting seems to correct the error but then it will occur
> > again
> > later on.
> >
> > Any comment or help will be appreciated.

>
>

Any errors in the Event Viewer?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
news:1F80A80F-7AA5-43E3-A6DD-9931C274F800@microsoft.com...

> Yes I can telnet and so does portquery and telnet show connectivity is ok.
> As a matter of fact as stated previously, after a reboot I am able to use
> RDC, but it seems after a while the services is not behaving properly.
>
> "Robert L. (MS-MVP)" wrote:
>

>> Can you telnet port 3389?
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>> "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
>> news:F12518CE-EA70-431D-AFF5-58C376613B42@microsoft.com...

>> > Hi.
>> > I have 2 XP SP2 clients trying to connect using RDP.
>> > Connecting Client uses RDC v6 and/or 5.1
>> > Serving client uses the default TermServices (5.1)
>> >
>> > RDC is enabled on serving client
>> > Ports are open and listening, communication is ok
>> >
>> > When trying to remotely log in into serving client, nothing happens.
>> > Hitting
>> > connect does nothing and return to RDC connexion dialog without error
>> > messages (nor visual or in the event log)
>> >
>> > I have checked settings for RDC and nothing seems wrong...
>> >
>> > fdenytsconnections is 0
>> > TSEnabled is 0
>> > TCP port 3389 (unknown service): LISTENING
>> > portqry.exe -n servingclient -e 3389 -p TCP exits with return code
>> > 0x00000000
>> >
>> > I have read that it maybe due to .NET 3 or SP3 but none of those are
>> > installed...
>> >
>> > This said, rebooting seems to correct the error but then it will occur
>> > again
>> > later on.
>> >
>> > Any comment or help will be appreciated.

>>
>>

As stated previously, "dialog without error messages (nor visual or in the
event log) "..no error message in the event log of both machines.

"Robert L. (MS-MVP)" wrote:

> Any errors in the Event Viewer?
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> news:1F80A80F-7AA5-43E3-A6DD-9931C274F800@microsoft.com...

> > Yes I can telnet and so does portquery and telnet show connectivity is ok.
> > As a matter of fact as stated previously, after a reboot I am able to use
> > RDC, but it seems after a while the services is not behaving properly.
> >
> > "Robert L. (MS-MVP)" wrote:
> >

> >> Can you telnet port 3389?
> >>
> >> --
> >> Bob Lin, MS-MVP, MCSE & CNE
> >> Networking, Internet, Routing, VPN Troubleshooting on
> >> http://www.ChicagoTech.net
> >> How to Setup Windows, Network, VPN & Remote Access on
> >> http://www.HowToNetworking.com
> >> "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> >> news:F12518CE-EA70-431D-AFF5-58C376613B42@microsoft.com...
> >> > Hi.
> >> > I have 2 XP SP2 clients trying to connect using RDP.
> >> > Connecting Client uses RDC v6 and/or 5.1
> >> > Serving client uses the default TermServices (5.1)
> >> >
> >> > RDC is enabled on serving client
> >> > Ports are open and listening, communication is ok
> >> >
> >> > When trying to remotely log in into serving client, nothing happens.
> >> > Hitting
> >> > connect does nothing and return to RDC connexion dialog without error
> >> > messages (nor visual or in the event log)
> >> >
> >> > I have checked settings for RDC and nothing seems wrong...
> >> >
> >> > fdenytsconnections is 0
> >> > TSEnabled is 0
> >> > TCP port 3389 (unknown service): LISTENING
> >> > portqry.exe -n servingclient -e 3389 -p TCP exits with return code
> >> > 0x00000000
> >> >
> >> > I have read that it maybe due to .NET 3 or SP3 but none of those are
> >> > installed...
> >> >
> >> > This said, rebooting seems to correct the error but then it will occur
> >> > again
> >> > later on.
> >> >
> >> > Any comment or help will be appreciated.
> >>
> >>

>
>

I am having this same problem. i can telnet to 3389, but when trying to RDP
in it will not work. NO message, no events, no nothing. Appears to try for
a second or 2 then stops

"KitKatNeko" wrote:

> As stated previously, "dialog without error messages (nor visual or in the
> event log) "..no error message in the event log of both machines.
>
> "Robert L. (MS-MVP)" wrote:
>

> > Any errors in the Event Viewer?
> >
> > --
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on
> > http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on
> > http://www.HowToNetworking.com
> > "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> > news:1F80A80F-7AA5-43E3-A6DD-9931C274F800@microsoft.com...

> > > Yes I can telnet and so does portquery and telnet show connectivity is ok.
> > > As a matter of fact as stated previously, after a reboot I am able to use
> > > RDC, but it seems after a while the services is not behaving properly.
> > >
> > > "Robert L. (MS-MVP)" wrote:
> > >
> > >> Can you telnet port 3389?
> > >>
> > >> --
> > >> Bob Lin, MS-MVP, MCSE & CNE
> > >> Networking, Internet, Routing, VPN Troubleshooting on
> > >> http://www.ChicagoTech.net
> > >> How to Setup Windows, Network, VPN & Remote Access on
> > >> http://www.HowToNetworking.com
> > >> "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> > >> news:F12518CE-EA70-431D-AFF5-58C376613B42@microsoft.com...
> > >> > Hi.
> > >> > I have 2 XP SP2 clients trying to connect using RDP.
> > >> > Connecting Client uses RDC v6 and/or 5.1
> > >> > Serving client uses the default TermServices (5.1)
> > >> >
> > >> > RDC is enabled on serving client
> > >> > Ports are open and listening, communication is ok
> > >> >
> > >> > When trying to remotely log in into serving client, nothing happens.
> > >> > Hitting
> > >> > connect does nothing and return to RDC connexion dialog without error
> > >> > messages (nor visual or in the event log)
> > >> >
> > >> > I have checked settings for RDC and nothing seems wrong...
> > >> >
> > >> > fdenytsconnections is 0
> > >> > TSEnabled is 0
> > >> > TCP port 3389 (unknown service): LISTENING
> > >> > portqry.exe -n servingclient -e 3389 -p TCP exits with return code
> > >> > 0x00000000
> > >> >
> > >> > I have read that it maybe due to .NET 3 or SP3 but none of those are
> > >> > installed...
> > >> >
> > >> > This said, rebooting seems to correct the error but then it will occur
> > >> > again
> > >> > later on.
> > >> >
> > >> > Any comment or help will be appreciated.
> > >>
> > >>

> >
> >

I was experiancing a similar problem, although it was working once if I
rebooted the system. Having used the RDC for a few years without issue, the
suspect for the cause of the problem was the graphics driver as I had updated
it recently. After downgrading from Nvidia Forceware 178.24 to 93.71 the
issue appears to have resolved itself.

Nick

"morriz1" wrote:

> I am having this same problem. i can telnet to 3389, but when trying to RDP
> in it will not work. NO message, no events, no nothing. Appears to try for
> a second or 2 then stops
>
> "KitKatNeko" wrote:
>

> > As stated previously, "dialog without error messages (nor visual or in the
> > event log) "..no error message in the event log of both machines.
> >
> > "Robert L. (MS-MVP)" wrote:
> >

> > > Any errors in the Event Viewer?
> > >
> > > --
> > > Bob Lin, MS-MVP, MCSE & CNE
> > > Networking, Internet, Routing, VPN Troubleshooting on
> > > http://www.ChicagoTech.net
> > > How to Setup Windows, Network, VPN & Remote Access on
> > > http://www.HowToNetworking.com
> > > "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> > > news:1F80A80F-7AA5-43E3-A6DD-9931C274F800@microsoft.com...
> > > > Yes I can telnet and so does portquery and telnet show connectivity is ok.
> > > > As a matter of fact as stated previously, after a reboot I am able to use
> > > > RDC, but it seems after a while the services is not behaving properly.
> > > >
> > > > "Robert L. (MS-MVP)" wrote:
> > > >
> > > >> Can you telnet port 3389?
> > > >>
> > > >> --
> > > >> Bob Lin, MS-MVP, MCSE & CNE
> > > >> Networking, Internet, Routing, VPN Troubleshooting on
> > > >> http://www.ChicagoTech.net
> > > >> How to Setup Windows, Network, VPN & Remote Access on
> > > >> http://www.HowToNetworking.com
> > > >> "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> > > >> news:F12518CE-EA70-431D-AFF5-58C376613B42@microsoft.com...
> > > >> > Hi.
> > > >> > I have 2 XP SP2 clients trying to connect using RDP.
> > > >> > Connecting Client uses RDC v6 and/or 5.1
> > > >> > Serving client uses the default TermServices (5.1)
> > > >> >
> > > >> > RDC is enabled on serving client
> > > >> > Ports are open and listening, communication is ok
> > > >> >
> > > >> > When trying to remotely log in into serving client, nothing happens.
> > > >> > Hitting
> > > >> > connect does nothing and return to RDC connexion dialog without error
> > > >> > messages (nor visual or in the event log)
> > > >> >
> > > >> > I have checked settings for RDC and nothing seems wrong...
> > > >> >
> > > >> > fdenytsconnections is 0
> > > >> > TSEnabled is 0
> > > >> > TCP port 3389 (unknown service): LISTENING
> > > >> > portqry.exe -n servingclient -e 3389 -p TCP exits with return code
> > > >> > 0x00000000
> > > >> >
> > > >> > I have read that it maybe due to .NET 3 or SP3 but none of those are
> > > >> > installed...
> > > >> >
> > > >> > This said, rebooting seems to correct the error but then it will occur
> > > >> > again
> > > >> > later on.
> > > >> >
> > > >> > Any comment or help will be appreciated.
> > > >>
> > > >>
> > >
> > >

I have came across a couple of things that point to KB957097 causing problems
with TS. Might be something for you guys to check into.

"Chimpster" wrote:

> I was experiancing a similar problem, although it was working once if I
> rebooted the system. Having used the RDC for a few years without issue, the
> suspect for the cause of the problem was the graphics driver as I had updated
> it recently. After downgrading from Nvidia Forceware 178.24 to 93.71 the
> issue appears to have resolved itself.
>
> Nick
>
> "morriz1" wrote:
>

> > I am having this same problem. i can telnet to 3389, but when trying to RDP
> > in it will not work. NO message, no events, no nothing. Appears to try for
> > a second or 2 then stops
> >
> > "KitKatNeko" wrote:
> >

> > > As stated previously, "dialog without error messages (nor visual or in the
> > > event log) "..no error message in the event log of both machines.
> > >
> > > "Robert L. (MS-MVP)" wrote:
> > >
> > > > Any errors in the Event Viewer?
> > > >
> > > > --
> > > > Bob Lin, MS-MVP, MCSE & CNE
> > > > Networking, Internet, Routing, VPN Troubleshooting on
> > > > http://www.ChicagoTech.net
> > > > How to Setup Windows, Network, VPN & Remote Access on
> > > > http://www.HowToNetworking.com
> > > > "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> > > > news:1F80A80F-7AA5-43E3-A6DD-9931C274F800@microsoft.com...
> > > > > Yes I can telnet and so does portquery and telnet show connectivity is ok.
> > > > > As a matter of fact as stated previously, after a reboot I am able to use
> > > > > RDC, but it seems after a while the services is not behaving properly.
> > > > >
> > > > > "Robert L. (MS-MVP)" wrote:
> > > > >
> > > > >> Can you telnet port 3389?
> > > > >>
> > > > >> --
> > > > >> Bob Lin, MS-MVP, MCSE & CNE
> > > > >> Networking, Internet, Routing, VPN Troubleshooting on
> > > > >> http://www.ChicagoTech.net
> > > > >> How to Setup Windows, Network, VPN & Remote Access on
> > > > >> http://www.HowToNetworking.com
> > > > >> "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in message
> > > > >> news:F12518CE-EA70-431D-AFF5-58C376613B42@microsoft.com...
> > > > >> > Hi.
> > > > >> > I have 2 XP SP2 clients trying to connect using RDP.
> > > > >> > Connecting Client uses RDC v6 and/or 5.1
> > > > >> > Serving client uses the default TermServices (5.1)
> > > > >> >
> > > > >> > RDC is enabled on serving client
> > > > >> > Ports are open and listening, communication is ok
> > > > >> >
> > > > >> > When trying to remotely log in into serving client, nothing happens.
> > > > >> > Hitting
> > > > >> > connect does nothing and return to RDC connexion dialog without error
> > > > >> > messages (nor visual or in the event log)
> > > > >> >
> > > > >> > I have checked settings for RDC and nothing seems wrong...
> > > > >> >
> > > > >> > fdenytsconnections is 0
> > > > >> > TSEnabled is 0
> > > > >> > TCP port 3389 (unknown service): LISTENING
> > > > >> > portqry.exe -n servingclient -e 3389 -p TCP exits with return code
> > > > >> > 0x00000000
> > > > >> >
> > > > >> > I have read that it maybe due to .NET 3 or SP3 but none of those are
> > > > >> > installed...
> > > > >> >
> > > > >> > This said, rebooting seems to correct the error but then it will occur
> > > > >> > again
> > > > >> > later on.
> > > > >> >
> > > > >> > Any comment or help will be appreciated.
> > > > >>
> > > > >>
> > > >
> > > >

We had a post before: KB957097 update breaks TS
http://www.chicagotech.net/netforums...pic.php?t=5434

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"morriz1" <morriz1@discussions.microsoft.com> wrote in message
news9E43065-705B-4D4F-ABF1-8A7DE43AE29A@microsoft.com...

>I have came across a couple of things that point to KB957097 causing
>problems
> with TS. Might be something for you guys to check into.
>
> "Chimpster" wrote:
>

>> I was experiancing a similar problem, although it was working once if I
>> rebooted the system. Having used the RDC for a few years without issue,
>> the
>> suspect for the cause of the problem was the graphics driver as I had
>> updated
>> it recently. After downgrading from Nvidia Forceware 178.24 to 93.71 the
>> issue appears to have resolved itself.
>>
>> Nick
>>
>> "morriz1" wrote:
>>

>> > I am having this same problem. i can telnet to 3389, but when trying
>> > to RDP
>> > in it will not work. NO message, no events, no nothing. Appears to
>> > try for
>> > a second or 2 then stops
>> >
>> > "KitKatNeko" wrote:
>> >
>> > > As stated previously, "dialog without error messages (nor visual or
>> > > in the
>> > > event log) "..no error message in the event log of both machines.
>> > >
>> > > "Robert L. (MS-MVP)" wrote:
>> > >
>> > > > Any errors in the Event Viewer?
>> > > >
>> > > > --
>> > > > Bob Lin, MS-MVP, MCSE & CNE
>> > > > Networking, Internet, Routing, VPN Troubleshooting on
>> > > > http://www.ChicagoTech.net
>> > > > How to Setup Windows, Network, VPN & Remote Access on
>> > > > http://www.HowToNetworking.com
>> > > > "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in
>> > > > message
>> > > > news:1F80A80F-7AA5-43E3-A6DD-9931C274F800@microsoft.com...
>> > > > > Yes I can telnet and so does portquery and telnet show
>> > > > > connectivity is ok.
>> > > > > As a matter of fact as stated previously, after a reboot I am
>> > > > > able to use
>> > > > > RDC, but it seems after a while the services is not behaving
>> > > > > properly.
>> > > > >
>> > > > > "Robert L. (MS-MVP)" wrote:
>> > > > >
>> > > > >> Can you telnet port 3389?
>> > > > >>
>> > > > >> --
>> > > > >> Bob Lin, MS-MVP, MCSE & CNE
>> > > > >> Networking, Internet, Routing, VPN Troubleshooting on
>> > > > >> http://www.ChicagoTech.net
>> > > > >> How to Setup Windows, Network, VPN & Remote Access on
>> > > > >> http://www.HowToNetworking.com
>> > > > >> "KitKatNeko" <KitKatNeko@discussions.microsoft.com> wrote in
>> > > > >> message
>> > > > >> news:F12518CE-EA70-431D-AFF5-58C376613B42@microsoft.com...
>> > > > >> > Hi.
>> > > > >> > I have 2 XP SP2 clients trying to connect using RDP.
>> > > > >> > Connecting Client uses RDC v6 and/or 5.1
>> > > > >> > Serving client uses the default TermServices (5.1)
>> > > > >> >
>> > > > >> > RDC is enabled on serving client
>> > > > >> > Ports are open and listening, communication is ok
>> > > > >> >
>> > > > >> > When trying to remotely log in into serving client, nothing
>> > > > >> > happens.
>> > > > >> > Hitting
>> > > > >> > connect does nothing and return to RDC connexion dialog
>> > > > >> > without error
>> > > > >> > messages (nor visual or in the event log)
>> > > > >> >
>> > > > >> > I have checked settings for RDC and nothing seems wrong...
>> > > > >> >
>> > > > >> > fdenytsconnections is 0
>> > > > >> > TSEnabled is 0
>> > > > >> > TCP port 3389 (unknown service): LISTENING
>> > > > >> > portqry.exe -n servingclient -e 3389 -p TCP exits with return
>> > > > >> > code
>> > > > >> > 0x00000000
>> > > > >> >
>> > > > >> > I have read that it maybe due to .NET 3 or SP3 but none of
>> > > > >> > those are
>> > > > >> > installed...
>> > > > >> >
>> > > > >> > This said, rebooting seems to correct the error but then it
>> > > > >> > will occur
>> > > > >> > again
>> > > > >> > later on.
>> > > > >> >
>> > > > >> > Any comment or help will be appreciated.
>> > > > >>
>> > > > >>
>> > > >
>> > > >

I, too, am having a similar problem. I have two XP computers (SP2 and
otherwise fully patched) on the network and I access the second one
regularly using RDC. This worked fine under RDC 5.x and 6.0.1000.
However, recently it became problematic. I've tried the suggestions
here to no success (yes, I can telnet to the port and ping the
machine). I, too, get no event viewer log entries, but I do get an
error message in the client. Below I describe the various symptomatic
results.

Even after a reboot of the REMOTE computer, I try to connect to it,
but it generally won't connect. Sometimes it will. After I login to
the REMOTE computer using the login name I connect with remotely, then
I can get the login box. Maybe. Then it may work for awhile. Or it may
not.

Every time I connect, I get the black screen first. When it works,
after a few seconds, I'll get the login screen. When it doesn't I get
this dialog box:

- - Remote Desktop Disconnected - -
Your Remote Desktop session has ended.
The connection to the remote computer was lost, possibly due to
network connectivity problems. Try connecting to the remote computer
again. If the problem continues, contact your network administrator or
technical support. (buttons: OK, Help)

I also sometimes get a message that it's trying to reconnect and it's
always attempt #1 of 20.

I've tried entering my password before connecting and waiting to enter
it after connecting. That doesn't seem to matter.

A reboot of REMOTE "fixes" the problem temporarily. Usually. It
appears to connect and try, but then times out or something.

If I connect without specify the password up front, I do connect to
the computer and it gives me the login box. I can even see it begin to
draw the screen. But before the desktop is fully engaged, usually
before I see the white background of a window, it fails and starts
again.

It may have something to do with the screensaver timeout maybe because
it seems to only happen after a long time left connected and letting
my LOCAL computer go to screen-saver. Interestingly, too, if I then go
to the REMOTE machine and try to logon locally (using the welcome
screen -- the one that lists all the local users) it never actually
logs in but rather loops back around to the welcome screen. I even
tried logging in this way once about 50 times to no success. The only
way to "fix" this is to reboot the computer from the welcome screen
(terminating any open apps, etc).

I've tried using both full screen mode as well as non-full screen
mode, but it doesn't seem to matter.

I've turned off firewalls and anti-virus for testing purposes but that
doesn't seem to affect the results. Also, I've not changed firewall
nor anti-virus software (Comodo and Avast, currently) which was in use
before this all started.

Started with 6.0.6000, updated to 6.1 (which shows as 6.0.6001). I did
have the settings to a modem connection and changed it to a LAN
connection, but that's only to control the amount of data passed.
Network traffic is minimal, connected via Intel 510T switch (yeah,
old, but a workhorse).

Still looking for a solution that doesn't require me to walk to the
far end of the building to access the computer I used to access
remotely quite easily for days/weeks on end without reboot needed.
Sigh.

Thanks,

Mark

On Mon, 1 Dec 2008 09:31:00 -0800, KitKatNeko
<KitKatNeko@discussions.microsoft.com> wrote:

>I have 2 XP SP2 clients trying to connect using RDP.
>Connecting Client uses RDC v6 and/or 5.1
>Serving client uses the default TermServices (5.1)
>
>RDC is enabled on serving client
>Ports are open and listening, communication is ok
>
>When trying to remotely log in into serving client, nothing happens. Hitting
>connect does nothing and return to RDC connexion dialog without error
>messages (nor visual or in the event log)
>
>I have checked settings for RDC and nothing seems wrong...
>
>fdenytsconnections is 0
>TSEnabled is 0
>TCP port 3389 (unknown service): LISTENING
>portqry.exe -n servingclient -e 3389 -p TCP exits with return code 0x00000000
>
>I have read that it maybe due to .NET 3 or SP3 but none of those are
>installed...
>
>This said, rebooting seems to correct the error but then it will occur again
>later on.
>
>Any comment or help will be appreciated.