Error received from peer file too large - Исправление ошибок и поиск оптимальных решений проблем

[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers.

You can see the details below.

https://www.yealink.com/ydmp-freetrial-2020

Thread Rating:

0 Votes — 0 Average
1
2
3
4
5

protaganist
Offline

Junior Member

Posts: 4

Joined: Jan 2019

Reputation: 0

Problem with low-level firmware of telephone T21 E2

Good day everyone,
i have a problem with low-level firmware of telephone T21 E2. the thing is in Russia this phone is sold only by local company (Mango office), and it has preset firmware which works only with certain VoIP provider.

When I try to install the firmware thru server TFTP the following bugs shows up:
1. 3CDaemon – Error received from peer: File too large
2. tftpd32 — Peer returns ERROR <File too large> -> aborting transfer

On the telephone display the following inscription shows up — Update failed (-6, 13)
All firmwares that are available for downloading (.rom) have size about 8 Mb.

Please help, what is the problem, how can I install normal-working firmware, which will work other then preset operator?
Windows 7×64

01-18-2019 06:48 AM

NI Junior Member Posts: 5 Joined: Oct 2018 Reputation: 0	RE: Problem with low-level firmware of telephone T21 E2 Я конечно не уверен, но попробуйте вот такую штуку в common.cfg static.auto_provision.attempt_expired_time = 60
01-18-2019 08:47 AM

protaganist
Offline

Junior Member

Posts: 4

Joined: Jan 2019

Reputation: 0

RE: Problem with low-level firmware of telephone T21 E2

(01-18-2019 08:47 AM)NI Wrote: Я конечно не уверен, но попробуйте вот такую штуку в common.cfg

static.auto_provision.attempt_expired_time = 60

Мил человек, подскажи пожалуйста где этот конфиг то найти.

В мыслях проскочило лишь — слить конфиг из web-морды телефона, добавить строчку, залить обратно через web?

(This post was last modified: 01-18-2019 11:51 AM by protaganist.)

01-18-2019 11:48 AM

Junior Member

Posts: 5

Joined: Oct 2018

Reputation: 0

RE: Problem with low-level firmware of telephone T21 E2

Не знаю как у вас сделано обновление через tftp, но у меня через autoprovision телефона. Для autoprovision T21P-E2 я использую 2 файла — common.cfg — общий конфиг для всех телефонов T21P-E2: там настройки адреса firmware, ntp сервер и тп. И второй файл с MAC-адресом телефона — где настройки уже самого sip-аккаунта. Когда обновлял T21P-E2 — заметил что у меня не обновлялась прошивка с ошибкой, не помню конкретно какая была, но что-то очень похожее на вашу. Исправил ошибку — добавив в common.cfg файл — эту строку.

01-18-2019 12:02 PM

protaganist
Offline

Junior Member

Posts: 4

Joined: Jan 2019

Reputation: 0

RE: Problem with low-level firmware of telephone T21 E2

Добавил строчку без #

т.к. в выгруженном файле 805ec0178121-non-static.cfg все строки были без #
Добавил смену часового пояса — после загрузки обратно назад файла 805ec0178121-non-static.cfg — часовой пояс сменился на мой, значит и строка Ваша прошла.

В итоге не получилось. Ошибка та же, ругается на большой файл

И это ведь всего лишь — Интервал отправки запроса (с)
Никак не связан с низкоуровневой прошивкой

(This post was last modified: 01-18-2019 12:49 PM by protaganist.)

01-18-2019 12:14 PM

protaganist Junior Member Posts: 4 Joined: Jan 2019 Reputation: 0	RE: Problem with low-level firmware of telephone T21 E2 help…
01-21-2019 11:50 AM

Possibly Related Threads…
Thread:	Author	Replies:	Views:	Last Post
	Firmware upgrade fails on T21P E2	p.pasquino@technology4you.it	0	2,699	11-02-2021 04:42 PM Last Post: p.pasquino@technology4you.it
	Lost my configuration trying to fix a static audio problem	nestman	0	2,943	06-22-2021 06:33 AM Last Post: nestman
	T21P_E2 firmware 84.0.125 slow with VLAN	GwenH	3	9,601	11-03-2020 11:01 PM Last Post: complex1
	T26P Can not upgrade firmware	martien.poels@bank2loyalty.com	2	7,653	09-21-2020 05:16 PM Last Post: complex1
	Yealink T28P Firmware Upgrade Fails	Michelth	11	49,555	06-27-2020 10:13 AM Last Post: complex1
	T28P LDAP Problem	oguzhan	1	6,426	06-10-2020 01:14 PM Last Post: beldimon
	«On hook» event problem	Rafal	6	13,448	03-26-2020 03:35 AM Last Post: Normfred
	default username/password not working after firmware upgrade	tfrohling	3	35,117	02-15-2020 01:30 PM Last Post: khalidnisar
	T22 and firmware upgrade	saleh	2	16,709	08-16-2019 01:15 PM Last Post: justingoldberg
	T21P dial problem	oguzhan	2	8,154	06-20-2018 09:27 AM Last Post: oguzhan

User(s) browsing this thread: 1 Guest(s)

Источник

We are encountering exactly the same issue:

I tried it on a fresh installation of Debian Buster with the ProFTPd version from the Debian repo (1.3.6) and also with Debian Sid (1.3.6c) with TLS enabled (without TLS it works fine).

My config looks like this (only thing changed):

/etc/proftpd/tls.conf:

<IfModule mod_tls.c>
TLSEngine                               on
TLSLog                                  /var/log/proftpd/tls.log
TLSProtocol                             SSLv23

TLSRSACertificateFile                   /etc/ssl/certs/ssl-cert-snakeoil.pem
TLSRSACertificateKeyFile                /etc/ssl/private/ssl-cert-snakeoil.key

TLSOptions                      EnableDiags NoSessionReuseRequired
TLSVerifyClient                         off
TLSRequired                             off
TLSRenegotiate                          off
</IfModule>

In /etc/proftpd/proftpd.conf I added the include for tls.conf.

If I now try to upload a txt file which is bigger than 16kb I get 450 Transfer aborted. Link to file server lost. I get this with the Ftp-Remote-Edit package of Atom (on Ubuntu Desktop) and the integrated FTP client of Coda 2 (Mac OS) but not with any FileZilla.

The logs only contain the following lines:

/var/log/proftpd/proftpd.log:

2020-05-27 15:24:44,933 ****** proftpd[4558] ****** (10.0.8.3[10.0.8.3]): notice: user xyz: aborting transfer: Link to file server lost
2020-05-27 15:25:21,180 ****** proftpd[4614] ****** (10.0.8.3[10.0.8.3]): notice: user xyz: aborting transfer: Link to file server lost

/var/log/proftpd/tls.log:

2020-05-27 15:25:21,045 mod_tls/2.7[4614]: [msg] received protocol record message (5 bytes)
2020-05-27 15:25:21,045 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,142 mod_tls/2.7[4614]: [msg] received protocol record message (5 bytes)
2020-05-27 15:25:21,142 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,158 mod_tls/2.7[4614]: [msg] received protocol record message (5 bytes)
2020-05-27 15:25:21,158 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,158 mod_tls/2.7[4614]: starting TLS negotiation on data connection
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [info] (unknown): before SSL initialization
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [info] accepting: before SSL initialization
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] received protocol record message (5 bytes)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [info] accepting: before SSL initialization
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] received TLSv1.3 'ClientHello' Handshake message (225 bytes)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] 
ClientHello:
  client_version = TLS 1.2
  random:
    gmt_unix_time = Fri Mar 14 20:16:31 1980 (not guaranteed to be accurate)
    random_bytes (28 bytes)
      9621e48c0946951a53e687288ba950a733de11e3cc937f13c0566506
  session_id (32 bytes)
    22dcb1b470cfe2edbd3a987052bddd473b9815aa94fe472dc8e77783c180f199
  cipher_suites (36 bytes)
    TLS_AES_128_GCM_SHA256
    TLS_AES_256_GCM_SHA384
    TLS_CHACHA20_POLY1305_SHA256
    TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
    [unknown/unsupported]
    [unknown/unsupported]
    TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
    TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
    TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
    TLS_RSA_WITH_AES_128_GCM_SHA256
    TLS_RSA_WITH_AES_256_GCM_SHA384
    TLS_RSA_WITH_AES_128_CBC_SHA
    TLS_RSA_WITH_AES_256_CBC_SHA
    SSL_RSA_WITH_3DES_EDE_CBC_SHA
  compression_methods (1 byte)
    None
  extensions (112 bytes)
    extension_type = extended_master_secret (0 bytes)
    extension_type = renegotiate (1 byte)
    extension_type = elliptic_curves (8 bytes)
    extension_type = ec_point_formats (2 bytes)
    extension_type = session_ticket (0 bytes)
    extension_type = signature_algorithms (20 bytes)
    extension_type = key_share (38 bytes)
    extension_type = psk_kex_modes (2 bytes)
    extension_type = supported_versions (5 bytes)

