Can't Connect to Remote iSCSI Target

n0ne · Thu Jul 14, 2011 11:19 am

Hi Support.

I was trying to connect to my iSCSI Target at home (iOmega StorCenter ix2-200). Port-Forwarding and DynDNS is configured for the Target and StarPort found it, but has problems to connect. I'm always getting an error message (

: iscsi.jpg (37.66 KiB) Viewed 16924 times

).
this is the log file:

7/14 13:12:13.689 >> CStarPortDoc::ResyncRegistryAndDriverContents(bAutomountDevices=0)
7/14 13:12:13.690 >> CStarPortAPI::GetDevices(...)
7/14 13:12:13.690 CStarPortAPI::GetDevices: Calling STARPORT_IOCTL_TARGET_LIST
7/14 13:12:13.690 CStarPortAPI::GetDevices: Output buffer:
7/14 13:12:13.695 CStarPortAPI::GetDevices: NumberOfTargets = 0
7/14 13:12:13.701 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:14.105 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:14.505 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:14.905 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:15.307 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:15.707 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:16.107 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:16.508 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:16.908 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:17.308 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:17.709 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:18.110 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:18.510 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:18.910 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:19.310 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:19.710 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:20.110 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:20.510 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:20.910 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:21.310 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:21.710 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:22.110 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:22.510 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:22.910 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:23.310 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:23.707 CMainFrame::OnTimer: Refreshing view, received REFRESH_TIMER_ID...
7/14 13:12:23.708 >> CStarPortDoc::ResyncRegistryAndDriverContents(bAutomountDevices=0)
7/14 13:12:23.708 >> CStarPortAPI::GetDevices(...)
7/14 13:12:23.708 CStarPortAPI::GetDevices: Calling STARPORT_IOCTL_TARGET_LIST
7/14 13:12:23.709 CStarPortAPI::GetDevices: Output buffer:
7/14 13:12:23.709 CStarPortAPI::GetDevices: NumberOfTargets = 0
7/14 13:12:23.710 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:24.110 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:24.510 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:24.910 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:25.310 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:25.710 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:26.110 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:26.510 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:26.910 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:27.310 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:27.710 CMainFrame::PoolingServiceEvents: Event checking failed, status == 2
7/14 13:12:27.718 >> CDriveLetterMap::~CDriveLetterMap()
7/14 13:12:27.718 >> CStarPortAPI::~CStarPortAPI()

Regards,

Randy

Thu Jul 14, 2011 4:02 pm

I'm not sure NAT would work with iSCSI. Did you try plain open ports on both target and initiator machines?

n0ne · Fri Jul 15, 2011 3:41 am

Firewall-Ports on the windows client are open due the first iSCSI-Initiator configuration (Win 7 does this on it's own). Idk if my router at home has NAT (I'm pretty sure it hasn't) but I configured an "IP Filter" (maybe the router understands this as NAT) with my inet IP, local ip for the target, port and allow.

I'll try it out later and tell you wether it worked or not.

Regards,

n0ne

Fri Jul 15, 2011 6:53 am

OK

One question so far - did you manage to connect and config everything properly with MS iSCSI initiator before?

n0ne wrote:Firewall-Ports on the windows client are open due the first iSCSI-Initiator configuration (Win 7 does this on it's own). Idk if my router at home has NAT (I'm pretty sure it hasn't) but I configured an "IP Filter" (maybe the router understands this as NAT) with my inet IP, local ip for the target, port and allow.

I'll try it out later and tell you wether it worked or not.

Regards,

n0ne

n0ne · Tue Jul 19, 2011 6:51 am

Yes, I managed to connect to the iSCSI-Target properly in my LAN with the MS Initiator

Wed Jul 20, 2011 9:36 pm

Weird... Can you install WinPCap and capture both sides failed handshake logs for us? And send them with your comments to support@starwindsoftware.com so we could tell what's wrong for sure (and fix it if it's our issue). Much appreciated...

n0ne wrote:Yes, I managed to connect to the iSCSI-Target properly in my LAN with the MS Initiator