Correct, clients.ini requires IP addresses. Internals (10.0.0.1) and the loop (127.0.0.1) also work.
This is actually clarified by the fact that the 12 additional characters added to the USR are the IP address and PORT number of the service to which the user 'belongs'. To clarify the ProcessAffinity, there are three keywords: ALL, FIRST, LAST And then the option to spec with cpu/core with a series of 1s and 0s which is equivalent to the design of the system. A two dual-core CPU server which makes use of the first and second cores (one whole CPU) would be = 1100 Robert -----Original Message----- From: Wolf, Gene [mailto:[EMAIL PROTECTED] Sent: Thursday, December 13, 2007 11:56 AM To: [email protected] Subject: RE: Witango-Talk: I'm totally stumped - Thanks! Thanks for the feedback Robert. Kevin finally figured it out. We have been told by corporate to use UNC coding wherever possible. We tried it in the Client.ini and Witango.ini files. Apparently the matching for userreference and cookies looks at the IP address. The UNC code was not the same as the IP address so Witango went to the next available stanza. When we changed everything back to standard IP addresses everything worked normally again. One good thing from this is we did learn from Tim Kelley exactly how to code the ProcessAffinity parameter. Since we have 8 cpu's in a box ours looks like: ProcessAffinity=FIRST ProcessAffinity=01000000 ProcessAffinity=00100000 ProcessAffinity=00010000 ProcessAffinity=00001000 ProcessAffinity=00000100 ProcessAffinity=00000010 ProcessAffinity=LAST Since I have never seen this illustrated before I thought I would include it here. -----Original Message----- From: Robert Shubert [mailto:[EMAIL PROTECTED] Sent: Thursday, December 13, 2007 10:41 AM To: [email protected] Subject: RE: Witango-Talk: I'm totally stumped Is it possible that cookies are being stripped by the firewall or web server? Witango - even the setup you describe - will maintain a user sessions automatically. Also, double check that the userarguments are 36 characters long. This means that Witango is aware that it's in a multi-service environment. Robert -----Original Message----- From: Wolf, Gene [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 12, 2007 5:09 PM To: [email protected] Subject: Witango-Talk: I'm totally stumped We are in the process of moving our Intranet to our datacenter in Dallas. We have some new servers there and we have upgraded to the professional version of Witango 5.5. These are Windows Server 2003 boxes with quad CPU's installed. We're currently testing and have run into something I cannot understand. Witango is up and working displaying pages. However every time a page is refreshed we go to a new stanza (we have 4 set up and each one has processaffinity=all set) and we get a new UserReference value. Needless to say all of the variables associated with the old user reference are lost. Anyone have any idea what I screwed up? I thought the userreference cookie would keep us on the original stanza for the life of the session. Any help would be appreciated. Gene Wolf Supervisor, Business Systems DRS Sensors & Targeting Systems-Optronics 2330 Commerce Park Drive NE Palm Bay, Florida 32905 Phone: 321-309-0685 321-309-0202 (fax) ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
