StarWind Software

All of my machines are running xp pro Sp2

Let me fill you in on what I thought I could do with Starport and Starwind Server. I have a laptop that I use primarily and want to burn some dvds off of various computers on my network. I have a pretty extensive setup with the following:

Xp 2000+ Desktop

Laptop Sony Vaio FX210

HTPC (Home Theater PC connected to a Mitsubishi 65 HD Set with a vga transcoder for image conversion)

Server: Win2k3

Xbox 1 and 2 on Lan

Dlink 624 Router - No previous issues at all, all xp firewalled disabled.


Etc.

I usually use RDP or VNC actually for specific reasons. When you use RDP you do not get the true resolution settings and graphic settings of that display. Using VNC overcomes this. It is crucial when working with home theater pcs because of the specific resolutions required to maintain sync and refresh rates. Powerstrip handles this task quite well. Since we use our HTPC to watch tv shows and movies, dvds upscaled, I want to do background tasks such as burning DVDs. So that brings me here thanks to a google search.

If you are still with me, this appears to be an amazing piece of software to allow you to share ide, usb, firewire, scsi devices over a lan. I have read the manuals extensively but am still coming back to the same issues over and over. Doesnt matter which machine its installed on. Starwind sets up fine and mounts the drive just fine. Star port connects to the drive just fine as well. Even shows up in My Computer. Then it starts.

No matter which application I chose:

Nero
Alchohol
RocketDivisions own Burning Software. They all hang at the splash screen every time. I have to do a hard boot. Not even taskmgr.exe will kill the processes. Isnt that wierd? Of course once it reboots finally after I cant take it anymore. I have to shut down starwind and restart the service just to get it to reconnect from the client side (*starport)

Any help here would be greatly appreciated. .

For what its worth, Im using an NEC 2500A drive when im attempting to set this up. Am I correct that if set up properly , the drive should show up as an available device under the burning application? So many questions, not sure this is going to go anywhere. BTW, i am nc88keyz on aim if anyone thinks they can help. Im really good with computers, networking, and even troubleshooting but this one has me stumped.

I have several apps on the computers as well. Way too many to list.

To recap, all the burning apps just sit there. Nero minimizes to sys tray never to come back up, alchohol just freezes up with blank screen, I think its any authoring app that is trying to access the drive. BTW, I have the latest versions from the website on both apps. All this time, the starwind app remains ok as in its not crashing the pcs. Its definately on the client side. I would be willing to pay for a great app like this. Would like to see it in its glory though.

Thanks for all your time,
Heres to an amazing application.

Nc88keyz

Attached Below is my Log from one of the machines - Since they all do the same thing I figure it wont matter which one the log is from.

