![]() ![]() Tell a Story day is coming up on April 27th, and were working on an interactive story for it. IT Adventures: Episode Five - Replacement Holidays.However, I was not the one who coordinated it. ![]() And they would provide a certificate of destruction as well. In times past I have worked for companies even as recently as a year ago that would come and get our retired IT equipment at no charge. Is there such a thing as free e-cycling anymore? Hardware.Snap! - Martian Pet Rock, Dinner in the Stratosphere, Gas Stations in Space Spiceworks Originalsįlashback: April 21, 2000: COPPA (Children's Online Privacy Protection Act) goes into effect (Read more HERE.)īonus Flashback: April 21, 2001: The Endeavor crew on flight STS-1.SpiceWorld is back in Austin from September 5th-7th and I want to see you all there with me! While we've seen a lot of registrations from the community come in, it seems as though some of you still need a bit more convincing or a better understanding of t. If you haven’t registered for SpiceWorld yet - Watch this! Spiceworks.Both will receive but only one will send. You can't simply have two NICs with different IPs on the same subnet and expect each to act independently. This isn't a SAN or Drobo thing, this is basic host networking. It would send them on the original NIC and the Drobo would never receive them. Under what conditions would it attempt to send packets to the Drobo. the other NIC would have the default gateway. If you had the same local subnet on both Windows interfaces it would never use the one that the Drobo is on. On the 2003 R2 server however, I had to manually add the IP address to the iSCSI Initiator (Discovery tab), and then on the Targets tab, do a manual log on. Also, on the 2008 R2 server, the dashboard found the Drobo by itself once connected. The tech suggested using the address range and this worked out well. ![]() So after a talk with support, the issue is that the IP addresses on the server NIC and the Drobo needs to be not only on the same network, but they also need to be segregated from the local network the servers/computers are using. "įrom their website: http:/ Opens a new window / / app/ answers/ detail/ a_id/ 240/ kw/ set%20up%20iSCSI%20on%20drobopro You are now ready to manage and use your Drobo device. Press the power toggle button on the back of your Drobo device once. Plug one end of the Ethernet cable to the iSCSI (Ethernet) port on your DroboPro, and plug the other end into your Ethernet port on your computer.ĩ. Unplug the USB cable from your DroboPro and host computer.Ĩ. Once the connection between your DroboPro and host computer have been established, safely shut down your DroboPro.ħ. Power on your DroboPro and format the drives when prompted.Ħ. Connect the power supply to the back of your Drobo device, and connect the other end to a power source.ĥ. See Connecting Cables on Your Drobo/Pro/S for more information.Ĥ. Connect one end of the USB cable into your DroboPro, and the other end into your host computer. If you haven’t already done so, insert the hard drives into your DroboPro.ģ. If you haven’t already done so, install Drobo Dashboard on your host computer.Ģ. In this configuration, you directly connect DroboPro via its iSCSI connection to your computer’s Ethernet port.ġ. "Connecting DroboPro Directly to Your Computer with iSCSI I did find a method on Drobo's support site (after looking through many pages of FAQs). I removed the dashboard software and I'll try again. ![]()
0 Comments
Leave a Reply. |