Ingo Asche
2022-Dec-07 13:42 UTC
[Samba] File server joined to a samba domain accessed by windows 10-11 clients, works via ip no via dns name
By the way: Just checked accessing on of the shares via IP. It's the same like your case: The share opens. Never checked that... Regards Ingo https://github.com/WAdama Ingo Asche via samba schrieb am 07.12.2022 um 10:58:> Hi Travis, > > just read "Synology"... > > As I have not complete read you first mails: > The combination with the Synology's is with DSM 7.1.1 and Samba 4.17.3? > > Shares with groups rights are not accessible, but if you give the user > direct rights it works? > > I have the same problem with this combination. An older device with > DSM 6.2.4 still works. > > I've already opened a case with Synology and delivered logs and > Wireshark captures. > > By the way Synology will release a new SMB service on the 13th. > > Regards > Ingo > https://github.com/WAdama > > Rowland Penny via samba schrieb am 07.12.2022 um 08:59: >> >> >> On 06/12/2022 22:48, Travis Wenks wrote: >>> I'm sorry guys I don't mean to spam the group. >>> I logged back into the pc after rejoining. >>> Attempted to access the share again via ip works fine >>> via fqdn still fails. >>> I could not find any logs on the Synology correlating to my attempts >>> to access file shares >>> >> >> Synology takes Samba and modifies it and it could be one of their >> changes that is causing this. I suggest you contact Synology to rule >> this out. >> >> Rowland >> >> > >
Rowland Penny
2022-Dec-07 14:09 UTC
[Samba] File server joined to a samba domain accessed by windows 10-11 clients, works via ip no via dns name
On 07/12/2022 13:42, Ingo Asche via samba wrote:> By the way: Just checked accessing on of the shares via IP. It's the > same like your case: The share opens. > > Never checked that... >I take it that all the obvious culprits have been checked: DNS; Can you ping the synology device by name ? Can you ping from the Synology device Time: is the time correct ? This all sounds like a dns problem or a kerberos problem caused by dns. When you try to connect using the name, kerberos will be used, but it falls back to NTLM if the ipaddress is used. You need dns for kerberos to work. Rowland