Forum Replies Created
-
AuthorPosts
-
We have gone as far as setting up an exact replica of our client’s infrastructure and allowed Wyse to access it 24/7.
They claim to only have suffered 1 TPF during their tests on our systems.
We can get it to bomb like clockwork, with more and more websites added to the list of sites that cause the TPF.
At this point, we have no choice but to move on with non-wyse thin clients. This issue has 3 of our most important clients furious.
FYI – we’re using 6.5.0_30 on S10 & V10L.
(anybody want to buy a bunch of S10s and V10Ls, cheap?)
apologies for the delay in this response.
Server side: Vmware View, Windows XP and Windows7 VMs, Test environment (low load on server).
Client side: P20.
WAN: VPN connection between 2 location each with 15/2 connection. (effective VPN rate: 2 mbps before overhead. Call is 1.75 mbps?)
Low load on both WAN connections.
WAN connections via same provider (Time Warner business-class). Distance between locations: about 5 miles.
Graphics performance was better than RDP, but was not nearly as close to the demo videos promoting PCoIP. More tests need to be done before we come to any conclusions though. will post when we have more results.
We’re still unable to make RDP connections using P20. Very strange.
Here’s the latest:
Now running 6.5.29 on both S10 & V10L.
We continue getting TPF errors on both units, but it’s isolated to Win7 VMs and Windows Terminal Server 2008. We can recreate the TPF about 50% of the time.
When connecting via RDP to XP or TS 2003, we cannot recreate the TPF.
This appears to be an issue isolated to Winterms connected via RDP to Win7 VMs.
Tests have only been run using Win7 x64 VMs.
Additional tests will be performed using Win7 x86 in a few days and I’ll post the results.
In the meantime, I have a pretty unhappy customer 👿 .
Quick update: Wyse is recommending FW 6.5.0_27 which supposedly fixes many trap Protection Fault errors.
Keeping my fingers crossed and will advise of the results.
Thanks for the reply.
We’re getting this at a few clients who use their systems in entirely different ways.
The website I outlined in my previous post will eventually bomb the S10 or V10L. Just not all the time. There are more sites too, and as I collect them I will post them.
We only use RDP, Not ICA.
Problem manifests itself whether Winterm is connected to a 2008 TS or a Windows-7 VM.
After the issue, there are times when a reboot of the WT will not reconnect to the host, and a reboot of the host is necessary to kill off the webpage that is causing the issue.
At both clients, we have broadband connections in excess of 20 mbps with only a handful of users. Plenty to go around.
LAN infrastructure is first rate: Cat5e cabling; Dell 5000 series gigabit switches. Dell T710 server with quad NICs, 48 GB RAM, 15k rpm disks, RAID-6 running vSphere (ESX 4), etc., etc. Horsepower is not an issue.
WNOS.INI is here:
DelCertificate=all
ClearLicense=Yes
FixLicense=Clean
AltCacheDisable=yes
EnableCacheIni=nosignon=NTLM
DisableGuest=yes
lastusername=yesDomainList=corp
DisableDomain=no
AutoLoad=1
language=us
Autopower=yes
FormURL=biglogo.bmp
Priviledge=none
LockDown=no
HideSysInfo=yes
HidePPP=yes
HidePN=yes
HideConnectionManager=yes
EnableNetworkTest=no
EnableTrace=no
ShowDisplaySettings=no
EnableKeyboardMouseSettings=no
KeepDHCPRequestIP=yes
SuppressTaskBar=yesadminmode=no
SessionConfig=ALL
unmapprinters=no
unmapserials=no
smartcards=yes
mapdisks=yes
disablesound=no
unmapusb=no
DisksReadOnly=no
WyseVDA=yesDevice=audio
volume=highTimeZone=’GMT – 08:00′
ManualOverride=yes
Daylight=yes
Start=030207
End=110107
TimeZoneName=PST
DayLightName=PDTTimeServer=192.168.1.10
TimeFormat=”12-Hour Format”
DateFormat=”mm/dd/yyyy”VNCPrompt=no
ViewOnly=no
ActiveVisible=noAutoSignoff=yes
Shutdown=noScreenSaver=30
LockTerminal=0
Type=2
Image=biglogo.bmpNoticeFile=Notice.txt
Resizable=yes
Timeout=360Community=public
EnableGKey=yes
KeySequence=yes
ctrl+alt+del=no
ctrl+alt+up=no
ctrl+alt+down=no
ctrl+alt+left=no
ctrl+alt+right=noShutdowninfo=no
DisableButton=no
Inactive=0
TCXLicense=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Include=$MAC.ini
$MAC.INI is here:
#Mac.ini file
Terminalname=Terminal01
Resolution=1440×900 Refresh=60Printer=LPT1
Name=”Jeanine’s Printer”
PrinterID=”HP Deskjet F4400 series”
Class=PCL5
Enabled=yes
EnableLPD=noUSER.INI is here:
connect=rdp
description=”Connecting…”
host=jeanine-vm
icon=smalllogo.bmp
UserName=$UN
Password=$PW
domainname=$DN
Colors=true
Fullscreen=yes
autoconnect=1
LocalCopy=No
KeepAlive=10
Lowband=no
Mapdisks=yes
NoReducer=no
Rdp_No_Animation=no
Rdp_No_Dragging=no
Rdp_No_Fontsmoothing=no
Rdp_No_Theme=no
Rdp_No_Wallpaper=no
Reconnect=noWe have 2x P20 units and were able to get PCoIP connections to work just fine using VMW View.
But we have been unable to make an RDP connection at all.
FYI: IMO PCOIP did not perform as well as we expected in our test. But we have more testing to do.
Hi CG – Yes, reset to factory default numerous times. Did everything I can think of.
Even downloaded FW version 6.3.0_12 from here, but then login=NTLM seems to have stopped working (any username & password gets rejected), so I went back to 6.5.0.23.
Requested a previous firmware from wyse support. Hope they deliver it and we’ll see what happens.
Let me know if you can think of anything in the meantime.
-
AuthorPosts