Re: Problems with DC and TS
- From: Javier <Javier@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 2 Jun 2008 22:40:01 -0700
Hi Vera,
The problem is fixed.I checked the limit of connections and it was checked
one connection.
Thanks a lot for your help and patience ;)
Best Regards !
"Vera Noest [MVP]" wrote:
You should never run Terminal Services on a DC, for bot performance.
and security reasons.
Keep in mind that a TS is just a multi-user workstation! Do you
really want to have your users log on to your DC and use it as
their PC?
Before you try to repair the installation, have you checked if
there is a limit on the number of concurrent connections configured
in Terminal Services Configuration - rdp-tcp connection - Network?
This should be configured with "unlimited" number of sessions.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?SmF2aWVy?= <Javier@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
02 jun 2008 in microsoft.public.windows.terminal_services:
Hi Vera,
Terminal Services is installed on the DC.I checked old
connections but there aren't anything.
I can connect with administrative session,but no with TS.
You say that it's not a good idea to install TS on a DC.What's
the reasons about this?
The only solution that is happened to me, is to repair the
installation of the server :(
"Vera Noest [MVP]" wrote:
Sounds to me as if Terminal Services isn't installed on the DC,
and you just have 1 administrative session left. And I
certainly hope that this is the case, because it is *not* a
good idea to install Terminal Services on a DC!
What you can do is to start the TS Manager on the DC, and check
if there is still an old disconnected session. If so, reset
that session. This will make sure that you can have 2
simultaneous administrative sessions to the DC + 1 to the
console, with the command "mstsc /console", for a total of 3
free administrative sessions.
Does this solve your problem?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?SmF2aWVy?= <Javier@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 30 maj 2008 in microsoft.public.windows.terminal_services:
Hi Vera,
Excuse me for my poor description.
Ok,this is the scene:
We have a windows 2003 domain whith several windows 2003
server.This servers have installed TS and our users works
fine in this servers.The LS is a windows 2003 member server
and mi DC is a windows 2003 server.
In all servers,TS works fine but in DC server Ts don't
work.If I try to connect to DC whith the remote desktop,i get
access via remote desktop.But,if i try to connect to DC with
two connections or more, a message is showed:
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 don't find any messages in the event viewer about the
problem.
I have tried to execute "mstsc /v:localhost" and i connect me
perfectly.
Where is the mistake?
Thanks a lot for your efforts
"Vera Noest [MVP]" wrote:
Javier, could you describe your problem in a bit more
detail? What exactly is it that doesn't work?
You are not able to connect to the DC? What error message do
you get when you try to connect?
Have you checked the EventLog on the server?
Can you logon to the physical console of the server?
If so, can you from the physical console connect to the
server itself, with "mstsc /v:localhost"?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
=?Utf-8?B?SmF2aWVy?= <Javier@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 30 maj 2008:
Hi Ratnesh,
I have tried the solution but the TS don't work in my DC.
My DC find the LS and others servers have TS working fine.
I try to reinstall the ts services but this doesn't fixed
it.
Thanks a lot for your efforts ;)
"Ratnesh Yadav [MSFT]" wrote:
You mean you have TS intsalled on DC.
And TS License Server on Domain joined machine.
Well I guess your TS is not able to discover TS License
Server. You need to specify the License Server on TS.
Please check following link for doing that
http://technet2.microsoft.com/windowsserver/en/library/468
44a 6e- 386f-4ce3-98e5-d5377b5d6ba91033.mspx?mfr=true
Ratnesh
"Javier" <Javier@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:419E7BF9-0CB1-41CE-A160-B8D4AA9A3A07@xxxxxxxxxxxxxxxx
Hi,
I have a 2003 domain with several servers Windows 2003.
The license's server is installed in a Windows 2003
member server.
The problem appears to me in my DC.It's a Windows 2003
to which I can not access with terminal server.If I
check to the license's server,I don't see the license
of my DC.
However, still I have free licenses.
do you know where can be the problem?
Thank you very much by your aid
- Follow-Ups:
- Re: Problems with DC and TS
- From: Vera Noest [MVP]
- Re: Problems with DC and TS
- References:
- Re: Problems with DC and TS
- From: Javier
- Re: Problems with DC and TS
- From: Vera Noest [MVP]
- Re: Problems with DC and TS
- Prev by Date: Re: Installed Terminal Services and Quickbooks now server hosed
- Next by Date: Thinclient show
- Previous by thread: Re: Problems with DC and TS
- Next by thread: Re: Problems with DC and TS
- Index(es):
Relevant Pages
|
