Solved

Wyse 3200 LE will not connect to terminal server rdp 5.0 while any other computer can RDP into just fine.

Posted on 2007-12-04
2
969 Views
Last Modified: 2013-11-21
Have a WYSE 3200LE (5 of them) that will not connect to Server 2000 RDP 5.0.  First thoughts is that the common denominator is the server but the server will Connect to itself through RDP as well as from any other computer on the network.  Only the Thin Clients will not connect .  Get an Error "terminal server had ended the connection or a network error occured".  have setup FTP on the server and downloaded the latest firmware (3.5.1 SP 2 build 441.22) and the latest addon for 5.0 from the wyse download site.

Other things related:  Reset thin client to factory default, network is not an issue being I can connect to the FTP server, Uses DHCP (have tried on static as well). Recently formatted Server 2000 with 5 terminal server CALS installed.  

Note:  nothing shows up in the event viewer on the server which you would normally get if the is a licensing issue or the connection is denied for some reason.

Any help would be appreciated!
 
0
Comment
Question by:dnscompanies
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 5

Accepted Solution

by:
t_swartz earned 500 total points
ID: 20406542
Did you format the 2000 Server (I'm assuming that this is and was the TS licensing server, and is a DC) prior to these connection problems occurring? Did they all stop working at the same time, or one at a time stopped over a perios of a few days or weeks? You may have two problems here. It is common for there to be problems similar to this when you blow away the ts licensing server. Remove the ts cal from the thin clients (factory reset may have done that) if they are still showing as installed on the thin clients. Check the ts licensing server and see if the thin clients are showing as having a ts cal installed (wether permanent or temporary). I suspect your solution is going to be delete the ts cal's from the thin clients and rename them. Then, try and connect ans see if they grab a temp cal. Let me know what you discover, I think we can get it working, but depending on your answers will dictate the direction we go.
0
 

Author Closing Comment

by:dnscompanies
ID: 31412675
Corrupted Cal License!
0

Featured Post

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

On a regular basis I get questions about slow RDP performance, RDP connection problems, strange errors and even BSOD, remote computers freezing or restarting after initiation of a remote session. In a lot of this cases the quick solutions made b…
Know what services you can and cannot, should and should not combine on your server.
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below. https://filedb.experts-exchange.com/incoming/2017/03_w12/1151775/Permutations.txt https://filedb.experts-exchange.com/incoming/201…

756 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