Citrix Web interface down

We currently have 4 Citrix presentation 4.5 servers in the farm each configured identical ( for application installation ). each of them have the web interface installed and when you connect to citrix from home you get one of the servers. The users have no idea we have four servers , it is seamless to them.

The problem is that if i shutdown our server called "Citrix01" no one can get to the web interface from home.

I know basically nothing about the citrix servers as i did not initially set them up,  but i think citrix has a database or something to manage itself. My guess is this piece is running on "Citrix01"

does this make sense ?

any one know a way to avoid this issue ?

Periodically we disable certain servers for maintencnce , but obviously "CITRIX01" cannot be shutdown for maintence

Thanks
EkuskowskiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Carl WebsterCommented:
You should have the Web Interface installed on only one server.  Ideally that server would be in the DMZ and be behind a Citrix Secure Gateway (CSG) server or Citrix Access Gateway appliance.  CSG is FREE and helps secure your Citrix traffic with SSL.

My recommendation would be to have 1 server, can be low end or virtual, that has CSG and WI installed.  The WI server points to the XML Broker/Data Collector for your farm (command prompt qfarm /zone will tell you that server) plus another for backup.  User hits the URL for the CSG box, CSG routes to WI, WI routes to XML Broker for authentication, XML Broker provides lists of apps and servers to WI, WI builds list of apps for the user and icons, users clicks an icon, XML Broker determines the least busiest server and directs the user to that server, the server launches the app and the user gets to work.
0
jvr006Commented:
I assume the NAT in your firewall points to Citrix01, which explains why your users can't connect when it is down. There really isn't anyway around this with your current setup.

Carl suggestions are great for securing your farm. The only thing that I would add is that if you would would want to add some redundancy, create two web interface server and use microsoft NLB.
0
EkuskowskiAuthor Commented:
Thanks CarlWebster for the security info, we are thinking of rebuilding our Citrix environment using 2008 servers and the latest version of Citrix maybe we will change our setup at that time and use the CSG as you suggested.

I'm still confused on the XML Broker/Data collector

Currently when i run qfarm /zone
I get Zone Name 192.168.1.0 and Data collector Citrix01 no backups ( which is probably my problem)

Is the data collector and XML broker the same thing ??

It seems that the webserver needs to contact the XML broker in order to display the published applications. Where in IIS do I look to see or change the location of the XML broker ?
0
EkuskowskiAuthor Commented:
One  more thing to add,  when i log into my web interface, it takes about 45-seconds before i see my published apps. Could this delay also be related to the webserver or XML Broker communication ???
0
Carl WebsterCommented:
> Is the data collector and XML broker the same thing ??

Yes and no.  The Data Collector is chosen by an election process.  You can dedicate a server to the role, if application enumeration takes a long time, but that does NOT guarantee that is the server that will be used for the Data Collector role.  Example, you have a dedicated ZDC and then install an update on another member server.  That member server could now have a higher version # and will instantly become the ZDC.  That is why you always update your ZDC first and then the backup ZDCs (if any).

> Where in IIS do I look to see or change the location of the XML broker ?

You don't look in IIS, you look in the config for the WI site.  http://www.dabcc.com/article.aspx?id=12795 and go down to Figure 15.

> One  more thing to add,  when i log into my web interface, it takes about 45-seconds before i see my published apps. Could this delay also be related to
> the webserver or XML Broker communication ???

That could be an overloaded ZDC or it could be slow network traffic or...  I would look first at the ZDC.  That is what is used to build the list of applications.

http://support.citrix.com/proddocs/topic/web-interface-hardwick/wi-how-web-interface-works-gransden.html
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Citrix

From novice to tech pro — start learning today.