Here's one for you, kids.
NBU 7.5.0.5 on a Windows 2008 R2 Server, most clients still running 7.5.0.3
I have a Linux FT media server that handles 2 fiber transport clients and I wanted to use it as a standard media server as well. 8 clients (MS-Windows policy) used the media server last night and all 8 failed with a Status 59, access denied. All 8 clients are VMWare boxes so I created a VMWare policy, added the 8 clients, selected the same media server, and the backups finished successfully. Why?
All of the clients are behind a DMZ firewall. Those are the only DMZ clients that were being backed up through that media server with an MS-Windows policy. MS-Windows clients on my production network don't have a problem writing to this particular media server.
A Status 59 is typically a very easy fix. If the 8 clients had failed using the VMWare policy, then it would have most likely pointed to a simple and obvious solution. But why does the MS-Windows policy get "access denied" but the same clients in a VMWare policy write successfully. I wouldn't think the firewall has anything to do with it. Does a VMWare policy used a different set of credentials?
Thanks in advance for any light you can shed on this.
Randy