Код ошибки 49152

Здравствуйте!

Есть два сервера и клиент. Один сервер работает на AltLinux 6 (в дальнейшем — AL6), другой — на BaseAlt 8 (BA8). Клиент — на WinXP.
Айпи AL6 — 172.30.54.1
Айпи BA8 — 172.30.54.100
Айпи WinXP — 172.30.54.144

Подключаюсь к клиенту из AL6 на адрес smb://172.30.54.144 запрашивает логин и пароль. Ввожу User и pass. Пускает.
Подключаюсь к клиенту из BA8 на адрес smb://172.30.54.144 запрашивает логин и пароль. Ввожу User и pass. Не пускает.

Стал выяснять разницу между самбами на AL6 и BA8. AL6 работает на версии 3.5.14, а BA8 — на 4.7.12.

Использовал tcpdump чтобы сравнить запросы к клиенту.
Вот такая команда: /usr/sbin/tcpdump -vv -i enp5s0 ip dst 172.30.54.144 and not dst port 3389

Чтобы не утомить, напишу только часть ответа tcpdump в AL6.

15:09:05.156500 IP (tos 0x0, ttl 64, id 5071, offset 0, flags [DF], proto TCP (6), length 234)
    SERVER.localdomain.57318 > 172.30.54.144.netbios-ssn: Flags [P.], cksum 0xc5aa (incorrect -> 0x8e81), seq 72:266, ack 5, win 46, length 194
>>> NBT Session Packet
NBT Session Message
Flags=0x0
Length=190 (0xbe)

А это ответ от tcpdump в BA8:

14:02:22.168307 IP (tos 0x0, ttl 64, id 46244, offset 0, flags [DF], proto TCP (6), length 256)
    172.30.54.100.48298 > 172.30.54.144.netbios-ssn: Flags [P.], cksum 0x582f (correct), seq 72:288, ack 5, win 229, length 216
>>> NBT Session Packet
NBT Session Message
Flags=0x0
Length=212 (0xd4)

Смотрю, разница в том, что AL6 не просит:

Dialect=SMB 2.002
Dialect=SMB 2.

Решил сделать то же самое и в BA8, для этого в конфиг smb.conf прописал:

server min protocol = NT1
client max protocol = NT1
Как и полагается, после запустил testparm, нет проблем, дальше — service smb restart
Итог: опять же не пускает к клиенту.
Посмотрел на tcpdump:

15:01:28.579802 IP (tos 0x0, ttl 64, id 24549, offset 0, flags [DF], proto TCP (6), length 234)
    172.30.54.100.48830 > 172.30.54.144.netbios-ssn: Flags [P.], cksum 0x113b (correct), seq 72:266, ack 5, win 229, length 194
>>> NBT Session Packet
NBT Session Message
Flags=0x0
Length=190 (0xbe)

Смотрю, различий в Dialect в запросах между AL6 и BA8 уже нет, но все равно AL6 клиент пускает, а BA8 — нет из-за ошибки в авторизации.

Кто подскажет мне в чем разница между этими самбами? Разбирать HEX-строчки не умею…

IIS has a limit for the size of the files users can upload to an application. If the file size exceeds the limit, the application will throw “Error in HTTP request, received HTTP status 413 (Request Entity Too Large)” error.

The default file upload size is 49 KB (49152 bytes). The application records the log below if user tries to upload a file that is bigger than this size.

Why this issue occurs for SSL sites? The reason is that the request body must be preloaded during the SSL handshake process.

Solution

The quickest solution is to increase the upload size limit. IIS uses uploadReadAheadSize parameter in applicationHost.config and web.config files to control this limit.

uploadReadAheadSize
Optional uint attribute.
Specifies the number of bytes that a Web server will read into a buffer and pass to an ISAPI extension or module. This occurs once per client request. The ISAPI extension or module receives any additional data directly from the client. The value must be between 0 and 2147483647.
The default value is 49152.

Server Runtime

Steps to change the value of this parameter:

1. Open IIS Manager
2. Select the site
3. Double click “Configuration Editor”
4. Select system.webServer and then serverRuntime
5. Modify the uploadReadAheadSize value
6. Click “Apply”

You may also want to change maxRequestEntityAllowed parameter. It specifies the maximum number of bytes allowed in the request body.

Note: In another case, the recommendations above didn’t work to solve 413 error. Please check this post for more information

I have a media-player, which used to connect to my main computer running Samba without a problem. It is running an old version of embedded Linux (kernel 2.6.22.19-27) and has CIFS.

At some point, after I upgraded Samba software on the server (samba-4.6.8 running on FreeBSD-10.4 at the moment), the player lost this ability — it can still list the same exported shares, but can no longer open anything: «wrong credentials».

An SMB-capable application on my phone opens the same folders just fine (using the same credentials)…

Is there some option I need to explicitly turn on the server to enable some sort of compatibility mode with old clients?

Update: based on the suggestion by @Tin, I added the following line to the [global]-section of smb4.conf:

max protocol = NT1

Unfortunately, this hasn’t changed things — I can still connect from most systems except the media player, which still tells me, my credentials are no good.

Using tcpdump on the server I captured the following exchange:

    SMB PACKET: SMBnegprot (REQUEST)
    SMB Command   =  0x72
    Error class   =  0x0
    Error code    =  0 (0x0)
    Flags1        =  0x0
    Flags2        =  0x1
    Tree ID       =  0 (0x0)
    Proc ID       =  1283 (0x503)
    UID           =  0 (0x0)
    MID           =  1 (0x1)
    Word Count    =  0 (0x0)
    smb_bcc=12
    Dialect=NT LM 0.12

To which the server responds:

SMB PACKET: SMBnegprot (REPLY)
SMB Command   =  0x72
Error class   =  0x0
Error code    =  0 (0x0)
Flags1        =  0x80
Flags2        =  0x3
Tree ID       =  0 (0x0)
Proc ID       =  1283 (0x503)
UID           =  0 (0x0)
MID           =  1 (0x1)
Word Count    =  17 (0x11)
NT1 Protocol
DialectIndex=0 (0x0)
SecMode=0x3
MaxMux=50 (0x32)
NumVcs=1 (0x1)
MaxBuffer=16644 (0x4104)
RawSize=65536 (0x10000)
SessionKey=0xA4AA
Capabilities=0x80F3FD
ServerTime=Sun Oct  1 18:00:38 2017
TimeZone=240 (0xf0)
CryptKey=Data: (1 bytes)
...

The client then says:

    SMB PACKET: SMBsesssetupX (REQUEST)
    SMB Command   =  0x73
    Error class   =  0x0
    Error code    =  0 (0x0)
    Flags1        =  0x0
    Flags2        =  0x1
    Tree ID       =  0 (0x0)
    Proc ID       =  1283 (0x503)
    UID           =  0 (0x0)
    MID           =  2 (0x2)
    Word Count    =  13 (0xd)
    Com2=0xFF
    Res1=0x0
    Off2=0 (0x0)
    MaxBuffer=16644 (0x4104)
    MaxMpx=50 (0x32)
    VcNumber=0 (0x0)
    SessionKey=0x0
    CaseInsensitivePasswordLength=24 (0x18)
    CaseSensitivePasswordLength=24 (0x18)
    Res=0x0
    Capabilities=0x80D0DC
    Pass1&Pass2&Account&Domain&OS&LanMan=
    smb_bcc=179
    ...

and finally the server:

SMB PACKET: SMBsesssetupX (REPLY)
SMB Command   =  0x73
Error class   =  0x6D
Error code    =  49152 (0xc000)
Flags1        =  0x80
Flags2        =  0x3
Tree ID       =  0 (0x0)
Proc ID       =  1283 (0x503)
UID           =  0 (0x0)
MID           =  2 (0x2)
Word Count    =  0 (0x0)
NTError = STATUS_LOGON_FAILURE
smb_bcc=0

What is going on?

Update: The way I can mount anything is by creating an account with empty password (smbpasswd -n ...) and editing smb.conf to allow null passwords.