KernSafe Technology

I am having some trouble with iStorage Server. I am testing it and another iSCSI solution. I have it installed on a new Windows 2008 standard x64 server. Testing with just the built in intel RAID. I get connection failures on adding the portal to the client machines when the firewall is turned on.

I am testing with a Win 2k8 and Vista Ultimate clients, both operate the same way. I have started the iSCSI service, and allowed it through the firewall. I have added the storage server program to the firewall. I have manually added 3260, 135, 138 udp to the firewall. No matter what gyrations i go through, it only works when i disable the firewall on the storage server.

Its a brand new server, no other applications installed. iStorage Server and the other iSCSI service i am testing both have the same problem. Are there other ports or something else i am missing? I tried loading a port monitor on the storage server to see if there were other ports in use, but i didnt see anything else.

Have you tried it with IP authentication instead of CHAP? I was seeing something very similar, with connections refused, using CHAP from Windows 7 machines but no connection issues with IP authentication.

Thanks for the suggestion. Same results unfortunately. With the firewall up, connection failure with IP address authentication. Turn the firewall off and re-register the target portal and it completes immediately, the disk shows up in storage manager and you can go to work. I started enabling firewall rules in batches to see if i could come up with one that was needed for the service to operate, but so far no luck.

are there any ancillary services it requires that i might need to add filters for? or patches that are problematic to have installed?

thanks for the help.

dantell wrote:I have manually added 3260, 135, 138 udp to the firewall.
...iStorage Server and the other iSCSI service i am testing both have the same problem.

There might be a problem in your firewall settings, the port 3260 you have opened is UDP or TCP? The only one port is needed to be opened is TCP 3260, if you do not use remote management function.
In my test, add a tcp port 3260 to the Inbound rules is OK, but if you want to use mirror function or make your sever use initiator program, you should also need to add this port to the Outbound rules.

Thanks for the response. Port 3260 that i opened was tcp. I was reading an MS KB article that listed ports required for their iscsi target. So i gave it a shot.