Can't Connect to VB365 v8 using IPv6

[MILJW002]

Hi All,

This is an odd one, and took me a little while to narrow down.

I've just upgraded to V8 and didn't have any errors during the process, but then wasn't able to connect from a remote host after.

I have a VB365 server running, but usually use a management workstation to connect to and manage it. I tried to connect and it just timed it. I was connecting using the FQDN as I have been since I first set this up (I think v 1.5).

If I change to the IPv4 address can connect with the console. If I try the IPv6 address, I can't.

If I use TCPView on the VB365 server itself, I can see components talking to each other on IPv6, but using the fe00 addresses.

Have I missed something, or is there something wrong with IPv6 with VB36 v8?

James

[Mike Resseler]

Hi James,

It shouldn't. However, there might be some additional firewall configuration you need to do? Although since you are taking about a management workstation, and therefore I assume the desktop UI to the VB365 server I don't believe anything has changed there.

Can you potentially check if it is something like that, and if not, please open a support case. The different components should be able to talk IPv6 against each other (but connecting to M365 service itself is another topic... there are still certain M365 services that are not supporting IPv6)

[MILJW002]

Hi,

Thanks for the quick response, but I'll clarify. I'm trying to run "Veeam.Archiver.Shell.exe" from a management workstation, and connecting to the Veeam Backup for M365 v8 sever. Worked since V1, and works if I specific an IPv4 address. If I use the FQDN, this resolves to an IPv6 address. If I try the FQDN or the IPv6 address, the connection times out.

I did try (as a troubleshooting step) to disable the Windows firewall on the Veeam Backup for M365 server and it didn't make any different (and it works with IPv4). I'll dig more, but this is a strange one.

James

[Mike Resseler]

Since this should work as we have tested IPv6 for the internal components, please open a support case on this one.

Thanks
Mike

[MILJW002]

Hi,

Sorry, it took me a while to log a case for this. I've been busy, and I was hoping the updates may fix this.

I've now logged a case Case #07469163 for this.

It's really strange. IPv6 has been working happily for years. It still works for the Restore Portal etc. It's only if I try and use the Console from to connect.

[MILJW002]

I've added heaps of details to the ticket. Firewall logs, config etc etc.

Using TCPView on the backup server, I can see it is listening on 9191 for 0.0.0.0, but there is no entry for :: for port 9191. It's like the Veeam service isn't listening on 9191 for some reason.

[MILJW002]

Hu All,

Just reporting back. Support has been able to reproduce the issue and have gone to engineering to investigate. I was also asked to upgrade to 8.0.4 (didn't even realise it was out), but it didn't help.

I'm not just in my head, and it's not just me!

J