Wrong IP address 0.0.0.0

[linux4guru]

Hello,

Has anyone ran into this issue with Veeam B&R 6.1.203 x64 - "Wrong IP address '0.0.0.0'

I have a ticket filed with Veeam support # 5211118

I don't know what else could be the cause as I can ping and browse to vcenter 4.1 and 5.0 without any issue.

Thanks,
Thomas

[linux4guru]

Looks like support may have found a bug in this version 6.1.0.203 - Somehow after upgrading to this version my proxy server no longer works. The workaround for now is to use another proxy on another server and point to it for backup.

My ticket has been escalated to the next level of support in hope to have this resolve soon.

[Gostev]

Only happens if your proxy has disconnected NIC. Just remove all NICs you are not using, or connect them to some network - this might be much easier workaround. Thanks!

[Mindflux]

Hit with same thing this morning. Ben Milligan suggested disabling any unused NICs on veeam proxy server and re-scanning managed servers under infrastructure. Curiously enough scanning managed servers with the unused NIC enabled is successful too?

[linux4guru]

Where do you go about disconnecting the NIC from Veeam?

[Mindflux]

Where do you go about disconnecting the NIC from Veeam?

Go disable your unused NIC in device manager.

[linux4guru]

Ok, this is what I found from the veeam server - I have a total of 3 NIC - two of which connected to 192.168.x.x but one of that 2 NIC is no longer connected or in use anymore. I have disabled it and then rescan the proxy - after that I relaunch veeam and backup seems to work again...

Thanks for all your help...!

Thomas

[Gostev]

We have updated the patch bits to address this issue. So you may as well just download and install the updated patch.

[linux4guru]

Thanks Gostev... Will download it when I get into the office.

Thomas

[jblanchard]

I would like to confirm that the patch did fix the error"Wrong IP Address 0.0.0.0"

[dellock6]

Only a quick note about the patch webpage, the new build is .204 but the page still state the correct build is .203.

[updated] My bad, haven't refreshed the page, the build number is correct in the page....

Check it out.

Luca.