Hi all, I’m new to this forum and was hoping to pick your collective brains on a strange issue that I am having.
I have a Drobo-FS that was installed back in September, its purpose in life is to act as a dumping ground for our ShadowProtect backups of the servers.
All was working well until the second week in November, when two of the servers started failing to backup. They were no longer able to access any network share on the device! When I manually tried to connect (via IP or DNS name or NetBIOS name) I receive the following error: “The specified network name is no longer available”.
I can ping the device (by DNS name/IP/NB name etc), and one of the servers runs the Drobo Dashboard and is able to find/manage the device (it just cannot map to the shares).
The servers in question are the two domain controllers for this network, one being 2008 Standard and the other 2003. Both are fully updated, and I do not have this problem from any other server, no matter the version.
I have done a TON of troubleshooting and my dead end usually ends up being to work in the Samba configs and/or to check the smb.log. I installed DropBear and SSH’d to the Drobo so I could check the smb.log but it seems to be quite lacking, even when I put the logging from 0 to 3. The configs seem to be pretty customized and I’m not sure what changes I can make without nuking this thing.
Does anybody here have any experience with the Samba server on these things, or perhaps has seen this issue before? I am open to any suggestions, and purposefully am leaving out much of my troubleshooting just to see what ideas pop up.
Help me Drobospace.com, you’re my only hope!