Search results

I'm glad you found a solution to your problem. I can confirm this was not how my diagnostics went. It was basically a 1 hour break for me while I beat my head against concrete (because that was a softer and more yielding thing to beat my head against) and when I returned everything was fine...

Unfortunately not. I haven't plugged in the other computer that was acting as the second node in the cluster since then for a few reasons.

Morning folks, bit of a conundrum here. Straight to the point: I've set up Proxmox on a second computer with the intention to use it as part of a cluster here at home. Post installation, all was well. Once I made it join the cluster however, the web UI on that second server stopped allowing...

Yeah, so, frustrations abound, but DHCP is working again. -.-; I'm just going to go over there and cry now. I'm a programmer, I should know technology doesn't work how you want it to by now. It does things to spite you until it's satisfied you're broken and then works again... I'm sorry...

Yes, 254 is my router. DHCP lease time iss hard coded to 24 hours on my router. I gave it a reboot this morning but the IP addresses are still the same. I can confirm the MAC addresses for each lease are identical as I've copied the MAC address out of Proxmox's hardware interface and pasted...

Referencing one of my Windows VMs: PS C:\Users\Administrator> ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : WIN-82DL8BGMTLV Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS...

More frustrating, it says the DHCP address is rightly my router. In this example the VM should be 192.168.0.6, but it's being assigned .11 instead from.... Somewhere. There is only one page on my router to assign static IP addresses, and none are assigned 11. The virtual card's MAC address...

Correct on the IPs. If I shut down a VM and start up a new one it maintains its IP. Like the MAC addresses have been auto assigned an IP, and then their IP is recorded in a database somewhere so it'll always have the same IP when it reboots. This is why I'm asking about Proxmox having a...

The VMs all get lower end IPs in no particular order: .16, .21, .7, and so on (again, all under the correct subnet) None of the migrated VMs would. My only other VM which would have that functionality maybe mistakenly enabled is TrueNAS, but I've confirmed it is not enabled. There is a...

Correct, though the old host is running CentOS and not Proxmox (yet). Each host as well has multiple VMs getting IPs for the network. It's just that the new Proxmox server is making VMs which make up their own IPs. More info on that: The network connection picks up on all the correct info...

Hardware: Homelab rack mounted server (Proxmox) (new) Homelab workstation (CentOS 8) (old) Netgear 8 port router (consumer) Various PCs All connectivity goes through the router, itself connected to a cable modem in bridge mode. To my knowledge, only the router is a DHCP server. Proxmox was...

Morning folks. I'm having a persistent problem with my VMs on Proxmox. For some reason, no matter how I set up static routes in my router, the VMs I make in Proxmox all seem to take whatever IP address they please. This is problematic as I'm migrating VMs from one computer to another and...