Can't connect to NAS with Veeame from laptop

[simonth]

Hello everyone,

this is my first post in this forum so I would like to say "Hi" to everyone.

I have a very strange issue and I hope I can find a help here.
I recently installed Veeame Agent for Windows since it was recommended to me in another forum.
I installed the programm on my desktop computer as well as on my laptop.
I wanted to configure my first backup using my NAS as storage which worked just fine on my desktop but didn't with on my laptop.
The issue is that I cannot find my NAS in the "shared folder" tab when creating a new backup job.
I can find it on my desktop but not on my laptop. I have compared all settings between my desktop and my laptop but they are all the same.
I cannot find the solution here and I was hoping you could help me find it?
Thank you very much for the support!
Simon

[Dima P.]

Hello and welcome to the community Simon!

Can you please clarify if the mentioned file share is accessible from you laptop via regular Windows explorer? Are you using the same account for both laptop and desktop to access these file share? Cheers!

[simonth]

Hello and thank you

Yes, the fire share is accessible via regular Windows Explorer. It is also listed in my Network. I can find it, I can connect to it both with my Laptop and my desktop. I am using the same account for both!
I even tried out diffrent backup programs to see if they can find the NAS and in fact they do. So I only have this problem when using Veeam on my Laptop (Dell Latitude e7470).

[Andreas Neufert]

Does that share contain any special words or any specific Veeam phrase in the name?

[simonth]

No, thats what I had in mind at first. So I changed the shared Folder to "backup" but with the same result.

[simonth]

Here is the error message I receive when trying to select my NAS:




The error I am getting is in german and says: "The server list in this workgroup is currently not availabe."

Thought it might help to clarify my problem.

Again: It works perfectly within the same network on my desktop. I can select my share and everything works perfectly.

[Egor Yakovlev]

Hi Simon,
(Your reference case #04410274, since it wasn't mentioned in this thread yet).

I have a few more things to check for you:
- are those machines domain joined or workgroup-based?
- please double check DNS resolution of NAS box name from your laptop(I can see you are using direct IP address everywhere and according to case-linked screenshots - SS#1 you have IP but no account entered - expected to fail, SS#2 you have IP with short account name - might fail without correct domain\computer name, SS#3 - you have IP and account full name - suppose to work). See if ping to said box name comes with valid IP address.
- try using \\nas_name\share format in the target field instead of pure IP, alike entered credentials format

/Thanks!

[simonth]

Hi Egor,

thank you very much - thanks to your tip (typing in the NAS name) I finally got it to work!
Thank you!!!
Just out of curiosity and because I like to solve problems entirely: Do you have any idea why I can find the NAS via "browse" on my desktop but not on my laptop?
It just doesn't make any sense to me and I like to understand what the problem is
Anyways, thank you very much!
Now I can use it on all of my platforms!

[Egor Yakovlev]

Veeam does network discovery based on SMB1, which is disabled by default on most Windows systems. If share ain't listed under "Browse" in Veeam Agent UI, it doesn't mean we cannot communicate with it, it is just a discovery challenge here. Share can be still accessed without discovery without any issue!
/Thanks!

[Gostev]

@Egor Yakovlev why do we use SMB1? This makes no sense considering it is disabled by default almost everywhere these days.

[Egor Yakovlev]

Agree, will check of possible improvements in this area for one of the next versions!

[coolsport00]

Hi Egor -
I was wondering if this behavior...doing network discovery via SMBv1 has changed? It doesn't appear to have. I can connect to my Share for a VAW backup repo, but clicking the browse button throws an error "Last error: The network location cannot be reached." Is it because you all are still using SMBv1 with VAW?
Thanks!