RDP Connection generates Event Viewer Entry

[rsageofdunstable]

Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1036
Date: 26/10/2008
Time: 18:54:57
User: N/A
Computer: VMSERVER
Description:
Terminal Server session creation failed. The relevant status code was
0xC0000037.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I have spent most of today investigating this and so far found very little.
I have uninstalled XP SP3 I have downloaded and run Regcure which fixed 1200+
errors but not this one.

Anyone else come across this

 

[Robert L. \(MS-MVP\)]

You my want to check the Terminal Services configuration. Or this cases
study may help.

Event ID 1036 - Terminal Server session creation failed
http://www.chicagotech.net/troubleshooting/eventid1036.htm

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

 

[rsageofdunstable]

Robert

Thanks for the quick response. I should have been more specific. I was
attempting to connect from work over the public internet to my home machine.
Both run Windows XP Pro. My work laptop runs SP1 my home machine runs now
runs SP3 after I re-installed it

I did identify that another applicaton DcomLaunch is also using port 3389
C:\Documents and Settings\Russell>netstat -a -o

Active Connections

Proto Local Address Foreign Address State PID
TCP VMServer:smtp VMServer:0 LISTENING 484
TCP VMServer:epmap VMServer:0 LISTENING 340
TCP VMServer:https VMServer:0 LISTENING 484
TCP VMServer:microsoft-ds VMServer:0 LISTENING 4
TCP VMServer:1038 VMServer:0 LISTENING 484
TCP VMServer:1827 VMServer:0 LISTENING 3504
TCP VMServer:1906 VMServer:0 LISTENING 484
TCP VMServer:1947 VMServer:0 LISTENING 736
TCP VMServer:3389 VMServer:0 LISTENING 2044


C:\Documents and Settings\Russell>tasklist /svc

Image Name PID Services
========================= ====== =============================================
System Idle Process 0 N/A
System 4 N/A
csrss.exe 1536 N/A
winlogon.exe 1580 N/A
services.exe 1704 Eventlog, PlugPlay
lsass.exe 1736 PolicyAgent, ProtectedStorage, SamSs
svchost.exe 2044 DcomLaunch, TermService
svchost.exe 340 RpcSs

Could this be my problem?

 

[Robert L. \(MS-MVP\)]

Yes, that could be the problem. For a test, disable DcomLaunch or change
the TS port. Please post back with the result.

Terminal Service
How to modify Terminal Server's accessing port How to Print to a Local
Network Printer in TS How to redirect TS client printers ...
www.howtonetworking.com/server/ts.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

 

[rsageofdunstable]

Excellent. I changed the TS port to 3390 and I have now access. Don't know
why DcomLaunch should have caused a problem but great work around. Thank you
very much

 

[rsageofdunstable]

Robert

It appears that I was premature. the second time I attempted to connect I
was refused and when I checked the DcomLaunch process has changed to match
the TS listening port

 

[Robert L. \(MS-MVP\)]

According to Microsoft, XP SP2 moves the Terminal Services service to the
DCOMlaunch service in Svchost.exe. This is to help reduce the restart
requirements in Windows XP SP2 when you update Windows and we can't stop
DCOMlaunch service.
You may want to go back to the link I post before to double check the TS
configuration.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com