Protocol Error 0x1104 connecting to 2003 Servers

Discussion:

(too old to reply)

Bruno Guardia

2005-06-09 02:21:07 UTC

When connecting to my 2003 servers via RDP I 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"

Previously, I could connect to them without any problem.

I am able to telnet port 3389; I have three Windows 2003 Terminal Servers,
they are all on the same domain; one of them is also the Licensing Server,
two of them are Domain Controllers (2000 Native because there still are
previous DC W2K).

And they worked OK until last week; but we have started to have the error. I
found on KB and Technet the suggestion to apply W2K3 Service Pack 1, because
it solves a lot of issues on TS; but the problem continues after applying SP1
(I haven't had other side effects, the servers worked nicely in every other
service after SP1).

I can connect to TS sometimes, when I am on the local network; but when on
the VPN, most of the time it doesn't work. Restarting all servers on the
domain doesn't correct the problem.

I have ISA Server, but the VPN traffic is not filtered and I have verified
port 3389 is opened for VPNs, and I double checked with telnet (server) 3389.

The TS doesn't have Exchange, so there is no other service that gets the
port 3389. So I don't think it would be adequate to adjust RPC ports.

I find over the Internet lots of mentions of this error, but no one seem to
have solved it except for problems on port 3389 blocking.

Vera Noest [MVP]

2005-06-09 20:32:00 UTC

Permalink

Anything in the EventLog on the Terminal Server or the client?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?QnJ1bm8gR3VhcmRpYQ==?=" <Bruno

Post by Bruno Guardia
When connecting to my 2003 servers via RDP I 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"
Previously, I could connect to them without any problem.
I am able to telnet port 3389; I have three Windows 2003
Terminal Servers, they are all on the same domain; one of them
is also the Licensing Server, two of them are Domain Controllers
(2000 Native because there still are previous DC W2K).
And they worked OK until last week; but we have started to have
the error. I found on KB and Technet the suggestion to apply
W2K3 Service Pack 1, because it solves a lot of issues on TS;
but the problem continues after applying SP1 (I haven't had
other side effects, the servers worked nicely in every other
service after SP1).
I can connect to TS sometimes, when I am on the local network;
but when on the VPN, most of the time it doesn't work.
Restarting all servers on the domain doesn't correct the
problem.
I have ISA Server, but the VPN traffic is not filtered and I
have verified port 3389 is opened for VPNs, and I double checked
with telnet (server) 3389.
The TS doesn't have Exchange, so there is no other service that
gets the port 3389. So I don't think it would be adequate to
adjust RPC ports.
I find over the Internet lots of mentions of this error, but no
one seem to have solved it except for problems on port 3389
blocking.

Bruno Guardia

2005-06-10 01:01:04 UTC

Permalink

No, there is anything unusual on any of them.

On the client, event 20158, when connecting to the VPN; later an event 3019
(MrxSmb), when browsing and authenticating for connecting to a server via
SMB. I can see the files on the server, after authentication; so the server
is up and responding to other services, not to RDP.

On the server, not a trace of anything, doesn't seem to register in the log
any connection attempt or fail.

Post by Vera Noest [MVP]
Anything in the EventLog on the Terminal Server or the client?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?QnJ1bm8gR3VhcmRpYQ==?=" <Bruno

Vera Noest [MVP]

2005-06-10 10:40:50 UTC

Permalink

Let's get down to the basics, then and forget VPN and ISA for a
moment.
Can you connect from a client on the same LAN as the Terminal
Server?
If not, can you telnet to port 3389? Is the TS listening on port
3389 (netstat /a)? Are you unable to connect from *any* client, or
only from some of them?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?QnJ1bm8gR3VhcmRpYQ==?="

Post by Bruno Guardia
No, there is anything unusual on any of them.
On the client, event 20158, when connecting to the VPN; later an
event 3019 (MrxSmb), when browsing and authenticating for
connecting to a server via SMB. I can see the files on the
server, after authentication; so the server is up and responding
to other services, not to RDP.
On the server, not a trace of anything, doesn't seem to register
in the log any connection attempt or fail.

