11 reputation
4
bio website
location Lexington, KY
age
visits member for 2 years, 3 months
seen Jul 31 '13 at 15:58

Technology Support Specialist IV for the University of Kentucky.


Jul
3
awarded  Tumbleweed
Sep
25
comment iSCSI no longer recognizing NAS drives
I've add the configuration screens and modified the original question.
Sep
20
awarded  Editor
Sep
20
revised iSCSI no longer recognizing NAS drives
clarification of issue with screenshots added
Sep
20
comment iSCSI no longer recognizing NAS drives
Interestingly this was working via both until a couple of weeks ago. The reason for iSCSI is for backng the NAS to an off-site IBM Tivoli TSM system on our campus. It requires an OS as a pass through. All of a sudden the iSCSI computer says it can't access the P: drive, which is the NAS I was backing up. While the back up was working users were also accessing the NAS via SMB just fine.
Sep
20
awarded  Commentator
Sep
20
comment iSCSI no longer recognizing NAS drives
I've set them up to be accessed by users mapping a network drive to the IP addresses (Mac's) or names (Windows) of the NAS's. Each user has separate login and password I created for them.
Sep
19
comment iSCSI no longer recognizing NAS drives
That is correct.
Sep
19
awarded  Student
Sep
19
asked iSCSI no longer recognizing NAS drives
Jul
5
comment Log On To Target results in “Authentication Failure”
More. The iSCSI device is a Dell Optiplex 780 with 4GB of RAM, a 3.33Ghz processor, 160GB hard drive and running 32-bit Windows 7. The network is 10/100GB.
Jul
5
comment Log On To Target results in “Authentication Failure”
Sorry, but the error message is "Authentication Failure." The Iomega NAS device is connected via TCP/IP. What else?
Jul
5
asked Log On To Target results in “Authentication Failure”
May
25
comment Unable to initialize BlackArmor after running iSCSI Manager and Windows 7 iSCSI Initiator
Here's what I've found - after setting the BlackArmor iSCSI manager's volume to different sizes it seems that Windows 7 Disk Manager cannot accept anything over 2TB. I've also found on the Windows 7 Support page the same conflict. So, anyone attempting to create an iSCSI target larger than 2TB is out of luck on a Windows 7 machine.
May
14
comment Unable to initialize BlackArmor after running iSCSI Manager and Windows 7 iSCSI Initiator
What's frustrating is I already have an Iomega ix2-200 initiated on the iSCSI machine, but this one won't cooperate.
May
14
comment Unable to initialize BlackArmor after running iSCSI Manager and Windows 7 iSCSI Initiator
I didn't see anything. So, no.
May
14
comment Unable to initialize BlackArmor after running iSCSI Manager and Windows 7 iSCSI Initiator
I've since watched a video about how to set up iSCSI link and have done everything up to 8:14 in the video. My Disk3 had Unknown under it. When it tell it to Initialize Disk3 using GPT (because they are 3TB disks) a Virtual Disk Manager error pops up - "The drive cannot find the sector requested." Are there any options to correct this issue?
May
13
comment Feasibility of controlling two or more NAS via iSCSI
I've done everything up to 8:14 in this video - technet.microsoft.com/en-us/edge/Video/ff710316. My Disk3 has Unknown under it. When it tell it to Initialize Disk3 using GPT (because they are 3TB disks) a Virtual Disk Manager error pops up - "The drive cannot find the sector requested." <br> <br>What are my options to correct this issue?
May
7
asked Unable to initialize BlackArmor after running iSCSI Manager and Windows 7 iSCSI Initiator
Apr
27
comment Feasibility of controlling two or more NAS via iSCSI
Actually discovered a newer firmware 4000.1311 provides an iSCSI Manager. Have enabled it, backed up the files and moving forward. Thanks so much.