From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Access Windows XP running in VirtualBox
Date: Sat, 14 Mar 2009 17:34:28 -0600 [thread overview]
Message-ID: <20090314233428.GJ6266@syscon4.inet> (raw)
In-Reply-To: <gphcs9$6an$1@ger.gmane.org>
On 03/15/09 00:59, Nikos Chantziaras wrote:
[snip]
>> XP (that is good), but:
>> 1.) the terminal I'm connecting to has to accept my connection, is it
>> possible to set it up so I connect to it automatically.
>> 2.) I'm taking control of the mouse and keyboard of the remote workstation
>> (in this case my server).
>> What I need is to connect to the server being able to use it without
>> taking control of the desktop mouse or keyboard.
>
> Then you need to enable the "terminal client" service of Windows XP instead
> (XP Professional has this). For this to work, you need to disable the RDP
> of VirtualBox or use another port. Also, since XP's RDP is a service, you
> need port forwarding if you're using NAT networking in VBox.
>
> You can Google on how to enable RDP/terminal services inside XP.
I'm trying now nxserver-freenx but it is giving me problem with configuration; do you know anything about setting up freenx?
when I run:
nxsetup --install --setup-nomachine-key --clean --purge
...
----> Testing your nxserver connection ...
Permission denied (publickey,keyboard-interactive).
Fatal error: Could not connect to NX Server.
Please check your ssh setup:
The following are _examples_ of what you might need to check.
- Make sure "nx" is one of the AllowUsers in sshd_config.
(or that the line is outcommented/not there)
- Make sure "nx" is one of the AllowGroups in sshd_config.
(or that the line is outcommented/not there)
- Make sure your sshd allows public key authentication.
- Make sure your sshd is really running on port 22.
- Make sure your sshd_config AuthorizedKeysFile in sshd_config is set to authorized_keys2.
(this should be a filename not a pathname+filename)
- Make sure you allow ssh on localhost, this could come from some
restriction of:
-the tcp wrapper. Then add in /etc/hosts.allow: ALL:localhost
-the iptables. add to it:
$ iptables -A INPUT -i lo -j ACCEPT
$ iptables -A OUTPUT -o lo -j ACCEPT
my sshd.conf:
Port 22
Protocol 2
PermitRootLogin no
AuthorizedKeysFile authorized_keys2
AllowUsers nx
AllowGroups nx
PasswordAuthentication no
UsePAM no
Subsystem sftp /usr/lib/misc/sftp-server
--
#Joseph
GPG KeyID: ED0E1FB7
next prev parent reply other threads:[~2009-03-14 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 16:58 [gentoo-user] Access Windows XP running in VirtualBox Joseph
2009-03-14 18:52 ` Roy Wright
2009-03-14 19:05 ` [gentoo-user] " Nikos Chantziaras
2009-03-14 19:30 ` Joseph
2009-03-14 19:54 ` Nikos Chantziaras
2009-03-14 20:58 ` Joseph
2009-03-14 22:59 ` Nikos Chantziaras
2009-03-14 23:34 ` Joseph [this message]
2009-03-15 0:56 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090314233428.GJ6266@syscon4.inet \
--to=syscon780@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox