After Upgrade to B&R 9.5 - broken Synology NAS as Repository

[PrimeNet]

Hi folks

Since we upgraded to the newest B&R 9.5 we cannot use the remote Synology NAS anymore as a Linux-Repository... We tried to remove them and add it from scratch... The add process works fine, but then we cannot use it for e.g. Backup Copy Jobs... Everytime we rescan the Linux Server or the Repository we get an answer "unable to detect IP address"

Before in the v9 this worked like a charm....

Does anybody else has this issue?

Note: Synology NAS on the same subnet works good... We open just port 22 and 2500-5000 TCP in the firewall for the remote NAS.

Thanks for an answer...

PrimNet
Support-ID 00406697

[Gostev]

Support-ID 00406697

Hello! This is not a valid support case ID, please include the correct one. Thanks!

[millardjk]

I've got a Synology box (DS2413+ running DSM 6.0.2-8451 Update 4) that I've had to tweak a time or two (http://blog.millard.org/2014/11/use-syn ... itory.html) to keep integrated with Veeam over the versions, but I didn't have to do anything to it after the 9.0->9.5 upgrade. I'd check for the usual network suspects like correct forward/reverse DNS and short/long DNS resolution.

[PrimeNet]

@Gostev

Sorry, but this is our only support-ID. Shall I send you a print-screen?

regards
PrimeNet

[foggy]

This is probably your company support ID, while we're asking for ID of the case you've opened with Veeam technical support regarding this issue.

[PrimeNet]

Hi foggy...

Ok, thanks... Then it is the following ID...
Case # 01982696

[foggy]

Thanks, let's see what our engineers could find out from the logs you've provided.

[skeezix]

Would love a response on what the problem was with this. Running into the same thing - a remote linux server (synology NAS) worked, but after an upgrade it began having problems. It will connect across the internet to the public IP (forwarding port 22, 2500-5000) and login, but then the logs show it returns the synology's private IPs and tries connecting to those instead of the actual IP in the linux server properties.

[foggy]

Roger was provided a hotfix that resolved the issue. So I recommend you to install Update 1 (if you haven't yet) and contact technical support if this doesn't help (not sure whether this hotfix was included in the update). Thanks.

[millardjk]

I'm seeing the same behavior (unable to detect IP address) with 9.5.0.823, so it's apparently not in Update 1. The odd piece is that the Util.VolumesHostDiscover_cli.log file on the Synology box shows what appears to be the successful enumeration of IP addresses.

[foggy]

Have you contacted support with this?

[vchrizz]

hi,
i am having same issue using b&r 9.5 with applied update2.
when trying to backup a linux-host, i am getting error "unable to detect ip address".
can the hotfix please be provided like the updates are provided? its cumbersome, to specifically asking for it via support case...
thanks

[tdewin]

Hotfixes are merged in updates. So as long as there is no new update, please work with our support team. You can just refer to this thread and/or existing case by the previous user to speed up the process (01982696)

[vchrizz]

ok, thanks for the explanation!