Solved

Wyse winterminals in TS 2008

Posted on 2010-09-20
15
663 Views
Last Modified: 2013-11-21
Hi all

My client has got a mixture of windows pc and older S10 and 1200LE Wyse terminals, mainly the latter two

I have installed a new TS server as part of the upgrade process and I have reached the point where I am ready for the clients to connect

The client currently runs a Citrix Metaframe XP environment on Win2k servers.

When I try to connect through the pc's all is ok. When I try through the Wyse terminals the screen flickers and returns to the connection console.

Is there anything I can do to set up a normal rdp connection on the Wyse terminals in order to get them to connect as expected?

Thanks

Dom
0
Comment
Question by:Dominic Lennon
  • 8
  • 4
  • 3
15 Comments
 
LVL 7

Expert Comment

by:oztrodamus
Comment Utility
0
 
LVL 1

Author Comment

by:Dominic Lennon
Comment Utility
Hi oztrodamus,

Yeah I figured I might, but I was just wondering if there was a workaround.  I am not sure the client has got a support contract with Wyse and whether we'd be able to get the firmware we need

I'll update you if I get anything working!

Thanks

Dom
0
 
LVL 7

Expert Comment

by:dnsguru44
Comment Utility
Dom- is IE installed on the thin clients?  If so have them connect via the WI.
0
 
LVL 1

Author Comment

by:Dominic Lennon
Comment Utility
Hi dnsguru44

No all I get is the green console with "connection manager" on it

Looks like and old windows 3.1 screen!
0
 
LVL 7

Expert Comment

by:dnsguru44
Comment Utility
There is no RDP client installed?  Since it's the WYSE OS it looks a little different.
0
 
LVL 1

Author Comment

by:Dominic Lennon
Comment Utility
hi,

erm.  I'm not sure as i'm not on site

all i can remember is that it hasa green desktop with the ability to create new connections for either ICA or RDP

Can I install a different RDP client?  If so how?  

I am pretty new to the Wyse clients to be honest, though I do like them :-)

Thanks

Dom
0
 
LVL 7

Accepted Solution

by:
dnsguru44 earned 250 total points
Comment Utility
Unfortunately no, you can't install a different RDP client as it's WYSE's ThinOS which is proprietary.  These workstations are meant to be used with XenDesktop or View from VMware.

I have configured these thin clients in the past and it does work, you have to manually configure the PNagent server in the ICA client.  Make sure you select TCP/IP and HTTP not HTTPS.
0
Why do Marketing keep bothering you?

Is your marketing department constantly asking for new email signature updates? Are they requesting a different design for every department? Do they need yet another banner added? Don’t let it get you down! There is an easy way to manage all of these requests...

 
LVL 1

Author Comment

by:Dominic Lennon
Comment Utility
Hi dnsguru44,

I'll give that a go.

I am back in at the clients on Thursday so I'll try then and let you know

Thanks

Dom
0
 
LVL 7

Expert Comment

by:dnsguru44
Comment Utility
Good luck, let me know how it goes...
0
 
LVL 7

Expert Comment

by:oztrodamus
Comment Utility
The RDP client is upgraded with the firmware upgrade.
0
 
LVL 1

Author Comment

by:Dominic Lennon
Comment Utility
Ah ok, makes sense!

I'm not sure I can get hold of the new firmware to be honest, tho I'll try

I'll update the question on Friday
0
 
LVL 1

Author Comment

by:Dominic Lennon
Comment Utility
Hi dnsguru44 / oztradamus

I managed to get into the clients a day early and made a few registry changes to the Terminal Server, namely the ones found here:

http://www.sepago.de/helge/2007/09/12/programmatically-determining-terminal-server-mode-on-windows-server-2008/

I tried to connect to the server using the Wyse terminals and it all worked a treat.

Thanks again for all your help on this.

Dom
0
 
LVL 7

Assisted Solution

by:oztrodamus
oztrodamus earned 250 total points
Comment Utility
I take it your terminal server was requiring network level authentication?
0
 
LVL 1

Author Comment

by:Dominic Lennon
Comment Utility
Hi oztradamus,

When I installed the TS role I selected the second option allowing for older clients to connect but with no luck.

Whether there was something else I was required to do in order to stop NLA being required I wasn't aware of it, however this seems to have allowed the older clients through now

Thanks

Dom
0
 
LVL 1

Author Closing Comment

by:Dominic Lennon
Comment Utility
The registry changes and connection settings combined to solve the problem
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
Introduction: Sometimes when I receive a call from my users to solve their problems it is very difficult for me to found their computer IP address. Even finding their computer Host to provide remote support can be a problem.  So I resorted to Goo…
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now