Post by Bruno Guardia
When connecting to my 2003 servers via RDP I 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"
Previously, I could connect to them without any problem.
I am able to telnet port 3389; I have three Windows 2003
Terminal Servers, they are all on the same domain; one of
them is also the Licensing Server, two of them are Domain
Controllers (2000 Native because there still are previous DC
W2K).
And they worked OK until last week; but we have started to
have the error. I found on KB and Technet the suggestion to
apply W2K3 Service Pack 1, because it solves a lot of issues
on TS; but the problem continues after applying SP1 (I
haven't had other side effects, the servers worked nicely in
every other service after SP1).
I can connect to TS sometimes, when I am on the local
network; but when on the VPN, most of the time it doesn't
work. Restarting all servers on the domain doesn't correct
the problem.
I have ISA Server, but the VPN traffic is not filtered and I
have verified port 3389 is opened for VPNs, and I double
checked with telnet (server) 3389.
The TS doesn't have Exchange, so there is no other service
that gets the port 3389. So I don't think it would be
adequate to adjust RPC ports.
I find over the Internet lots of mentions of this error, but
no one seem to have solved it except for problems on port
3389 blocking.

Bruno Guardia

2005-06-11 00:38:03 UTC

Permalink

1 - Sometimes; there is no clear pattern for when I can connect and when I
cannot. I have tried on different clients: sometimes I can connect from
client A, sometimes from cliente B, sometimes from both, sometimes from
neither. Both on the LAN or by VPN, sometimes it works, most of last times it
doesn't. It is not related with restarting the servers, for example.

2 - Yes, I can telnet to port 3389. And yes, TS is listening.

3 - When I cannot connect, most clients cannot connect. The only pattern is
that is most frequent the error from the VPN, that from the LAN.

Thanks

Post by Vera Noest [MVP]
Let's get down to the basics, then and forget VPN and ISA for a
moment.
Can you connect from a client on the same LAN as the Terminal
Server?
If not, can you telnet to port 3389? Is the TS listening on port
3389 (netstat /a)? Are you unable to connect from *any* client, or
only from some of them?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?QnJ1bm8gR3VhcmRpYQ==?="

Post by Bruno Guardia
When connecting to my 2003 servers via RDP I 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"
Previously, I could connect to them without any problem.
I am able to telnet port 3389; I have three Windows 2003
Terminal Servers, they are all on the same domain; one of
them is also the Licensing Server, two of them are Domain
Controllers (2000 Native because there still are previous DC
W2K).
And they worked OK until last week; but we have started to
have the error. I found on KB and Technet the suggestion to
apply W2K3 Service Pack 1, because it solves a lot of issues
on TS; but the problem continues after applying SP1 (I
haven't had other side effects, the servers worked nicely in
every other service after SP1).
I can connect to TS sometimes, when I am on the local
network; but when on the VPN, most of the time it doesn't
work. Restarting all servers on the domain doesn't correct
the problem.
I have ISA Server, but the VPN traffic is not filtered and I
have verified port 3389 is opened for VPNs, and I double
checked with telnet (server) 3389.
The TS doesn't have Exchange, so there is no other service
that gets the port 3389. So I don't think it would be
adequate to adjust RPC ports.
I find over the Internet lots of mentions of this error, but
no one seem to have solved it except for problems on port
3389 blocking.

Vera Noest [MVP]

2005-06-12 20:38:50 UTC

Permalink

Mmm, the fact that it doesn't happen all the time is *not* helping.
I've searched high and low during the weekend, and found only
references to other services occupying port 3389, as you did.

However: I found at least one posting where the problem was caused by
a trojan.

http://www.winserverkb.com/Uwe/Forum.aspx/windows-2000-terminal-
server/2503/Protocol-Error-on-Small-Business-Server-2000

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?QnJ1bm8gR3VhcmRpYQ==?="

