The specified network name is no longer available

Availability for the Always-On Enterprise

The specified network name is no longer available

Veeam Logoby shabbaranker » Wed 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.
shabbaranker
Influencer
 
Posts: 11
Liked: never
Joined: Thu Feb 02, 2017 9:42 am

Re: The specified network name is no longer available

Veeam Logoby PTide » Thu Jul 20, 2017 11:11 am

Hi,

Have you tried any solutions from this article already?

Thanks
PTide
Veeam Software
 
Posts: 3147
Liked: 262 times
Joined: Tue May 19, 2015 1:46 pm

Re: The specified network name is no longer available

Veeam Logoby shabbaranker » Thu 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..
shabbaranker
Influencer
 
Posts: 11
Liked: never
Joined: Thu Feb 02, 2017 9:42 am

Re: The specified network name is no longer available

Veeam Logoby foggy » Thu Jul 20, 2017 4:02 pm

I'd also check the port requirements. Feel free to contact support if nothing helps.
foggy
Veeam Software
 
Posts: 15094
Liked: 1111 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 52 guests