Noob install network shared folder destination

[nogero]

Windows 8.1 Pro on Lenovo wireless ultra-laptop
I installed Endpoint and have not been able to enter a shared folder for destination.

If I browse the network it just hour-glasses forever. If I manually enter a share I have write permission Veeam says Error: Access is denied, failed to create or open file.

Clues?

[Dima P.]

Hello Bob,

Can you access the said file share via regular windows browser?

[nogero]

Hello Bob,

Can you access the said file share via regular windows browser?

Yes, Windows Explorer access just fine.

[Dima P.]

Try to type in the same path (simply copy it from explorer) and make sure you specified account with the password below the path field.

[nogero]

I've tried that already.

[Mike Resseler]

Hi Bob,

Are you using credentials to access the share? If not, could you try and fill in the credentials that you are logged in with manually to see if it makes a difference? (It shouldn't but...)

[jensenjk]

I encounter same problem - I can access the network share in windows explorer, but not in Veeam endpoint - the share is located on a backup appliance with no security credentials.

[IvanM]

Same issue here. Windows 8.1 Pro and the share is in Windows 7 Pro. I have shared the entire drive on the remote system and gave Everyone Full Control. I am able to create folders, files, move them, delete them, etc. with Windows Explorer. Turned both clients firewalls off, but VEEAM keeps throwing the same Error: Access is denied, failed to create or open file.

Would logs help? Which ones do you need?

Thanks

[IvanM]

UPDATE: I found the solution here: http://forums.veeam.com/veeam-backup-re ... t4982.html

Got to your Windows Services -> Veeam Backup and Replication -> Edit the logon account information from Local System to your user account -> Restart the service.

[Dima P.]

Hey IvanM,

I am glad you nailed it and additional thanks for sharing the solution with the community!

[alfredbird]

Similar situation that I cannot set up network shared folder as destination, any further possible solution for the same issue?