2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [info] accepting: SSLv3/TLS read client hello
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] sent TLSv1.3 'ServerHello' Handshake message (122 bytes)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [info] accepting: SSLv3/TLS write server hello
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] sent TLSv1.3 ChangeCipherSpec message (1 byte)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [info] accepting: SSLv3/TLS write change cipher spec
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [info] accepting: TLSv1.3 write encrypted extensions
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [msg] sent TLSv1.3 'Certificate' Handshake message (768 bytes)
2020-05-27 15:25:21,159 mod_tls/2.7[4614]: [info] accepting: SSLv3/TLS write certificate
2020-05-27 15:25:21,161 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,161 mod_tls/2.7[4614]: [msg] sent TLSv1.3 'CertificateVerify' Handshake message (264 bytes)
2020-05-27 15:25:21,161 mod_tls/2.7[4614]: [info] accepting: TLSv1.3 write server certificate verify
2020-05-27 15:25:21,161 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,161 mod_tls/2.7[4614]: [msg] sent TLSv1.3 'Finished' Handshake message (36 bytes)
2020-05-27 15:25:21,161 mod_tls/2.7[4614]: [info] accepting: SSLv3/TLS write finished
2020-05-27 15:25:21,161 mod_tls/2.7[4614]: [info] accepting: TLSv1.3 early data
2020-05-27 15:25:21,161 mod_tls/2.7[4614]: [info] accepting: TLSv1.3 early data
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [msg] received protocol record message (5 bytes)
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [msg] received protocol record message (5 bytes)
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [info] accepting: TLSv1.3 early data
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [msg] received TLSv1.3 'Finished' Handshake message (36 bytes)
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [info] accepting: SSLv3/TLS read finished
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [info] (unknown): SSLv3/TLS write session ticket
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [msg] sent TLSv1.3 'NewSessionTicket' Handshake message (57 bytes)
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [info] accepting: SSLv3/TLS write session ticket
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [msg] sent TLSv1.3 'NewSessionTicket' Handshake message (57 bytes)
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [info] accepting: SSLv3/TLS write session ticket
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [info] accepting: SSL negotiation finished successfully
2020-05-27 15:25:21,164 mod_tls/2.7[4614]: [msg] received protocol record message (5 bytes)
2020-05-27 15:25:21,180 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)
2020-05-27 15:25:21,180 mod_tls/2.7[4614]: [msg] sent protocol record message (5 bytes)

