Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
Bluesky
- Posts: 4
- Joined: Wed Jul 28, 2010 1:16 pm
Wed Jul 28, 2010 1:24 pm
Dear Support Team,
I am currently testing the the starport Storage Controller Software.
I am using this on Win7 an try to connect some AoE Devices.
I opened the Star Port Controller Software and add a new device.
> Choose AoE Remote
>select a network device
This contains nothing to choose. How can I get a network device here. The Pc has a Gbit/Network card enabled.
But i can not see anything here. What is wrong?
Can you help?
Thx Blue
-
Max (staff)
- Staff
- Posts: 533
- Joined: Tue Apr 20, 2010 9:03 am
Wed Jul 28, 2010 2:10 pm
Have you tried to connect the device using any other AoE initiator software?
This could be an AoE device problem.
I would also like to know about the software version you are using.
Max Kolomyeytsev
StarWind Software
-
Bluesky
- Posts: 4
- Joined: Wed Jul 28, 2010 1:16 pm
Wed Jul 28, 2010 2:22 pm
Max (staff) wrote:Have you tried to connect the device using any other AoE initiator software?
as far as I know , no I havn't. But I have a NDAS software running. I hope this is not on AoE base?
Max (staff) wrote:I would also like to know about the software version you are using.
I tried the latest version, I think > 5.5 build.... 903
-
Max (staff)
- Staff
- Posts: 533
- Joined: Tue Apr 20, 2010 9:03 am
Wed Jul 28, 2010 2:47 pm
I'd like to ask you to disable the NDAS and reproduce the problem, if this were a StarPort bug the symptomes would have been a bit different.
Max Kolomyeytsev
StarWind Software
-
Bluesky
- Posts: 4
- Joined: Wed Jul 28, 2010 1:16 pm
Wed Jul 28, 2010 3:02 pm
I disabled this Driver (NDAS) and reboted the system since this one is starting on boot.
Now this is no running anymore, (has not been started after booting), but the problem remains the same.
I looked up in the nework properties for my Gigaethernet NIC:
I have 2 StarEther inputs:
a) ...NDIS Protocol Driver for FCOE
b) ...NDIS Protocol Driver
Is this enough?
-
Bluesky
- Posts: 4
- Joined: Wed Jul 28, 2010 1:16 pm
Thu Jul 29, 2010 10:26 am
Hi what I did so far:
This morning I deinstalled die Starport Software completely. After boot and reinstallation and new boot it was fixed. Maybe there was something wrong during the installtion, or the NDIS Driver did something?? I don't know. The new installtion was done without working NDIS Driver. Maybe this helps somebody as well?
After all, I allso installed and tried your new version with the AoE initiator. Works also!
Good work and many thanks!
-
anton (staff)
- Site Admin
- Posts: 4021
- Joined: Fri Jun 18, 2004 12:03 am
- Location: British Virgin Islands
-
Contact:
Thu Jul 29, 2010 7:32 pm
As you've uninstalled and we cannot get driver load statuses I can only GUESS NDIS protocol driver did not start for some reason or did not bind to network interface (improper boot order, NDIS protocol started BEFORE NDIS miniport driver did load). So you did not give us a chance to find this out, pinpoint and fix
Bluesky wrote:Hi what I did so far:
This morning I deinstalled die Starport Software completely. After boot and reinstallation and new boot it was fixed. Maybe there was something wrong during the installtion, or the NDIS Driver did something?? I don't know. The new installtion was done without working NDIS Driver. Maybe this helps somebody as well?
After all, I allso installed and tried your new version with the AoE initiator. Works also!
Good work and many thanks!
Regards,
Anton Kolomyeytsev
Chief Technology Officer & Chief Architect, StarWind Software

-
anton (staff)
- Site Admin
- Posts: 4021
- Joined: Fri Jun 18, 2004 12:03 am
- Location: British Virgin Islands
-
Contact:
Thu Jul 29, 2010 7:34 pm
...and it's good to know everything is up and running at your side

Regards,
Anton Kolomyeytsev
Chief Technology Officer & Chief Architect, StarWind Software
