I wouldn't mind installing WI on Server 1, but since it's a DC (domain controller, not data collector, sorry), it doesn't work. I get strange errors trying to install it. I've checked the Citrix forums and found that it appears WI doesn't work/isn't supported installing on a domain controller. I think I'm going to have to investigate using a different port number. Now that I think about it, I could just put a redirect at www.site.com/citrix to point to www.site.com:81/citrix/metaframe or whatever the URL happens to be (and another for SSL). Other than the non-standard port, can you think of anything that would prevent that from working correctly, with only 1 public IP? On 3/12/07, Carl Stalhood <cstalhood@xxxxxxxxxxxxx> wrote:
Why not install WI on Server 1? Otherwise, if you want the same port number (80/443) to hit two different internal servers you will need two different public IPs. Or install Microsoft ISA with its server publishing capability? *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On Behalf Of *Adam Granatela *Sent:* Monday, March 12, 2007 2:23 PM *To:* thin@xxxxxxxxxxxxx *Subject:* [THIN] IIS/Web Interface question Small network, 2 servers, 1 public IP address. Server 1 is a DC/file server, Server 2 is going to be the Citrix/Web Interface server. Problem is that I'm running into, Server 1 is also a web server. The router passes 80 and 443 to Server 1, which hosts the site's 3 different domains using host headers. No DMZ, ports opened up to the DC, I know. But I don't have a lot to work with here. How do I go about getting Web Interface set up on Server 2 so it can be hit from the outside? Can I set up a virtual directory on one of Server 1's web sites to point to Server 2? If I had 2 public IP addresses this would be easy, unless I'm missing something straight forward and my inability to think after my brain went through time travel this weekend is gone. Any suggestions? Both servers are Win2k3, PS4 (possibly 4.5), a simple network with a few simple apps. Thanks much, Adam