Post by Bruno Guardia
1 - Sometimes; there is no clear pattern for when I can connect
and when I cannot. I have tried on different clients: sometimes
I can connect from client A, sometimes from cliente B, sometimes
from both, sometimes from neither. Both on the LAN or by VPN,
sometimes it works, most of last times it doesn't. It is not
related with restarting the servers, for example.
2 - Yes, I can telnet to port 3389. And yes, TS is listening.
3 - When I cannot connect, most clients cannot connect. The only
pattern is that is most frequent the error from the VPN, that
from the LAN.
Thanks

Post by Vera Noest [MVP]
Let's get down to the basics, then and forget VPN and ISA for a
moment.
Can you connect from a client on the same LAN as the Terminal
Server?
If not, can you telnet to port 3389? Is the TS listening on
port 3389 (netstat /a)? Are you unable to connect from *any*
client, or only from some of them?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?QnJ1bm8gR3VhcmRpYQ==?="

Post by Bruno Guardia
No, there is anything unusual on any of them.
On the client, event 20158, when connecting to the VPN; later
an event 3019 (MrxSmb), when browsing and authenticating for
connecting to a server via SMB. I can see the files on the
server, after authentication; so the server is up and
responding to other services, not to RDP.
On the server, not a trace of anything, doesn't seem to
register in the log any connection attempt or fail.

Post by Vera Noest [MVP]
Anything in the EventLog on the Terminal Server or the
client?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?QnJ1bm8gR3VhcmRpYQ==?=" <Bruno

Post by Bruno Guardia
When connecting to my 2003 servers via RDP I 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"
Previously, I could connect to them without any problem.
I am able to telnet port 3389; I have three Windows 2003
Terminal Servers, they are all on the same domain; one of
them is also the Licensing Server, two of them are Domain
Controllers (2000 Native because there still are previous
DC W2K).
And they worked OK until last week; but we have started to
have the error. I found on KB and Technet the suggestion
to apply W2K3 Service Pack 1, because it solves a lot of
issues on TS; but the problem continues after applying SP1
(I haven't had other side effects, the servers worked
nicely in every other service after SP1).
I can connect to TS sometimes, when I am on the local
network; but when on the VPN, most of the time it doesn't
work. Restarting all servers on the domain doesn't correct
the problem.
I have ISA Server, but the VPN traffic is not filtered and
I have verified port 3389 is opened for VPNs, and I double
checked with telnet (server) 3389.
The TS doesn't have Exchange, so there is no other service
that gets the port 3389. So I don't think it would be
adequate to adjust RPC ports.
I find over the Internet lots of mentions of this error,
but no one seem to have solved it except for problems on
port 3389 blocking.

unknown

2005-06-15 14:40:35 UTC

Permalink

hi,

You can try this :

http://support.microsoft.com/kb/898060

Bye

--
edaPosted from http://www.pcreview.co.uk/ newsgroup acces

FedericoRicci

2006-09-21 13:48:42 UTC

Permalink

Hi!
I had this problem when i moved a server from a location to another.
My 2003 server has got two NIC and i used one for the first location and the
other for the second location.
When i tried to connect with RDP to this server i found this problem.
Looking for a solution in Terminal Services Configuration, i've founded it
by authorizing the second Nic to be used for RDP.
The location of the command is:
Terminal Services Configuration
+RDP-Tcp Properties
+ Network Adapters.
See YA

pganze

2005-06-30 14:50:06 UTC

Permalink

Hi,

I had this issue with a remote user this morning and was able to fix
it. The user was in a hotel trying to VPN into the corporate network
and receiving the 0x1104 error.

After some troubleshooting I was able to determine that the Hotel's
subnet was 192.168.0 which is the same as the network that was being
connected to through the PPTP VPN. The VPN would connect, but when the
user tried to connect the remote desktop he would get the error because
the terminal server is not available on the local hotel network.

The hotel provided an alternative IP that was a 10.0.0 number that we
had to hardcode in order for the routing to work to the corporate
network.

Thought it might help,

Pete

pganze

2005-06-30 14:52:47 UTC

Permalink