From: Joe#2 on
One desktop in an office of 10 locks up when you attempt to connect to it
using the remote connect from another desktop or connect via terminal
services from the server.

As soon as you attempt to connect, this desktop locks up. You have to do a
hard reset with the power button.

The Terminal services client is running.
The user is set up to connect remotely. (sys admin has the same result)
Firewall is set up for terminal services, If you turn off the firewall, same
thing.
Computer does return a ping OK .
Got any ideas.
I'm at the customers site tonight. Can't work on this one remotely!!
From: Cliff Galiher on
1) This is an SBS group. Since this happens from one workstation to another
workstation, we can safely remove SBS from the equation, which makes this an
off-topic post. Just worth pointing that out...

2) Almost *always* a driver issue. Since it happens regardless of souce,
the NIC driver is probably not handling a unique aspect of the incoming RDP
packets. Try updating the NIC driver, or if necessary, replacing the NIC.

-Cliff


"Joe#2" <Joe2(a)discussions.microsoft.com> wrote in message
news:1A638435-571E-46C3-AEC9-67613FB9736E(a)microsoft.com...
> One desktop in an office of 10 locks up when you attempt to connect to it
> using the remote connect from another desktop or connect via terminal
> services from the server.
>
> As soon as you attempt to connect, this desktop locks up. You have to do a
> hard reset with the power button.
>
> The Terminal services client is running.
> The user is set up to connect remotely. (sys admin has the same result)
> Firewall is set up for terminal services, If you turn off the firewall,
> same
> thing.
> Computer does return a ping OK .
> Got any ideas.
> I'm at the customers site tonight. Can't work on this one remotely!!

From: Leythos on
In article <1A638435-571E-46C3-AEC9-67613FB9736E(a)microsoft.com>, Joe2
@discussions.microsoft.com says...
> One desktop in an office of 10 locks up when you attempt to connect to it
> using the remote connect from another desktop or connect via terminal
> services from the server.
>
>

If the computer uses an NVIDIA video card/driver then you should go to
the NVIDIA site and download the latest driver - I see this same issue
in a lot of computers from Dell that ship with NVIDIA drivers.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)
From: Lanwench [MVP - Exchange] on
Leythos <spam999free(a)rrohio.com> wrote:
> In article <1A638435-571E-46C3-AEC9-67613FB9736E(a)microsoft.com>, Joe2
> @discussions.microsoft.com says...
>> One desktop in an office of 10 locks up when you attempt to connect
>> to it using the remote connect from another desktop or connect via
>> terminal services from the server.
>>
>>
>
> If the computer uses an NVIDIA video card/driver then you should go to
> the NVIDIA site and download the latest driver - I see this same issue
> in a lot of computers from Dell that ship with NVIDIA drivers.

Amen. I had a whole batch of Precision Workstations go screwy with this in
August. It was a nightmare.

I applied the following in a reg file to all PCs at startup via GPO and the
problem went away ..mind word wrap!

---------------cut 'n paste ----------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management]
"ClearPageFileAtShutdown"=dword:00000000
"DisablePagingExecutive"=dword:00000000
"LargeSystemCache"=dword:00000000
"NonPagedPoolQuota"=dword:00000000
"NonPagedPoolSize"=dword:00000000
"PagedPoolQuota"=dword:00000000
"PagedPoolSize"=dword:00000000
"SecondLevelDataCache"=dword:00000000
"SystemPages"=dword:000c3000
"PagingFiles"=hex(7):43,00,3a,00,5c,00,70,00,61,00,67,00,65,00,66,00,69,00,6c,\
00,65,00,2e,00,73,00,79,00,73,00,20,00,32,00,30,00,34,00,36,00,20,00,34,00,\
30,00,39,00,32,00,00,00,00,00
"PhysicalAddressExtension"=dword:00000001
"SessionViewSize"=dword:00000030
"SessionPoolSize"=dword:00000004
"WriteWatch"=dword:00000001
"SessionImageSize"=dword:00000020

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\PrefetchParameters]
"VideoInitTime"=dword:0000056e
"EnablePrefetcher"=dword:00000003
"AppLaunchMaxNumPages"=dword:00000fa0
"AppLaunchMaxNumSections"=dword:000000aa
"AppLaunchTimerPeriod"=hex:80,69,67,ff,ff,ff,ff,ff
"BootMaxNumPages"=dword:0001f400
"BootMaxNumSections"=dword:00000ff0
"BootTimerPeriod"=hex:00,f2,d8,f8,ff,ff,ff,ff
"MaxNumActiveTraces"=dword:00000008
"MaxNumSavedTraces"=dword:00000008
"RootDirPath"="Prefetch"
"HostingAppList"="DLLHOST.EXE,MMC.EXE,RUNDLL32.EXE"

----------------------



From: Joe#2 on
Thanks to both. I will try that.

Didn't think about it being off topic! It all started he couln't logon
remotely thru SBS and I went in to troubleshoot it. I started at the server
then migrated to a desktop with the common point of error being his desktop.
It was all working fine for months, then it started about a month ago.

PS, where would be the proper place to post this? The XP forum?

"Leythos" wrote:

> In article <1A638435-571E-46C3-AEC9-67613FB9736E(a)microsoft.com>, Joe2
> @discussions.microsoft.com says...
> > One desktop in an office of 10 locks up when you attempt to connect to it
> > using the remote connect from another desktop or connect via terminal
> > services from the server.
> >
> >
>
> If the computer uses an NVIDIA video card/driver then you should go to
> the NVIDIA site and download the latest driver - I see this same issue
> in a lot of computers from Dell that ship with NVIDIA drivers.
>
> --
> You can't trust your best friends, your five senses, only the little
> voice inside you that most civilians don't even hear -- Listen to that.
> Trust yourself.
> spam999free(a)rrohio.com (remove 999 for proper email address)
> .
>