Solved

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

Posted on 2008-10-20
3
923 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

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

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.
Learn how to PXE Boot both BIOS & UEFI machines with DHCP Policies and Custom Vendor Classes
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

856 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