|
Can’t access TS with error
code 0x1104
Because of protocol error
detected at the client (code 0x1104)
Situation: The client has been RDC to access their Terminal Server for
years. Since last week, he can't access the TS any more.
Troubleshooting: 1. Telnet port 3389 from the Internet,
receive this result: ╙├╗º╩²▓╗╣╗ú¼╟δ╙δ╥ú╓╛╚φ╝■┴¬╧╡╣║┬≥
http://www.youngzsoft.com/cn/
2. Telnet port 3389 inside, it is normal.
3. If using RDC to access TS, you will receive this message: "Because of
protocol error detected at the client (code 0x1104), this session will be
disconnected".
4. If we run netstat –no, the port 3389 is connecting to
117.26.176.32 and PID 3396. The PID 3396 is spoolsv.exe.
Case 1: Someone changed the port 3389 to 2288. Fixing it
by change the router forward port from 3389 to 2288.
Case 2: New installed software changed the port from 3389
to 3399.
Case 3: The RDP-Tcp folder was deleted from regedit:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal
Server\WinStations\
Case 4: It could be virus or spyware. More information can
be found this post:
What's the spoolsv.exe
Post your questions, comments, feedbacks and suggestions
Contact a consultant
Related Topics
|