Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
edvdave
Novice
Posts: 5
Liked: never
Joined: Sep 24, 2018 11:14 am
Full Name: edvdave
Contact:

Re: Veeam Endpoint for Windows 2.1 cannot access Shared folders

Post by edvdave » Sep 30, 2018 12:27 pm

Hi Vitaliy,

i installed SMBv1 / Cifs Client and Server function. That doens't change anything sadly.

best regards

Vitaliy S.
Product Manager
Posts: 22445
Liked: 1443 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Veeam Endpoint for Windows 2.1 cannot access Shared folders

Post by Vitaliy S. » Sep 30, 2018 5:30 pm

Ok, in this case let our support team to take a closer look at the issue.

vnavna
Influencer
Posts: 18
Liked: never
Joined: Sep 03, 2015 7:34 pm
Full Name: Steve Vujnovich
Contact:

Re: Veeam Endpoint for Windows 2.1 cannot access Shared folders

Post by vnavna » Nov 11, 2018 5:11 pm

Any updates on this issue? This seems to be a huge issue with users that are not able to update the NAS devices to support anything other that SMBv1.
This is so frustrating that you do not implement a Linux restore option as well to allow the access of network storage. The only way that I could think of resolving this issue would be to install a default Windows 10 1511 or 1607 virtual PC in virtualbox and then install the latest version of VEAM Endpoint then create the recovery media through the virtual PC to a connected USB drive.

Dima P.
Product Manager
Posts: 9911
Liked: 790 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Veeam Endpoint for Windows 2.1 cannot access Shared folders

Post by Dima P. » Nov 12, 2018 3:17 pm

Hi Steve.

Was the Recovery Media in the question created on Windows 10 machine with latest update? If yes - please follow How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server KB article in order to get SMB1 feature enabled on the Windows machine. Once done, recreate Recovery Media and check the connection to SMB1 (should work without any issues). Cheers!

The80srocked
Lurker
Posts: 1
Liked: 1 time
Joined: Mar 26, 2019 11:52 am
Full Name: Martin Musket
Contact:

Re: Veeam Endpoint for Windows 2.1 cannot access Shared folders

Post by The80srocked » Mar 26, 2019 11:54 am 1 person likes this post

If anyone else is having this issue..i have noticed that i have two NIC cards on my backup machine. One was enabled and being actively used and the other was disabled. It seems that VEEAM endpoint decided to bind itself to the disabled adapter which was causing the error. I confirmed this by enabling the adapter and plugging it into the switch and it was able to discover the network. Hopefully this helps someone. The SMB1 is a rabbit hole, so dont bother going down that path...

Dima P.
Product Manager
Posts: 9911
Liked: 790 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Veeam Endpoint for Windows 2.1 cannot access Shared folders

Post by Dima P. » Mar 26, 2019 4:27 pm

Hello Martin,

Thank you for taking your time to share these observations, I've passed it to RnD team for further investigation. Cheers!

Pemil
Lurker
Posts: 1
Liked: never
Joined: May 14, 2019 12:43 pm
Full Name: Pemil Peduru
Contact:

Re: Veeam Endpoint for Windows 2.1 cannot access Shared folders

Post by Pemil » May 14, 2019 12:59 pm

Hi,

I had the same issue with the Agent for MS Windows 3.0.1.1039.
Client was Windows 10
Target was a CIFS share on NetApp.
I couldn't get the network devices or path listed by clicking brows.
So, I've just entered the full shared path as the User Guide describes, and then just clicked populate. Voilà ! Everything looks great. And that was it.

@ https://helpcenter.veeam.com/docs/agent ... tml?ver=30

Regarsd
Pemil

jdrch
Novice
Posts: 9
Liked: 3 times
Joined: Jun 18, 2018 2:41 am
Contact:

Re: Veeam Endpoint for Windows 2.1 cannot access Shared folders

Post by jdrch » May 15, 2019 6:48 pm

edvdave wrote:
Sep 30, 2018 12:27 pm
Hi Vitaliy,

i installed SMBv1 / Cifs Client and Server function. That doens't change anything sadly.

best regards
Why would you use SMBv1 at all? It's got major security problems.

Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests