The specified network name is no longer available

[shabbaranker]

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]

Hi,

Have you tried any solutions from this article already?

Thanks

[shabbaranker]

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]

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