r/synology•
alkrun

Can't add Synology Router to Synology Directory Server domain? NTLMv1 disabled

NSFWNetworking & security

I'm trying to add a Synology router (tried with RT2600 and RT6600) to a Synology DSM Directory Server domain and I get an error on the DSM server about:

failed to log in via [SMB] due to [NVLMv1 not permitted]

https://i.imgur.com/yWRF9dS.png

The client gives an error that it was unable to join the domain, the computer account does get created but left in the deactivated state.

I want/need to add the router so I can authenticate VPN clients against the directory.

  • SRM 1.3.1-9346 Update 5
  • DSM 7.2-64216

I do see the option on DSM -> File Services -> SMB -> Advanced -> Others -> Enable NVLMv1 authentication, but I tried that briefly and it didn't work, and I'd really rather not have to enable that given the big security warning. And since NTLMv1 auth is disabled by default in DSM 7.X, I'd like to not take the step backwards if I can avoid it.

Is there a way to have the router use NTLM v2 or v3 for authentication, or another workaround for getting this going?

Posted May 15, 2023, 9:44 PM UTC · edited

04
[deleted]•

[removed]

2
netguy473•

What are you using as a primary domain controller, Windows AD or Synology Directory Service?

In SRM what Domain Options do you have checked?

I was able to add me Synology Router to my Synology Directory Service. I did encounter the same issue, but did not need to enable NTLMv1.

2
alkrunOP•

It's Synology Directory Server as the only DC. I did create a support ticket, Synology did see an issue trying to join but say it was slightly different than what I reported so they're escalating. I mentioned to them this is a DSM 6, Directory Services created/configured, then upgraded to DSM 7 environment. I'll make sure to loop back with whatever support figures out in case anyone else hits this.

I did encounter the same issue, but did not need to enable NTLMv1

Do you mean you saw the log entry about NTLMv1 on server but the join still succeeded? Or did you have to do something else to get it to join?

In case it's interesting to anyone else or for search engine indexing, the log entries I see. I tried googling these to see if I could get some Samba hits but nothing really helpful from that:

DSM - /var/log/samba/log.samba

CVE-2022-38023: client_account[ROUTER$] computer_name[ROUTER] schannel_type[2] client_negotiate_flags[0x600fffff] real_account[router$] NT_STATUS_DOWNGRADE_DETECTED reject_des[0] reject_md5[1] ../../source4/rpc_server/netlogon/dcerpc_netlogon.c:255: [2023/05/17 01:31:22.686926, all 0] dcesrv_netr_ServerAuthenticate3_check_downgrade
CVE-2022-38023: Check if option 'server reject md5 schannel:router$ = no' might be needed for a legacy client.


SRM - /var/log/messages

Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:1018 specify domain name=HOME.ME.US
Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:563 Use ads join
Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: WINIGetRealm(452) can't get ads realm
Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:578 ads join: use FQDN=HOME.ME.US
Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: SYNOWinISearchLDAP(35) net lookup ldap success.
Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:589 ads join: get dc ip=192.168.16.2:389
Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: get domain workgroup:HOME
Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:611 ads join: get domain netbios name=HOME
Jan 2 09:42:11 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:188 CheckDNSHostConflict(188) SYNOILnxGetIP failed.(2000)
Jan 2 09:42:18 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_do_krb5login.c:89 kinit success
Jan 2 09:42:29 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:547 check and join failed (-1) (0)
Jan 2 09:42:57 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:547 check and join failed (-1) (1)
Jan 2 09:42:57 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:669 Use rpc join
Jan 2 09:42:57 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: wins_join1.c:679 rpc join: use NetBios name=HOME
Jan 2 09:43:02 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: WININt4Join(730) rpc join failed
Jan 2 09:43:02 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: SYNOWinJoin1(1146), Restore
Jan 2 09:43:02 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: domain.cpp:819 domain dns name error
Jan 2 09:43:02 router entry.cgi_SYNO.Core.Directory.Domain[1].set[16151]: domain.cpp:1316 Failed to save domain/workgroup info.
1
netguy473•

It was in my NAS Connection Logs and digging a little deeper i found the log entries that corrected it. I granted the SMB Application to both the DOMIAN\Domain Controller Group and DOMAIN\Domain Computer, which the User you are using to connect needs to be a member of.

2