Has smbclient behavior changed from 2.2.8a to 3.0.0?
sfrench at us.ibm.com
Wed Nov 5 17:16:08 GMT 2003
>Forcing smbclient to connect to port 139
>*should* fix the problem, since NetServerEnum2 is supported on port 139.
>If you grab a trace of smbclient 3.0.9, please verify that it is
>connecting on 139 rather than 445.
This line of investigation based on the port number makes no sense.
NetServerEnum2 (and the other RAP calls) should be the same on both 139 and
445 - at some level NetServerEnum2 is just an SMB transact and no one has
theorized that basic SMB operations (other than session establishment) act
differently on the two ports. The 139 and 445 calls end up in the same
place. Other theories - security settings, restrictions on client
computer name, restrictions on anonymous connections etc. seem more likely.
Senior Software Engineer
Linux Technology Center - IBM Austin
email: sfrench at-sign us dot ibm dot com
More information about the samba-technical