Сбой операции read tcp сокета ошибка 64

Содержание

1. A Short List of Windows Remote Desktop Server Error Messages
2. Remote Desktop Gateway Connection Issues
3. Popular Topics in Microsoft Remote Desktop Services
4. 7 Replies
5. Read these next.
6. poor wifi, school’s third floor
7. Need help crafting a job posting for an IT Pro
8. Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal
9. Spark! Pro series – 13th January 2023
10. Решено проблема с remote desktop
11. akbars
12. akbars
13. NanoSuit
14. Windows 10 Pro, RDP Server, «An internal error has occurred»

Hello,

I have a small, newly set up network consisting of three Windows 10 Build 1607 desktops, all up to date, a 2016 Essentials server and a Windows 10 Build 1607 laptop and desktop on the other end of a OpenVPN tunnel. The remote laptop and desktop are successfully
joined to the domain and mapping drives no problem. I’ve been pushing GPOs out to all the machines and everything seems to work, up to the point where I enabled remote desktop and began to test with it. The OpenVPN tunnel should not be an issue, as the remote
desktop session to the Server 2016 Essentials machine from the remote machine is rock solid stable, even when the network is under heavy use. My problem lies with making and maintaining remote desktop sessions to each of the three Windows 10 machines in the
office from the remote Windows 10 machines. All three office machines exhibit the same issue.

Here is a scenario:

You are already pinging the remote machine you want to control with RDP, and you are getting responses back as expected. You can make a connection just fine, but whether using the session or leaving it idle, you can watch the pings going to the machine randomly
drop as if the NIC on the remote machine has been reset. The RDP session is interrupted, then a few seconds later reconnected. It has done this thousands of times during my troubleshooting session on all three office machines. You can see that the session
is not being starved for bandwidth. The first event in the RDPCoreTS logs that happens right at the time of the connection drop is almost always a slew «TCP socket WRITE operation failed, error 64.» and «TCP socket READ operation failed, error
64» followed by «The server has terminated main RDP connection with the client.» Then another error-level event comes up: «‘Failed CreateVirtualChannel call on this Connections Stack’ in CUMRDPConnection::CreateVirtualChannel at 2349 err=[0x80004005]»
followed by number disconnect events, and then: «Disconnect trace:CUMRDPConnection Disconnect trace:’calling spGfxPlugin->PreDisconnect()’ in CUMRDPConnection::PreDisconnect at 4477 err=[0x0], Error code:0x0.» The last event you see in this grouping
is: «The disconnect reason is 14.» Upon automatically reconnecting, you see: «The network characteristics detection function has been disabled because of Reason Code: 2(Server Configuration)..» Then the connection is restored,
only to drop in anything from a few seconds up to a few minutes later.

So, in recap (TL:DR):

RDP from the remote machines to the 2016 Essentials Server through the VPN tunnel:
Rock Solid Stable
RDP from the remote machines to the office machines through the VPN tunnel:
Constant drops and numerous logged events.
RDP from 2016 Essentials Server to office machines on LAN only:
Rock Solid Stable
RDP from the office machines to the remote machines through the VPN tunnel: Constant drops and numerous logged events.
ALL network traffic ceases to and from the host machine when the drop happens, including ICMP traffic (pings).
ALL of the Windows 10 machines can ping each other without issue and without any drops when not using RDP.

What this tells me is that the issue lies in some configuration issue either with a GPO setting or something inbuilt wrong with all of the Windows 10 1607 machines I have.

I have tried a variety of fixes, and have probably put 20 hours into researching a solution to this problem so I am prepared for this to be difficult to fix. My google powers have failed me.

• Moved by

  Friday, November 4, 2016 9:04 AM
  from RDC forum

A Short List of Windows Remote Desktop Server Error Messages

Assumption and proposed solution:

Issue occurs when Windows 10 1809 clients connect to Server 2019. Windows 10 1803 or older are not having this problem. Here’s an item to test on the server.

There appears to be a threshold on Windows to limit the number of connections. Client OS would be 100, and server OS as 3000 by default. Here’s how to set this to a maximum value.

Event viewer messages:

Comment: this message appears to be expressing proper English. Although, I don’t know what to do with it.

Comment: I’m also unsure about any interpretation of the error above. Although, this correlates to a Windows 2019 Server with RDS role enabled. This machine is behind strict network zones (HIPPA). Clients often using Windows 10 to RDP-access this ‘bastion’ host.