04:46:32 - Entering func: CLanguager::LoadLanguage(language=0x409)
04:46:32 - Exiting func: CLanguager::LoadLanguage(language=0x409)
04:46:32 - CStarPortApp::CheckLicense: License data not found.
04:46:32 - CStarPortApp::CheckLicense: *** TRIAL VERSION *** [ expires in 15 day(s) ]
05:12:57 - Entering func: CStarPortAPI::CStarPortAPI()
05:12:57 - Entering func: CStarPortAPI::DriverOpen()
05:12:57 - Exiting func: CStarPortAPI::DriverOpen()
05:12:57 - Entering func: CStarPortAPI::DriverVersion(...)
05:12:57 - CStarPortAPI::DriverVersion: Calling STARPORT_IOCTL_GET_VERSION
05:12:57 - CStarPortAPI::DriverVersion: Input buffer:
05:12:57 - CStarPortAPI::DriverVersion: Signature = 72417453:
05:12:57 - CStarPortAPI::DriverVersion: ApiVersion = 20002:
05:12:57 - CStarPortAPI::DriverVersion: Calling DeviceIoControl(...)
05:12:57 - CStarPortAPI::DriverVersion: DeviceIoControl(...) called successfully
05:12:57 - CStarPortAPI::DriverVersion: Output buffer:
05:12:57 - CStarPortAPI::DriverVersion: Signature = 52615473
05:12:57 - CStarPortAPI::DriverVersion: Version = 20050310
05:12:57 - CStarPortAPI::DriverVersion: ApiVersion = 20002
05:12:57 - CStarPortAPI::DriverVersion: Flags = 0
05:12:57 - Exiting func: CStarPortAPI::DriverVersion(...)
05:12:57 - CStarPortAPI::CStarPortAPI: StarPort version: 20050310; StarPort driver: API v20002, Build 0x20050310
05:12:57 - Exiting func: CStarPortAPI::CStarPortAPI()
05:12:57 - Entering func: CDriveLetterMap::CDriveLetterMap()
05:12:57 - Entering func: CDriveLetterMap::Refresh()
05:12:58 - Exiting func: CDriveLetterMap::Refresh()
05:12:58 - Exiting func: CDriveLetterMap::CDriveLetterMap()
05:12:58 - Entering func: CStarPortDoc::CStarPortDoc()
05:12:58 - Exiting func: CStarPortDoc::CStarPortDoc()
05:12:58 - CMainFrame::OnCreate: Minimizing application to tray.
05:12:58 - Entering func: CStarPortView::OnInitialUpdate()
05:12:58 - Entering func: CStarPortDoc::ResyncRegistryAndDriverContents(bAutomountDevices=1)
05:12:58 - Entering func: CDriveLetterMap::Refresh()
05:12:58 - Exiting func: CDriveLetterMap::Refresh()
05:12:58 - CStarPortDoc::ResyncRegistryAndDriverContents: Resyncronizing contents...
05:12:58 - Entering func: CStarPortAPI::GetDevices(...)
05:12:58 - CStarPortAPI::GetDevices: Calling STARPORT_IOCTL_TARGET_LIST
05:12:58 - CStarPortAPI::GetDevices: Input buffer:
05:12:58 - CStarPortAPI::GetDevices: Signature = 72417453
05:12:58 - CStarPortAPI::GetDevices: Calling DeviceIoControl(...)
05:12:58 - CStarPortAPI::GetDevices: DeviceIoControl(...) called successfully
05:12:58 - CStarPortAPI::GetDevices: Output buffer:
05:12:58 - CStarPortAPI::GetDevices: Signature = 52615473
05:12:58 - CStarPortAPI::GetDevices: NumberOfTargets = 0
05:12:58 - Exiting func: CStarPortAPI::GetDevices(...)
05:12:58 - Entering func: CStarPortAPI::InsertiSCSIDevice(dwIPAddress=0xC0A80204, dwPort=3260, szInitiaotrName=iqn.2003-06.com.rocketdivision.starport:xp2000, szTargetName=nec, szAdditionalParameter=, nTargetID=...)
05:12:58 - CStarPortAPI::InsertiSCSIDevice: Calling STARPORT_IOCTL_TARGET_MOUNT
05:12:58 - CStarPortAPI::InsertiSCSIDevice: Input buffer:
05:12:58 - CStarPortAPI::InsertiSCSIDevice: Signature = 72417453
05:12:58 - CStarPortAPI::InsertiSCSIDevice: Flags = 0
05:12:58 - CStarPortAPI::InsertiSCSIDevice: ServerAddress = 192.168.2.4:3260
05:12:58 - CStarPortAPI::InsertiSCSIDevice: Parameter[0] = InitiatorName=iqn.2003-06.com.rocketdivision.starport:xp2000
05:12:58 - CStarPortAPI::InsertiSCSIDevice: Parameter[1] = TargetName=nec
05:12:58 - CStarPortAPI::InsertiSCSIDevice: Calling DeviceIoControl(...)
05:12:58 - CStarPortAPI::InsertiSCSIDevice: Session failed, status == 1326 !
05:12:58 - Exiting func: CStarPortAPI::InsertiSCSIDevice(dwIPAddress=0xC0A80204, dwPort=3260, szInitiaotrName=iqn.2003-06.com.rocketdivision.starport:xp2000, szTargetName=nec, szAdditionalParameter=, nTargetID=...)
05:12:58 - CStarPortDoc::ResyncRegistryAndDriverContents: Exception caught: Logon to the server failed.
05:12:58 - Exiting func: CStarPortDoc::ResyncRegistryAndDriverContents(bAutomountDevices=1)
05:12:58 - Exiting func: CStarPortView::OnInitialUpdate()
05:13:10 - CMainFrame::OnCmdMsg: Enabling a command with ID=45000
05:13:12 - Entering func: CDriveLetterMap::~CDriveLetterMap()
05:13:12 - Exiting func: CDriveLetterMap::~CDriveLetterMap()
05:13:12 - Entering func: CStarPortAPI::~CStarPortAPI()
05:13:12 - Exiting func: CStarPortAPI::~CStarPortAPI()


Machine 2: Laptop AMD Athon4 1200MHZ *What the heck, Another log wont hurt. Heres to maybe the longest post to date

