Availability for the Always-On Enterprise
Post Reply
shabbaranker
Influencer
Posts: 11
Liked: never
Joined: Feb 02, 2017 9:42 am
Contact:

The specified network name is no longer available

Post by shabbaranker » Jul 19, 2017 4:11 pm

Hi guys,

Im convinced this problem relates to Veeam in one way or another but I cant prove it. What's happening is if I try to connect to a NAS using UNC (IP or FQDN) I get an error that the specified network name no longer exists. I can ping the device fine from the server. The NAS was previously a backup target and so the machine "once upon a time" could connect to it. I have no problems connecting from any other machine on the network JUST the server 2012 which hosts Veeam.

Please someone shed some light on this and tell me Im not going mad it has to be Veeam related???

Thanks as always.

PTide
Veeam Software
Posts: 4251
Liked: 350 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: The specified network name is no longer available

Post by PTide » Jul 20, 2017 11:11 am

Hi,

Have you tried any solutions from this article already?

Thanks

shabbaranker
Influencer
Posts: 11
Liked: never
Joined: Feb 02, 2017 9:42 am
Contact:

Re: The specified network name is no longer available

Post by shabbaranker » Jul 20, 2017 1:27 pm

Thanks I have followed that and tried "some" of the tests but considering its not even using the share for backups currently Im wondering if its down to that Kerberos timeout..

foggy
Veeam Software
Posts: 16711
Liked: 1346 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: The specified network name is no longer available

Post by foggy » Jul 20, 2017 4:02 pm

I'd also check the port requirements. Feel free to contact support if nothing helps.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], JimmyO and 55 guests