Windows Server 2003
--
Questions
--
Followers
Top Experts
Don't know how many of you uses a product called "Drobo" - it is a big storage device that uses up to 4 hard drives, and it kind of acts like a RAID-5 (but isn't) and gives redundancy backup capabilities.
I purchased the Drobo 2nd generation (wish I can have my money back) and it's been nothing but headaches.
The biggest problem is I don't think it behaves well with Windows (particularly Windows Server 2003) - it breaks network share periodically that I needed to reset.
For example:
Let's say I created a fold named "shared" under the folder "storage" and shared both of them; the link is \\server\storage\shared - where shared is our company files. So both \\server\storage\shared and \\server\shared will work
However, let's say on individual client machines there's mapped drive that goes to \\serve\storage\shared - one day I come in and it won't work, get nothing but blank or say network resources not available. Long story short the fix is: use the other link \\server\shared (instead of \\server\storage\shared) and it will work.... until the next time it won't work which the "fix" is to revert back to the previous link.
Obviously this is a hassle for all of us at the company. Drobo support is useless and incompetent. Thought there are people in here that have better insights.
Windows Server 2003, 4 GB of Ram, Xeon CPU
Drobo 2nd Generation USB 2.0
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
I have worked with a large number of Drobo's and USB external drives.
All of the Drobo's are on a shelf right now and I have gone to SATA technology for external drives when that type of technology is needed. In my opinion, USB external drives have absolutely no place in a business environment. Save yourself alot of pain and let it go.
How often does this issue happen? Is it random?






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Definitely happens when I have to power-cycle the attached server and it reconnects itself.
If the drive letter was S: for example, I would use the script that I just attached.
Then I inform users that if they have an issue connecting to their files, to simply run that icon.
You can also put a drive delete command in your login script that might be helpful also.
Just like the code for the "band-aid" fix.
Net use S: /delete /y
Net use S: \\servername\sharename /y

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Let me wait on this and if not then I'll credit you with the points since you have been kind enough to care and post numerously here.
Windows Server 2003
--
Questions
--
Followers
Top Experts
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).