© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Here's a different perspective. Accessing the Win10 machine again:
tester@vub1904:~$ smbclient -L vwin10 -U smbuser
Unable to initialize messaging context
Enter WORKGROUP\smbuser's password:
Sharename Type Comment
--------- ---- -------
ADMIN$ Disk Remote Admin
C$ Disk Default share
Documents Disk
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
Shared Disk
Users Disk
Reconnecting with SMB1 for workgroup listing.
protocol negotiation failed: NT_STATUS_
Unable to connect with SMB1 -- no workgroup available
tester@vub1904:~$ smbclient //vwin10/Shared -U smbuser
Unable to initialize messaging context
Enter WORKGROUP\smbuser's password:
Try "help" to get a list of possible commands.
smb: \>
And the equivalent of smbstatus on Windows:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\WINDOWS\
Dialect ClientComputerName
------- ------------------
3.1.1 192.168.1.177
smbclient -L automatically goes to SMB1 to get the share listing then tells me it cannot connect to these which makes sense in that state.
Yet I can use smbclient itself to access the share if I specify it. This is what gvfsd-smb-browse needs to do. Drop down to NT1 to get the share list which it's doing now then release it and allow the normal smb negotiation to take place.