Remote Desktop connects, then disconnects right away

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am having a strange issue here. It is on my LAN with a Windows XP SP2
machine that I have set up for RDP. The only firewall on my network is the
external hardware firewall and the Windows Firewall. Since this is on my
LAN, I doubt the issue is with the hardware firewall, and the windows
firewall is open to RDP. I can connect to some degree (my screen changes to
the normal rdp session with the toolbar at the top of the scren saying the IP
and stuff), but a split second later it comes up saying:

Your Remote Desktop session has ended, possibly for one of the following
reasons:
The administrator has ended the session.
An error occured while the connection was being established.
A network problem occured.

I have tried to enable logging to find an answer with the informtion in
KB894565 (http://support.microsoft.com/?kbid=894565), but there isn't any
referance to the login attempt.

I am completely open to any ideas/suggestions as this booger has me baffeld!
 
It could be the MTU issue. This search result may help,

Troubleshooting terminal server issues"The remote session was disconnected because another user has connected to the session" ... A: You need to install Remote Desktop ActiveX Control. ...
http://www.chicagotech.net/troubleshootingts.htm


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
I am having a strange issue here. It is on my LAN with a Windows XP SP2
machine that I have set up for RDP. The only firewall on my network is the
external hardware firewall and the Windows Firewall. Since this is on my
LAN, I doubt the issue is with the hardware firewall, and the windows
firewall is open to RDP. I can connect to some degree (my screen changes to
the normal rdp session with the toolbar at the top of the scren saying the IP
and stuff), but a split second later it comes up saying:

Your Remote Desktop session has ended, possibly for one of the following
reasons:
The administrator has ended the session.
An error occured while the connection was being established.
A network problem occured.

I have tried to enable logging to find an answer with the informtion in
KB894565 (http://support.microsoft.com/?kbid=894565), but there isn't any
referance to the login attempt.

I am completely open to any ideas/suggestions as this booger has me baffeld!
 
No such luck. I tried to update the NIC drivers. Then I tried to manually
set the MTU for the nic at 1460. still same issue. I know that the RDP
function of the client works... I have used it to connect to maybe 100 hosts.
But I cannot get this perticular host to stay connected. Please, thow me
any other ideas that you might have!
 
Oh, one other thing I forgot to note: The host machine connects to the
network shares and the internet without an issue. I have been using a VNC
program to remote into it and that works fine. Just the RDP.....
 
Kirk Christian said:
Oh, one other thing I forgot to note: The host machine connects to the
network shares and the internet without an issue. I have been using a VNC
program to remote into it and that works fine. Just the RDP.....
Click to expand...
 
Hey Kirk.

I've been having the exact same problem.

I have 2 desktops and a laptop.
From desktop A i can rdp with the laptop but not to desktop B.

Desktop B can also RDP with the laptop.
But not the other way around.
I cannot connect to desktop B from any other machine, and i get the same
error message you reported.

I was wondering if you've found any solutions to the problem.

I'm not an IT pro, but do you have IIS server running?
Did you upgrade your Windows Xp Home to windows Xp professional?

I tried connecting with telnet to desktop B on port 3389 (the one used by
RDP) and i get an even in Event Viewer > System as Follows

Event Type: Error
Event Source: TermDD
Event Category: None
Event ID: 50
Date: 20/03/2007
Time: 11:14:18
User: N/A
Computer: RG
Description:
The RDP protocol component X.224 detected an error in the protocol stream
and has disconnected the client.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 05 00 02 00 54 00 ......T.
0008: 00 00 00 00 32 00 0a c0 ....2..À
0010: 00 00 00 00 32 00 0a c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 0b 00 00 00 61 ....a

i'm just as baffled as you are. this was supposed to be simple.

please do let me know if you've made any progress.

Gaddy
 
--
MCP, MCDST, CompTia A+


Gaddy said:
Hey Kirk.

I've been having the exact same problem.

I have 2 desktops and a laptop.
From desktop A i can rdp with the laptop but not to desktop B.

Desktop B can also RDP with the laptop.
But not the other way around.
I cannot connect to desktop B from any other machine, and i get the same
error message you reported.

I was wondering if you've found any solutions to the problem.

I'm not an IT pro, but do you have IIS server running?
Did you upgrade your Windows Xp Home to windows Xp professional?

I tried connecting with telnet to desktop B on port 3389 (the one used by
RDP) and i get an even in Event Viewer > System as Follows

Event Type: Error
Event Source: TermDD
Event Category: None
Event ID: 50
Date: 20/03/2007
Time: 11:14:18
User: N/A
Computer: RG
Description:
The RDP protocol component X.224 detected an error in the protocol stream
and has disconnected the client.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 05 00 02 00 54 00 ......T.
0008: 00 00 00 00 32 00 0a c0 ....2..À
0010: 00 00 00 00 32 00 0a c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 0b 00 00 00 61 ....a

i'm just as baffled as you are. this was supposed to be simple.

please do let me know if you've made any progress.

Gaddy
Click to expand...
No, nothing special installed or configured. Like you said, "this was
supposed to be simple."

I did try enabling IIS in hopes that it would reconfigure Terminal Services,
but no such luck. I have not tried telnet, but I assume it would be the same
issue. I am leaning twords a faulty driver, possibly the one for
touch-screen, but do not have any hard evidence on the driver assumption.

This is not an upgrade; this is a flat OEM load. I wasn't the person who
set it up, so I don't have the specifics on the installation of Windows, but
the setup log shows no kind of errors or anything unusual.

What I understand is that it is making a connection, but something in the
Remote Desktop Protocol is crashing, causing an very quick disconnect. This
is why I believe it to be a driver issue. I did try to update all the
drivers that might be used by RDP (NIC, audio, video, etc) and they are all
for hardware that I am familiar with (Intel NIC, Intel Video, Realtek Audio,
etc.).

I just dunno.....
 
Back
Top