Community

« Back to Windows version

Error #53 Unable to connect a network drive.network path was notfound

Links used in this discussion

agomes, User (Posts: 14)

Sep 08, 2020 5:32:28 pm EDT

Support level: Free or trial

Dear, thanks for your attention!
When using Remote install to install a Viewer

agomes, User (Posts: 14)

Sep 08, 2020 5:38:15 pm EDT

Support level: Free or trial

(sorry, I've hit something before time :-(

When using Remote install communicating with a machine running the Agent, using Internet ID over a internet connection, I am getting the above error, no matter what user/password.

Is it possible to use Remote install in such situation? If so, do I need to add something to the username and/or to the Domain?

Thanks again!

Pauline, Support (Posts: 2775)

Sep 09, 2020 5:41:56 pm EDT

Hello,

Thank you for your message.

This error might mean that admin$ (admin share) is not allowed on the remote machine or you don't have access to it.
In addition, this error might also be caused by the fact that the disc Z is mapped on the Viewer computer and, therefore, is not available. Please make sure that the Z drive/letter on your Viewer PC is empty and available because the program uses that drive temporarily for the installation/upgrade process.

Hope that helps.

agomes, User (Posts: 14)

Oct 03, 2020 6:56:46 pm EDT

Support level: Free or trial

Thank you! And sorry for the delay.

In this scenario, how could I access the admin share? How should I provide the user and domain on the Remote Install dialog?

Thanks again!

Pauline, Support (Posts: 2775)

Oct 05, 2020 5:29:16 pm EDT

Hello,

Thank you for your message.

Could you please clarify what Connection type do you use when connecting to the remote machine via the Remote Install Tool? In case if you use Remote Utilities security, please try using the Windows NT security instead, as it allows you to connect to a remote computer using admin$ share.

In addition, please note that since you've mentioned above that you're connecting to Agent running on a remote machine, this might also be causing the issue as Agent runs as an application under the current Windows user without administrative privileges.
Please try restarting Agent as administrator first using the Restart Agent as command and using the Remote Install Tool via Remote Utilities security (in case if you're connecting to the remote machine over the Internet) once again.

Hope that helps.

Submit a reply

^* Website time zone: America/New_York (UTC -4)