Solved

Window 2000 Terminal Service - Cannot connect to terminal server

Posted on 2004-04-03
11
991 Views
Last Modified: 2010-04-13
Windows 2000 Enviroment.  I have one terminal server and one DC.  I can connect from the terminal server using the terminal service client; however, i cannot connect from the DC to the terminal server.  The PDC is in Administration Mode, and the terminal server is in application mode.  I have installed and activated the terminal server licensing server on the DC.  I have reinstalled the terminal service.  I can do a tracert from the Terminal Server to the DC; however, when i do a tracert from the DC to the terminal server, I get "Transmit Error Code 65".  For testing purposes I changed from Application mode to Administration mode, but i still got the same error.  When trying to connect to the terminal server I get "The Client could not connect to the terminal server.  The server may be too busy.  Please try connecting again"  I have check DNS and I can ping by name and IP from both servers.  Need Help.  Thank you.
0
Comment
Question by:Jlopez025
[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
  • 6
  • 3
  • 2
11 Comments
 
LVL 2

Accepted Solution

by:
The_Master_Chief earned 500 total points
ID: 10748355
Do you have any firewalls installed or running on the DC?  If so, disable them and try again.
0
 
LVL 2

Expert Comment

by:The_Master_Chief
ID: 10748366
0
 
LVL 2

Expert Comment

by:The_Master_Chief
ID: 10748387
From what I have been reading about this "Transmit Error Code 65", they talk alot about a zone alarm firewall and ICS.
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 

Author Comment

by:Jlopez025
ID: 10748401
Thank you.  I know that Zone Alarm was installed on the DC. I have shut this down, but I still cannot connect.  It seems that the terminal server is not seeing the DC.  It needs to be able to see it, so it can confirm that a License server does exist on the network.  Do you think it would be necessary to uninstalled Zone Alarm?
0
 
LVL 2

Expert Comment

by:The_Master_Chief
ID: 10748569
I would uninstall it anyways.  A lot of the time you disable something or shut it down but it stays resident.  Are you using ICS?
0
 

Author Comment

by:Jlopez025
ID: 10748586
I am not using Internet Connection Sharing.  Completely uninstalling it would be the only thing left to do.  If that does not work, reinstalling the OS would be my next option.
0
 
LVL 2

Expert Comment

by:The_Master_Chief
ID: 10748611
the terminal server is not running a firewall is it?

0
 
LVL 2

Expert Comment

by:The_Master_Chief
ID: 10748618
So how is itr set up?

                            PDC
                              |
                       [ROUTER]
                              |
                              |
                [TERMINAL SERVER]

give an example of how it is set up.
0
 
LVL 5

Expert Comment

by:visioneer
ID: 10748641
You will have to completely uninstall ZoneAlarm from the DC, and also from the Terminal Server if it is running there.
0
 

Author Comment

by:Jlopez025
ID: 10748664
The terminal service does not have a firewall.  I turned off zone alarm and changed the Terminal server to Administration mode, and I was able to get in.  But i still cant get in when is set to Application mode.  It tells me that the server disconnected my session.  In my opinion, this would be because the server can't see the licensing service, due to zone alarm being installed on the server.  I will uninstall it a will let you know how it went.  Thank you for your quick responses.
0
 
LVL 5

Expert Comment

by:visioneer
ID: 10748672
Ah, that most surely what it is.  Check the Event Log on the Terminal Server for event IDs 1000 or 1004, and if you see those then it is definitely a licensing issue.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

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

Suggested Solutions

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
In a recent question (https://www.experts-exchange.com/questions/29004105/Run-AutoHotkey-script-directly-from-Notepad.html) here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…

751 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