Rsync has been running for some time without any problem. The server is Windows Server 2003 and the clients are also Windows OS. All of my clients are working except one. In troubleshooting, I worked on the problem-child but got no where. So, I went to a working client and tried to change the behavior of that client to get a better idea if the problem is with the problem-child or my server. Well, I can't change the behavior of the one that is working. Here is part of my rsyncd.conf.
****************** rsyncd.conf*****************
use chroot = false
strict modes = false
hosts allow = *
log file = rsyncd.log
pid file = rsyncd.pid
hosts allow = 192.168.1.0/24, 5.6.7.8
path = d:/customers/clienta
read only = no
list = no
hosts allow = 192.168.1.0/24, 1.2.3.4
path = d:/customers/clientbRemoteBackup
read only = no
list = no
****************** rsyncd.conf*****************
ClientB is the one that is the problem. 1.2.3.4 is a representation of a public ip address. From ClientB's computers I try "telnet rsyncserver.mydomain.com 873". But if I go to ClientA's computer and try "telnet rsyncserver.mydomain.com 873", I get through with the message " @RSYNCD: 28
@ERROR: protocol startup error"
So, as a test, I changed the ip address on the working client to see if I could make it fail and I couldn't.
Here's what I changed it to...notice I changed the last octet of the ip address in the hosts allow line. That should've caused the telnet to fail but it didn't. I even restarted the rsync service just in case. I know you don't have to do that but I wanted to make sure.
hosts allow = 192.168.1.0/24, 5.6.7.9
path = d:/customers/clienta
read only = no
list = no
I even removed the clienta module from the file and clienta could still connect. I thought maybe there was another rsyncd.conf file stuck somewhere that I didn't know about...there isn't.
So, it seems that the problem is with my server and not the clients but I just can't seem to get to the bottom of this.
thanks for your help,
Mike