Disconnects after WI 3.0 Upgrade

[mjbrown]

Interesting situation I'm running into here. Last week, I upgraded the MF Web Interface Software on 2 of my Web Servers to 3.0. (I have had this running in a Test Environment for a couple of months with no issues.) After the Upgrade in production, I have selected a few 'test' users to use the system to work out any bugs or problems. They are complaining that after 'about' 10 minutes of being connected, they are getting disconnected and then immediatelt re-connected (with the 'attempting to reconnect in 30 seconds, click reconnect now or cancel'). They are able to re-connect and pick up where they left off without issue, but very annoying. To test some theories, I had them use our OLD connection method, and the problem went away. Here is the Environment:

Citrix Servers: IBM Servers, Windows 2000 sp4
Metaframe: Metaframe XPe SP3/FR3
DataStore: SQL running on an Enterprise SQL Server
Web Interface Servers: Win2k SP4, IIS
Citrix Connection Config: No Connection Timeout, No Idle Timeout and Disconnect Timeout=1 Min
Pushing Client wficat.cab 8,0,24737,0 with connection
ICA Keep-Alives are Active and set to 60 seconds, but this does not change anything when unchecked....

I would assume that once a connection is made to the Published Application that the WI server would be out of the loop, so not sure if the upgrade has something to do with it...

Any help, suggestions or fixes would be greatly appreciated.



Mike Brown

 

[mjbrown]

After investigation, it appears to be Client related. Once the new (web) client is installed on a PC, even our old connection method's time-out. If the client is downgraded, the problem goes away.

Is there a setting in a freshly downloaded client that would cause this or be able to modify to prevent the problem???

Mike Brown

 

[Ogi]

Hi,

Sounds like your Terminal Server CALS on your PC's. What do you have in the MSLicensing key.

What you could do is log onto the PC as an Administrator, log into your Web Interface as the user, run a published application for a while. Log out of Citrix. Close the browser. Log out as the Admin. Log in as the user, start the browser, start a published application, what happens?

Cheers,
Carl.

 

[mjbrown]

Thanks,

All workstations are XP and all Servers (Web and Citrix) are 2000.
I would agree about the licensing (as it's caused other issues in the past), but it still works with no time-outs/disconnects with our old Manual Web Page with the preconfigured .ica files.
This also happens to me logged on as an Admin. I have deleted the TS License from my workstation and will try again to see if it still occurs.
Also, thought there may be something in the "Client Scripts" directory on the Web Interface Server, but I have not yet had the chance to dig around in the coding to see if there is a disconnect time interval set in there somewhere.
Just seems fishy that our old method works without issue and only since installing WI 3.0 has the problem come up...also, I would think that once a session is opened on Citrix, the Web Interface Server would no longer be in the mix, but who knows???

Mike Brown

 

[mjbrown]

Nope, just happened to me...Was connected to a Citrix session, 10 minutes went by and it disconnected, and immediately re-connected me to the same session...very weird!!!

Any other thoughts?

I am still pointing at the "Client Scripts" and a setting in there!

Mike Brown

 

[mjbrown]

Sorry for the frequent updates, but this problem is really bugging me!!!

I found article CTX103672 on the Citrix KB that mentions a time-out in the ASPX scripts. Maybe I will give it a shot and see wha happens...

Mike Brown

 

[mjbrown]

Thanks for the help Ogi...PROBLEM RESOLVED!!!

Looks to be a setting in the Proxy Servers (Novell bordermanager). In the WIAdmin, I changed the Client Side proxy Settings to NONE and all is good!! Know it had to be something easy, but couldn't find it!!



Mike Brown