| Author |
Messages |
|
Claw
Posts:5
 |
| 05/15/2008 9:48 AM |
|
Hi there!
Several clients are reporting a new issue:
- Terminal gets to login screen, and after login, it jumps back to connect to server screen.
tested with both V.4.03.090.3 and V4.03.091, WITHOUT SP3.
Anyone with the same problem? solution?
Thanks in advanced
|
|
|
|
|
Jhon
Posts:35
|
| 05/15/2008 1:09 PM |
|
Stupid question time: How long has the host been up? Is the problem still there immidately after a power-cycle? Does it show up again a day or 3 later?
|
|
|
|
|
Claw
Posts:5
|
| 05/16/2008 3:15 AM |
|
Hi!
"Is the problem still there immidately after a power-cycle?"
yes, tested after several power cycles.
"Does it show up again a day or 3 later?"
Yes, this issue as shown up a few days, and several times tested.
I've no idea what's causing this. So far, I've got 3 clients with this problem.
Thanks |
|
|
|
|
Jhon
Posts:35
|
| 05/16/2008 11:35 AM |
|
So it's there all the time... It doesn't go away with a power cycle only to return a day or more later?
It's unlikely that a production machine would just spontaneously devolop this problem. Was there any updates/chages to the host or software ON the host prior to this problem popping up? Can you roll back the system to a day prior to the first reported event? Then start manually applying what ever changes/updates and see if you can identify the problem? |
|
|
|
|
Claw
Posts:5
|
| 05/19/2008 6:03 AM |
|
No, it's there all the time...
It seems there weren't any changes... just maybe anti virus updates or so... rollback doesn't solve...
Maybe windows updates?
thanks |
|
|
|
|
Jhon
Posts:35
|
| 05/19/2008 8:54 AM |
|
Posted By Claw on 05/19/2008 6:03 AM
No, it's there all the time...
It seems there weren't any changes... just maybe anti virus updates or so... rollback doesn't solve...
Maybe windows updates?
thanks
If there were windows updates, there were changes. The change was that windows updated. If there were any software updates, the chage would be that your software was updated. If there was any hardware added, again -- that would be a change.
Can you try some easy checks, but I doubt it would be causing your problem. An easy check to rule out a NETWORK issue, for example would be to hook a terminal directly to the server via a cross over cable. See if the issue still presents itself.
Do you keep restore points on your production servers? If so, I would recommend rolling back to your last known good image. If not, I'd strongly recommend suspending automatic updates and manually test and apply updates on a test machine -- or a machine you can easily roll back if something breaks. |
|
|
|
|
Claw
Posts:5
|
| 05/19/2008 12:00 PM |
|
I've run all those tests, network etc.
No restore point available.
i cannot see if any update was installed (excepted sp3, i know it wasn't), since i have not access to server/terminals (they're from clients). That´s why I've asked if someone else have the same problem.
It's not just one client, but till now, 3 of them.
thanks |
|
|
|
|
jjchang
Posts:1
|
| 05/22/2008 5:22 PM |
|
| I have the same issue. I built a new machine that had all the Windows updates as of 5/16 except SP3. I get the same problem where the client logs out as soon as it logs in. |
|
|
|
|
Aubry
Posts:13
|
| 05/23/2008 10:26 AM |
|
The following solution for this issue has been posted in the NComputing Support Knowledgebase (http://www.ncomputing.com/support.aspx):
L-Series: Windows login disconnect with NCT version 4.03.091 update
We have found that for some customers, they experience a terminal login to Windows problem after installing NComputing software version NCT 4.03.091. We have also found a workaround for this until this is corrected in our next software release.
The symptom for this problem is: The L-device user attempts to log in to host PC with the L-terminal, and after seeing the Windows user login screen, and after entering their Windows login credentials, instead of logging into Windows, the terminal returns the user to the L-terminal Server Selection screen without presenting any error screen.
This problem seems to occur with users who are installing version 4.03.090 (v090 for short or sometimes v90.3), of the NComputing NCT-2000-XP software for the first time, or if they are upgrading from the software found on the driver CD, 4.03.084 (or v084).
For a temporary workaround, to correct this login issue we recommend an alternative installation sequence that involves installing software version 4.03.090 first, then upgrading from v090 to the new v091 (sometimes v91.3)
For reference, here are the steps:
1) Uninstall current software
Please start by uninstalling your current version of the NCT software. You can do this through the Add/Remove Programs utility in Control Panel, or by starting the uninstaller in the NCT-2000-XP folder in the Start Menu.
NOTE: If you already have v090 installed, then you do not need to uninstall the software, and may skip to the final step.
2) Install software version v090
Once you have uninstalled the software, and restarted the computer (your terminals will not be able to connect till this point), please go to http://www.ncomputing.com/download/L230_r090.3.zip and extract the folder's contents to your desktop.
Now, from the extracted files, locate and run "setupnc.exe" to install v090 of the NCT software.
3) Register device serial numbers.
After the installation completes and your system reboots, you must then register the NComputing software and device serial numbers to be able to use the NComputing automatic software update.
4) Update software from v090 to v091
Now you can update the product to the latest version, without encountering the station disconnect issue. Use the NComputing software automatic update feature, or alternatively you can download the software direct from here:
http://ncomputing.com/download/l230.zip |
|
|
|
|
jibsen
Posts:1
|
| 06/01/2008 3:13 PM |
|
I still have this particular issue happening on my WinXP SP3 machine.
The version mentioned and downloaded through step 2 does not install on SP3. I then install the software downloaded in step 4 and the same problem continues to happen.
Any assistance would be greatly appreciated. |
|
|
|
|
roms
Posts:33
|
| 06/02/2008 3:05 AM |
|
Only version 4.03.091 and 4.03.094 work on a Windows XP SP3 fresh install and i got the same problem !
So the solution for now is to run setup version 4.03.090 in Windows 2000 "Compatibility mode" and then run the update to version 4.03.091 or 4.03.094
That's currently works with version 4.03.090 (compatibility mode) to 4.03.091.
There are chance that's also works from version 4.03.090 (compatibility mode) to 4.03.094. |
|
|
|
|
|