/var/log/proftpd/xferlog:

Wed May 27 15:25:21 2020 0 10.0.8.3 0 /home/xyz/testfile.txt b _ d r xyz ftps 0 * c
Wed May 27 15:25:21 2020 0 10.0.8.3 0 /home/xyz/testfile.txt b _ i r xyz ftps 0 * i

I tested this with the following file:
testfile.txt

I hope this helps. Please tell me if you need any further information to dig deeper into that problem.

Источник

Hi I can login to the GCE VM with WinSCP using my own username, cannot login as root…this is by default according to Google, and can be changed.

Changed like this:

Step 1: Login SSH and Su Root

# sudo su root

Step 2: Change password Root

#passwd root

Step 3: Config SSHD allow Root login

#nano /etc/ssh/sshd_config
PermitRootLogin yes
PasswordAuthentication yes

#service sshd restart (I used ssh as I'm using ubuntu and sshd wouldn't work)

Tried to login as root via WinSCP but I get

«Received too large (1349281121 B) SFTP packet. Max supported packet
size is 1024000 B. The error is typically caused by message printed
from startup script (like .profile). The message may start with
‘Plea’.» Cannot initialize SFTP protocol. Is the host running a SFTP
server?»

Any ideas?

asked Oct 29, 2015 at 8:28

