After migrating to new release and upgrading to version 2409 the SMB share is not longer connecting, this appears to be causing lots of crashfiles to generate which overt he week caused the applayering platform to stop functioning all together until the crash files were cleared.

We recommend the following action items which should help to resolve the issue:

1. Please don't use DFS. Specify the FQDN of one of the file servers that is part of the DFS system or use a different non-DFS file server.
2. Configure the DFS share to use fully qualified server names in referrals. See the Microsoft documentation:
https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-dfs-use-domain-names

3. Configure the ELM to be able to resolve the unqualified names. There are 2 ways to do this:
a) Update the ELM's DHCP server to return the domain the file servers in the DNS search list (option 119).
b) Manually configure the ELM to include the file servers' domain in the DNS search list by running these commands on the ELM (includes restarting the ELM). This assumes the file servers are in the domain named "local".

If not, then just swap that with the correct domain in step 1:
- nmcli con mod "System eth0" ipv4.dns-search "local"
- nmcli con reload
- reboot

Problem Cause

This is a DFS share and the DFS is not configured to give fully qualified names back in referrals to the individual servers. The ELM is not able to resolve the individual file server names since they are note fully qualified:

Mar 24 08:43:09 localhost key.dns_resolver[8153]: FILES-03: No address associated with name