![drobo dashboard cannot connect to ip address drobo dashboard cannot connect to ip address](https://support.elephantdrive.com/hc/article_attachments/360018904313/Screen_Shot_2018-11-15_at_4.19.06_PM.png)
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. 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?
![drobo dashboard cannot connect to ip address drobo dashboard cannot connect to ip address](https://i0.wp.com/www.alphr.com/wp-content/uploads/2014/11/it_photo_31844.jpg)
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). to manually set a static IP address for each iSCSI data port you use. 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. It can be installed on client computers which connect to the Drobo B1200i via a. 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.