- Remove From My Forums
-
Вопрос
-
Здравствуйте!
Обрывается сессия с сервером терминалов (2008 r2) с ошибкой TermDD 56
Уровень безопасности сервера терминалов обнаружил ошибку в потоке протокола и отключил этот клиент. IP-адрес клиента: **********.
В какую сторону копать? Где эти уровни безопасности настраиваются? Подскажите, пожалуйста.
-
Изменено
it-eng
7 марта 2016 г. 15:58
-
Изменено
Ответы
-
-
Помечено в качестве ответа
Petko KrushevMicrosoft contingent staff
28 марта 2016 г. 10:40
-
Помечено в качестве ответа
Все ответы
-
Не нахожу в статье этой ошибки. Уровни безопасности и так стоят на минимуме
—<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event«>
—
<System><Provider Name=»TermDD« />
<EventID Qualifiers=»49162«>56</EventID>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime=»2016-03-08T21:30:13.974328100Z« /><EventRecordID>487283</EventRecordID>
<Channel>System</Channel>
<Computer>*************</Computer>
</System>
—
<EventData><Data>DeviceTermdd</Data>
<Binary>0000040002002C000000000038000AC00000000038000AC00000000000000000000000000000000006000AD0</Binary>
</EventData>
</Event>
-
Изменено
it-eng
9 марта 2016 г. 16:07
-
Изменено
-
Наиболее вероятная причина все же в сетевой карте, точнее драйверах и их параметрах.
Обновите драйвер. Попробуйте подобрать настройки параметров.
Сазонов Илья
https://isazonov.wordpress.com/
-
Получается у нас два сервера терминалов одни и те же ошибки сыпят (только на разные ip и в разное время естественно). Они оба виртуальные и на разных хостах. Причем один на windows server 2012 r2, а второй на hyper-v server 2008 r2
-
Изменено
it-eng
9 марта 2016 г. 16:37
-
Изменено
-
-
Помечено в качестве ответа
Petko KrushevMicrosoft contingent staff
28 марта 2016 г. 10:40
-
Помечено в качестве ответа
Yesterday a customer complain about he couldn´t connect using MSTSC client to a Win2008R2 hosted on Amazon AWS/EC2
The error was on event log, but only one time, but the user says that he tried more than 5 times, allways with the same error message and the TS logs shows all retries of the user, but only one Event ID 56 was in the event log. There are several Event IDs
1149 (Remote Desktop Services: User authentication succeeded) in the log showing his attemps (more thant 9), but only one event ID 56 in the event logs, all Event IDs 1149 showing login OK and for several hours it was working and suddenly stops, after
the Event ID 56
We had this problem in the past (event ID 56), and was related to the traffic it was flowing through a (very very busy) fortigate appliance and after removing the fortigate the problem never happened again. IN this case, there was a fortigate also, but only
making traffic flow through a VPN, not the same thing and during the diagnostic, two new information: There was a change in fortigate changing cluster mode from A-A to A-P AND the user tried also to connect from a Amazon Workspace (VDI) inside the Amazon Network
and the problem ocurred again, even fortigate having (apparently) nothing to do with the matter.
I could connect with no problem through the fortigate VPN from a remote network using my domain user and the local useranme the user was trying to use it was a local user, in a disconnected state running several LOB APP services (don´t laugh) and i couldn´t
disconnect/logoff the user, nor reboot the server.
This error is new to me. In the past we had several TermDD Event ID 56 errors, but it´s the first time i see this specific error:
>temperrerr.exe C000020D —> FIRST TIME, after the fortigate change
# for hex 0xc000020d / decimal -1073741299 :
STATUS_CONNECTION_RESET ntstatus.h
# The transport connection has been reset.
# 1 matches found for «C000020D»
>temperrerr.exe C0000184 —> 2 or 3 times in the last 4 months
# for hex 0xc0000184 / decimal -1073741436 :
STATUS_INVALID_DEVICE_STATE ntstatus.h
# The device is not in a valid state to perform this request.
# 1 matches found for «C0000184»
>temperrerr.exe C000005E —> 2 or 3 times in the last 4 months
# for hex 0xc000005e / decimal -1073741730 :
STATUS_NO_LOGON_SERVERS ntstatus.h
# There are currently no logon servers available to service
# the logon request.
# 1 matches found for «C000005E»
>temperrerr.exe C00A0032 —> 2 or 3 times in the last 4 months
# for hex 0xc00a0032 / decimal -1073086414 :
STATUS_RDP_PROTOCOL_ERROR ntstatus.h
# The RDP protocol component %2 detected an error in the
# protocol stream and has disconnected the client.
# 1 matches found for «C00A0032»
>temperrerr.exe C00000DC —> 2 or 3 times in the last 4 months
# for hex 0xc00000dc / decimal -1073741604 :
STATUS_INVALID_SERVER_STATE ntstatus.h
# Indicates the Sam Server was in the wrong state to perform
# the desired operation.
# 1 matches found for «C00000DC»
The source for the err application was taken from: https://blogs.technet.microsoft.com/askperf/2010/03/24/the-curious-case-of-event-id-56-with-source-termdd/
Why does the EventID 56 shows only once, but the user reported several attempts of the error?
Maybe the network really is a problem?
-
Edited by
Thursday, February 4, 2016 11:32 AM
typo error
Yesterday a customer complain about he couldn´t connect using MSTSC client to a Win2008R2 hosted on Amazon AWS/EC2
The error was on event log, but only one time, but the user says that he tried more than 5 times, allways with the same error message and the TS logs shows all retries of the user, but only one Event ID 56 was in the event log. There are several Event IDs
1149 (Remote Desktop Services: User authentication succeeded) in the log showing his attemps (more thant 9), but only one event ID 56 in the event logs, all Event IDs 1149 showing login OK and for several hours it was working and suddenly stops, after
the Event ID 56
We had this problem in the past (event ID 56), and was related to the traffic it was flowing through a (very very busy) fortigate appliance and after removing the fortigate the problem never happened again. IN this case, there was a fortigate also, but only
making traffic flow through a VPN, not the same thing and during the diagnostic, two new information: There was a change in fortigate changing cluster mode from A-A to A-P AND the user tried also to connect from a Amazon Workspace (VDI) inside the Amazon Network
and the problem ocurred again, even fortigate having (apparently) nothing to do with the matter.
I could connect with no problem through the fortigate VPN from a remote network using my domain user and the local useranme the user was trying to use it was a local user, in a disconnected state running several LOB APP services (don´t laugh) and i couldn´t
disconnect/logoff the user, nor reboot the server.
This error is new to me. In the past we had several TermDD Event ID 56 errors, but it´s the first time i see this specific error:
>temperrerr.exe C000020D —> FIRST TIME, after the fortigate change
# for hex 0xc000020d / decimal -1073741299 :
STATUS_CONNECTION_RESET ntstatus.h
# The transport connection has been reset.
# 1 matches found for «C000020D»
>temperrerr.exe C0000184 —> 2 or 3 times in the last 4 months
# for hex 0xc0000184 / decimal -1073741436 :
STATUS_INVALID_DEVICE_STATE ntstatus.h
# The device is not in a valid state to perform this request.
# 1 matches found for «C0000184»
>temperrerr.exe C000005E —> 2 or 3 times in the last 4 months
# for hex 0xc000005e / decimal -1073741730 :
STATUS_NO_LOGON_SERVERS ntstatus.h
# There are currently no logon servers available to service
# the logon request.
# 1 matches found for «C000005E»
>temperrerr.exe C00A0032 —> 2 or 3 times in the last 4 months
# for hex 0xc00a0032 / decimal -1073086414 :
STATUS_RDP_PROTOCOL_ERROR ntstatus.h
# The RDP protocol component %2 detected an error in the
# protocol stream and has disconnected the client.
# 1 matches found for «C00A0032»
>temperrerr.exe C00000DC —> 2 or 3 times in the last 4 months
# for hex 0xc00000dc / decimal -1073741604 :
STATUS_INVALID_SERVER_STATE ntstatus.h
# Indicates the Sam Server was in the wrong state to perform
# the desired operation.
# 1 matches found for «C00000DC»
The source for the err application was taken from: https://blogs.technet.microsoft.com/askperf/2010/03/24/the-curious-case-of-event-id-56-with-source-termdd/
Why does the EventID 56 shows only once, but the user reported several attempts of the error?
Maybe the network really is a problem?
-
Edited by
Thursday, February 4, 2016 11:32 AM
typo error