On Monday 12 January 2009 03:36, Scott Silva wrote:
on 1-9-2009 12:41 PM Marko Vojinovic spake the following:
I have a WinXP machine that is to be unattended for a period of 3 years
(yes, I know, it sounds ridiculous, but still...). What I need is remote
access to it to perform regular
On Monday 12 January 2009 04:13, Christopher Chan wrote:
the connection must be initiated from C's side to A. This simply cannot
work simultaneously, so I tried to make use of my public server B which
can be used as a bridge between A and C. So, A connects to B, C
connects to B, and then A
Marko Vojinovic wrote:
On Monday 12 January 2009 09:01, Sorin Srbu wrote:
ssh -L 3390:private-ip-of-remote-XP-machine:3389
usern...@ip-or-hostname-of-remote-nat-server
Well, first, private-ip-of-remote-XP-machine is dynamic, given by my ISP's
dhcp server, so I cannot have 100% guarantee
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of
Marko Vojinovic
Sent: Sunday, January 11, 2009 1:36 AM
To: CentOS mailing list
Subject: Re: [CentOS] [OT] Remote control of a WinXP machine from a Linux
host
ssh -L 3390:private-ip
No, the main problem is that A is behind my ISP's NAT. I want to access it
from C (yes, I'll be travelling a lot and C might be just about anywhere).
But the problem is that since A is behind a NAT, the connection must be
initiated from A's side to C. Also, since C might be behind some other
on 1-9-2009 12:41 PM Marko Vojinovic spake the following:
Sorry for an off topic post, but a lot of you folks are sysadmins here or
there, and just might have a suggestion... ;-)
I have a WinXP machine that is to be unattended for a period of 3 years (yes,
I know, it sounds ridiculous, but
the connection must be initiated from C's side to A. This simply cannot work
simultaneously, so I tried to make use of my public server B which can be
used as a bridge between A and C. So, A connects to B, C connects to B, and
then A and C communicate. Roughly speaking...
That was my
Marko Vojinovic wrote:
Sorry for an off topic post, but a lot of you folks are sysadmins here or
there, and just might have a suggestion... ;-)
I have a WinXP machine that is to be unattended for a period of 3 years (yes,
I know, it sounds ridiculous, but still...). What I need is remote
On Friday 09 January 2009 21:41, Marko Vojinovic wrote:
I have a WinXP machine that is to be unattended for a period of 3 years
(yes, I know, it sounds ridiculous, but still...). What I need is remote
access to it to perform regular system maintenance, virus cleanups,
occasional software
Marko Vojinovic wrote:
Sorry for an off topic post, but a lot of you folks are sysadmins here or
there, and just might have a suggestion... ;-)
I have a WinXP machine that is to be unattended for a period of 3 years (yes,
I know, it sounds ridiculous, but still...). What I need is remote
On Saturday 10 January 2009 23:03, John R Pierce wrote:
Marko Vojinovic wrote:
I have a WinXP machine that is to be unattended for a period of 3 years
(yes, I know, it sounds ridiculous, but still...). What I need is remote
access to it to perform regular system maintenance, virus cleanups,
On Saturday 10 January 2009 22:48, you wrote:
I am confused by your description. Do you mean you have Machine A and
Machine B and you want to be able to access both of them at any time
over the next three years from Machine C but you could be behind a
firewall with machine C i.e. I assume you
That was my initial idea, but seems too complicated to work out, so I asked
for a possible easier alternative. :-)
Might be to easy an alternative.
http://www.gotomypc.com
___
CentOS mailing list
CentOS@centos.org
On Sun, Jan 11, 2009, Marko Vojinovic wrote:
On Saturday 10 January 2009 23:03, John R Pierce wrote:
Marko Vojinovic wrote:
I have a WinXP machine that is to be unattended for a period of 3 years
(yes, I know, it sounds ridiculous, but still...). What I need is remote
access to it to
Bill Campbell wrote:
The real issue is how one would script this on the Windows side
as the OpenVPN client I've seen for Windows assumes GUI control.
the Windows OpenVPN implementation supports pretty much the same command
line interface as the Unix version... the OpenVPN GUI is just an
On Sat, Jan 10, 2009, John R Pierce wrote:
Bill Campbell wrote:
The real issue is how one would script this on the Windows side
as the OpenVPN client I've seen for Windows assumes GUI control.
the Windows OpenVPN implementation supports pretty much the same command
line interface as the Unix
Sorry for an off topic post, but a lot of you folks are sysadmins here or
there, and just might have a suggestion... ;-)
I have a WinXP machine that is to be unattended for a period of 3 years (yes,
I know, it sounds ridiculous, but still...). What I need is remote access to
it to perform
OpenVPN.
Tim Nelson
Systems/Network Support
Rockbochs Inc.
(218)727-4332 x105
- Marko Vojinovic vvma...@panet.co.yu wrote:
Sorry for an off topic post, but a lot of you folks are sysadmins here
or
there, and just might have a suggestion... ;-)
I have a WinXP machine that is to be
On Fri, Jan 9, 2009 at 3:41 PM, Marko Vojinovic vvma...@panet.co.yu wrote:
Sorry for an off topic post, but a lot of you folks are sysadmins here or
there, and just might have a suggestion... ;-)
I have a WinXP machine that is to be unattended for a period of 3 years (yes,
I know, it sounds
Marko Vojinovic wrote:
Sorry for an off topic post, but a lot of you folks are sysadmins here or
there, and just might have a suggestion... ;-)
I have a WinXP machine that is to be unattended for a period of 3 years (yes,
I know, it sounds ridiculous, but still...). What I need is remote
Well use Radmin 2.2 for the server and
Wine and Radmin 3 for the Client
Works fine for me
--
Franklin S Werren ad...@chautauqualake.net
www.chautauqualake.net
Confidentiality Note: This email and any attachments are confidential and may
contain privileged information intended for the
21 matches
Mail list logo