Solved

Unable to attach to Terminal Server from Workstation

Posted on 2004-08-11
4
1,047 Views
Last Modified: 2010-05-18
I currently have one Windows 2000 Server running an accounting application.  I also have a second Terminal Server for access to the accounting application.  The Windows 2000 server is the Terminal Services License Manager and it has been activated from Microsoft for 5 user licenses.  The local workstations are all running Windows XP Home Edition.  Three of the four workstations access the Terminal Server with no problem.  The fourth workstation gets the following error message

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

"The most likely causes are
1.  Remote Connections may not be enabled at the remote computer
2.  The Maximum number of connections was exceeded at the remote computer
3.  A network error occured while establishing the connection."

I have rebooted both servers to make sure all connections have been cleared and I still get the same error message.  Here are some of the event logs from both servers.

Any help or ideas would be greatly appreciated.

Thanks
Kenny



Event Type:      Information
Event Source:      TermService
Event Category:      None
Event ID:      1003
Date:            8/10/2004
Time:            4:03:26 PM
User:            N/A
Computer:      TERMSERVER
Description:
The terminal service client 'DCGZJN21' has provided an invalid license.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1000
Date:            8/10/2004
Time:            3:22:38 PM
User:            NT AUTHORITY\SYSTEM
Computer:      TERMSERVER
Description:
Windows cannot determine the user or computer name. Return value (1722).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type:      Information
Event Source:      DnsApi
Event Category:      None
Event ID:      11156
Date:            8/10/2004
Time:            4:15:13 PM
User:            N/A
Computer:      TERMSERVER
Description:
The system failed to register pointer (PTR) resource records (RRs) for network adapter
with settings:

   Adapter Name : {F1177ABB-3A6E-4615-881A-D2C53FF8068B}
   Host Name : TERMSERVER
   Adapter-specific Domain Suffix : ruizsales.com
   DNS server list :
     151.164.1.8, 151.164.11.201
   Sent update to server : None
   IP Address : 192.168.1.25

 The reason that the system could not register these RRs was because the update request that was sent to the specified DNS server timed out. This is probably because the authoritative DNS server for the name being registered is not running.

 You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. For specific error code information, see the record data displayed below.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: b4 05 00 00               ´...    





Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5774
Date:            8/10/2004
Time:            3:55:16 PM
User:            N/A
Computer:      FAMOUS
Description:
Registration of the DNS record 'ruizsales.com. 600 IN A 192.168.1.10' failed on the DNS server (with IP address %3) with the following error:
%2
The DNS server returned an error code given in the Data field.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 29 23 00 00               )#..    


Event Type:      Information
Event Source:      TermServLicensing
Event Category:      None
Event ID:      5
Date:            8/10/2004
Time:            3:55:16 PM
User:            N/A
Computer:      FAMOUS
Description:
The description for Event ID ( 5 ) in Source ( TermServLicensing ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: %SystemRoot%\system32\tls236.dll, Microsoft Corporation, A02.






0
Comment
Question by:kwh3856
  • 2
  • 2
4 Comments
 
LVL 83

Accepted Solution

by:
oBdA earned 500 total points
ID: 11773441
That's probably what's happening with your XP client trying to access the Terminal Server.

Windows XP Clients Cannot Connect to a Windows 2000 Terminal Services Server
http://support.microsoft.com/?kbid=323597

And the DNS errors are resulting from incorrect DNS settings:
DNS server list :
151.164.1.8, 151.164.11.201
IP Address : 192.168.1.25

The correct DNS settings in short: On *all* of your domain members, make sure the *only* DNS server configured in the DNS settings in the TCP/IP properties is your internal DNS. Do *NOT* specify your ISP's DNS there. For internet lookups, delete the root zone (".") in your DNS forward lookup zones (if it's present), and configure forwarders to point to your ISP's DNS. The forwarder entries are the *only* places in your domain where you define external DNS servers.

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382
0
 

Author Comment

by:kwh3856
ID: 11778661
oBda,
Thanks but that did not help.  We also installed SP 4 on both of the servers which did not help either.  Any other ideas?????  I noticed also that I am getting 1004 errors in the event log also.

Thanks
Kenny
0
 
LVL 83

Expert Comment

by:oBdA
ID: 11795725
First question: Did you fix the DNS errors (this might be related)?
From what I could make out of youre description you seem to have the following setup (correct me if I'm wrong):
An AD domain with an FQDN name of ruizsales.com; the DC is "FAMOUS" and the IP address 192.168.1.10; it has TS licensing installed. It should be running DNS as well.
The TS is named "TERMSERVER" with the IP address 192.168.1.25.
The XP Home client that is making the problems is named DCGZJN21.
In that case, the correct DNS settings in the TCP/IP properties on *all* machines (clients and servers, including the DC) would be:
Primary DNS: 192.168.1.10; no secondary DNS.
Then open the DNS MMC, open the "forward lookup zones", delete the root zone (the single dot, ".") if present.
Right-click your server in the DNS MMC, choose "Properties", go to the "Forwarders" tab. Define 151.164.1.8 and 151.164.11.201 there.

Then check in the TS License Manager if you have TS licenses available.
You might try to delete the TS CAL that is stored on the machine causing the trouble, following the instructions in this article:
How to Transfer Terminal Services CAL from One Client Computer to Another
http://support.microsoft.com/kbid=315262

Note that this will *not* free a license on the TS license server that the client might have taken. If you have SP4 on your licensing server, the old license should be available again after some months:
Terminal Services Licensing Enhancements
http://support.microsoft.com/kbid=287687

A faster solution would be to call the MS Clearinghouse and have them issue you a new license.
0
 

Author Comment

by:kwh3856
ID: 11886967
Turned out to be DNS problems.  Thanks for your help.


Kenny
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

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…
Find out what Office 365 Transport Rules are, how they work and their limitations managing Office 365 signatures.
This video discusses moving either the default database or any database to a new volume.
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…

707 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

17 Experts available now in Live!

Get 1:1 Help Now