VBScript: Remote Desktop Disconnected

here are a list of troubleshooting steps that should help you diagnose the issue.
http://technet2.microsoft.com/windowsserver/en/library/d5336104-c7c3-4a6c-84a6-ef6eaecd80771033.mspx?mfr=true

None of those solutions work.  I should also note that the terminal server the client is connecting to is Windows 2000 Server.  I myself can connect to it from a variety of machines, just not the clients.

i can't get to it either...

have they tried with the ipaddress instead of the name? does it work?
what results do youget from the troubleshooting?
what steps have you taken?

i need more input in order to get a good solution


At the command prompt, run the ping command from each computer to each computer by using:
" Fully qualified domain name (for example, term2.dtacoremarketing.com)
" NetBIOS name (dtacoremarketing.com)
" The IP address (for example, 206.73.118.1)
 

chances are their firewall is preventing them from getting out to it.

You can't ping it from any PC.  I can get to the address fine from my laptop and even my pocket pc.  I have tried the straight IP, same problem.

term2.dtacoremarketing.com doesn't work, but
term2.datacoremarketing.com does, as does
216.58.252.113


Pinging term2.datacoremarketing.com [216.58.252.113] with 32 bytes of data:

sorry.  I didn't realize I typed it in wrong in the question. term2.datacoremarketing.com is the correct address that will not work on the clients workstation.

Things I have tried on the workstation in question.  Disable all anti-virus, anti-spyware and firewall applications.  Updated drivers for NICs.  Removed and re-added the terminal liscence key in the registry.  Connected to a different IPS and router.

from here
http://support.microsoft.com/kb/187614

If you delete the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing subkey on a client that is running Windows Vista or a later version, later attempts to connect to a Terminal Server may fail. Also, you receive the following error message:

An Error occurred in the Licensing Protocol

To resolve this problem, right-click the Remote Desktop Connection shortcut, and then click Run as Administrator. By default, the remote desktop connection runs as a user with the lowest user permissions. By default, a restricted user does not have permission to write registry entries to HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys.

--------------------------------------------------------------------------------

I did try that one.  It did not work.

Even that fails.  Let me add one more tidbit.  The client has 2 PC's with this problem. One a Vista notebook and the other a XP Pro desktop.  The problem began after they had "Geeks on Call' come and setup netork sharing between their PC's.

Thanks for the last article.  That worked.  I removed the MS Liscensing keys, then ran rdp as admin and it worked!