[Samba] 答复: ??????: Is the "\\x.x.x.x" type tree connect request a client related feature?

Rowland Penny rpenny at samba.org
Sun Jan 22 11:46:36 UTC 2017

On Sun, 22 Jan 2017 10:04:29 +0000
Chenyehua via samba <samba at lists.samba.org> wrote:

> Thanks for your reply, Louis
> However, I am still blocked by this problem now. !-_-
> I tried to set the samba server as the DNS server and visit the
> shared folder by input "\\aaa.bb.com" at windows 7 client. In some
> cases it works and will not fail. However the similar abnormal
> phenomenon also occasionally happens (especially at changing the
> authentication, such as local to ldap): 1) I can pass the
> authentication and see the shared folder, but when I try to open the
> folder , it fails with a windows error message like "cannot find the
> route to the network". It may recover to normal later (means I can
> open that folder) 2) I have collected the wireshark record and find
> it may due to the same reason:  NT_STATUS_BAD_NETWORK_NAME Part
> records in the Wireshark:
>   > Tree connect request Tree\\aaa.bb.com\IPC$
>   >  Tree connect response : SUCCESS
>   > Tree connect request Tree \\aaa.bb.com
>   >  Tree connect response : NT_STATUS_BAD_NETWORK_NAME
>   > Tree connect request Tree \\aaa.bb.com
>      Tree connect response : NT_STATUS_BAD_NETWORK_NAME
>   ...
>   ...
> In your last email, you mentioned that "after the "badlock" patches,
> MS applies some checks. ". 1) Do you mean that sending "\\serverpath"
> type tree connect request is some kind of check sent by windows 7
> relevant to the badlock patches? And What does this check for? 2) Are
> those checks reasonable and normal? As they have affected the normal
> use of the samba share in my case. 3) Are there any solutions to my
> problem? 4) the badlock bug -- do you mean the bug which was
> discovered by Stefan Metzmacher, disclosed in 2016-04-12, and
> referenced by CVE-2016-2118 for samba, CVE-2016-0128/ MS16-047 for
> windows ?

Though there have been references to individual smb.conf lines, it
seems that the full smb.conf hasn't been posted. From what has been
posted, I still don't know how Samba is being run, so I think the next
step is for the OP to post their full smb.conf.


More information about the samba mailing list