Remote Desktop Disconnected

Has anyone had this error and found a solution? Can't
find anything in the knowledge base regarding this.

As soon as I click "Connect" using Remote Desktop, the
following box appears:

"Because of a protocol error detected at the client (code
0x1104), this session will be disconnected. Please try
connecting to the remote computer again."

Yet, I've loaded Remote Desktop on another machine to
access the same server and it works fine. Does not seem
to be OS dependent 'cause I've tried on a few XP, ME, 98
and have the same failure, yet another XP and 98 work fine.

What is the OS for the Terminal Server? Are you using the latest Remote
Desktop client?

http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp

Jim Bricker

"Scott Zotigh" <zot...@hourglass-usa.com> wrote in message
news:027d01c36e4d$03017470$a101...@phx.gbl...

Windows 2000 Server. And, yes...I've even tried with the
new client. Baffling....it works fine from some machines,
but not at all from others, regardless of operating system
on the client.

Evening gentlman,

I was wondering if you found a solution to this as of yet? I just initiated Terminal Services this evening and ran into the same issue with an XP Home machine that is patched up. I have the Windows 2003 server sitting behind a Linkys Router for initial testing.

I am looking at several remote access solutions and wanted to see if Terminal services could provide an answer to our remote access dilemma. We are also looking at Citrix, Neoteris, F5, and SonicWall's VPN solution. Have either of you worked with any of these products? I am also wondering how secure TS really is...I have seen some postings about FIPS causing issues and then you are left with 128 bit.

I would prefer to have the 168 triple des solution to establish due dilegence.

Thanks for the help and I hope we find the solution soon, quite aggravating when you are trying to test a product.

M

----- Scott Zotigh wrote: -----

.