G
Guest
Hi,
I have been experiencing this problem for a while now and am yet to find out
what the problem is, please help. This happens on my Dell Dimension and also
on an IBM thinkpad laptop so I don't think it is machine specific.
I am running a Windows XP SP2 PC (all security patches etc). Some times I
wish to sit in front of the PC and use it and other times I wish to control
it via Remote Desktop from the internal lan (ie no internet connection is
involved). I normally power the computer into a standby mode when I've
finished using it. When I come to sit in front of it I bring the computer out
of standby by either pressing the power button, pressing a key or moving the
mouse. Any of these actions fires up the PC and the monitor turns on. If
however I wake the PC by WOL the monitor does not "come on" and then when I
try and connect to it by Remote desktop it prompts me to login but as soon as
I login the Remote Desktop client crashes. If I wake the PC normally and then
connect via Remote Desktop it works fine.
So in summary:
- When the PC is ON I can connect, login and control the PC perfectly.
- When the PC is OFF I can send a wake on lan magic packet to wake the PC
and then I can connect, login and control the PC perfectly.
- When the PC is on STANDBY I send the wake on lan magic packet which wakes
the PC. At this point I can connect to network drives etc so the PC is on.
However if I try and connect via Remote Desktop I am prompted for the
username and password fine however as soon as I click "OK" or press enter the
window disappears and the "Remote Desktop Connection" dialog returns (asking
me which computer I want to connect to")
The exact same thing happens to both my PC and my laptop at home which both
run windows XP.
Any ideas how I can get round this problem.
I have been experiencing this problem for a while now and am yet to find out
what the problem is, please help. This happens on my Dell Dimension and also
on an IBM thinkpad laptop so I don't think it is machine specific.
I am running a Windows XP SP2 PC (all security patches etc). Some times I
wish to sit in front of the PC and use it and other times I wish to control
it via Remote Desktop from the internal lan (ie no internet connection is
involved). I normally power the computer into a standby mode when I've
finished using it. When I come to sit in front of it I bring the computer out
of standby by either pressing the power button, pressing a key or moving the
mouse. Any of these actions fires up the PC and the monitor turns on. If
however I wake the PC by WOL the monitor does not "come on" and then when I
try and connect to it by Remote desktop it prompts me to login but as soon as
I login the Remote Desktop client crashes. If I wake the PC normally and then
connect via Remote Desktop it works fine.
So in summary:
- When the PC is ON I can connect, login and control the PC perfectly.
- When the PC is OFF I can send a wake on lan magic packet to wake the PC
and then I can connect, login and control the PC perfectly.
- When the PC is on STANDBY I send the wake on lan magic packet which wakes
the PC. At this point I can connect to network drives etc so the PC is on.
However if I try and connect via Remote Desktop I am prompted for the
username and password fine however as soon as I click "OK" or press enter the
window disappears and the "Remote Desktop Connection" dialog returns (asking
me which computer I want to connect to")
The exact same thing happens to both my PC and my laptop at home which both
run windows XP.
Any ideas how I can get round this problem.