search for: 5msecs

...available >> >> But, it would be good if you could tell "smbclient" that you don't >> want it to check for NetBIOS which means you would not get an ERROR >> code. > The code in 4.4.x is quite sophisticated, in that is by > default tries port 445 and then 5msecs later tries 139. > > So it should be trying 445 by default. What is your > smb.conf set to, and can you post a debug level 10 log > from this smbclient command ? I solved the problem a couple of hours ago. Well I am using Samba 3.6.x version and after I installed Samba 4.4.x it worke...

Hello, I have noticed that smbclient returns an error code when a windows server has disabled NetBIOS, but should it do this, if you know NetBIOS has been disabled. I think there should be a flag to indicate that you don't want to check port 139 (NetBIOS). For example the following command which tries to connect to a Windows server with NetBIOS disabled returns an ERROR! $ smbclient -L

...disabled -- no workgroup available > > But, it would be good if you could tell "smbclient" that you don't > want it to check for NetBIOS which means you would not get an ERROR > code. The code in 4.4.x is quite sophisticated, in that is by default tries port 445 and then 5msecs later tries 139. So it should be trying 445 by default. What is your smb.conf set to, and can you post a debug level 10 log from this smbclient command ?