Last night, I tried the TS-119 jobs and guess what the same thing happened (and I needed to change the hostnames to the IP's). After much head scratching (and the invention of a completely and very satisfying new swearword) I tried changing the 'Name or IP address of the remote server' entry from the hostname to the IP address and it returned the success message almost instantaneously. When I edited the jobs and hit the 'test' button I got the 'remote doesn't exist' message back at the top of the browser. I've done this many times in the past, but a couple of days back, I tried running the jobs (to backup to the TS-219) they no longer worked. I've used these in the past to back up 3 shares from the TS-659 to my TS-219P+ or TS-119P+ (all on the same internal subnet). I have a TS-659 with 6 jobs set up in remote replication. I'm possibly missing something really obvious, but it's just not jumping out at me at the moment, so I thought I'd post this in case anyone has had anything similar (or any comment that might inspire me to realising what I've done to break it).
I've been through absolutely everything and it all looks to be in place and set up correctly. I don't think I've changed any critical settings anywhere else (well, not that I remember) but the last time I ran the jobs was on the previous Qnap FW (and previous Draytek router FW). This is a rather curious one! In summary, my existing manually activated Qnap-Qnap rsync jobs (internal network) no longer work and I've had to edit them and change from using hostnames to using IP addresses.
0 kommentar(er)
