Wait a second, Sky, did you mention FTP? Can you confirm that Dashboard uses “PASV” FTP connection, not the “classic” one, which requires that client side (Dashboard user) either accepts INCOMING connections for the FTP data connection originating from the Drobo server after FTP handshake or uses some firewall with stateful packet inspection to arrange things (temporary firewall opening) on client side? If you’re not using PASV, it will fail badly in many, if not most, typical user-behind-the-NAT scenarios. I remember it working once, maybe, during the 2.5 years I’m using my Drobo. Edits Taxonomy Home Edit Site Menu Mapping Dashboard Tag Pages Community Social. I remember it was “unable to connect” pretty much every time I tried, with the the latest and all the previous Dashboard versions I had. However, they failed to get past the play-ins and fell to the Pelicans. Nothing is blocking outgoing TCP connections on my system but the update checking function never really worked for me at all. I’m only using the built-in default Windows Firewall (on Windows 7). From your host, connect to the DroboApps share using explorer for Windows, finde r for Mac, and command-line if using Linux (e.g. We will be expl aining how to manually install a Drobo App. You’ll want to do this in the Windows Firewall settings as well, if it’s on. There are several ways to install a Drobo App onto the Drobo 5N. They can all be found in C:\Program Files\Drobo\Drobo Dashboard. It usually works better to make Drobo Dashboard, DDAssist and DDService ‘trusted’ in McAffee’s settings. My experience with McAffee is that it’s never really off even when disabled. That message means something is blocking Dashboard from connecting to our FTP server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |