What is the point of Session Reliability?

[cbrunet17]

I'm currently having a problem with our citrix web connection. Everytime anyone tries to open a published application, they get an error message stating that "Cannot connect to citrix metaframe server. Protocol driver error." Now, what I'm seeing all over the citrix boards and all over these boards and all over the rest of the net, is that the best bet is to turn off Session Reliability. What I'm wondering is, are there any other users out there who have tried this? What kind of consequences does this bring? Does this actually fix the problem?

Thanks in advance.

 

[MikeBatters]

If you are doing this through a firewall you may want to just open up 2598 & 1604 as well as 1494.

Mike

*************************************

Remember - There is always another way..........I just haven't found out what it is yet!

 

[cbrunet17]

Well, we removed session reliability and are getting a different error now.

SSL error 29 - Proxy denied access to <multiple characters> port 1494

From what I can tell, we need port 443 opened on our firewall, which we tried. We do indeed have port 2598 and 1494 opened, but what is 1604 for? From what I see is its icabrowser according to:

http://www.iana.org/assignments/port-numbers

Anyways, added it too and the same problem is arising. The log on the access gateway is telling us that it seems to use a dfferent protocol now that session reliability is off. Before it was simply failing on STA/CGP, but now its "STA/SOCKS Context error" that seems to be the problem.

 

[MikeBatters]

That sounds more like it might be a proxy problem at the remote end for the new error messages.

When we deploy similar solutions we permit 1494, 2598 & 1604 and everything works just fine. I would turn it back on and permit it on the firewall just as a test.

Also is all the routing set properly so that the server can route back to the connecting machine? What happens if you run a traceroute?

Mike

*************************************

Remember - There is always another way..........I just haven't found out what it is yet!

 

[cbrunet17]

Well, we got everything working. It was indeed a firewall problem. We did at one point have all the ports opened that were needed, but perhaps there must have been some rule that we missed. We removed all the settings and redid the rules on the firewall and things are coming through now.

 

[MikeBatters]

Cool.....

Mike

*************************************

Remember - There is always another way..........I just haven't found out what it is yet!