Citrix

[rpmiller]

I'm using the latest wingate on my windows NT server. I'm trying to set up a web-based citrix client to access outside machines, but once I try to connect using citrix, I can't establish the connection and I get web page not found. I've got my browser set to use my local proxy server on port 80 for all protocols (I've tried setting SOCKS to port 1080, too). I'm not sure how citrix works or what it's trying to do - set up a VPN tunnel?

I'm sure I have to change some settings either in the browser or wingate or both, but I don't know how to proceed. Any help is greatly appreciated.

Ryan

[jamesc]

Is using NAT an option? You will not require to use any proxy settings.

Or if you are trying to access it from the same computer that WinGate is installed on, you should not have to set any proxies. Can you explain your setup with a bit more detail?

Some information about NAT is available on this post: http://forums.qbik.com/viewtopic.php?p=17352#17352

[rpmiller]

Hi,

I've got a DSL modem connected to the internet and an NT server with 2 network cards - one to the DSL modem and one to the internal LAN. I'm using NTLM authentication and fixed IP addresses on the client machines. I had to set up the proxy in IE to get the client machines to browse properly, but I think that interferes with Citrix. Not sure what to try next. Thanks for your help.
Ryan

[jamesc]

1. Have you tried using NAT? It can be used by itself, or with proxies. NAT will take care of any extra port required by the citrix web client.

2. If the citrix web client is being delivered from a remote web server, you may want to turn off caching for that URL in question. So if the client was located at www.server.com/citrix, you could create a rule as follows:

Gatekeeper --> Caching --> What to cache --> Specify which requests to cache --> Add filter --> Add critereon --> "This Critereon is NOT met if" --> HTTP URL CONTAINS www.server.com/citrix --> ok --> ok

[jamesc]

Re-reading this post, and from experience I had in the lab today...

When using the proxy directly from a client machine, it was not passing on the NTLM authentication properly (for a MS SharePoint server). What we had to do was use NAT, with transparent proxies (intercepts).

So in the case I had in the lab today, I had to do as follows.

1. Open Internet Explorer, and set it not to use a proxy server. You "may" also want to set the security settings to prompt for a username and password. (IE --> Tools Menu --> Security tab --> Custom Level --> Scroll to the bottom and select under the label "User Authentication" --> Prompt for Username and Password)

2. Check NAT was installed



3. Set the client computers TCP/IP settings to utilise NAT

If WinGate Server internal TCP/IP settings is:
192.168.9.1 / 255.255.255.0

Then WinGate Client TCP/IP settings is:
192.168.9.2 / 255.255.2555.0
Gateway and DNS 192.168.9.1


4. Then turn on intercepts in the WWW Proxy service
GateKeeper --> Services --> WWW Proxy Service --> Sessions




Then try again.

[rpmiller]

Hi,

Thanks for your help. That's exactly what I did and it now works just fine! Good to have confirmation that the settings I changed are the correct ones. Thanks again,
Ryan