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
976 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

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

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

Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
Remote Apps is a feature in server 2008 which allows users to run applications off Remote Desktop Servers without having to log into them to run the applications.  The user can either have a desktop shortcut installed or go through the web portal to…
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…

636 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