Serious probems at work!!!

[Blammo300]

At my work we have 2 offices, on 1 side we have all the main work computers with Windows XP and on the other side we have a computer with. Windows 2000 Advanced Server. Now we connect to the Advanced server using a Remote Desktop Connection so that we can access certain programs and information.

Everyone is able to connect to this server using the Remote desktop except for 2 computers. We have 5 Desktops and 1 Laptop connecting via the Remote Desktop using 2 linksys routers (1 is Wireless) and a switch, the laptops are using the wireless and can connect fine.

On the 2 Laptops that do not work it gives this error

?The Client could not establish a connection to the remote computer.

The most likely causes for this are:
1)Remote Connections might 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 tried connecting them to the remote desktop using both wireless and direct Ethernet cord. I have been over all the settings and cannot figure out whats going on. I know the remote server is not out of available connections. It is very important that those 2 computers are able to access the remote server. Anyone have recommendations?

 

[mikecel79]

Can you ping the server? Have you tried connecting by IP address?

 

[cdurbin]

Were you ever able to connect to it? Are you running Windows XP Professional on the laptop(s) as well?

Sounds like a problem that I recently had with a client. They had Windows 98 on a remote system and when it first connected AS assigend a temporary license to it which expired in 90 days. Took a few minutes to figure out what happened. If you look in the Terminal Server License Manager it will list all the licenses and what type they are. If they are temporary (expired) licenses you'lll have to buy a 5 Pk CAL for your server.
Windows 2000 Profession and XP Professional are given unlimited licenses on Terminal Server, where ME on down & Windows XP Home are given temporary 90 day licenses.

C.Durbin

 

[imported_LobbDogg]

Also, is there a firewall on the 2 laptops that might be blocking the connection?

 

[JonathanYoung]

This does sound like a licensing issue. I don't remember exactly but when you first connect to an application terminal server with a computer, the server remembers that computer and subtracts one of its available licenses. So, if you happened to re-install the OS on the client computer, then the Terminal Server will forget that that computer is licensed, and you'd have to call MS to get the license reset (if you have no more licenses). Also, I think that terminal services licenses and CALs are separate; with CALs it means you can connect to shared resources, printers, etc., but it doesn't necessarily mean you can connect to a TS in application mode. Don't you just hate MS licensing schemes?

 

[cdurbin]

Originally posted by: JonathanYoung
This does sound like a licensing issue. I don't remember exactly but when you first connect to an application terminal server with a computer, the server remembers that computer and subtracts one of its available licenses. So, if you happened to re-install the OS on the client computer, then the Terminal Server will forget that that computer is licensed, and you'd have to call MS to get the license reset (if you have no more licenses). Also, I think that terminal services licenses and CALs are separate; with CALs it means you can connect to shared resources, printers, etc., but it doesn't necessarily mean you can connect to a TS in application mode. Don't you just hate MS licensing schemes?

How I understand it is this: If you have a NT, WIN2k or XP Professional desktop, these OS's have a permanent Terminal Server Client Access License built into them. If you have a device (printer or something else), Windows ME on down or Windows XP Home you have to purchase a seperate Client Access License for Terminal Server for each device you wish to connect to the server. I don't believe these are revolving Licenses either. I am pretty sure each license gets assignd to a device and can only be used by that device.
MS license schemes give me a headache.

C.Durbin

 

[stash]

I don't remember exactly but when you first connect to an application terminal server with a computer, the server remembers that computer and subtracts one of its available licenses. So, if you happened to re-install the OS on the client computer, then the Terminal Server will forget that that computer is licensed, and you'd have to call MS to get the license reset (if you have no more licenses).

If you wipe a computer that took a license, the computer will get a new license when it is reinstalled. If no CALs are available, it will get a temporary CAL that lasts for a period of 52-89 days. The perm license that it took before it was formatted will expire after 90 days and go back to being available for use.

If you have a NT, WIN2k or XP Professional desktop, these OS's have a permanent Terminal Server Client Access License built into them

No client has a built-in CAL. 2000 pro and XP pro clients connecting to a 2000 terminal server can pull a license from the built-in pool. The pool is located on the license server.

 

[Blammo300]

So would it be a coincidence that both computers that cannot connect are Windows XP home or would that have something to do with it?

 

[stash]

That could have something to do with it, since XP Home clients will not get a CAL from the built-in pool when they connect to a 2000 TS. So if there aren't any per-device licenses available on the licensing server, XP Home clients wouldn't be able to connect.

 

[Blammo300]

So if thats the reason why the 2 XP home Laptops wont connect how can I fix that problem?

 

[stash]

You need to check your license server to see if there are available licenses. If not, you will need to purchase some.

 

[Blammo300]

Hmm theres no way to reset the computers so that they will not have the outdated license at least without formatting and reinstalling OS?

 

[stash]

Yes there is, if you think that is the problem. Delete the HKLM\Software\Microsoft\MSLicensing key in the registry on the client. Delete the entire MSLicensing key and all subkeys.

 

[Blammo300]

If I delete all the registry entries under HKLM\Software\Microsoft\MSLicensing and also the sub folders could it possibly mess anything else up?

 

[Blammo300]

I deleted the Registry Entries and it worked. Kudos to everyone and especially Stash for the help.