If you mean as a stand-alone daemon on the server responding to external requests on port 873, no.
Why are you using ssh port forwarding?
It is the recommended way for XP (AFAIK the reason is Firewall problems) (rsync is cwRsync [itefix.no], and I`m following the format of a batch file provided). Remember, the port-forwarding is working. This is the only success that I have had so far!
Rsync can use ssh as the transport instead of rsh, and does by default in newer versions.
The ssh bundled with cwRsync (and Cygwin) is well known for it`s instability on Windows. I have been using PuTTY [chiark.greenend.org.uk] for almost 2 years, and it has proven rock-solid so far. Both XP + Linux rsync (& PuTTY) are latest versions (2.6.3).
I *did* try
--rsh="<PuTTY command>", also without success, also without any means of finding out *why* it failed.
If you are running rsync as a daemon, try starting the daemon with the --no-detach option so it stays attached to the terminal. Any errors/warning should then appear on the terminal.
That is helpful.
Telling us what command you're using might be helpful.
I have a feeling that that will *not* be helpful, but what do I know? Remember, my request was for troubleshooting assistance with rsync on the server. When I know *why* it fails I can do something about it. Hopefully.