I don't know what 's FIN_WAIT_2, but you may try to start the system with
clean boot. If it works, it may be 3rd party software. Also check this
search result.
Error code 0X1104
Because of a protocol error, detected at the client (code 0x1104) this
session will be disconnected. Symptom: When attempting to access a remote
computer ...
www.chicagotech.net/remoteissues/code0x1104.htm
--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"6DOF" <6DOF@discussions.microsoft.com> wrote in message
news:E4D3A9B0-831F-4447-9FC8-3AD198C50F06@microsoft.com...
>I recently installed a new XP Pro PC to our existing system and the remote
> desktop will not run on it. I can go into network places and find the NT
> machine and access it OK. I can read all files on it. With the RDP I
> keep
> getting "Because of a protocol error, this session will be disconnected.
> Please try to connect to the computer again."
>
> When I check the active network connections using netstat -a
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\Documents and Settings\stsuser>netstat -a
>
> Active Connections
>
> Proto Local Address Foreign Address State
> TCP GENERIC-RT:epmap 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:microsoft-ds 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:2869 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:3071 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:3389 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:6543 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:6545 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:8432 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:8434 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:8555 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:49152 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:49258 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:netbios-ssn 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:microsoft-ds 10.0.1.1:1026 ESTABLISHED
> TCP GENERIC-RT:microsoft-ds 10.0.2.1:1025 ESTABLISHED
> TCP GENERIC-RT:microsoft-ds 10.0.3.1:1025 ESTABLISHED
> TCP GENERIC-RT:1079 10.0.3.1:7000 ESTABLISHED
> TCP GENERIC-RT:1082 10.0.2.1:7000 ESTABLISHED
> TCP GENERIC-RT:1083 10.0.1.1:7000 ESTABLISHED
> TCP GENERIC-RT:1517 10.0.4.1:3389 FIN_WAIT_2
> TCP GENERIC-RT:6545 10.0.4.1:1084 ESTABLISHED
> TCP GENERIC-RT:1039 0.0.0.0:0 LISTENING
> TCP GENERIC-RT:1121 localhost:6543 ESTABLISHED
> TCP GENERIC-RT:6543 localhost:1121 ESTABLISHED
> TCP GENERIC-RT:epmap [::]:0 LISTENING 0
> TCP GENERIC-RT:2869 [::]:0 LISTENING 0
> UDP GENERIC-RT:microsoft-ds *:*
> UDP GENERIC-RT:isakmp *:*
> UDP GENERIC-RT:1026 *:*
> UDP GENERIC-RT:1041 *:*
> UDP GENERIC-RT:4500 *:*
> UDP GENERIC-RT:5571 *:*
> UDP GENERIC-RT:ntp *:*
> UDP GENERIC-RT:netbios-ns *:*
> UDP GENERIC-RT:netbios-dgm *:*
> UDP GENERIC-RT:1900 *:*
> UDP GENERIC-RT:ntp *:*
> UDP GENERIC-RT:1025 *:*
> UDP GENERIC-RT:1042 *:*
> UDP GENERIC-RT:1050 *:*
> UDP GENERIC-RT:1900 *:*
>
> The RDP to 10.0.4.1:3389 shows a network state of "FIN_WAIT_2". Does
> anyone
> out there know how to fix this issue?