He guy's from Rocket Division got some work for you ;) First thing I see (and its been there in earlier versions) is that when I remove the default 'localhost:3260' connection in the GUI -> make a new connection instead -> exit the GUI and start it again the default connection is there again togethe...

Where do you want me to send logs. I didn't post them here because I read somewhere that this is unwanted. I'll try to explain what I've done: One server with VMware ESX 3.0.2 plus Qlogic qla4052c, this is the initiator. The target consists of a server with Windows Server 2003 plus StarWind 3.5 inst...

I've been experimenting with the combination qla4052c + ESX 3.0.2 -> StarWind 3.5. Using a Seagate Cheetah in the StarWind server I was: - Unable to connect to it when configured as SPTI device - Able to connect when using an image file on that disk - Able to connect when configured as a diskbridge ...

Thanks that explains the behaviour I see. It would probably be a good idea to remove $(id) macro the from the documentation (StarWind configuration.doc) From the configuration file: <!--<DefTargetName value="iqn.2003-06.com.rocketdivision.starwind:$(host).$(symid)"/>--> So the default targ...

From the configuration file: <!--<DefTargetName value="iqn.2003-06.com.rocketdivision.starwind:$(host).$(symid)"/>--> So the default target name is based on $(symid) not $(id). I would like to use iqn.2003-06.com.rocketdivision.starwind:$(host).$(id). But what ever combination I use I'm un...

So I can check "Use file system buffering", which should speed things up, and leave "Header size in sectors:" untouched? If you're using "alien" disk images (like the ones you still have from the WinTarget) you may make StarWind ignore some initial offset (where WinTarg...

Could somebody explain this setting? What is it for? Is it related with the "Use file system buffering" setting? How do I determine the value to type here?

Regards,
Han Valk.

Can somebody explain the use of $(id) in the target's name e.g.: iqn.2003-06.rocketdivision.starwind.$(host).$(id)? Whenever I try to use the $(id) macro the following is logged: target name 'iqn.2003-06.rocketdivision.starwind.stor01.$(host).$(id)' is invalid according to RFC 3722! Regards, Han Valk.

[quote="bohdan (staff)"]Han, SANs are really not expected to be used in DMZ or ourside corporate LANs (no gateway to WAN in other words). So there is no necessity at separating management and data traffic. But we'll think about your suggestion.[/quote] Well if security is not a concern tha...

Thanks for this very good answer. StarWind offers the possibility to restrict the service to listen on just 1 IP address, at least as far as iSCSI goes. Wouldn't it security wise be a good idea to build in the option to restrict the control channel to a certain IP address as well? iSCSI traffic pref...

I know port 3260 is the iSCSI port. But when I issue a netstat -an when the StarWind service runs it seems to listen on 3261 too. What's the purpose of this port? Also I'm a bit confused about security. Authentication can be required twice: once for the connection between management console and the ...

Ok so the issue I've seen is a disk access issue.
How about the other questions. I've read the help and did some experiments but I still do not completely understand. Or should I start a new thread?

Han.

Ok so what can I do to help. I was able to connect so one would think the firewall wasn't the issue... just wasn't able to partition the exported disk. I know port 3260 is the iSCSI port. But when I issue a netstat -an when the StarWind service runs it seems to listen on 3261 too. What's the purpose...

Ok I had the time to try Windows Server 2003 (plain SP1) instead of 2008 beta 3. Configured StarWind the same way and it works perfect. So it looks like a 2008 issue.
Who or what is the OP?

2 VM's running on VMware Workstation 6 1 VM Windows XP SP2 MS iSCSI initiator 2.04 1 VM Longhorn beta 3 StarWind 3.2.3.20070524 with one 16 GB DiskBridge target. Both VM's firewall switched of. XP client is able to see the target but when I want to initialize the disk this error appears in the Syste...