Problems with ProCurve Switch Trunking

[MattBCA]

Hi

I'm hoping this is the right place to be posting this.

I'm new to trunking and configuring managed switches.

I have a hp procurve 1800-24g, a windows server 2008, and a qnap (NAS).

I have add a dual port intel nic to the windows server which I have set with static ip's of 11.1.1.3 and 11.1.1.4

The qnap has 2 nic ports which I have set with static ip's of 11.1.1.1 and 11.1.1.2 

The rest of the network is on a different ip range but all are on the subnet 255.255.255.0

I have connected all 4 nic ports to the procurve ports 19-22

I then went into the procurve config and setup ports 19-22 as a T1 trunk.

As soon as I do that I can no longer communicate to the qnap from the windows server via web config page or even ping it. I also tried from the procurve web interface "diagnostics", trying to ping 11.1.1.1 or 11.1.1.2 but when the trunk is setup it times out. But if I ping the windows server the same way on 11.1.1.3 or 11.1.1.4 I get a reply.

(I plan on setting up on the windows server and qnap "nic teaing" or "MPIO" (was told that I shouldn't use nic teaming for NAS devices but instead MPIO) but I haven't set this up yet as I just want to get the procurve part of the setup going first)

Any help would be great, as I haven't been able to work it out from the hp manuals.

thanks

[Davy Priem]

If you give every interface a dedicated ip, you don't need to trunk the interfaces.

second: I would not use public ip addresses in a LAN.