05:06:46 - Entering func: CLanguager::LoadLanguage(language=0x409)
05:06:46 - Exiting func: CLanguager::LoadLanguage(language=0x409)
05:06:46 - CStarPortApp::CheckLicense: License data not found.
05:06:46 - CStarPortApp::CheckLicense: *** TRIAL VERSION *** [ expires in 14 day(s) ]
05:07:08 - Entering func: CStarPortAPI::CStarPortAPI()
05:07:08 - Entering func: CStarPortAPI::DriverOpen()
05:07:08 - Exiting func: CStarPortAPI::DriverOpen()
05:07:08 - Entering func: CStarPortAPI::DriverVersion(...)
05:07:08 - CStarPortAPI::DriverVersion: Calling STARPORT_IOCTL_GET_VERSION
05:07:08 - CStarPortAPI::DriverVersion: Input buffer:
05:07:08 - CStarPortAPI::DriverVersion: Signature = 72417453:
05:07:08 - CStarPortAPI::DriverVersion: ApiVersion = 20002:
05:07:08 - CStarPortAPI::DriverVersion: Calling DeviceIoControl(...)
05:07:08 - CStarPortAPI::DriverVersion: DeviceIoControl(...) called successfully
05:07:08 - CStarPortAPI::DriverVersion: Output buffer:
05:07:08 - CStarPortAPI::DriverVersion: Signature = 52615473
05:07:08 - CStarPortAPI::DriverVersion: Version = 20050310
05:07:08 - CStarPortAPI::DriverVersion: ApiVersion = 20002
05:07:08 - CStarPortAPI::DriverVersion: Flags = 0
05:07:08 - Exiting func: CStarPortAPI::DriverVersion(...)
05:07:08 - CStarPortAPI::CStarPortAPI: StarPort version: 20050310; StarPort driver: API v20002, Build 0x20050310
05:07:08 - Exiting func: CStarPortAPI::CStarPortAPI()
05:07:08 - Entering func: CDriveLetterMap::CDriveLetterMap()
05:07:08 - Entering func: CDriveLetterMap::Refresh()
05:07:10 - Exiting func: CDriveLetterMap::Refresh()
05:07:10 - Exiting func: CDriveLetterMap::CDriveLetterMap()
05:07:10 - Entering func: CStarPortDoc::CStarPortDoc()
05:07:10 - Exiting func: CStarPortDoc::CStarPortDoc()
05:07:10 - CMainFrame::OnCreate: Minimizing application to tray.
05:07:11 - Entering func: CStarPortView::OnInitialUpdate()
05:07:11 - Entering func: CStarPortDoc::ResyncRegistryAndDriverContents(bAutomountDevices=1)
05:07:11 - Entering func: CDriveLetterMap::Refresh()
05:07:11 - Exiting func: CDriveLetterMap::Refresh()
05:07:11 - CStarPortDoc::ResyncRegistryAndDriverContents: Resyncronizing contents...
05:07:11 - Entering func: CStarPortAPI::GetDevices(...)
05:07:11 - CStarPortAPI::GetDevices: Calling STARPORT_IOCTL_TARGET_LIST
05:07:11 - CStarPortAPI::GetDevices: Input buffer:
05:07:11 - CStarPortAPI::GetDevices: Signature = 72417453
05:07:11 - CStarPortAPI::GetDevices: Calling DeviceIoControl(...)
05:07:11 - CStarPortAPI::GetDevices: DeviceIoControl(...) called successfully
05:07:11 - CStarPortAPI::GetDevices: Output buffer:
05:07:11 - CStarPortAPI::GetDevices: Signature = 52615473
05:07:11 - CStarPortAPI::GetDevices: NumberOfTargets = 0
05:07:11 - Exiting func: CStarPortAPI::GetDevices(...)
05:07:11 - Entering func: CStarPortAPI::InsertiSCSIDevice(dwIPAddress=0xC0A80204, dwPort=3260, szInitiaotrName=iqn.2003-06.com.rocketdivision.starport:fx210, szTargetName=nec2500, szAdditionalParameter=, nTargetID=...)
05:07:11 - CStarPortAPI::InsertiSCSIDevice: Calling STARPORT_IOCTL_TARGET_MOUNT
05:07:11 - CStarPortAPI::InsertiSCSIDevice: Input buffer:
05:07:11 - CStarPortAPI::InsertiSCSIDevice: Signature = 72417453
05:07:11 - CStarPortAPI::InsertiSCSIDevice: Flags = 0
05:07:11 - CStarPortAPI::InsertiSCSIDevice: ServerAddress = 192.168.2.4:3260
05:07:11 - CStarPortAPI::InsertiSCSIDevice: Parameter[0] = InitiatorName=iqn.2003-06.com.rocketdivision.starport:fx210
05:07:11 - CStarPortAPI::InsertiSCSIDevice: Parameter[1] = TargetName=nec2500
05:07:11 - CStarPortAPI::InsertiSCSIDevice: Calling DeviceIoControl(...)
05:07:11 - CStarPortAPI::InsertiSCSIDevice: Session failed, status == 1232 !
05:07:11 - Exiting func: CStarPortAPI::InsertiSCSIDevice(dwIPAddress=0xC0A80204, dwPort=3260, szInitiaotrName=iqn.2003-06.com.rocketdivision.starport:fx210, szTargetName=nec2500, szAdditionalParameter=, nTargetID=...)
05:07:11 - CStarPortDoc::ResyncRegistryAndDriverContents: Exception caught: The network location cannot be reached. For information about network troubleshooting, see Windows Help.
05:07:12 - Exiting func: CStarPortDoc::ResyncRegistryAndDriverContents(bAutomountDevices=1)
05:07:12 - Exiting func: CStarPortView::OnInitialUpdate()

