I'm now running mc-4.8.26-1.fc33.x86_64 and I cannot connect to my local
SMB/Samba/CIFS shares.
I get:
{{{
Cannot chdir to "/smb://localhost/tmp"
}}}
Here's my entire samba server config:
{{{
[global]
workgroup = MYGROUP
security = user
passdb backend = tdbsam
guest account = nobody
map to guest = Bad User
printing = bsd
printcap name = /dev/null
load printers = no
cups options = raw
disable spoolss = yes
# log files split per-machine:
log file = /var/log/samba/log.%m
[TMP]
path = /tmp
public = yes
only guest = yes
writable = yes
printable = no
}}}
smbclient //localhost/tmp works perfectly.
--
Ticket URL: <http://www.midnight-commander.org/ticket/4288>
Midnight Commander <https://midnight-commander.org>
Midnight Development Center
Comment (by birdie):
Samba doesn't log anything as if MC doesn't even attempt to connect
properly.
--
Ticket URL: <http://www.midnight-commander.org/ticket/4288#comment:1>
Comment (by birdie):
At log level = 3 I get this:
{{{
[2021/09/07 18:04:23.005022, 3]
../../source3/smbd/oplock.c:1427(init_oplocks)
init_oplocks: initializing messages.
[2021/09/07 18:04:23.253900, 3]
../../source3/smbd/process.c:1956(process_smb)
Transaction 0 of length 76 (0 toread)
[2021/09/07 18:04:23.253950, 2]
../../source3/smbd/reply.c:707(reply_special)
netbios connect: name1=LOCALHOST 0x20 name2= 0x0
[2021/09/07 18:04:23.254707, 2]
../../source3/smbd/reply.c:747(reply_special)
netbios connect: local=localhost remote=, name type = 0
[2021/09/07 18:04:23.254916, 3]
../../source3/smbd/process.c:1956(process_smb)
Transaction 0 of length 168 (0 toread)
[2021/09/07 18:04:23.254947, 3]
../../source3/smbd/process.c:1548(switch_message)
switch message SMBnegprot (pid 162581) conn 0x0
[2021/09/07 18:04:23.255205, 3]
../../source3/smbd/negprot.c:636(reply_negprot)
Requested protocol [PC NETWORK PROGRAM 1.0]
[2021/09/07 18:04:23.255222, 3]
../../source3/smbd/negprot.c:636(reply_negprot)
Requested protocol [MICROSOFT NETWORKS 1.03]
[2021/09/07 18:04:23.255229, 3]
../../source3/smbd/negprot.c:636(reply_negprot)
Requested protocol [MICROSOFT NETWORKS 3.0]
[2021/09/07 18:04:23.255235, 3]
../../source3/smbd/negprot.c:636(reply_negprot)
Requested protocol [LANMAN1.0]
[2021/09/07 18:04:23.255241, 3]
../../source3/smbd/negprot.c:636(reply_negprot)
Requested protocol [LM1.2X002]
[2021/09/07 18:04:23.255248, 3]
../../source3/smbd/negprot.c:636(reply_negprot)
Requested protocol [Samba]
[2021/09/07 18:04:23.255254, 3]
../../source3/smbd/negprot.c:636(reply_negprot)
Requested protocol [NT LANMAN 1.0]
[2021/09/07 18:04:23.255260, 3]
../../source3/smbd/negprot.c:636(reply_negprot)
Requested protocol [NT LM 0.12]
[2021/09/07 18:04:23.255317, 3]
../../source3/smbd/negprot.c:757(reply_negprot)
reply_negprot: No protocol supported !
[2021/09/07 18:04:23.255505, 3]
../../source3/smbd/server_exit.c:220(exit_server_common)
Server exit (no protocol supported)
}}}
--
Ticket URL: <http://www.midnight-commander.org/ticket/4288#comment:2>
Comment (by birdie):
This could be fixed by setting:
{{{
server min protocol = CORE
client min protocol = CORE
}}}
but I really really dislike this solution. It makes Samba use a insecure
protocol.
--
Ticket URL: <http://www.midnight-commander.org/ticket/4288#comment:3>
* status: new => closed
* component: mc-core => mc-vfs
* resolution: => duplicate
* milestone: Future Releases =>
Comment:
Closed as duplicate of #1.
--
Ticket URL: <http://www.midnight-commander.org/ticket/4288#comment:4>