Received too large SFTP packet. Max supported packet size is 102400 B

Cause:
This problem can arise when your .bashrc file is printing data to the screen (e.g.archey, screenfetch). The .bashrc file runs every time any console shell is initialized.

Solution:
Simply move any scripts that generate output from your .bashrc file to your .bash_profile. The .bash_profile only runs when you create a physical shell session.

answered May 9, 2016 at 16:09

coddiwomplefrogcoddiwomplefrog

7591 gold badge6 silver badges18 bronze badges

NOTE: Just for anyone who comes across this and simply wants to copy files and doesn’t matter what file protocol they use. You can just switch file protocol from SFTP to SCP to avoid this issue. Thought it might be worth a mention.

answered May 17, 2016 at 9:30

Luke RixsonLuke Rixson

5974 silver badges20 bronze badges

If you used Ubuntu linux and try to connect the server then «Please login as the Ubuntu user» you should sftp as the ubuntu user, not as root.

Try that, hope it will work for you!

Thanks!

answered Jul 22, 2017 at 13:16

Hmmm, I added this in WinSCP in advanced settings under «protocol options»:
sudo /usr/lib/openssh/sftp-servers

I can login with my own username and move files now. Although not exactly sure how this works, I think it somehow changes you to root user at login?

More info: https://winscp.net/eng/docs/faq_su

answered Oct 29, 2015 at 8:53

EricEric

1691 gold badge1 silver badge6 bronze badges

See WinSCP article on Received too large (… B) SFTP packet. Max supported packet size is 102400 B

If … (from the subject [error message]) is a very large number then the problem is typically caused by a message printed from some profile/logon script. It violates an SFTP protocol. Some of these scripts are executed even for non-interactive (no TTY) sessions, so they cannot print anything (nor ask user to type something).

answered Oct 29, 2015 at 9:03

Martin PrikrylMartin Prikryl

181k53 gold badges461 silver badges933 bronze badges

To add to @ThatOneCoder’s answer on the cause being too much output from .bashrc: in e.g. Ubuntu, there is also the system wide /etc/bash.bashrc that might be «too wordy» and cause the Received too large SFTP packet error.

It’s a «system wide .bashrc», and if you want to execute code for all logging in, that’s one location to place it. If you nixed ~/.bashrc and still get the error, check the contents of /etc/bash.bashrc.

answered Nov 5, 2021 at 16:51

BytechBytech

1,1157 silver badges22 bronze badges

It is happening because you haven’t given shell access permission to the user.

answered Sep 20, 2022 at 22:48

I faced the same issue trying to login on my ubuntu 16.04 EC2 server as «root» via WinSCP. I spent a lot of time trying to fix it but in the end a simple workaround worked for me.

I ssh into the instance using PuTTY with the username «ubuntu». After this I typed

sudo -i

and with this the user was changed to root.

answered Apr 5, 2019 at 15:20

Источник

Покажи фотку настроек БИОСа, где написано «грузиться по PXE». Само слово PXE там есть? Какие ещё слова есть кроме PXE?

: pxe.jpg (38 КБ) 21861 просмотр

У хайпер-в как бы нет биоса, но тем не менее

: bios.png (24.37 КБ) 21861 просмотр

У клиентов стоят старенькие тазики, там везде по-разному написано, что-то типа LAN Boot rom enabled.
В любом случае настройки биоса на клиентах не трогались.

