We are currently implementing new firewall rules and I'm seeing connections that I can not see in Veeam's used ports documentation.
For example: random ESXi hosts to Veeam Windows proxy/mount servers ports 111 (NFS/portmapper). I know that mount server provides powerNFS for instant restore etc. But the direction is from ESXi in HQ to Windows servers in a remote location (which has it's own proxy/mount server). Or other connections that not really make sense. It looks purely random and there are a lot of them.
-
- Veteran
- Posts: 599
- Liked: 87 times
- Joined: Dec 20, 2015 6:24 pm
- Contact:
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Veeam firewall traffic ESXi -> Veeam incoming port 111?
Make sure that the correct mount server is being utilized (by default it is a repository server itself but another server could be configured for the repository during its creation).
-
- Veteran
- Posts: 599
- Liked: 87 times
- Joined: Dec 20, 2015 6:24 pm
- Contact:
Re: Veeam firewall traffic ESXi -> Veeam incoming port 111?
mount servers are fixed in repository extent configuration. Still an ESXi host at location A is connecting to Veeam mount server at location B on port 111.
Who is online
Users browsing this forum: Bing [Bot], ncapponi and 96 guests