Network Settings for iSCSI

Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
jldodge710
Posts: 2
Joined: Sat May 08, 2010 5:52 pm

Sat May 08, 2010 7:07 pm

I have a Thecus NAS Server with 5GB RAID 6 config. It's IP is 192.168.2.102 and 192.168.2.254.

The network config is DSL modem (192.168.1.254) to Linksys Wireless router (192.168.2.1) to 3com router. My computer and the NAS are connected into the 3Com router.

I had some connection problems with my DSL provider which have now been fixed. However, I cannot connect to the NAS Server via Starport. Starport tries to connect to 192.168.2.105 (never used that IP address before) and I cannot add a "new" device with the 102 setting.

Can someone give me some ideas of what to do or change? Thanks in advance ...
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Sat May 08, 2010 8:20 pm

Can you telnet from your client to iSCSI port 3260 on your iSCSI target IP?
jldodge710 wrote:I have a Thecus NAS Server with 5GB RAID 6 config. It's IP is 192.168.2.102 and 192.168.2.254.

The network config is DSL modem (192.168.1.254) to Linksys Wireless router (192.168.2.1) to 3com router. My computer and the NAS are connected into the 3Com router.

I had some connection problems with my DSL provider which have now been fixed. However, I cannot connect to the NAS Server via Starport. Starport tries to connect to 192.168.2.105 (never used that IP address before) and I cannot add a "new" device with the 102 setting.

Can someone give me some ideas of what to do or change? Thanks in advance ...
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
jldodge710
Posts: 2
Joined: Sat May 08, 2010 5:52 pm

Sun May 09, 2010 12:35 am

I could not telnet to port 3260 nor the IP address ... errors both times.
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Sun May 09, 2010 12:41 am

This means StarPort is not guilty and you have either outging ports blocked by firewall on the client or incoming ports blocked by firewall on target side. Double-check firewall, routing and your target settings.
jldodge710 wrote:I could not telnet to port 3260 nor the IP address ... errors both times.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Post Reply