encryption error in Remote Desktop

[Mike Downey]

I have a customer running Windows XP Pro with SP1 installed. In the past, I
was able to set up a Remote Desktop connection with no problems. However,
lately, I keep getting the following message: "Because of an error in data
encryption, this session will end. Please try connecting to the remote
computer again." This happens repeatedly when I try to connect.

One major change that I've made to the system is that I installed Office
2003 Professional. Unfortunately, I don't know if that was when the
problems started happening. I also used to use the Terminal Server client,
but now I'm using the Remote Desktop Connection v5.2.3790.0 client.
However, I'm able to connect successfully to about eight or 10 other XP or
2003 machines with that client.

Does anyone know what I should be looking at to fix this problem?

Thanks,
Mike

 

[Bill Sanderson]

Tell us about all devices in the path (as far as possible!)--i.e. you have a
machine, connected to the Internet by (what??)---<Internet>---(customer's
connection to the Internet--what devices?)--customer's XP machine.

If there are nat/router devices, particularly at the customer end, give
make/model, and, ideally, firmware versions, if possible.

 

[Mike Downey]

On my end, I have a Roadrunner cable connection and a Netgear FVS318 running
firmware v1.1. On the customer's end, it's also a Roadrunner cable
connection and there's a Linksys BEFSR11 with firmware v1.45.6 running NAT.
IPSec and PPTP Pass Through are both enabled. I have two other customers
with the same router on their end that I never have encryption issues with,
but I just confirmed the have firmware v1.44.2 and v1.45.7.

Here is what was fixed in v1.45.7. Maybe I should try upgrading to that on
the customer's end?

Current Firmware : Version 1.45.7
Product PartNo : BEFSR41 ver. 1 & ver. 2.x/BEFSR11/BEFSRU31

Release Notes
----------------------
Below is a list of enhancements made on the Router's firmware version
1.45.7:

1.Supports multi-L2TP-pass-through
2.Supports DHCP relay agent
3.Fixed fragmented packets arriving out of order.

 

[Bill Sanderson]

I don't have any clear picture to offer you about what will fix what.

Many people reporting this issue have Linksys BEFSR series routers on the
host end. (MANY people have Linksys BEFSR series routers.!)

Some respondents have reported a fix or a change in frequency of occurrence
with a firmware change--up or down. I don't have a picture of a particular
version which "fixes" the issue.

Keep the current version around if you update, just in case the change makes
it worse. At present, I don't have any clients using these routers--I've
had sites using BEFSR11's for years without seeing this, but I have seen it
with a single site using the 4-port version--but wasn't able to resolve it,
and no longer have access to it as a test case.

 

[Jeffrey Randow (MVP)]

Take a look at
http://www.dslreports.com/forum/remark,7704424~mode=flat

Some have reported that 1.44.2 works well...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Bill Sanderson]

I don't get a clear answer out of that thread. 1.44.2 seems good--if
needed, I think I can point folks to a linksys FTP site with that version on
it.

However, a good deal of the discussion seemed to center around MTU issues
which I find quite believable.

Anybody in this thread with the issue who has changed MTU settings, or
changed the type of service the router is connecting to?

 

[Mike Downey]

Just wanted to let everyone here know that upgrading the LinkSys router
firmware from 1.45.6 to 1.45.7 fixed the problem. That's probably why
1.45.6 wasn't around very long.

 

[Bill Sanderson]

Thanks, and happy to hear it. These issues can be resolved with expert
assistance via a network trace, but that takes an expert and some time.