To automate the solution for the "network path not found" issue when joining a client to Active Directory (AD), you can write a PowerShell script that applies the necessary configurations for the SMB and Windows registry services. The script ensures that both the srvsvc (Server Service) and winreg (Windows Registry Service) are enabled and running. Additionally, it configures SMB protocols, enabling SMB1 for older networks and SMB2/3 for newer ones. It also restarts the relevant network services, like lanmanserver and netlogon, to ensure the changes are applied. The script can be saved as a .ps1 file and run with administrator privileges to automatically resolve the issue when a client tries to join the domain. This can be integrated into an automated process or scheduled to run as needed.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116363 Title: "network path not found" on joining a client to AD; "+smb -s3fs; +winreg +srvsvc" fixes it; please automate this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1116363/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