Hi,

It looks like your StarPort machine has some network problems.
The default connection timeout for StarPort is about 60 seconds.
DUring this time all applications that try to use the disconnected drive are blocked as tou specified.
Could you wait for a minute when the machine freazes to check whether it is an issue with network connection?

Do you use the recent Starport v2.6.0 build 0x20050314?

The other way is to try the MS iSCSI initiator instead of StarPort.
You can download it from the MS site.

Please let us know about the results.

I am using that version according to the about screen. Funny though that the log shows a differnt version? Any ideas. Im gonn reboot the starwind machine and see if anything diff happens. I will also try the MS initiator as well.

I would love to get this functioning soon!

Anonymous wrote:I am using that version according to the about screen. Funny though that the log shows a differnt version? Any ideas. Im gonn reboot the starwind machine and see if anything diff happens. I will also try the MS initiator as well.

I would love to get this functioning soon!

The version in the log is the StarPort driver's build.

We 're looking forward to see the results of your tests.

Anyone wanna step in here and help out some more, perhaps via aim instant messenger.

Im almost down to a barebones system after about 20 reboots.

Is there any issues with symantec av 9 corp ed.
WinVNC
Airplus Extreme G
ANIO Service
ATI Display Driver
ATI Display Driver Utilities
BitTorrnet 3.4.2
Grab and Burn V.3.1.0
Live Update 2.0 *Symantec Corperation*
Microsoft .NET Framework 1.1
Microsoft .NET Framework 1.1 Hotfix
MS Office Pro 2003
MSN Messenger 6.1
Oncourse Navigator 4
PowerNow 2.0
Snapmedia Upgrade
Snapsync DLL Upgrade
Snapsync Software
Snapsync Upgrade
Starport Version 2.6.0 *Build 2005 03 - 14, Win32
Torrent Storm
TvT-RSS 1.3
VNC Free Edition 4.1.1
Widcomm Bluetooth Software
WinXP SP2

Thats It!.....Anyreason why this would not be functioning correctly at this point.

Also could someone link to the MS ISCSI innitiator. I wasnt able to locate it on the website. If its not posted please excuse my ignorance.

Oh well there you have it , Thats my laptop config. Not barebones but getting there. The next thing to come out is symantec.


Well thanks for the help. I enjoy testing this for ya for free! lol

Also,


I have waited and waited way past 60 secs.

FYI in the about screen I see the following.


2.6.0 Build 0x20050314
Starport Driver Version 0x00020002 Build 0x20050310

14 days left.

Any reason why the build numbers do not match???

Is there a way to fix this. Ive already uninstalled and reinstalled.

I am grabbing this from the link on your site for the free version for personal use only.

Shouldnt they match in this case?

If so, is there an easy fix or walk thru on this issue.

Thanks

Same results with MS initiator.




Back to square 1!

I have stripped down the PC that has starwind installed:

Here is what is left:

AC3 Filter:
ATI - Software Uninstall Utility
ATI Control Panel
ATI Display Driver
Broadcom 440x Driver Installer
ffdshow (remove only)
Powerstrip 3 (remove only)
Realtek AC97 Audio
Starwind, Version 2.6.0 Build 2005 03-14 Win32
Zoom Player (Remove Only)

I just dont get it, Ive stripped down both the server and the client. Something is buggering this sw up for me.

I really wanna find the culprit at this point.

Im gonna start disabling services at this point. I had a similar problem with RDP and nvidia detonator drivers on Server 2003. It would log in and then force a log out. It is documented on the web. Something is crashing Starport on the client side. The Starwind side remains active. Feel free to chime in.

