![]()
DROBO DASHBOARD INSTALL PROI tested to see if the broadcast is coming out of the 5002 port on my Mabook pro and I see the broadcast stream from the Drobodashboard. But I can use the AFP protocol and mount the share afp://Drobo-fs /backup. When my MAcbookpro is connected to the 192.168.5.x network I tried the following : nc -lvu 5002 | nc 192.168.1.x(Drobo ip) and I get the response “Connection Succeeded” but the DROBO Dashboard does not detect the DROBO at all. I have two different network 192.168.1.x ( where the DROBO is connected) and I have 192.168.5.x with the WAN port connected to the 192.168.1.x. DROBO DASHBOARD INSTALL MAC OSXI own a DROBO FS and tried using the net cat under MAC OSX LION. Hi interesting to see how DROBO can be remotely accessed. Then you have a point-and-click solution that any user could use. It should be simple to write a shell script that opens both the Dashboard and the echoing software, waits for a specified period of time chosen to be long enough for communication to be established between the Drobo and the Dashboard, and then quits the echoing software. DROBO DASHBOARD INSTALL SOFTWAREIf you close and reopen the Dashboard software, you’ll need to restart the echoing software until the Drobo and the Dashboard have seen each other. At this point, the software that was doing the echoing is no longer needed: all further communication is direct. If, on the same computer that’s running the Drobo Dashboard, you run some software that detects that UDP broadcast packet on port 5002 and echos that packet to the Drobo’s IP address, the echoed packet is no longer a broadcast packet, the routers will route it properly, and the Drobo will respond to the Dashboard. If your Drobo is on another subnet, it will never see this broadcast packet, so it will never respond to the Dashboard. Since it is a broadcast packet, most routers will not resend that packet to other subnets (unless the routers have been configured in a bizarre way). When it starts up, the Drobo Dashboard sends out a broadcast UDP packet on port 5002 at five second intervals, alerting any Drobos that receive the packet that it is running. I realized my original description is too vague, so here’s a second attempt: Yeah, I know this would solve the problem, but what if I have no choice or control over my local and/or remote subnet? Why do I have to change my network configuration to work around a shortcoming in their software? I’ve contacted the Drobo support, and they suggested to either put myself into the Drobo subnet or putting the Drobo into my subnet. Yes, there it is possible! Why not in the administration part? You can mount its shares, and you can even configure it as a DroboSync target by manually entering its IP address in the DroboSync settings. Many companies split their network into subnets, and if you happen to be in a different subnet from the Drobo, you can’t manage it. This is really annoying, especially considering the $3K DroboPro FS is marketed for business users. There is no way to add it manually to the dashboard by entering an IP address or hostname manually. If the Drobo is in a different subnet, it simply won’t find it. Drobo Dashboard uses a broadcast mechanism to detect Drobo units in the local subnet. However I find the dashboard is lacking some essential features. The DroboPro FS itself is quite impressive, good performance and easy to set up. There is no web interface like other NAS have, and there is no way to configure it from Linux natively. DROBO DASHBOARD INSTALL WINDOWSI’m using two DroboPro FS units, and the only way to manage them is to use Drobo Dashboard for Windows or OSX. Drobo Dashboard: cannot add Drobo IP address manually ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |