On Thu, Feb 22, 2018 at 05:31:19AM -0500, Jason Mitchell wrote:
> 
> > On Feb 21, 2018, at 9:16 AM, Stephen Borrill <net...@precedence.co.uk> 
> > wrote:
> > 
> >> On Wed, 21 Feb 2018, Patrick Welche wrote:
> >> I haven't tried SMB in years (it definitely worked against a different
> >> windows server). Quick attempt on -current/amd64 gets:
> >> 
> >> $ smbutil -v login -I wibble //prlw1@wibble
> >> Password:
> >> smbutil: can't get handle to requester (no /dev/nsmb* device available)
> >> smbutil: can't get handle to requester (no /dev/nsmb* device available)
> >> smbutil: could not login to server WIBBLE: syserr = Invalid argument
> > 
> > I guess it is possible the error messages are spurious and the real problem 
> > is that SMBv1 is disabled on the target (unless SMBFS supported SMBv2 or 
> > later).
> > 
> > -- 
> > Stephen
> > 
> If this is the case, then the following might help. It talks about how to 
> enable SMBv1 on Windows 7 and later:
> 
> https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

Thank you for your suggestions!

- the test server is an ancient real pentium running windows server 2003, so
  I don't think it knows about SMBv2.
- as pointed out in private email, I should have been root given the
  permissions on /dev/nsmb*

Now when I try, I see

# smbutil -v login -I wibble //prlw1@wibble
Password:
smbutil: connection already exists
# smbutil lc
SMB connections:
None

        error = smb_ctx_lookup(ctx, level, 0);
        if (error == 0) {
                smb_error("connection already exists", error);
                exit(0);
        }

smb_ctx_lookup does complete, and ctx looks sane, but lc doesn't list
anything.


Cheers,

Patrick
  • SMB Patrick Welche
    • Re: SMB Stephen Borrill
      • Re: SMB Jason Mitchell
        • Re: SMB Patrick Welche

Reply via email to