Remote desktop connection problem


 Hi All,

          We have a win2kserver with terminal services installed in it. We were able to connect to the server through the remote desktop connection. This includes from all the other client systems. But now that it is possible to connect to the server only through fewer machines. when i try to connect to the server, the following error message appears,

      The client could not establish a connection to the remote computer.

 The most likely causes for this error are,
1) Remote connections might not be enabled at the remote computer.
2) The maximum no. of connections was exceded at the remote computer.
3) A network error occured while establishing the connection.

    We were able to ping to the server, and i checked if it has got to do anything with the domain from which we are trying to connect. Everything is fine. What could  be the problem. Does it got to do anything with the Terminal services. Please help me out.

 Thanks & Regards
 Murugan Kalicharan S
mkcharanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rindiCommented:
Have you checked the eventviewer on your server? could you possibly send a small output of the events here? What type of clients are you using to connect to your TS? Are they XP PCs or do are they using another OS, or are they mixed clients? If mixed, does the issue occur only on a certain type of client?
0
kain21Commented:
Check and verify terminal services licensing is installed and functioning properly... if licensing is installed and not activated it will issue temporary licenses to client machines... these licenses will expire after time and that is more than likely the reason you are able to connect with less machines...
0
kain21Commented:
if licensing is the problem then you have two solutions... switch to remote administration mode and remove licensing from the server.. this will allow only two concurrent connections... or... application mode with licensing installed... activate licensing with microsoft.. this will allow all windows 2000 pro and xp pro machines to connect with their built-in licenses (pro comes with a terminal services license)... all other operating systems will need a terminal services license purchased for them or they will receive a temporary license and it will expire (after 90 days I believe).
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

ghermanCommented:
Hi.

Do you have Norton Antivirus installed? That might cause the problem.
0
mkcharanAuthor Commented:

 Hi Rindi,

           I have checked the event viewer on the server. The following are the details that i got  from the server.

 Type : Information
 Date  : 11/9/2004
 Time : 9:15:42 P.M
 Source : Termservice
 Category : None
 Event : 1004
 User  : N/A
 Computer : Name of the system.
 
      And it is a a combination of 9x, 2000 and xp systems. And it does not occur on certain type of clients. Some xp machines were able to connect while some could not.
     
 Hi Kain21,

         I have checked the terminal services licensing. As you said its not been activated. That could be the reason why some of the machines were able to connect and some of them could not.
Is there any possibility by which i can extend the license for the machines whom license has expired. And do the activation of the terminal services comes for free or that we need to pay for that??

       And gherman we dont have Norton Antivirus installed in any of the machines.

   Thanks for all your suggestions.

 Thanks & Regards
 Murugan Kalicharan S
   
0
kain21Commented:
activation of terminal services licensing is free... i would recommend uninstalling terminal services licensing and reinstalling it... then open the terminal services licensing snapin and right click on the server you want to activate... and click activate server... then you can follow the steps... make sure you put in a valid email address that you can check... an email will be sent to you immediately with your activation code...

what this will do is allow all xp pro and 2000 pro systems to connect all the time... as far as 9x systems go... they will only be issued a temporary license which will last 90 days... at that time those workstations will no longer be able to access the server via terminal services unless you purchase terminal services client licenses and install them on the server...

if you don't need to have more than two workstations connected to the server at the same time i would recommend changing the terminal services mode from application mode to remote administration mode... this way terminal services licensing doesn't need to be installed or activated and you could have two computer logged in from any type of workstation without worrying about temporary licenses....
0
kain21Commented:
p.s.  if you uninstall terminal services licensing and reinstall it prior to the activation it should clear out the expired licenses...
0
rindiCommented:
Since you hadn't installed the licensing that will be your problem. If you google for event id 1004 you'll find some extra links concerning thin clients.

A win2k server system will only issue licenses for 30 days, not 90 as suggested (90 days is correct for win2k3 servers).
0
mkcharanAuthor Commented:

 Hi Kain21,

            I will try to implement as you have suggested. But then i would like to know one thing if that is possible. After the activation of Terminal Licenses, i dont want every systems ( xp pro & 2000 pro) to connect all the time. I would want only some of the xp pro & 2000 pro machines to get connected all the time. Is that possible. Thanks again for the suggestion.

 Thanks & Regards
 Murugan Kalicharan S
0
kain21Commented:
After activation windows xp and windows 2000 pro computers will have a permanent license for terminal services and will be able to connect all the time... windows 9x systems and NT 4.0 systems will receive a temporary license which will expire after 90 days and they will no longer be able to connect....

rindi... from the microsoft website...
"Q.  What if no Terminal Services CAL tokens are available on the license server?
   
A.  If your license server's pool of available license tokens is depleted, the license server issues 90-day temporary license tokens to unlicensed clients. The temporary license token helps prevent denying service to a user. It gives you time to account for and purchase any additional required licenses, and install the corresponding tokens. The license server tracks when and to which machine a temporary license token is issued; including the date it will expire. You can review this information using the Terminal Services Licensing Manager utility."

here's the link... http://www.microsoft.com/windows2000/server/howtobuy/pricing/tsfaq.asp


 


If you want to evaluate Terminal Services for a full 120-day period, a license server can be activated 30 days after the product is installed. This will provide the client devices with temporary license tokens, which are good for an additional 90 days from the day the license server was activated. After 120 days, the server itself will cease to function."
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kain21Commented:
disregard the last three lines of my last post... that snuck in there in a cut and paste operation...
0
rindiCommented:
Kain21, I was talking about a terminal server which hasn't been licensed yet with M$. Your link applies to Licensed terminal servers, where unlicensed clients are connecting.
0
kain21Commented:
I was talking about his 9x workstations being able to connect to the server after licensing was activated (that's what he needs to do at this point).  We were both right... just talking about different situations.
0
mkcharanAuthor Commented:

 Hi Kain21 and Rindi,

                          Thanks for your suggestions. Though i havent done the activation as per the order from my higher officials i finally get to know the solution for the problem. Thanks again.

 Regards
 Murugan Kalicharan S
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.