General discussion

Locked

Remote Desktop connections disconnect

By ross.laing ·
I support a Network running windows 2000 Server Terminal Server and a host of Client OS's, all of which use Remote Desktop to access the server to run various apps. However they keep getting this error message - "Remote Desktop Disconnected because of a protocol error"
The only thing it says in Microsoft knowledge Base about this in the XP section is if it happens again contact your system administrator. I did find a fix for this but it only relates to Windows CE.
Please Help!!!!

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by scottsman In reply to Remote Desktop connection ...

I assume:

1. That the server is running in Application mode NOT admin mode (admin only allows 2 simultaneous connections)
2. Clients are 2k or XP
3. You have Terminal connection licesnes bought and placed into the server (2k had a built in license XP does not)

Is this new problem or have the Clients never connected?

If new problem check the terminal services manager and look for connections that are stale. Sometimes if users disconnect and you have not set the timeouts you can use up your licenses causing some clients to fail to connect.

Collapse -

by ross.laing In reply to

The Terminal server is running in App mode.
The clients are a mixture of OS, XP, 2K, NT4 Win 95. All have Remote desktop installed.
The clients get connected ok, but after a while get booted off with the afore mentioned error.
The Licenses are fine and there are no disconnected sessions.

Collapse -

by scottsman In reply to Remote Desktop connection ...

Sounds like a tough one. I found one other post with a similar issue. But no resolution. Could this be a domain issue? or perhaps there is a pattern in the application that is being accessed when the disconnect occurs?

I found the following kb article.
http://support.microsoft.com/?kbid=829485

The first line under symptoms sounded interesting. Although this probably would not apply.

Judgeing by your reponse You would have included any recent changes or patches to the server or the clients.

Did you try running a session Using IP instead of a DNS name and see if it disconnects still? (Unless of course you use IP to connect now)

Good luck with this one. I will ask around.

Collapse -

by ross.laing In reply to

Thanks,
All the users have a shortcut on their desktop for the TS connection, it uses IP address rather than DNS name. It does seem to only be within Sage that they have this problem, however i have also been hunting high and low on other tech forms and groups and have found no solutions. Other people only seem to have this problem when they are using a particular app, but there doesnt seem to be a pattern or a fix. I have logged a support call with Microsoft to stop my head exploding and will post the fix, IF THEY HAVE ONE!!!!

Collapse -

by scottsman In reply to Remote Desktop connection ...

A real quick thought here. Did you install terminal services in backward compatability mode?

If not try elevating a users rights so that they can modify the registry on the terminal server and see if that solves the problem.

It may be some little thing in the app that needs compatability mode on or higher user rights on the server.

Collapse -

by ross.laing In reply to

Will try this at some point, although the users are members of the domain admins group as they do need to be able to install automatic updates for Sage.

Collapse -

by lmayeda In reply to Remote Desktop connection ...

We've been running Terminal services for years and it appears that if a client is "idle" for x minutes, the connection will be dropped regardless of whether the setting on the local PC is set to NEVER sleep. Another tech once told me that if you get connected at a certain bandwidth and subsequently the bandwidth drops a certain increment, the terminal server will disconnect the session. I don't know what to believe and I really can't offer much help except to set a 10 minute timer and if the user hasn't "worked" on the session within that time period ... you're allowed to crack that whip. We're resigned to "live with it" ... but would surely appreciate an answer too.

Collapse -

by lou In reply to Remote Desktop connection ...

In the registry at HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server, create or edit the DWORD value of KeepAliveEnable and set it to 1. This will turn Keep Alives on. This will serve to stabilize the connection by sending 'heartbeat' packets to the client every so often. This will cause an idle connection to be probed every so often just to be sure that the connection is still alive and that the client is still listening on the other side. This will also help prevent disconnects by preventing network devices from killing off sockets that it assumes to be idle. Because terminal services is such a low bandwidth protocol, when a user is idle, no network activity will occur. Some network devices will interpret a connection that is in the idle state for an extended period of time to be a dead connection, and thus will terminate the socket. However, when the user comes out of the idle state, the terminal services client can no longer contact the terminal server because the socket is dead. By turning on Keep Alives, the connection will not appear idle, and therefore the network device will not attempt to terminate the socket.

Collapse -

by marc.decroos In reply to Remote Desktop connection ...

Hi,
I do not have an answer but the same question.
I just have a user that gets this error in a reproducable way. She is just opening an Excel and going to a specific Sheet and then the session gets disconnected. If I do the same on the same Terminal Server I do not get the error.
We have both XP and she is in the same site as the Terminal Server and I'm in a remote location so network delays are on my side ...
Very strange... the problem must be situated somewhere in teh bitmap cache or so because when She clicks that sheet there is maybe some graphical function unsupported ... to many colors ...
Hope this new info brings us all to a solution.
Kind regards,
Marc

Collapse -

by ross.laing In reply to

Poster rated this answer.

Back to Networks Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums