Application Server Mode

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

i'm having some strange problems with my terminal server, i have setup
terminal services in Application Mode with all the nessessary licensing, but
for some reason i cannot connect, i can connect in Remote Administration Mode
fine no problems.

i tried re-activating the license server and even re-installed terminal
services, i also re-installed my firewall just in case, but i am still having
the same trouble, i keep getting the following error:

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

The most likely causes for this error 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 occurred while establishing the connection.

i dont know what else to do except re-install the OS.

Also someone did mention to me that Windows XP Pro comes with a terminal
server license, is this true?

Please Help Me, as this is driving me MAD!!!

Regards,

Alex Saager
 
To start with your last question:
Also someone did mention to me that Windows XP Pro comes with a
terminal server license, is this true?
Click to expand...

No operating system comes with a build-in Terminal Server Client
Access License. BUT: W2K Pro and XP Pro clients receive a free TS
CAL from the TS Licensing Server, *when they connect to a W2K
Terminal Server* (NOT to a Windows 2003 TS!).

So regardless of the OS on your TS, you need an activated TS
Licensing Server, and the TS must be able to locate it.
If you run 2003 on the TS, you also have to install TS CALs. For
2003, TS CALs are either Per User or Per Device. Your TS must be
in the same licensing mode as the type of TS CALs you installed.

Check the EventLog on your TS to see the cause of your problem,
and feel free to repost here with the EventIDs and Source
information, as well as the OS on your TS.
 
thanks for your reply.

i'm using a 2000 TS with XP Prro clients, as requested i'm getting the
following Event ID's in the Event Viewer:

1013
1004
1003
18

thats all the info i have at the minute

let me know if this info help
 
OK, it's the first Event (in chronological order), that explains
your problem and the other events:

EventID: 18
Source: TermServLicensing
Description:
Terminal Services Licensing on server <server name> has not been
activated. Terminal Services Licensing will only issue temporary
licenses until the server is activated.

It seems that your Licensing Server is not properly activated.
Check if this helps (be sure to activate the LS when logged on to
the console, not through an rdp session)

306622 - HOW TO: Activate a License Server by Using Terminal
Services Licensing in Windows 2000
http://support.microsoft.com/?kbid=306622

306578 - HOW TO: Deactivate or Reactivate a License Server Using
Terminal Services Licensing
http://support.microsoft.com/?kbid=306578

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
the TS server has been activated, i just put that in there as i put in all
event ID's relating to TS.

but my server is activated
 
Now I'm not sure what you mean, Alex.
Do you mean that you have activated the Licensing Server *after*
Event 18 was recorded? Because if Event 18 still occurs, then the
Licensing Server does *not* think that it is activated, and that's
the cause of the problem.

If you actually activated the Licensing Server after Event 18, we
can forget about that Event.

Event 1003:
"The terminal service client has provided an invalid license."

This is usually caused by an invalid certificate.
Delete the certifcate from the server and the license from the
client, as described here:

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

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
we can forget about that event id 18, as you are right, it was activated
after event 18
 
hi, well i have done what is described in the article that you sent me, and i
have the same problem still. i'm really not sure what else to do except from
re-install the server from scratch.

if you have any other suggestions i'd be extremly grateful

many thanks

alex
 
No, I'm sorry. If you have deleted the certificates from the
server and the license from the client and still get Event 1003,
I've no idea how to continue.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Had the same problem (actually I have now again with one singel client, but
thaqt is another story):

I assume your TS is also the Licenseserver. The follwing helped in my case:

start the terminalserver service with the -nodc in service panel. Second
enter the ip adresse of your licenseserver in the following key:

Hkey_local_machine_\system\currentcontrolset\services\termservice\parameters
defaultlicenseserver

that helped for me so far.
unfortuantly I have the "black screen" Remote Desktop problem now...
 
I would not recommend this.
The -nodc flag is an undocumented flag, for internal
troubleshooting purposes only, which could stop functioning with
the next update / ServicePack.

It will not solve a situation with a corrupt X.509 certificate
either.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Back
Top