Hi folks,
I'm installing a Bacula server 9.0.6 under CentOS 7.4. I have also
purchased a binary license for backing up a couple of Windows servers
with the Bacula client. The purchased Windows client version is 7.4.4.
When I run bconsole, status, Network, and select the Windows client
(192.168.0.205), the report is:
Connecting to Storage xxxx-Sd at 192.168.0.103:9103
Connecting to Client yyyy-Fd at 192.168.0.205:9102
Running network test between Client=yyyy-Fd and Storage=xxxx-Sd with
52.42 MB ...
2999 Invalid command
I also have got Bacula 9.0.6 installed on a CentOS 7.4 server, and
running the same network status works without errors. Also running
network status on the local machine reports no errors.
I have made a successful test backup of the Windows client, without any
error messages.
As it's a small network with just a few servers, I prefer to use IP
addresses instead of names. Using names and register them in the
DNS-server doesn't change anything. The behavior is identical. Also, the
appropriate ports are open in the firewalls, so turning off the
firewalls under Windows and CentOS reps., makes no difference.
Is the error message due to compatibility issues between the Windows
7.4.4 Bacula client and the 9.0.6 server, or is there some problem that
will jump up and bite me in the future?
Best regards,
Peter
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
