Because Of A Protocol Error, Detected, Cant login to my server

When i try to connect to my server via RDP i for some strange reason get the
following error "because of a protocol error, detected at the client (code
0x1104) this session will be disconnected. Please try connecting to the
remote computer again" Ive tried several things by connecting to the servers
registry and adding values as indicated at
http://support.microsoft.com/kb/q154596/ (which was advised by a friend) but
still no luck anyone know what to do?

RDP uses port 3389 TCP on the server and I don't believe the referenced KB
would help anything. What I would try to do is to connect from a couple of
clients to see if you get the same error to try and track down if this is a
problem with the server or the client. Running netstat -an on the server
should show port 3389 TCP listening and from the client you should be able
to telnet into port 3389 TCP on that server to verify that port 3389 TCP is
open. Use the command " telnet xxx.xxx.xxx.xxx 389" where xxx.xxx.xxx.xxx is
the IP address of the server. If port 3389 TCP is open you will get a blank
command line screen with a flashing cursor. If it is not you will get an
access denied message. --- Steve


"Jamie" <(E-Mail Removed)> wrote in message
news3B69D3A-C7C9-4C0E-940A-(E-Mail Removed)...
> When i try to connect to my server via RDP i for some strange reason get
> the
> following error "because of a protocol error, detected at the client (code
> 0x1104) this session will be disconnected. Please try connecting to the
> remote computer again" Ive tried several things by connecting to the
> servers
> registry and adding values as indicated at
> http://support.microsoft.com/kb/q154596/ (which was advised by a friend)
> but
> still no luck anyone know what to do?
>

Thanks i tried to use telnet ***.***.***.*** 389 it showed a blank screen and
then hung like that same happened when using the server name. When i used
just the server name/ ip address i.e. telnet ***.***.***.*** it returned an
error "could not open connection to the host, on port 23: connect failed" i
turned off the firewall etc but with the same problem.

I think it must have been a program i installed that could have caused this
problem as the program picks up the current IP and sends it to another server
(saves me having to remeber the new IP each time as i have dynamic IP) so im
imagining it must have changed the IP or something. Anyway my theory was in
trying to remove this program via a cmd line - is that possible? if so please
advise

Thanks


"Steven L Umbach" wrote:

> RDP uses port 3389 TCP on the server and I don't believe the referenced KB
> would help anything. What I would try to do is to connect from a couple of
> clients to see if you get the same error to try and track down if this is a
> problem with the server or the client. Running netstat -an on the server
> should show port 3389 TCP listening and from the client you should be able
> to telnet into port 3389 TCP on that server to verify that port 3389 TCP is
> open. Use the command " telnet xxx.xxx.xxx.xxx 389" where xxx.xxx.xxx.xxx is
> the IP address of the server. If port 3389 TCP is open you will get a blank
> command line screen with a flashing cursor. If it is not you will get an
> access denied message. --- Steve
>
>
> "Jamie" <(E-Mail Removed)> wrote in message
> news3B69D3A-C7C9-4C0E-940A-(E-Mail Removed)...
> > When i try to connect to my server via RDP i for some strange reason get
> > the
> > following error "because of a protocol error, detected at the client (code
> > 0x1104) this session will be disconnected. Please try connecting to the
> > remote computer again" Ive tried several things by connecting to the
> > servers
> > registry and adding values as indicated at
> > http://support.microsoft.com/kb/q154596/ (which was advised by a friend)
> > but
> > still no luck anyone know what to do?
> >
>
>
>

Oh another thing, i tried to connect from another machine and had tge same
problem and i just tried to uninstall the program in the previous post and i
still have the same problem i uninstalled the program using the run command
and naviageted to the program on the server

"Jamie" wrote:

> Thanks i tried to use telnet ***.***.***.*** 389 it showed a blank screen and
> then hung like that same happened when using the server name. When i used
> just the server name/ ip address i.e. telnet ***.***.***.*** it returned an
> error "could not open connection to the host, on port 23: connect failed" i
> turned off the firewall etc but with the same problem.
>
> I think it must have been a program i installed that could have caused this
> problem as the program picks up the current IP and sends it to another server
> (saves me having to remeber the new IP each time as i have dynamic IP) so im
> imagining it must have changed the IP or something. Anyway my theory was in
> trying to remove this program via a cmd line - is that possible? if so please
> advise
>
> Thanks
>
>
> "Steven L Umbach" wrote:
>
> > RDP uses port 3389 TCP on the server and I don't believe the referenced KB
> > would help anything. What I would try to do is to connect from a couple of
> > clients to see if you get the same error to try and track down if this is a
> > problem with the server or the client. Running netstat -an on the server
> > should show port 3389 TCP listening and from the client you should be able
> > to telnet into port 3389 TCP on that server to verify that port 3389 TCP is
> > open. Use the command " telnet xxx.xxx.xxx.xxx 389" where xxx.xxx.xxx.xxx is
> > the IP address of the server. If port 3389 TCP is open you will get a blank
> > command line screen with a flashing cursor. If it is not you will get an
> > access denied message. --- Steve
> >
> >
> > "Jamie" <(E-Mail Removed)> wrote in message
> > news3B69D3A-C7C9-4C0E-940A-(E-Mail Removed)...
> > > When i try to connect to my server via RDP i for some strange reason get
> > > the
> > > following error "because of a protocol error, detected at the client (code
> > > 0x1104) this session will be disconnected. Please try connecting to the
> > > remote computer again" Ive tried several things by connecting to the
> > > servers
> > > registry and adding values as indicated at
> > > http://support.microsoft.com/kb/q154596/ (which was advised by a friend)
> > > but
> > > still no luck anyone know what to do?
> > >
> >
> >
> >

Well your second telnet failure may be because telnet is not enabled on the
server or port 23 TCP is blocked since you did not specify port 3389 TCP.
When you use telnet to test a port being open all you will see is the blank
command line screen with a blinking cursor until you close the window. I
don't know what program you are referring to but if it is installed as a
service you should be able to stop it via the command line. Otherwise you
can use Task manager or command line tools to view and kill a running
process such as pslist/pskill from SysInternals. The command net start will
list running services on a computer. Msinfo32 will provide a lot of
information about what is running on a computer and can also be used to
display information on remote computers if you can connect to them.
Sysinternals has tools such as psexec that can be used to display the
command line on a remote computer. --- Steve

http://www.sysinternals.com/ntw2k/freeware/psexec.shtml
http://www.sysinternals.com/ntw2k/fr.../pstools.shtml -- PsTools

"Jamie" <(E-Mail Removed)> wrote in message
news:59B7CCAD-DAD7-4CE3-89CA-(E-Mail Removed)...
> Thanks i tried to use telnet ***.***.***.*** 389 it showed a blank screen
> and
> then hung like that same happened when using the server name. When i used
> just the server name/ ip address i.e. telnet ***.***.***.*** it returned
> an
> error "could not open connection to the host, on port 23: connect failed"
> i
> turned off the firewall etc but with the same problem.
>
> I think it must have been a program i installed that could have caused
> this
> problem as the program picks up the current IP and sends it to another
> server
> (saves me having to remeber the new IP each time as i have dynamic IP) so
> im
> imagining it must have changed the IP or something. Anyway my theory was
> in
> trying to remove this program via a cmd line - is that possible? if so
> please
> advise
>
> Thanks
>
>
> "Steven L Umbach" wrote:
>
>> RDP uses port 3389 TCP on the server and I don't believe the referenced
>> KB
>> would help anything. What I would try to do is to connect from a couple
>> of
>> clients to see if you get the same error to try and track down if this is
>> a
>> problem with the server or the client. Running netstat -an on the server
>> should show port 3389 TCP listening and from the client you should be
>> able
>> to telnet into port 3389 TCP on that server to verify that port 3389 TCP
>> is
>> open. Use the command " telnet xxx.xxx.xxx.xxx 389" where xxx.xxx.xxx.xxx
>> is
>> the IP address of the server. If port 3389 TCP is open you will get a
>> blank
>> command line screen with a flashing cursor. If it is not you will get an
>> access denied message. --- Steve
>>
>>
>> "Jamie" <(E-Mail Removed)> wrote in message
>> news3B69D3A-C7C9-4C0E-940A-(E-Mail Removed)...
>> > When i try to connect to my server via RDP i for some strange reason
>> > get
>> > the
>> > following error "because of a protocol error, detected at the client
>> > (code
>> > 0x1104) this session will be disconnected. Please try connecting to the
>> > remote computer again" Ive tried several things by connecting to the
>> > servers
>> > registry and adding values as indicated at
>> > http://support.microsoft.com/kb/q154596/ (which was advised by a
>> > friend)
>> > but
>> > still no luck anyone know what to do?
>> >
>>
>>
>>