Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a DroboPro I've connected the device directly via USB and it works fine.

If i connect the ethernet cable directly from the 2nd Network card on my host machine, to the DroboPro (in order to use ISCSI) then it doesn't seem to connect- I get a "Acquiring Network Address" message, on the network icon... This eventially gives up and I get "This connection has limited or no connectivity"

I've set the Drobo to use DHCP (obtain address automatically)

I'm using Windows 2003 on the host machine, microsoft iscsi initiator (not that it can get this far yet!)

share|improve this question
This site is for Professional Administrators, please see FAQ for more information. SuperUser is the site for casual computer users. – Chris S Dec 6 '10 at 14:39
it's attached to a Windows Server 2003 SERVER. Not really fitting for a "casual" computer user. Thanks – alex Dec 6 '10 at 14:56
I think Chris is trying to say you're having a very basic networking issue and has nothing to do with "servers" but two peers. You need to set a static IP address on both the Drobo and the second NIC on your host. You need to make sure this does not conflict with your primary NIC's network. So if your primary NIC is then you need to adjust the third octet for this dedicated network, say – SpacemanSpiff Dec 6 '10 at 15:35
as Tom pointed out, I was trying to be nice and avoid saying you have a very simple configuration problem that any professional should know better. The OS is irrelevant in this case, it's quite obvious you don't know much about configuring network interfaces. Also, you've got a 42% accept rate, you should work on that. – Chris S Dec 6 '10 at 15:40
up vote 0 down vote accepted

You should probably configure both the NIC and the Drobo with static IPs from the 1918 range. Alternately you could configure the server as a DHCP server, but this is going to add a lot of completely needless complexity.

share|improve this answer

The default iSCSI configuration of the DroboPro is marked "Automatically configure (Default)" in the Drobo Dashboard utility. This doesn't mean DHCP but instead resorts to using Zeroconf addresses ( In a point-to-point configuration such as yours, you have two choices:

1) Leave the Drobo Pro in the "Default" network configuration and configure your network adapter for DHCP. The DHCP client in Windows will eventually timeout and you should receive a 169.254.X.X address for the network adapter. The Drobo Dashboard utility should eventually find the DroboPro (could take a few minutes) and make an iSCSI connection.

2) Connect the DroboPro to your Windows system via USB and setup a static IP address on the DroboPro. Then, statically configure you second network adapter for an IP address within the same subnet. Restart your Windows system, remove the USB cable, and wait patiently for the Drobo Dashboard to find your DroboPro and make an iSCSI connection.

The benefit of the latter configuration is that you lose the "limited or no connectivity" message for your NIC. If you're impatient and don't want to wait for Drobo Dashboard to find you DroboPro then you can setup the connection through the MS iSCSI Initiator in the control panel when you're using static IP addresses.


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.