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

[Chenyehua]

Hi folks

   I face a problem when using the samba share, Here is the detail:

1) Phenomenon

   In windows 7, sometimes, I type the samba server ip address and can see the shared folder. (the samba version is 4.3.11)

a、However when I try to open the shared folder, it fails with a windows error message like “please check the spelling of the name, or some problem may related to the network”, and returns the error code 0x80070035(cannot find the network path).

The shared folder may be opened successfully in a while. Or it will always fail in a long period with the error returned above(not sure if it will automatically recover finally)

b、The problem in a may be client-related and occasionally appeared. At some other windows 7 environments, it may never happen(at least I have tried dozens of times, but it turns out normal each time)



2) Analysis

a、 Something abnormal can be found in the samba log as below:

[2016/12/26 22:15:35.238956,  0, pid=605906, effective(0, 0), real(0, 0)] ../source3/param/loadparm.c:3240(process_usershare_file)

  process_usershare_file: share name //172.16.37.96 contains invalid characters (any of %<>*?|/\+=;:",)

[2016/12/26 22:15:35.238973,  3, pid=605906, effective(0, 0), real(0, 0)] ../source3/param/service.c:249(find_service)

  find_service() failed to find service //172.16.37.96

[2016/12/26 22:15:35.238985,  3, pid=605906, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_tcon.c:266(smbd_smb2_tree_connect)

  smbd_smb2_tree_connect: couldn't find service //172.16.37.96

[2016/12/26 22:15:35.239004, 50, pid=605906, effective(0, 0), real(0, 0), class=tevent] ../lib/util/tevent_debug.c:66(samba_tevent_debug)

  s3_tevent: Schedule immediate event "tevent_req_trigger": 0x56007af6bd80

[2016/12/26 22:15:35.239021, 50, pid=605906, effective(0, 0), real(0, 0), class=tevent] ../lib/util/tevent_debug.c:66(samba_tevent_debug)

  s3_tevent: Cancel immediate event 0x56007af6bd80 "tevent_req_trigger"

[2016/12/26 22:15:35.239035, 10, pid=605906, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_server.c:2789(smbd_smb2_request_error_ex)

  smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_BAD_NETWORK_NAME] || at ../source3/smbd/smb2_tcon.c:135

[2016/12/26 22:15:35.239053, 10, pid=605906, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_server.c:2680(smbd_smb2_request_done_ex)

  smbd_smb2_request_done_ex: idx[1] status[NT_STATUS_BAD_NETWORK_NAME] body[8] dyn[yes:1] at ../source3/smbd/smb2_server.c:2837



b、Something abnormal may also be observed in the wireshark:

the tree connect requests of the normal case may follow like this order:

Tree connect request Tree \\172.16.37.96\IPC$

Tree connect request Tree \\172.16.37.96\sharedfolder1

Tree connect request Tree \\172.16.37.96\sharedfolder2

…

…



the tree connect requests of the abnormal case may follow like this order:

Tree connect request Tree \\172.16.37.96\IPC$

Tree connect request Tree \\172.16.37.96

Tree connect request Tree \\172.16.37.96

…

…



3) Confused

I am confused about the abnormal facts above and have some questions:

When and Why does the windows 7 sometimes send a pure ip address tree connect request (like \\x.x.x.x) to the samba server after the IPC$ request?

Is it fine for the samba 4.3.11 to accept the pure ip address tree connect request?

Is this really a client-related phenomenon?

Are there any solutions about this problem?





Thanks

Best regards!









-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!