Маршрутизатор есть. 1шт. Тупо роутинг.
Воткнул клиента в сеть с втваре, такая же ошибка. Т.е. Роутер не причем.

попробую wireshark’ом посмотреть, что происходит.

aka писал(а): ↑

Пн дек 11, 2017 5:42 pm

А работающий лог tftpd32 покажи.

Connection received from 192.168.1.121 on port 2070 [12/12 11:22:40.251]
Read request for file <5.6.12wtware.pxe>. Mode octet [12/12 11:22:40.251]
OACK: <tsize=16282,> [12/12 11:22:40.251]
Using local port 53868 [12/12 11:22:40.251]
Peer returns ERROR <TFTP Aborted> -> aborting transfer [12/12 11:22:40.251]
Connection received from 192.168.1.121 on port 2071 [12/12 11:22:40.267]
Read request for file <5.6.12wtware.pxe>. Mode octet [12/12 11:22:40.267]
Using local port 53870 [12/12 11:22:40.267]
<5.6.12wtware.pxe>: sent 32 blks, 16282 bytes in 0 s. 0 blk resent [12/12 11:22:40.563]
Connection received from 192.168.1.121 on port 57089 [12/12 11:22:40.595]
Read request for file <5.6.1279996ad9-0f5b-7c43-b47f-f236ead073c9>. Mode octet [12/12 11:22:40.595]
File <5.6.1279996ad9-0f5b-7c43-b47f-f236ead073c9> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57090 [12/12 11:22:40.595]
Read request for file <5.6.121-00-15-5d-e6-8c-19>. Mode octet [12/12 11:22:40.595]
File <5.6.121-00-15-5d-e6-8c-19> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57091 [12/12 11:22:40.595]
Read request for file <5.6.12C0A80179>. Mode octet [12/12 11:22:40.595]
File <5.6.12C0A80179> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57092 [12/12 11:22:40.595]
Read request for file <5.6.12C0A8017>. Mode octet [12/12 11:22:40.595]
File <5.6.12C0A8017> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57093 [12/12 11:22:40.595]
Read request for file <5.6.12C0A801>. Mode octet [12/12 11:22:40.595]
File <5.6.12C0A801> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57094 [12/12 11:22:40.595]
Read request for file <5.6.12C0A80>. Mode octet [12/12 11:22:40.595]
File <5.6.12C0A80> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57095 [12/12 11:22:40.595]
Read request for file <5.6.12C0A8>. Mode octet [12/12 11:22:40.595]
File <5.6.12C0A8> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57096 [12/12 11:22:40.595]
Read request for file <5.6.12C0A>. Mode octet [12/12 11:22:40.595]
File <5.6.12C0A> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57097 [12/12 11:22:40.595]
Read request for file <5.6.12C0>. Mode octet [12/12 11:22:40.595]
File <5.6.12C0> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57098 [12/12 11:22:40.595]
Read request for file <5.6.12C>. Mode octet [12/12 11:22:40.595]
File <5.6.12C> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:40.595]
Connection received from 192.168.1.121 on port 57099 [12/12 11:22:40.595]
Read request for file <5.6.12pxe.cfg>. Mode octet [12/12 11:22:40.610]
OACK: <tsize=182,> [12/12 11:22:40.610]
Using local port 53882 [12/12 11:22:40.610]
<5.6.12pxe.cfg>: sent 1 blk, 182 bytes in 0 s. 0 blk resent [12/12 11:22:40.610]
Connection received from 192.168.1.121 on port 57100 [12/12 11:22:40.610]
Read request for file <5.6.12packages/kernel>. Mode octet [12/12 11:22:40.610]
OACK: <tsize=2519280,> [12/12 11:22:40.610]
Using local port 53883 [12/12 11:22:40.610]
<5.6.12packageskernel>: sent 4921 blks, 2519280 bytes in 4 s. 0 blk resent [12/12 11:22:44.434]
Connection received from 192.168.1.121 on port 57101 [12/12 11:22:44.434]
Read request for file <5.6.12packages/initrd>. Mode octet [12/12 11:22:44.434]
OACK: <tsize=3444748,> [12/12 11:22:44.434]
Using local port 53884 [12/12 11:22:44.434]
<5.6.12packagesinitrd>: sent 6729 blks, 3444748 bytes in 5 s. 0 blk resent [12/12 11:22:49.688]
Connection received from 192.168.1.121 on port 59971 [12/12 11:22:52.562]
Uncorrect message [12/12 11:22:52.562]
Connection received from 192.168.1.121 on port 53472 [12/12 11:22:52.562]
Read request for file <5.6.12packageslib6>. Mode octet [12/12 11:22:52.562]
OACK: <tsize=2001023,> [12/12 11:22:52.562]
Using local port 53886 [12/12 11:22:52.562]
<5.6.12packageslib6>: sent 3909 blks, 2001023 bytes in 5 s. 1 blk resent [12/12 11:22:57.144]
Connection received from 192.168.1.121 on port 52211 [12/12 11:22:57.191]
Read request for file <Everyonesource.wtc>. Mode octet [12/12 11:22:57.191]
OACK: <tsize=2500,> [12/12 11:22:57.191]
Using local port 53887 [12/12 11:22:57.191]
<Everyonesource.wtc>: sent 5 blks, 2500 bytes in 0 s. 0 blk resent [12/12 11:22:57.191]
Connection received from 192.168.1.121 on port 43161 [12/12 11:22:57.191]
Read request for file <Everyonelist.wtc>. Mode octet [12/12 11:22:57.191]
OACK: <tsize=1322,> [12/12 11:22:57.191]
Using local port 53888 [12/12 11:22:57.191]
<Everyonelist.wtc>: sent 3 blks, 1322 bytes in 0 s. 0 blk resent [12/12 11:22:57.191]
Connection received from 192.168.1.121 on port 33744 [12/12 11:22:57.191]
Read request for file <Terminals0.15.5D.E6.8C.19config.wtc>. Mode octet [12/12 11:22:57.191]
File <Terminals0.15.5D.E6.8C.19config.wtc> : error 3 in system call CreateFile Ñèñòåìå íå óäàåòñÿ íàéòè óêàçàííûé ïóòü. [12/12 11:22:57.191]
Connection received from 192.168.1.121 on port 50112 [12/12 11:22:57.191]
Read request for file <Terminals0.15.5D.E6.8C.19.wtc>. Mode octet [12/12 11:22:57.191]
File <Terminals0.15.5D.E6.8C.19.wtc> : error 2 in system call CreateFile Íå óäàåòñÿ íàéòè óêàçàííûé ôàéë. [12/12 11:22:57.191]
Connection received from 192.168.1.121 on port 33559 [12/12 11:22:57.207]
Read request for file <Everyonedefault.wtc>. Mode octet [12/12 11:22:57.207]
OACK: <tsize=1989,> [12/12 11:22:57.207]
Using local port 53891 [12/12 11:22:57.207]
<Everyonedefault.wtc>: sent 4 blks, 1989 bytes in 0 s. 0 blk resent [12/12 11:22:57.207]
Connection received from 192.168.1.121 on port 43633 [12/12 11:22:57.207]
Read request for file <Everyoneall.wtc>. Mode octet [12/12 11:22:57.207]
OACK: <tsize=268,> [12/12 11:22:57.207]
Using local port 53892 [12/12 11:22:57.207]
<Everyoneall.wtc>: sent 1 blk, 268 bytes in 0 s. 0 blk resent [12/12 11:22:57.207]
Connection received from 192.168.1.121 on port 42486 [12/12 11:22:57.207]
Read request for file <Everyonewtware.lic>. Mode octet [12/12 11:22:57.207]
OACK: <tsize=2480,> [12/12 11:22:57.207]
Using local port 53893 [12/12 11:22:57.207]
<Everyonewtware.lic>: sent 5 blks, 2480 bytes in 0 s. 0 blk resent [12/12 11:22:57.222]

PS. Wtware крутится на windows server 2016. Приезжали обновления на сервер недавно, м.б. MS опять что-нибудь поломали.

Источник