- #Drobo dashboard windows not seeing drive install
- #Drobo dashboard windows not seeing drive pro
- #Drobo dashboard windows not seeing drive free
I've had one since October 2007 and it works just fine. I'm open to ideas, recommendations, and/or suggestions. So what do you all do at home? What do you use? Why do you use what you use? I don't have a budget - I could buy a iMac if that made the most sense. I'm done some homework on Netgear's ReadyNAS NV+, Synology's DS209+II, Lacie's 2big Network 2. The third option is one that I'm fairly new to - NAS.
#Drobo dashboard windows not seeing drive free
I could forgo all the "sharing" and just free up HD space on my notebook by getting a Drobo (FireWire 800) and then moving the bulk of data from my internal HD to the Drobo. Time Machine wireless backup would be a great addition as well. Purchase a Mac mini and set it up as a "home server" and setup iTunes to share, and also keep all documents there as the primary storage (you can copy local if you want to take something out of the house for example). I'm not sure which solution would make the most sense for us. Pictures would need to remain local as I use Lightroom to browse and make any modifications. I have lots of music, movies, and documents. I am nearly out of HD space and I'm looking at ways to "share" the data that I keep on my HD.
#Drobo dashboard windows not seeing drive pro
SMB 1 … I thought that was unsafe and deprecated and a recommended removal?Įveryone should be using SMB 3 now - the best part of Windows 8.I have a MacBook (wife) and a MacBook Pro (me) in my house.
#Drobo dashboard windows not seeing drive install
When I moved to 1809 I decided to go nuclear: I did a clean install of W10 1809 on ALL my machines. So my best guess is MSFT screwed something up. I noticed (by accident) that the last devices to be upgraded from 1709 could all see others on the network. None of the 'fixes' worked for me and I tried headbanging too 😞ġ803 was the version where MSFT removed Homegroup. I had the same issue network-wide across W10 Pro machines running 1803. From memory one has to get about 4 ducks in a row … but no-one gave an explanation of the problem cause. There is another thread on this forum which offers some options, typically tinkering with Windows services. This is driving me nuts so any advice would be greatly appreciated. Where is Windows getting the mapping from that it is directing that address to the Synology? It's just this new desktop, and everything is running Windows 10.Īnother strange phenomenon that I discovered is that if I go to "\\DROBO" (verbatim, not a sample name) it leads me to the Synology. Every other machine I have can access the Drobo without issue. I've already enabled the SMB 1.x protocol, ensured the workgroup names are the same, rebooted both the machine and the Drobo, made sure network sharing is enabled, and even did a fresh install to ensure that some program I installed didn't cause the issue. What could be preventing Windows from seeing the Drobo on the network? What's strange is that I can see and manage the Drobo through the Drobo Dashboard software. When I try to go to \\N5, it results in a message saying it cannot find that location.
I recently got a new desktop which is where the issues are coming up. I've always connected to both via Windows Explorer by simply going to the network address i.e., \\N5 and \\SYN (sample names). I have a Drobo 5N and a Synology RS816 on my network, both of which have been working without issue for quite some time now.
Hoping the very intelligent crew here can help me out. I've been banging my head for a few days now trying to figure this out and I've run out of ideas.
0 kommentar(er)