A possible workaround is to change the display setting on the .rdp to a lower display resolution setting (e.g. 1280×1024). This happens when client machine’s resolution is 2560 x 1440 and the [virtual] video card in the host machine isn’t as capable. Another idea is to peruse the Windows 10 Remote Desktop UWP app.

Comment: pre-pending a username with DOMAINusername would work when encountering these errors.

Complain: Remote Desktop Session Does Not Show Login Prompt, and session would disconnect after 2 seconds…

Comment: Some Internet sources have alluded to CredSSP being the culprit. I have not yet tested setting CredSSP value to TRUE yet. On the same note, I’m guessing the issue would be more related to RemoteFX, rather than authentication. Will update this note once I gather more info.

Источник

Remote Desktop Gateway Connection Issues

I’ve got a remote desktop gateway setup on a Hyper-V machine for our network. Licensing is on the DC VM, Gateway/Web Access is on one VM, Connection Broker is a third VM and the Session Host is a final VM. I’m using Windows Server 2016 Datacenter in a AD setting.

I frequently have issues where when I try to use one of the remoteapps i’ll get the login prompts and then the window just disappears. On the offsite computer I’ll get a warning event:

Per the Server Manager, I’m not noticing any errors on the Connection Broker. In the Event Viewer under RemoteDesktopServices-RdpCoreTS I can see a connection was made via TCP, and then UDP, but then there’s the following error:

This is followed by a Disconnect Error 0, and then

The Session Host is just displaying the error:

This is follwed by Event 40 giving the disconnect reason code 12 which I’ve found to mean: «The user logged off, disconnecting the session.»

The gateway logs are showing that the Connection Authorization Policy requirements were met as were the Resource Authorization Policy requirements, a connection happened, lasted about 4 seconds and then disconnected.

I’ve tried making sure that group policy clearly states the licensing server, the connection broker, the security layer (SSL), the encyrption level (High).

Popular Topics in Microsoft Remote Desktop Services

what kind of deployment virtual desktop or session host?

I tried restarting the TermService on the Session Host, and instead of the login screen disappearing, I started getting a Black screen on login instead. I’ve seen the thread here:

And taken a look at our computers. The frequent remote computers I have access to via Teamviewer, so I’m now doublechecking their logins.

So, I’m not sure what’s happened in the last 8 hours. When I went to remote in from home tonight, it didn’t work. I got in a different way, and I can see that someone tried unsuccessfully to remote in as I left the office, and then nothing’s been able to bring this back up. I’ve restarted all the servers in the Remote Desktop configuration and no success (in the past, that has worked as a solution to fix the problem). I undid a lot of the GPO settings thinking that might help and that did not.

Right now for some unclear reason, from an on-prem machine/VM I can’t even RDP into the session host VM. And when I use my home computer to try to go through the gateway, I get an error message about not finding the connection broker on the network.

I’ll be revisiting it in the morning after more sleep.

Ok. I’m noticing that the RDP Session Host is not listening on Port 3389 and I’m trying to figure out why not. The Remote Desktop Services service is running, but the Remote Desktop Services UserMode Port Redirector service is not.

In the registry, it is still showing as Port Number 3389 under the RDP-Tcp section.

The firewall (Windows Firewall with Advanced Security) has both TCP and UDP port 3389 open.

There’s something weird going on with the printers, I don’t know if that would be related. It kept saying that the driver is unavailable for a networked printer, but then isn’t letting me delete or remove it. That printer installs via GPO and I’ve disabled the GPO, but no better success.

Still not working. I rolled out a second Session Host VM and a new collection and having the same problems there. To add the second session host, I had to disable all the Remote Desktop Services related GPOs, so those are still disabled. I’ve tried lowering the security settings. Still no success.

Any luck with solving this?

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

poor wifi, school’s third floor

I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.

Need help crafting a job posting for an IT Pro

