Hi,

If you do a DNS lookup for nas.local, does it resolve to the correct IP? what happens if you target it via IP instead?

Mhh, three spontan ideas to this:

• Incompatible SMB version?
• Times on server and NAS are not synchronized?
• Path length is too long?

Are you able to browse the UNC path from the Windows agent machine?  I would start there to see if you can access it using the credentials and this should give you an indication of where the problem could be.  After that check the permissions for the SMB share on Synology to ensure they are correct and that the “veeam” user has Read/Write permissions.

Let us know how that goes.

SMB version is allowed from 1 to 3 on Syno.

Yes, on Windows machine i can open UNC path folder, create/remove files.

In Syno user has read/write permisisons.

Time is correct, and synchronized by pool.ntp.org

DNS resolved correct ip. If specify in config IP - error, like by DNS name.

Please use the following format for the username:

HOSTNAME\username

Only the name has never worked for me.

from the guide:

“The user name must be specified in the down-level logon name format. For example, DOMAIN\UserName or HOSTNAME\UserName“

https://helpcenter.veeam.com/docs/agentforwindows/userguide/backup_job_share.html?ver=50

Tried this to. No result :(

Are there any firewalls between the agent and Synology?  If so be sure the ports are open for communication.  Thinking about other suggestions.

No. This is my local home network. Syno and Windows machine in one subnet, all shared folders are perfectly work except Veeam backup.

In Syno logs creates this records, when i try create Backup job.

I would check here for the log files for the Agent and see if there are any clues there - C:\ProgramData\Veeam\Endpoint

Otherwise open a case with Support.

@mva994 have you tried using IP instead FQDN?

In any case, I find a similar but not too much issue: https://forums.veeam.com/veeam-agent-for-windows-f33/backup-configuration-t43324.html

Did you try “.\veeam” for the username? Also check if the user has really Full Permissions on the folder, not only read/write.

Thank for all! I solved my problem - unsupported chars in password. I generate strong pass for my users, and if Syno works perfect with generated pass, Veeam give me error.

Very well. Nice to know.

@mva994 Thanks for this info - can you specify which char was not supported? Did it show up correctly within the GUI (when viewing the password). 
If there’s an issue with unsupported chars this should be fed back to the Helpcenter to improve our documentation - I am happy to do this with more info.

Yes, i used this set of chars:

ßâ̸ì©ã¶¨¢¬Ïòø¥ÑØÐ×ÓÃôµÂÆÖ°ÉÞÚèű¤úæ§Ë»üÜàáʼٮñ¦ûÈù¹õÀë¡óöÝêÕº£ïé«Î³Ä¾½äÒÇðå¿·÷²´ÿýþíÔÁçÍÛ

In Keepass for Windows this checkbox:

Ok, this are very special chars…

Glad you figured it out

Thank you, I forwarded this to our docs team.