Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I created a batch file to run called it c:\stupid.bat and put the command to run in it and verified it would run when i typed 'c:\stupid.bat'

I then go on my windows box and create a scheduled task.
Start --> Programs --> Accessories --> System Tools --> Scheduled tasks
It takes you through a Wizard to set it up. Put c:\stupid.bat in for the command to run.

I've never messed with the private key on windows but you could probably do that instead of putting in the -pw command for your password.

I've had some success with winscp for scping stuff from a linux box. Note that whichever side you're initiating the connection from is the client; the other machine is the server. That means that whichever machine is connected to will need to be running the openssh daemon. My point, anyway, is that either your script will have to be on the windows box or your windows box will have to be running a ssh daemon.

This isi a case where experimentation will supply the best answer. You may need an active session started from the windows box. Start the ssh program from windows ( putty or ssh32 ) and leave it running. Then try the 'scp command from the Linux box. If they were linux boxes, you could have a script on Machine C that would scp a file from Machine A to Machine B. If this experiment works then this may be possible if Machine A or B were windows.

Thanks to all for you ideas! One of my problems is that I didn't have SSH running on the Windows box. I'm looking at a couple of the free SSH programs and I'm going to experiment. I'm also looking at trying to get the private key working to I can pull the file from Linux with no password. I had created a public key and that is probably why things didn't work.

For others who may have the same problem, here are the steps I followed:

1) On the Windows box (client) Use puttygen.exe to create a public/private key.
2) Using a text editor, copy the public key that puttygen creates to a file called 'authorized_keys' (or authorized_keys2 depending on whether you are using SSH1 or SSH2).
3) Place the 'authorized_keys' file on the Linux box in the directory you need to access in the .ssh sub-directory. chmod 644 on the 'authorized_keys' file.
4) On the Windows box, using the pscp command, enter the following: