Hi,
I'm facing a network or firewall issue with my cluster that I don't even know where to start solving.
I have a Windows 2008 R2 Server VM that has a Bitdefender anti-virus and a Google Chrome browser.
Users access this server and make use of remote desktop (terminal service) on it.
So, users use Google Chrome to access certain websites over the internet, including internal websites as well.
However, if I put the VM to run on a specific node of the Cluster, users using Chrome inside this VM are no longer able to access several sites that return with a timeout error.
They ping the internet normally, there is no configuration change. Just the fact of moving the VM from one node to another (even doing hot migration) changes the VM's internal behavior, with access to sites starting to show the timeout error.
It's very strange, as the VM can resolve the IP, but it's as if the server I'm accessing on the other side isn't responding.
Moving the VM back to another node, even by hot migration, makes the VM go back to accessing sites normally...
Theoretically the firewall settings of my Proxmox nodes are factory default. I installed the cluster and didn't mess with it.
On the surface, it looks like the firewall settings are the same on every single nodes.
The error happens whenever the VM is running on node 12. Why and how is it working differently depending on which node the VM is running on?
Any ideas on how to start looking for the problem?
Thanks for the help!
I'm facing a network or firewall issue with my cluster that I don't even know where to start solving.
I have a Windows 2008 R2 Server VM that has a Bitdefender anti-virus and a Google Chrome browser.
Users access this server and make use of remote desktop (terminal service) on it.
So, users use Google Chrome to access certain websites over the internet, including internal websites as well.
However, if I put the VM to run on a specific node of the Cluster, users using Chrome inside this VM are no longer able to access several sites that return with a timeout error.
They ping the internet normally, there is no configuration change. Just the fact of moving the VM from one node to another (even doing hot migration) changes the VM's internal behavior, with access to sites starting to show the timeout error.
It's very strange, as the VM can resolve the IP, but it's as if the server I'm accessing on the other side isn't responding.
Moving the VM back to another node, even by hot migration, makes the VM go back to accessing sites normally...
Theoretically the firewall settings of my Proxmox nodes are factory default. I installed the cluster and didn't mess with it.
On the surface, it looks like the firewall settings are the same on every single nodes.
The error happens whenever the VM is running on node 12. Why and how is it working differently depending on which node the VM is running on?
Any ideas on how to start looking for the problem?
Thanks for the help!
Last edited: