Snappa2000
asked on
Using a MultiHomed Server and Citrix
Hi all,
We currently run a Citrix PS 4.5 Farm with all servers (HP) having teamed NIC's. We need to connect three of the servers to a seperate WAN B as well as being connected to the WAN A.
What we would like to do is break the team, and split each NIC off to the WAN A and WAN B. I only want Citrix to be accessible via WAN A NIC, as this is the client facing side, and the server to have access to the WAN B Side.
What changes are required to only provide citrix access to the WAN A NIC, as when you do this and run a QFARM it shows both IP Addresses in the list. We have seen a problem with Secure Gateway unable to run the published application as its trying to get to the server using the other NIC (WAN B).
The WAN B would (I assume) be set up without a gateway, and static routes be placed on the server, therefore allowing access to the devices on WAN B.
End of the day we would like the three servers able to access systems in WAN B, and appear like a single IP on the WAN A side for Citrix.
Thanks
We currently run a Citrix PS 4.5 Farm with all servers (HP) having teamed NIC's. We need to connect three of the servers to a seperate WAN B as well as being connected to the WAN A.
What we would like to do is break the team, and split each NIC off to the WAN A and WAN B. I only want Citrix to be accessible via WAN A NIC, as this is the client facing side, and the server to have access to the WAN B Side.
What changes are required to only provide citrix access to the WAN A NIC, as when you do this and run a QFARM it shows both IP Addresses in the list. We have seen a problem with Secure Gateway unable to run the published application as its trying to get to the server using the other NIC (WAN B).
The WAN B would (I assume) be set up without a gateway, and static routes be placed on the server, therefore allowing access to the devices on WAN B.
End of the day we would like the three servers able to access systems in WAN B, and appear like a single IP on the WAN A side for Citrix.
Thanks
ASKER
Thats what we thought in theory.. What is happening is we do that, and the two addresses appear in QFARM. If we go and disable the WAN B network card and restart the server it appears as one nic (the correct one) in QFARM and all works well via the web interface.. We then can re-enable the WAN B network card and all is fine until the next restart.
We have even tried to recreate the ICA Listerner to the correct nic, but still nothing.
Cheers
We have even tried to recreate the ICA Listerner to the correct nic, but still nothing.
Cheers
Did you set the nic here (my screenshot shows all nics, but you should be able to select a nic here, reboot, and it should show up correct in qfarm after the reboot.
ASKER
Yes we set it to the correct NIC, and double checked, and rebooted. We even went as far as deleting the ICA Listener and cleared the LHC and recreated it.
Does it appear in QFRAM because of another service?
Cheers
Does it appear in QFRAM because of another service?
Cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
missed the dscheck /clean options, hence why it was still appearing!!
Thanks
Thanks
Start > Run > tscc.mcs
Under Connections, right click ICA-tcp, Left Click Properties
Network Adapter tab
In here you can select the appropriate NIC for your WAN B and then restart IMAService. After that the server should listen only on that NIC card and show up in qfarm with just that address.
ica-tcp.JPG