I’d really appreciate some thoughts and advice. I’m looking to hire an IT pro to be our resident go-to for all things IT (device support, SQL Server, network admin, etc) but who also is interested in learning — or even has some experience in — the.

Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 13, 1874: Adding Machine Patented (Read more HERE.) Bonus Flashback: January 13, 1990: Astronauts awakened to the song Attack of the Killer Tomatoes (Read mor.

Spark! Pro series – 13th January 2023

Happy Friday the 13th! This day has a reputation for being unlucky, but I hope that you’ll be able to turn that around and have a great day full of good luck and good fortune. Whether you’re superstitious or not, .

Источник

Решено проблема с remote desktop

Участник

Участник

Сведения об ошибке:
Причина ошибки: Неизвестное имя пользователя или неверный пароль.
Состояние: 0xC000006D
Подсостояние: 0xC000006A

Сведения о процессе:
Идентификатор процесса вызывающей стороны: 0x1260
Имя процесса вызывающей стороны: C:Program Files (x86)Kaspersky LabKaspersky Endpoint Security for Windowsavpsus.exe

Участник

Не удается найти описание для идентификатора события 0 из источника igfxCUIService2.0.0.0. Вызывающий данное событие компонент не установлен на этом локальном компьютере или поврежден. Установите или восстановите компонент на локальном компьютере.

Если событие возникло на другом компьютере, возможно, потребуется сохранить отображаемые сведения вместе с событием.

К событию были добавлены следующие сведения:

akbars

Случайный прохожий

Участник

Да но при чем тут RDP ?
Есть еще event id 10000 RestartManager
Запуск сеанса 2 — ‎2021‎-‎09‎-‎08T06:32:14.183987300Z.

Все равно не ясно что не так.

akbars

Случайный прохожий

Участник

Участник

NanoSuit

Специалист

Я где то читал что RDP часто глючит в последних версиях Windows 10 или в некоторых случаях вообще не работает.
Посмотрите может в этом дело:

Когда клиент удаленного рабочего стола теряет подключение к Удаленному рабочему столу, ему не удается сразу же повторно подключиться. Пользователю отображается одно из таких сообщений об ошибке:

• Клиенту не удалось подключиться к серверу терминалов из-за ошибки системы безопасности. Убедитесь, что вы вошли в сеть, и повторите попытку подключения.
• Удаленный рабочий стол отключен. Из-за ошибки безопасности клиент не смог подключиться к удаленному компьютеру. Убедитесь в том, что вы вошли в сеть, и повторите попытку подключения к серверу.

При повторном подключении клиента Удаленных рабочих столов сервер RDSH подключает клиента к новому, а не исходному сеансу. Но при проверке состояния сервера RDSH сообщается, что исходный сеанс еще активен и не был отключен.

Чтобы устранить эту проблему, можете включить политику Настроить интервал проверяемых на активность подключений в папке групповой политики, выбрав Конфигурация компьютераАдминистративные шаблоныКомпоненты WindowsСлужбы удаленных рабочих столовУзел сеансов удаленных рабочих столовПодключения. Если вы включите эту политику, нужно будет задать интервал проверки активности. Интервал проверки активности позволяет определить, как часто (в минутах) сервер проверяет состояние сеанса.

Эту проблему также можно устранить, изменив параметры аутентификации и настройки. Вы можете изменить их на уровне сервера или с помощью объектов групповой политики. Чтобы изменить параметры, выберите Конфигурация компьютераАдминистративные шаблоныКомпоненты WindowsСлужбы удаленных рабочих столовУзел сеансов удаленных рабочих столовБезопасность.

1. Откройте на сервере узла сеансов Удаленных рабочих столов соответствующее средство настройки.
2. В области Подключения щелкните правой кнопкой мыши имя подключения и выберите Свойства.
3. В диалоговом окне Свойства для этого подключения на вкладке Общие в разделе Безопасность выберите метод защиты.
4. Выберите нужное значение для параметра Уровень шифрования. Можно выбрать значение Низкий уровень, Совместимый с клиентом, Высокий уровень или FIPS-совместимый.

src

Источник

Windows 10 Pro, RDP Server, «An internal error has occurred»

I have a Windows 10 Pro machine that is functioning as a RDP terminal for a single user.

This machine was configured more than 2 years ago and has had no major changes made to its configuration, except of course for the obligatory Windows 10 automatic updates.

Everything has been working fine until a few months ago, when the user started getting this error when window attempting to connect via RDC:

Remote Desktop Connection
An internal error has occurred.

I tried logging in via RDC via my Admin credentials, and I get the same error. The error appears immediately after clicking connect. There is no processing time and the connection attempt seem to be immediately rejected by the server.

I can’t trace the problem down to any specific time, or event. It occurs seemingly at random. Sometimes after a few days, sometimes twice in one day.

Restarting the Windows 10 Pro machine always seems to fix the problem.

Strangely, accessing the Event Viewer on the Windows 10 Pro machine also seemed to fix the problem, but it almost always returns much more quickly if I use this «fix».

Speaking of the Event Viewer , these are relevant errors I found in the log related to RDC at the time that my login was rejected:

These are some other errors I noticed in the log, but don’t correspond to the moment I try to connect:

Note that the client machines are also running Windows 10 Pro.

Источник