Dear Sir,

I'd recommend you to install some third party iSCSI target software and try MS iSCSI initiator Vs. 3rd party iSCSI target software. If you'll have identical picture I guess it's your network problem and has nothing to do with the Rocket Division Software. Of course we'd try to help you in all of the cases but I'd prefer us to isolate the problem. For now StarPort seems to be not guilty at all. Next suspected one is StarWind. So if replaced with other iSCSI target and result preserved - your network is broken and we'd try to find out what's wrong with it.

So please use UNH, DataCore or SBS iSCSI targets with MS iSCSI initiator.

Thank you!

guest - nc88keyz wrote:Same results with MS initiator.




Back to square 1!

Hi,

I guess you have already downloaded the MS iSCSI initiator, but here is the link to it to be sure:
http://www.microsoft.com/downloads/deta ... laylang=en

So the MS initiator behaves the same way as our StarPort?
It seems for me that there is some problem with your network or the machine where the initiator runs...

Have you tried to install StarPort or MS initiator on some other machine?
Does it hang too?

It's all right with the StarPort versions. One of them (2.6.0 Build 0x20050314) - is the StarPort application version and the other is the verson of the StarPort kernel driver.

There may be issues with a firewall software or with a antivirus blocking TCP/IP port 3260.
You could try to analyze the network traffic wth Ethereal sniffer to see what's happen.

Definitely using a clean Windows installation with StarPort could show is this a network related problem or one of the installed software family leads to the problem.

anton (staff) wrote:Dear Sir,

I'd recommend you to install some third party iSCSI target software and try MS iSCSI initiator Vs. 3rd party iSCSI target software. If you'll have identical picture I guess it's your network problem and has nothing to do with the Rocket Division Software. Of course we'd try to help you in all of the cases but I'd prefer us to isolate the problem. For now StarPort seems to be not guilty at all. Next suspected one is StarWind. So if replaced with other iSCSI target and result preserved - your network is broken and we'd try to find out what's wrong with it.

So please use UNH, DataCore or SBS iSCSI targets with MS iSCSI initiator.

Thank you!

Anton,

I guess the problem has nothing to do with StarWind.
The initiator machine hangs when trying to mount a StarWind's drive, not the target machine.

There should be a network problem or one of the programs installed on the initiator machine messes things up.

Valery,

I also think it's network problem. However I'd like to be 200% sure

valery (staff) wrote:

anton (staff) wrote:Dear Sir,

I'd recommend you to install some third party iSCSI target software and try MS iSCSI initiator Vs. 3rd party iSCSI target software. If you'll have identical picture I guess it's your network problem and has nothing to do with the Rocket Division Software. Of course we'd try to help you in all of the cases but I'd prefer us to isolate the problem. For now StarPort seems to be not guilty at all. Next suspected one is StarWind. So if replaced with other iSCSI target and result preserved - your network is broken and we'd try to find out what's wrong with it.

So please use UNH, DataCore or SBS iSCSI targets with MS iSCSI initiator.

Thank you!

Anton,

I guess the problem has nothing to do with StarWind.
The initiator machine hangs when trying to mount a StarWind's drive, not the target machine.

There should be a network problem or one of the programs installed on the initiator machine messes things up.

Define a network problem - Are you saying it has something to do with my router.


Absolutely everything is working just fine all my machines except this software program.

I have now stripped both machines down to the bare minimums. Its unfortunate, but I dont see this software being that important if I have to jump through hoops just to get it to do a basic function.

I have tryed switching starwind to differnt machines and starport accordingly. Same results. Like I said. Never had an issue with Dlink router, Using latest firmware etc. Also using a dlink wireless G card, although it doesnt make a difference because all machines do the same thing wireless or not.

Can you try NTTtcp or IPerf to verify what's your network throughoutoput between target and initiator machines? Do you use NAT or some other IP mangling installed?

Anonymous wrote:Define a network problem - Are you saying it has something to do with my router.


Absolutely everything is working just fine all my machines except this software program.

I have now stripped both machines down to the bare minimums. Its unfortunate, but I dont see this software being that important if I have to jump through hoops just to get it to do a basic function.

I have tryed switching starwind to differnt machines and starport accordingly. Same results. Like I said. Never had an issue with Dlink router, Using latest firmware etc. Also using a dlink wireless G card, although it doesnt make a difference because all machines do the same thing wireless or not.

Could you please give me a step x step on using either iperf or NTTCP

I have located them both, just dont know what you mean. Sorry for being a noob at this level.

thanks.