VM connection issues after subnet change. What am I missing? Real time problem.

Onslow said:
I'm afraid I give up ;-(.

On Saturday I asked you:

1) Just in case, execute in the PVE hosts: [ hosts in PLURAL form]

grep -rF 192.168. /etc

and search for any leftovers of the old addressing.

But you showed the result only from ONE host.


2) Double check the network configurations of the VMs (you failed to deliver them here).

[ Again: VMs in PLURAL. And I wasn't the only one who asked for that ].

Today you posted the result from one VM only.

I feel exhausted, sorry, @Bikersmurf

Before I quit I have one more idea to check by you. You mentioned some routers... Double check their IP addresses, network masks and routings. Also, firewall rules, if there are any.

Good luck!
Click to expand...
There is only one PVE host which is why I only provided one host. I'm not having connection issues involving more than one host. The issues I'm having are all within that one host. None of the VMs had static IPs and when I set up the server on a different router (hence the different subnet), the router assigned IP addresses from it's assigned pool.

I'm not sure what other information I can provide. If I connect use RDP on my physical desktop to connect to any of the VMs on the PVE host it works with no issues. If I map a drive on the physical desktop computer (or laptops or other desktops) the credentials are accepted and everything works as it should. I can also use my phone from anywhere I have service to create a hotspot for my laptop, connect a VPN connection, and then RDP into any of the VMs just the same as if they were a physical computer running any version of Windows Pro software. I can also connect from any of the VMs within the PVE to any computer outside of the that host.

The issue I'm having after moving the server from on one router to another is that no Windows 11 VM can connect to another Windows 11 VW withing the same PVE host. It doesn't matter if I try to use RDP or try to map drives. Suddenly it's as though the credentials are wrong... even if I copy and paste them from another computer, from outside the host, where they work as they should.

I've run grep, posted the results, and searched everywhere I can think of with Grep and manually. The only thing I have found is the Certificate below:

1771531514868.png

On the right hand side of the second certificate it has 192.168.8.120 (8 subnet is the old one), whereas I believe it should be 192.168.3.120 (3 subnet is the current one). Now, I'm learning this as I'm going along, but I'd think a certificate with an IP address that doesn't match the host could potentially be a problem. To eliminate this possible cause, I'd like to correct this. Do you know how? Or can you point me in the direction of a solution?

If the Certificate isn't causing the problem, wherever it got it's information could be the problem. I'd really appreciate a bit more help to explore this last avenue. I'm hoping it is either the problem, or a clue to what the problem is.

Thanks you in advance. :cheers: I owe you one.
 
mram said:
Do any of your VMs still have 192.168.8.x addresses statically assigned in them?
Did you check your Proxmox firewalls? Try disabling the Proxmox firewalls.
Do you have the KVM guest tools installed in the VMs? I assume they are Windows since you want to RDP. https://pve.proxmox.com/wiki/Qemu-guest-agent
The IPs of the VMs should be visible like the pictures below, except they should be 192.168.3.x addresses now. Note: you will have to power down each vm for a moment to enabled the QEMU guest agent.

View attachment 95853View attachment 95852
Click to expand...
Reviewing previous posts to see if there was anything I overlooked.

None of the VMs have had Static IP addresses assigned to them before or after the Subnet change they are all dynamic IPs. The issues are all inside of one host/node. Physical computers (outside of the host) have no issues connecting to VMs inside the host using both RDP and SMB.

Thanks.
 
Last edited:
Bikersmurf said:
I'd think a certificate with an IP address that doesn't match the host could potentially be a problem
Click to expand...
has nothing to do with network between guests.
triple check within your guests.
No third party app within guest ?
Have you multiple Windows accounts ? Windows 11 lock out account after multiple failure.
edit: do you use hostname to connect ? if yes, try ip
 
Last edited:
You must log in or register to reply here.
Top Bottom
Back