120 days RDP trial over... help plz... 1

[maddog12321]

ok i have a problem using remote desktop on windows 2003 coroprate edition. i use rdp alot and well not to long ago when i tried to connect it said that my trial period has ended and i needed a licence server to continue use of this service. everything but RDP works great and well i was wondering if anyone knew what i could do to fix this problem with out reinstalling windows every 120 days.

 

[aftertaf]

how many users connect to the server with rdp?

what mode is it on?

if you are using application and not remote admin, you need a licence server (and licences) in order to use it.

Aftertaf
We shall prevail, and they shall not

 

[llevon]

Hi,

If all you are wanting RDP for is to remote control your server for admin purposes then you dont need terminal services installed.

Instead right click on 'my computer' and choose properties.
Click on the tab called 'Remote'
Check the box 'enable remote desktop on this computer'

Now from your remote PC run mstsc /console

The /console switch run s the RDP client in console mode. It will lock the console on the server and allow you to actually control what is on the screen. This is different to when you RDP and it cerates a new session for your user.

However if you are using terminal services in Application Mode with many people connecting then as stated above you do need to install terminal services licnesing. You can then activate the licensing server with MS clearing House over the internet. Then you need to by CALS and install them on your licensing server. NB that in a Windows 2000/2003 domain the licensing server must be either the DC with the PDC emulator role or a standalone server i.e. not a member of the domain.

Regards,

Llevon

 

[markdmac]

The license server can also be a member server but you would need to make a registry modification to point your servers to it.

http://support.microsoft.com/?id=279561

I hope you find this post helpful.

Regards,

Mark

 

[maddog12321]

ok i have uninstalled termal service and did the mstsc /client and now when i try to connect to it i get a message saying "because of a protocol error, this session will be dissconnected" and or "because of a protocol error at the client (code 0x1104) this session will be disconnected" and i did everything llevon said and now it wont even connect and it gives me an error (it would connect before but wouldnt let me log in) i have the port changed but i tried to connect to it on the defualt port and it didnt even respond. i have serached around on the net a little using code 0x1104 and couldn't find anything that did help... if anyone has an idea plz post it here; if you have an idea or know of another application i could run that would let me do what rdp does and is free plz let me know
Thanxs,
Gary

 

[llevon]

Hi maddog

You havre removed Terminal Services using control panel? Does this server have TS Licensing intstalled?

Firstly try just runnign a normal RDP to the server.
Secondly it isnt 'mstsc /client' but 'mstsc /console'

Lastly backup this registry key first then delete the registry key MSLicensing

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSLICENSEING

Thirdly undo the port change unless you have a valid reason for wanting to run terminal services on a different port. If you run a netstat -an from a command prompt this will tell you what port your server is listening on. Adding the following will tidy it up a bit
netstat -an |find "LIST"
Ypu can also telent to the listening server on the port to prove that it is accepting inbound connections i.e.
telent servername 3389

llevon

 

[maddog12321]

Yeah i havent been able to fix it not even anyhting you said here helped me and i did do /console but i said the wrong thing when i posted... and well i am just reinstalling the O/s on it and not installing termal server again... thanks for tring to help me and well i hope that maybe someday i can help you with a problem although you seem o know so much more than i do..