<div>
You can limit the IP address that Citrix uses by going into the Terminal Server Configuration Tool, once here you can force the ICA connector to only use a certain nic card (default is to listen on every interface).<br />
<br />
Start &gt;&nbsp;Run &gt;&nbsp;tscc.mcs<br />
Under Connections, right click ICA-tcp, Left Click Properties<br />
Network Adapter tab<br />
<br />
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.<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2009/03_w12/119097/ica-tcp.JPG" target="_blank" class="file-inline" title="SS of Network Adapter screen (29 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>ica-tcp.JPG</a>
</div>


ica-tcp.JPG

<div>
Thats what we thought in theory.. What is happening is we do that, and the two addresses appear in QFARM. &nbsp;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.<br />
<br />
We have even tried to recreate the ICA Listerner to the correct nic, but still nothing.<br />
<br />
Cheers<br />

</div>


<div>
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.
</div>


<div>
Yes we set it to the correct NIC, and double checked, and rebooted. &nbsp;We even went as far as deleting the ICA Listener and cleared the LHC and recreated it.<br />
<br />
Does it appear in QFRAM because of another service?<br />
<br />
Cheers<br />

</div>


<div>
missed the dscheck /clean options, hence why it was still appearing!!<br />
Thanks
</div>


<div>
<div class="content wysiwyg-content">
Hi all,<br />
<br />
We currently run a Citrix PS 4.5 Farm with all servers (HP) having teamed NIC's. &nbsp;We need to connect three of the servers to a seperate WAN B as well as being connected to the WAN A.<br />
<br />
What we would like to do is break the team, and split each NIC off to the WAN A and WAN B. &nbsp;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. <br />
<br />
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. &nbsp;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).<br />
<br />
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. &nbsp;<br />
<br />
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.<br />
<br />
Thanks 
</div>
</div>


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 

Using a MultiHomed Server and Citrix

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

Citrix is the synonym for the virtualization and application infrastructure systems developed by the company of the same name. Main areas are application virtualization, Software-As-A-Service (SaaS), cloud-computing and networking. The two most well-known are Citrix XenApp or Citrix CloudPlatform.