ok, now I figure out what's the problem. It's still the Symantec Client Security problem. I uninstalled it and found starport worked. I don't know what's the difference between disable it and uninstall it.

This is not a name resolution problem. I used IP address to connect to the target. The folowing is the starwind log: 3/9 0:33:53.874 6e8 Srv: StarWind iSCSI Target v3.5.3 (Build 20080229, Win32) 3/9 0:33:53.874 6e8 Srv: Built Feb 29 2008 12:20:05 3/9 0:33:53.874 6e8 Srv: System CPU count: 1 3/9 0:33...

The starport log contains only the following 3 lines: 3/4 21:53:15 a3c ntsrv: StarPort Service v3.5 (Build 20080111, WinXP x86) 3/4 21:53:15 a3c Srv: No bound volumes found. 3/4 21:53:15 a3c Srv: Service started. Installed Softwares: 2007 Office System Compatibility Package 3D-FTP 7.01 Adobe Flash P...

Thank you for your reply. Firewall problem. That was my first thought. However, please note that when I turn off firewalls completely at the client side and at the server side. The result is the same. Please also note that Microsoft Initiator can logon to starwind at the server. So, as I said, it's ...

To add to the above description: I tried using starport on the server to connect starwind on the client. Succeeded. I installed Wireshark on the server to captured port 3260 traffic. When using starport on the client to connect the server, no traffic captured. When using MS initiator 1.06 to connect...

I used starport 3.5.4 free edition to add remote iscsi device, but got the following error message: "Failed to connect to remote server. Server maybe refusing network connections. You may need to check firewall setting" There is firewall installed on the server. port 3260 is allowed inboun...