Steve, That would be great. Please also look at the -L option too, as that should default to 139 as well. (Sort of... it's not necessary for listing shares.)
The -p option should override the defaults in any case, though. There are folks who use port-redirection (for SSH links to the server, etc.). They'd want -p to be authoritative, rather than just explicit. :) Thanks! Chris -)----- On Mon, Jan 06, 2003 at 11:33:40AM -0600, Steve Langasek wrote: > On Mon, Jan 06, 2003 at 11:08:32AM -0600, Christopher R. Hertel wrote: > > > So, smbclient should default to using port 139 for the NetServerEnum2 > > calls (-L option) unless -p is actually specified. Basically, the same > > problem as -M. > > Ok, that was the same conclusion I arrived at. I'll put together a > patch to make 'smbclient -M' force a connection to port 139. > > > In your example, though, you specify both -M and -p. Personally, I think > > that in this case smbclient is doing the right thing. If I enter > > 'smbclient -M server -p 10973', then I would expect smbclient to try > > sending the message to that port. The defaults should be 'best normal > > behavior' but smbclient is much more useful if I can bend it to my will. > > Well, the -p option was added only for the purpose of being explicit. In > 3.0, port 445 is currently the default port for *all* operations, > including smbclient -M. So the code does need to change if -M needs port > 139. > > -- > Steve Langasek > postmodern programmer -- Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- [EMAIL PROTECTED] OnLineBook -- http://ubiqx.org/cifs/ -)----- [EMAIL PROTECTED]
