Storage Migration tool Config Scan Failed

Question

Hi, I am facing a "Couldn't find network path error" when I am trying to scan my source server, Validation error says that there is "NO SMB Connection" I looked into the server and found that both smb10 and smb20 are running, I tried disabling the firewall rules, it didn't work, help please!

Answer 1

Hello Mohammad,

Thank you for your question and for reaching out with your question today.

When encountering a "Couldn't find network path error" and a validation error stating "NO SMB Connection," it indicates that there is a problem with establishing an SMB (Server Message Block) connection between the source server and the destination.

Here are a few steps you can take to troubleshoot the issue:

1. Check SMB versions: Ensure that both the source server and the destination server support the same SMB version. In your case, since both SMBv1 (smb10) and SMBv2 (smb20) are running, make sure that the version supported by the destination server matches the version used by the source server.
2. Verify network connectivity: Confirm that there is proper network connectivity between the two servers. Check the network configuration, including IP addresses, subnet masks, and gateways, to ensure they are correctly configured and allow communication between the servers.
3. Review firewall settings: Even if you've disabled firewall rules, it's worth double-checking the configuration to ensure that no firewall settings are blocking SMB traffic. Ensure that the necessary ports (such as TCP port 445) are open in the firewall rules of both servers to allow SMB communication.
4. Check SMB sharing settings: On the destination server, verify that SMB sharing is enabled and properly configured. Ensure that the shared folder or resource you are trying to access is correctly set up for SMB sharing.
5. Validate permissions: Ensure that the appropriate permissions are set on the shared folder or resource. Check both the share-level permissions and the NTFS permissions to ensure that the user or account accessing the folder has the necessary permissions.
6. Update SMB drivers and firmware: Ensure that the server's network adapter drivers and firmware are up to date. Outdated or incompatible drivers can cause connectivity issues.
7. Test with different clients: If possible, try connecting to the destination server from a different client machine or vice versa. This can help determine if the issue is specific to the source server or if it's a broader networking issue.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.