E
Exotic Hadron
Hello!
I am having difficulties logging into an existing session with RDP
Client 6.0 to a Windows XP SP3 computer. This is what I as my setup
and what I experience.
1. Windows 7 RC1 as a caller client (this is where I run the RDP
Client)
2. Windows XP Professional with SP3 as a called machine (this is where
I want remotely log to)
3. All the computers are in the same workgroup
4. The Windows XP SP3 machine automatically boots into a user account
that does not require password.
Now that I want to log into the booted Windows XP SP3 computer from my
Windows 7 RC1 rig. I fire up the RDP Client using the following
command:
mstsc /v:winxpsp3 /admin
I expect to have logged into the already created session on a remote
Windows XP box (since the XP box automatically boots and logs the
default user it has only a single user account + the default one
administrator account).
(And yes, I understand that is not the best way for keeping all
secret but since it is a testbed environment I don't really care much
about that.)
HOWEVER. When I rush into the XP box, instead of directly logging into
it, I get the login screen window asking me to specify user account
name and password. Since the default user account that is currently
logged into the Windows XP box has no password, I specify its name and
leave the password field blank. The system however does NOT allow me
using the blank password! Seesh...
Now that I specify the administrator (default RID 500) account which
has a password in SAM specified during Windows XP SP3 setup. However,
the system tells me that the already logged user (the one whose
session I want to log in) will be logged out! So I log as a new user
and subsequently I am required to start all my applications again
(which I have automatically starting for me with that account that is
used by default and has no password.)
So the question is:
Is there any way that I boot the XP box into the default account and
then control it remotely without having to log into an another
session?
The thing is that my monitor "passed over" and I have to work with my
XP desktop box from my laptop. For now, as you see, this requires my
to have a completely new workspace when I RDP to XP box. However, I
would like to see my configured standard desktop that I would get if I
had to sit at my burnt monitor.
Thank you in advance for helping.
I am having difficulties logging into an existing session with RDP
Client 6.0 to a Windows XP SP3 computer. This is what I as my setup
and what I experience.
1. Windows 7 RC1 as a caller client (this is where I run the RDP
Client)
2. Windows XP Professional with SP3 as a called machine (this is where
I want remotely log to)
3. All the computers are in the same workgroup
4. The Windows XP SP3 machine automatically boots into a user account
that does not require password.
Now that I want to log into the booted Windows XP SP3 computer from my
Windows 7 RC1 rig. I fire up the RDP Client using the following
command:
mstsc /v:winxpsp3 /admin
I expect to have logged into the already created session on a remote
Windows XP box (since the XP box automatically boots and logs the
default user it has only a single user account + the default one
administrator account).
(And yes, I understand that is not the best way for keeping all
secret but since it is a testbed environment I don't really care much
about that.)
HOWEVER. When I rush into the XP box, instead of directly logging into
it, I get the login screen window asking me to specify user account
name and password. Since the default user account that is currently
logged into the Windows XP box has no password, I specify its name and
leave the password field blank. The system however does NOT allow me
using the blank password! Seesh...
Now that I specify the administrator (default RID 500) account which
has a password in SAM specified during Windows XP SP3 setup. However,
the system tells me that the already logged user (the one whose
session I want to log in) will be logged out! So I log as a new user
and subsequently I am required to start all my applications again
(which I have automatically starting for me with that account that is
used by default and has no password.)
So the question is:
Is there any way that I boot the XP box into the default account and
then control it remotely without having to log into an another
session?
The thing is that my monitor "passed over" and I have to work with my
XP desktop box from my laptop. For now, as you see, this requires my
to have a completely new workspace when I RDP to XP box. However, I
would like to see my configured standard desktop that I would get if I
had to sit at my burnt monitor.
Thank you in advance for helping.