We have a Drobo setup with a fixed IP on ethernet which we've named BoxA. It shows up in the finder list, everyone can connect to it and share files.

We brought a second Drobo to backup the first, this was given a different fixed ip and a different name BoxB.

When we connect BoxB to the network all the clients which are connected to BoxA receive the message "BoxA has closed down" clicking on BoxA on the finder reveals the content of BoxB.

Any idea what might be causing Finder to display this message? Why would it see two different network servers as the same?

  • You might be better served by asking on Drobo's support website or contacting their support staff. – Aaron Lake Aug 4 '11 at 15:58
  • Have done, but not much luck :( – Tom Aug 4 '11 at 15:59
  • Can you (are you) access (ing) the drobo shares using mac only software or is drobo software loaded on the macs that have the issues? Perhaps adding software details might help if different versions have different functions or bugs. – bmike Aug 4 '11 at 16:16
  • So don't use a fixed IP address. Allow your router to handle the DHCP. Try that and see if it helps. – Slick Aug 4 '11 at 16:20
  • 1
    @bmike My only guess is that somewhere they have the same identifier (netbios?, afp?) and finder is getting mixed up between the two, which sucks. – Tom Aug 4 '11 at 21:46

Have you tried placing each in it's own NetBIOS Domain Name to keep them from chatting/colliding on a shared port or name?

  • Is there a terminal command to display netbios names on the current network? – Tom Aug 5 '11 at 6:22
  • I don't know of a command line, but you could fire up the Directory Utility and View in node /Search and see if any of the following will browse your current network: SharePoints, NetGroups (see apple.stackexchange.com/questions/17937/… ) for more starting details – bmike Aug 5 '11 at 15:53

It turns out that along with the real static IP that is set in the Drobo Dasbhoard each Drobo was assigned a local link address. After some digging around in the firmware I found that both Drobo's were just binding themselves to: without checking if another device was using this address.

This is why Finder was showing DroboA as DroboB as it was using the local link address to resolve the DroboA.local address.

If you install Drobo Apps and Dropbear you can SSH into the device and adjust the address used, these changes probably won't stick around after a firmware update but you need to adjust the IP in following files:

  • /etc/init.d/net_config
  • /etc/udcpc.sh

Now DroboA is bound to and DroboB is bound to both appear as separate entries in the finder and work as I first expected. I've filed a bug with Drobo as I don't see why it should assign an IP without first checking if it already exists.

  • Wow! That is egregious behavior for a networked device - but makes prefect sense in hindsight. Great catch! – bmike Aug 8 '11 at 15:07

You must log in to answer this question.

Not the answer you're looking for?Browse other questions tagged .