RE: Terminal Server session creation failed

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ah, now we're getting somewhere...

Try these links to see if they help:
http://support.microsoft.com/?kbid=312030

as well as these knowledgebase articles:
Q270588, Q258021, Q186645

-M

"Martijn Heerkens" wrote:

> I did a netstat -an but there is no port 3389 listed. In the TSAdmin utility
> I'm not able to connect to this computer.
>
> "Matthew Harris [MVP]" wrote:
>
> > Hmm..you shouldn't need to restart the server to recreate the rdp-tcp
> > listener...
> >
> > Once the server is up, can you do a netstat -an to see if something is
> > listening on port 3389?
> >
> > If you bring up the tsadmin utility, is the RDP-tcp listener in the
> > listening state, rather than being 'down' or similar state?
> >
> > -M
> >
> > "Martijn Heerkens" wrote:
> >
> > > I've tried that but after restarting the server it comes up with the same
> > > error messages.
> > >
> > > "Matthew Harris" wrote:
> > >
> > > > Have you tried deleting your RCP-tcp listener in your terminal services
> > > > configuration and then recreating it?
> > > >
> > > > -M
> > > >
> > > > "Martijn Heerkens" wrote:
> > > >
> > > > > We're running a Windows 2003 Standard Server as a Terminal Server. The server
> > > > > has been working fine for the first three months but yesterday client could
> > > > > no longer connect. When we rebooted the server we received an error stating
> > > > > that one service failed to start. In the eventlog the following error
> > > > > messages was listed:
> > > > >
> > > > > EventID:1036
> > > > > Terminal Server seesion creation failed. The relevant status code was
> > > > > 0xC0000034.
> > > > >
> > > > > EventID:7026
> > > > > The following boot-start or system-start driver(s) failed to load: TermDD
> > > > >
> > > > > We decided to install ServicePack 1 for Windows 2003 Server because we read
> > > > > about identical issues and how they would be solved in the next ServicePack.
> > > > > But after we installed SP1 we still have the same issues.
> > > > >
> > > > > Please help quick because we now have 15 users who are not able to work the
> > > > > last few days.
.

Relevant Pages

  • Re: ISA 2004 & companyweb
    ... You cannot access companyweb via http://comanyweb ... By default the Web Listener is listening on the external network adapter. ... Server computer in the selected network". ... Please send the IIS metabase to me for further analysis: ...
    (microsoft.public.windows.server.sbs)
  • Re: Trust Between 2 domain Controllers
    ... Here the netdiag status of the server ripples... ... Testing DNS ... LISTENING ... Binding Paths: ...
    (microsoft.public.win2000.active_directory)
  • Re: how to disable Default OBEX Server.
    ... There is a description of the process of creating an SDP ... record and listening on a service in the SDK documentation. ... I need to develop my own server over bluetooth using normal ... I have disabled the default obex server by making changes ...
    (microsoft.public.pocketpc.developer)
  • Re: RealVNC
    ... Default listening port for RealVNC server that runs on the machine on which ... Then there is default Java listening port on port 5800 on the client machine ...
    (microsoft.public.windows.server.sbs)
  • Re: Publishing A web Server
    ... Socket Pooling is enabled. ... it effectively disables ... listening on all other addresses. ... >>Begin to look around for a good ISA Server tutorial;). ...
    (microsoft.public.isa)