Terminal Services over VPN - protocol error 1

[UniqueFD]

For a number of years I have been successfully using Remote Desktop on XP Pro clients to connect to a W2K Server running Terminal Services (with an NT4 domain controller). However, part of the LAN is an expensive Kilostream (Point-to-Point always on telephone) line connecting a branch 60 miles away and I am attempting to replace this with VPN.

The VPN seems to be working well. However, when using Terminal Services I am encountering the following error:

[blue]Because of a protocol error, this session will be disconnected, Please try connecting to the remote computer again.[/blue]

This error is intermittent - anything from a few seconds to a few minutes of service before the connection is lost - and I am drawing blanks trying to find the root of my problem. Initially I was receiving a similar message (but much less connection time) referring to an Encryption Error. However, reducing the Encryption level on Terminal services to 'LOW' cured that. With this one I'm stumped.

Microsoft, in their support articles, 'helpfully' suggest I contact the server administrator if this problem continues - problem is, that's me!

Any suggestions would be gratefully received.

Tony
___________________________________________________
Reckless words pierce like a sword,
but the tongue of the wise brings healing (Solomon)

 

[ascotta]

In the Citrix world we cann up the Time To Live parameters quite easily. The problem here is that both RDP and ICA need a robust network. Even using VPN you are subjected to the vagaries of the internet. As I said using RDP is not something I do too often and therfore do not know where to look, but I am sure if you upped your TTL then this would help it.

The other thing I have seen for this is offline caching of files. Have a look and make sure it is switched off. Unfortunately this is a per user setting.

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[UniqueFD]

Scott

Thanks for your suggestions. Taking them in turn:

I've found some registry changes on another site to adjust the TcpMaxDataRetransmissions from the default of 5, and a keepalive entry to stop inactive sessions from being prematurely terminated. Are either of these similar to the Time To Live parameters on Citrix?

I'm also trying a connection without bitmap caching - great thought. As I'm only looking at 8-10 users, I don't mind making changes per user.

Tony
___________________________________________________
Reckless words pierce like a sword,
but the tongue of the wise brings healing (Solomon)

 

[UniqueFD]

An update on this problem: I've employed the registry hacks and removed bitmap caching, and have achieved another slight improvement. I still encounter the same error, but the Terminal Services session can be OK for up to 15 minutes before dropping out. Still not a workable long-term solution yet.

Scott, a star for your suggestions - I sincerely appreciate your help.

If anyone else meantime can offer any alternative tweaks that might properly stabilise Terminal Services over VPN, or alternatives, I would be very grateful.

Tony
___________________________________________________
Reckless words pierce like a sword,
but the tongue of the wise brings healing (Solomon)