60001 Unable to connect to server

Question

60001 Unable to connect to server

Help Desk 0

getting error 60001, Unable to connect to Ubuntu Linux server using azure migration tool during discovery stage. Needing to know how to resolve this issue as all prerequisites have been met and no errors up to this point. I confirmed SSH is enabled on the VM

Suchitra Suregaunkar 1,890 Reputation points Microsoft External Staff Moderator

2025-10-06T20:40:00.1033333+00:00
Validate User Permissions

The account must have sudo access and NOPASSWD enabled for required commands (e.g., ls, netstat) to allow agentless dependency analysis.

Update /etc/sudoers accordingly: <username> ALL=(ALL) NOPASSWD: ALL Reference: https://free.blessedness.top/en-us/azure/migrate/tutorial-discover-physical?view=migrate#prepare-linux-server

Network & Proxy Settings

If a proxy is configured, ensure details are correctly entered in the appliance setup.

Add the Linux VM’s IP to the TrustedHosts list on the appliance if needed: Set-Item WSMan:\localhost\Client\TrustedHosts -Value "<Linux_VM_IP>"

Firewall Rules

Confirm that TCP port 22 is allowed between the appliance and the Linux VM.

Retry Discovery

After fixing connectivity/authentication, go back to the appliance configuration manager and revalidate the server.

If you are still experiencing same issue after these checks then let us know for further investigation.

Thanks,

Suchitra.

1 answer

Your answer

Suchitra Suregaunkar 1,890 Reputation points Microsoft External Staff Moderator

2025-10-06T20:40:00.1033333+00:00

Validate User Permissions

The account must have sudo access and NOPASSWD enabled for required commands (e.g., ls, netstat) to allow agentless dependency analysis.

Update /etc/sudoers accordingly: <username> ALL=(ALL) NOPASSWD: ALL Reference: https://free.blessedness.top/en-us/azure/migrate/tutorial-discover-physical?view=migrate#prepare-linux-server

Network & Proxy Settings

If a proxy is configured, ensure details are correctly entered in the appliance setup.

Add the Linux VM’s IP to the TrustedHosts list on the appliance if needed: Set-Item WSMan:\localhost\Client\TrustedHosts -Value "<Linux_VM_IP>"

Firewall Rules

Confirm that TCP port 22 is allowed between the appliance and the Linux VM.

Retry Discovery

After fixing connectivity/authentication, go back to the appliance configuration manager and revalidate the server.

If you are still experiencing same issue after these checks then let us know for further investigation.

Thanks,

Suchitra.

Answer 1

Hello Help Desk,

Thank you for posting your query on Microsoft Q&A portal.

The error “UnableToConnectToPhysicalServer” is due to the below reasons:

Network connectivity issues between the Azure Migrate appliance and the Linux server.
Authentication misconfiguration (wrong method or credentials).
Firewall or proxy restrictions blocking SSH traffic.

Reference: https://free.blessedness.top/en-us/azure/migrate/troubleshoot-assessment?view=migrate-classic

The prerequisites to connect to the server have not been met or there are network issues in connecting to the server, for instance some proxy settings.

Reference: https://free.blessedness.top/en-us/azure/migrate/migrate-appliance?view=migrate&branch=pr-en-us-….

Recommended actions:

Ensure that the server meets the prerequisites for discovery and assessment as documented here
Ensure that you have chosen the correct authentication method on the appliance to connect to the server.

(Note: Azure Migrate supports both password-based and SSH key based authentcation for Linux servers).

1. Verify SSH Connectivity:

From the Azure Migrate appliance, run: ssh <username>@<Linux_VM_IP> Ensure it connects without errors. If it fails, check:
- SSH port 22 is open on the Linux VM.
- No firewall rules are blocking inbound SSH.
- Network routing between appliance and VM is correct.
Check Authentication Method:
Azure Migrate supports password-based and SSH key-based authentication for Linux.
Confirm the method configured in the appliance matches what the VM expects.
- If using SSH keys, ensure the public key is in ~/.ssh/authorized_keys for the user.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Share via

60001 Unable to connect to server

1 answer

Your answer