[THIN] Re: Metaframe 1.8 Published Application
- From: Jason Miller <JMiller@xxxxxxxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Mon, 7 Jun 2004 17:21:52 -0400
In my own opinion, I wouldn't go with 2 active NIC's on your Citrix servers
unless there's a real need to do so. Just seems like that'd be too much to
worry about.
Anyhow...to find out what's doing your load balancing, you need to know what
your "zone data collector" or "ZDC" is. To find this out, go to a command
prompt on one of your Citrix servers and type: qfarm /zone That will
tell you what your ZDC is.
Just for kicks, I'd try adding a persistent route on this server to the
subnet that you're having an issue with & see if you can connect. Sounds
like your ZDC just doens't know how to get back to your 192.168.100 subnet.
Hope this helps.
-Jason Miller
-----Original Message-----
From: Matt Barys [mailto:MBarys@xxxxxxxxxxxxxxx]
Sent: Monday, June 07, 2004 4:38 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Metaframe 1.8 Published Application
That might be! I added the .100 subnet to the second nic on each server and
everything was fine until the reboot Sunday morning. After that no on could
connect to the servers via 192.168.0.0, but the 100 subnet worked. I
disabled the secondary nics and went back to the old configuration that
worked. Maybe they are still trying to route? How would I know which server
is the master?
Thanks
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf
Of Jason Miller
Sent: Monday, June 07, 2004 3:11 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Metaframe 1.8 Published Application
I seem to remember a problem like this where I used to work. I'm going back
about 2 years, so bare with me. However, we had the same problem at a
branch office not being able to see the citrix servers which were on a
different subnet. I didn't fix it, but I remember it having something to do
w/ the routing table on the citrix server that did the load balancing.
Keep in mind I didn't fix it at the time and didn't get an explanation of
what he chaned to resolve the issue, but I'm sure of the fact that he told
me it was a problem w/ the routing table on the server that did the load
balancing.
Hope that helps push you in the right direction.
-----Original Message-----
From: Matt Barys [mailto:MBarys@xxxxxxxxxxxxxxx]
Sent: Monday, June 07, 2004 3:54 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Metaframe 1.8 Published Application
They are there. That's what's confusing. The servers are listed as
192.168.0.82, .83, and .84. If I'm a client on 192.168.0.0 everything works
great. If I'm a client on 192.168.100.0, I can't get the ICA Client to find
the servers. I even gave the three Citrix servers a .100 address each and
tried it that way with no luck.
Matt
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf
Of Gabe Knuth
Sent: Monday, June 07, 2004 2:41 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Metaframe 1.8 Published Application
How is the Application Set configured? Check the primary servers under the
app set properties and see if you have the MF server(s) listed. If it's
empty, that probably explains it.
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Matt Barys
Sent: Monday, June 07, 2004 12:17 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Metaframe 1.8 Published Application
I have a question for all. Up until Saturday, my Published Application
called Fairrington Desktop which is the desktop for our users doesn't work
anymore when we are on the second subnet. If I set up a new client I can't
even see that or my servers in the list, but if I go back on the original
subnet 192.168.0.0 everything is fine. If I'm on the second subnet
(192.168.100.0) I can go directly to one of the servers, but not through the
Published Application. If there anything I can look at to see when this is
happening?
Thanks,
Matt
Other related posts:
