I'm trying to connect to share "backup" on server "ran", which has a path of
"/mnt/backup/machines/%m" in smb.conf. I'm connecting with machine "lodur" with
ip 192.168.97.91. This used to work, but just now i noticed it doesn't anymore.
It tries to use path "/mnt/backup/machines/192.168.97.91" instead of
I also have a "log file = /var/log/samba/%m.log" which now logs to
"/var/log/samba/192.168.97.91.log" instead of "/var/log/samba/lodur.log" as it
used to. I see three other "<ip>.log" files, but most of the other machines
(about 10-20) seem to work fine.
I will attach my config and a log file.
Created attachment 743 [details]
The log file from when "lodur" tries to connect.
Created attachment 744 [details]
My config-file on "ran".
I should add that nmbd is running fine on lodur:
kreiger@ran:~$ nmblookup -A 192.168.97.91
params.c:pm_process() - Processing configuration file
added interface ip=192.168.97.161 bcast=192.168.97.255 nmask=255.255.255.0
Looking up status of 192.168.97.91
LODUR <00> - B <ACTIVE>
LODUR <03> - B <ACTIVE>
LODUR <20> - B <ACTIVE>
IMCODE <00> - <GROUP> B <ACTIVE>
IMCODE <1e> - <GROUP> B <ACTIVE>
MAC Address = 00-00-00-00-00-00
Now, a couple of hours later, it works again! However, that doesn't mean i
advocate closing this bug. I'd like to know what happened.
when using SMB via TCP (port 445) the netbios name is not transmitted and in
that case it is normal that %m ist not the name but the IP instead
All right, thank you. What could have caused this to temporarily use port 445?