Remote Desktop Connection problems

[Guest]

I use Windows XPs Remote Desktop Connection tool found under
programs>Accessories>Communication. I have a client machine that when I
attempt a remote connection it crashes(reboots). I believe I have it
configured correctly using the directions on Microsofts web site directions:
http://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx

The machine is on the network at my company

I also tried some of the suggestion on this page:
http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
The netstat -a showed that 3389 port is being listened to. I downloaded the
PortQuery tool and when I query the 3389 port with this the system also
crashed(rebooted).

On the Windows XP newsgroup for Remote Desktop one read had a similar
problem and later found it to be there video card. Updating the drive on his
client machine solved his problem. I tried updating my video drive and it
did not help.

The system specs for the client machine are;
Windows XP Professional Service Pack 2
P4 3 Ghz, 1 gig RAM
The video card is a Intel 82865G Graphics Controler

I have tried the connection from 2 different machines and had the same
problem.

Any Ideas what the problem could be?

 

[Sooner Al [MVP]]

Anything in the event log on the failing PC that may provide a clue?

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[Guest]

It does seem to say much, but maybe that is because I don't know how to read
it.

In System events I see:

Information Event ID 6009
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Multiprocessor Free.

Then:

Error; Category (102) Event ID 1003
Error code 1000008e, parameter1 c0000005, parameter2 bf93da60, parameter3
ecfc87e4, parameter4 00000000.

One thing about the client system is it has hyper threading, I tried
disabling it in the bios but this did not help. A mindump has created, I'll
try to take a look at that.

--
Regards,
Kevin D.

Anything in the event log on the failing PC that may provide a clue?

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[Sooner Al [MVP]]

Is there a "Source" for the error Event ID?

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

It does seem to say much, but maybe that is because I don't know how to
read
it.

In System events I see:

Information Event ID 6009
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Multiprocessor Free.

Then:

Error; Category (102) Event ID 1003
Error code 1000008e, parameter1 c0000005, parameter2 bf93da60, parameter3
ecfc87e4, parameter4 00000000.

One thing about the client system is it has hyper threading, I tried
disabling it in the bios but this did not help. A mindump has created,
I'll
try to take a look at that.