Rolard

Well pulling it from the domain helped. I was able to log into the 2k server using both a 2k client and my Windows 8.1 machine. Unfortunately I have to have it on the domain for my app. So I went through the links again and applied kb829395 which I did miss the last time around and fired up lsview to see what the box was seeing as license servers. That's where it got interesting. My DC with the TS licensing on it is named AD-box2.domain.com but lsview saw ad-box no 2 or domain but it is the right licenses listed. I went ahead and changed the registry to point at that and I'm able to connect without errors now. My only concern now is am I actually getting a valid license or only a 90 day license. Once I have that verified I think I'll be in business. Thanks for the help on this! It's nice to have somewhere to bounce these kinds of questions as I'm the only left here with any real NT4 or 2k experience any more and my 2k experience was limited. (We mostly skipped from NT4 to 2k3) Thanks! Paul

I have read both of those articles and I'm going back through them again. I likely have done more than what was in them though as I was fighting the machine for a while on Wednesday and Thursday before coming across these forums. I was out on Friday but I just wanted to let you know I'm not ignoring your suggestions. One thing I may try today is pulling the server off the domain which will let me install local TS licensing. On 2003 and up local licensing is always an option but on 2000 if I'm part of a domain the TS licensing has to be on a Domain Controller. I'll let you know if local licensing works shortly. Thanks! Paul

So a bit of background. We are a Windows 2003 domain level but DCs are all 2008R2 now. We run 2003 and 2008R2 terminal servers in the environment but 2003 support for FoxPro DOS is sketchy at best so we'd like to stand up a Windows 2000 Terminal Server that will only host FoxPro. I've built the server and it seems to be running well except I can't connect to it from any clients. Windows 2003, Windows 7, and Windows 8/8.1 all give the same error. The remote computer disconnected the session because of an error in the licensing protocol. I've tried following the various reg tweaks online to set the default license server on the 2k box and delete the cryptography keys on it as well as deleting the MSlicensing key on my various clients with no luck. The 2k box logs an event ID 1004 for each connection attempt and the client keeps seeing the same error. Am I just out of luck with 2k support for RDP at this point or I'm hoping I'm just missing a tweak. If I had any hardware onhand that would still run NT4 I'd go that route as I have experience with NT4 TSE (we skipped from NT4 to 2003) and NT4 is even better for FoxPro than 2000 is. Anyway any suggestions anyone can offer would be greatly appreciated. Even if they are just forget you are hosed. Thanks! Paul