Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Click Here to receive this Complete Guide absolutely free.
I have several WinXP laptops which have been backing up to a FreeBSD 6.0 server via rsync for a good while now. Now one laptop is giving me grief. I am running cwRsync and invoking a remote rsync daemon via a shell command:
Yeah, the Windows f/w is the first thing I checked. Off.
I can also SSH to the server no problem. I checked for any other Windows gizmo that might impede traffic. Nada. Well, there was SafeEyes but the user assured me that it is used to block pr0n websites and suchlike things.
You can force rsync to use ssh for transport. Since you say ssh works have you tried that to see if it works? If it does then it would tend to prove the issue is something blocking the port being used by default (873 for daemons).
I think the OP said that ssh was working correctly. I've never tried cwRsync, but would it be possible to try the Cygwin version of rsync? I'm not suggesting changing over, but if both versions of rsync fail that tells us something different to one version working and the other not working.