Connecting to Multiple targets

olesailor · Thu Jul 28, 2005 3:59 am

Can Starwind connect to a linux target device. If so how. I tried to add the target but kept recieving rejected errors.

Thu Jul 28, 2005 1:08 pm

1) StarWind is iSCSI target itself. So it cannot connect to another iSCSI target. You're confused. Either you mean StarPort or I have no idea what you're doing.

2) Screenshots, logs always help us to help you. "Does not work" and "How" are not very informative reports/questions.

olesailor wrote:Can Starwind connect to a linux target device. If so how. I tried to add the target but kept recieving rejected errors.

olesailor · Thu Jul 28, 2005 7:08 pm

Sorry about the lack of information.
While under Star Management on Machine A I tried to add connection to a Linux target device Machine B.

Machine A
Amd
XP Pro SP 2
MS iscsi initriator
StarWind 2.6.1

Machine B
Intel P4
Host 192.168.0.108 Port 3260.
Host OS running Fedora Cora 4
linux iscsi target 3.6.2

Machine C
Ultra 5
Solaris 10
solaris initiator

At the current time I have machine a, and c initiators connected to this target machine b.
With no user or password required.

When running connect from Star Management I recieve this error
Cannot connect to the Server
NO connection could be made because the target machine actively refused it.

Here is the log with me connecting to machine b then connecting to machine A

18:49:30:206 (2468) P: '192.168.0.108:3260' <<< login
18:49:30:206 (2468) P: Connecting to '192.168.0.108:3260'...
18:49:31:198 (2468) P: '192.168.0.108:3260' panic!
18:49:31:218 (2468) P: '192.168.0.108:3260' <<< logoff
18:49:31:218 (2468) P: '192.168.0.108:3260' panic!
18:49:31:218 (2468) P: '192.168.0.108:3260' >>> logoff reply '105 '
18:49:31:218 (2468) P: '192.168.0.108:3260' >>> logoff reply '105 '
18:49:31:218 (2468) P: '192.168.0.108:3260' disconnecting...
18:49:31:218 (2468) P: '192.168.0.108:3260' panic!
18:49:31:218 (2468) P: Disconnect failed: An operation was attempted on something that is not a socket.

18:49:31:218 (2468) P: '192.168.0.108:3260' panic!
18:57:47:702 (2468) P: 'loner:3260' <<< login
18:57:47:702 (2468) P: Connecting to 'loner:3260'...
18:57:47:722 (2468) P: 'loner:3260' connected.
18:57:47:882 (2468) P: 'loner:3260' >>> banner
18:57:47:882 (2468) P: 'loner:3260' >>> login reply '200 Completed.'
18:57:47:892 (2468) P: 'loner:3260' <<< list -what:"devices"
18:57:47:892 (2468) P: 'loner:3260' <<< license
18:57:47:902 (2468) P: 'loner:3260' >>> list reply '200 Completed.'
18:57:47:902 (2468) P: 'loner:3260' <<< statistics
18:57:47:912 (2468) P: 'loner:3260' >>> statistics reply '200 Completed.'

I tried set it to security to Anonymous connection.
I hope this will help.

Thu Jul 28, 2005 8:31 pm

We would check the logs, hold on...

BTW, "fresh" idea - do you have firewalling software enabled on target?

Val (staff) · Thu Jul 28, 2005 8:35 pm

Hi olesailor,

It seems you misunderstand what StarWind can do and what it is.

StarWind is an iSCSI target server.
The installation consists of 2 parts:
1) StarWind Service - the iSCSI Service itself
2) StarWind COntrol Application (StarWind.exe) that is a remote controller for StarWind Servers. It communicates with a StarWind Service using our proprietary protocol (SWCP).

The two parts can be installed on separate machines and communicate over TCP/IP protocol.

But StarWind COntroller knows nothing about any third-party iSCSI target (as your Linux target is). That's why you have no success connecting StarWind GUI to the target.

If you need another iSCSI initiator, you can download our StarPort Storage Controller that can be used instead of the MS initiator to connect to an iSCSI target.