Solved

Remote Desktop Protocol Error between XP pro PC and NT Server 4.0

Posted on 2008-10-20
3
921 Views
Last Modified: 2013-12-21
Hi all.

I just upgraded  windows XP professional to Service pack 3
After doing this users who use Remote Desktop to access a Windows NT 4.0 server are now having difficulty
they get a popup error stating
"Because of  a protocol error, this session will be disconnected. Please try connecting to the remote computer again"
Users who are still running XP Pro with service pack 2 are not getting this error'

So i am thinking it is related to an upgrade to a remote desktop protocol

I am about ready to pull my hair out

Any help would be greatly appreciated

0
Comment
Question by:cdubbcisco
3 Comments
 
LVL 5

Accepted Solution

by:
micalkin earned 500 total points
ID: 22759518
according to the help on RDP:

To change authentication options, open Remote Desktop Connection, click Options, and then click the Advanced tab. If you're not sure which option to choose, ask your system administrator or the owner of the remote computer.

Remote computers that are running Windows Server 2003 with Service Pack 1 (SP1) or earlier operating systems cannot provide their identity for verification. If you know that the remote computer is running one of those operating systems, you can avoid authentication warnings by choosing Always connect, even if authentication fails, and then saving that change by clicking Save or Save As on the General tab.

The default option is "Always connect, even if authentication fails." To change it for future use, select the authentication level you want, and then, on the General tab, click Save or Save As to save your settings to an .rdp file. To connect to the same remote computer in the future, double-click the .rdp file.
0
 

Author Comment

by:cdubbcisco
ID: 22767147
i ended up just uninstalling service pack 3 and that fixed the error
0
 
LVL 28

Expert Comment

by:asavener
ID: 24186003
I realize this is an old thread, but :

Find an XP SP2 machine.

Copy MSTSC.exe and related DLL (mstsc??.dll, I forget the exact name) from c:\windows\system32\ to a network location.

Then run that executable from the XP SP3 machine when connecting to the NT 4 terminal server.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
How to record audio from input sources to your PC – connected devices, connected preamp to record vinyl discs, streaming media, that play through your audio card: Vista, Windows 7, Windows 8, Windows 8.1 and Windows 10 – both 32 bit & 64.
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question