TimV Posted November 13, 2022 Share Posted November 13, 2022 I had a VM (Windows 10) I could connect to via RDP with no problems and when I upgraded my motherboard, I'm no longer able to do so. After reconfiguring the VM to start, I can only connect thru VNC. The VM still has network and internet access. but has a strange IP address. Instead of having a 192.168.0.x IP, it has a 192.168.122.x address. If I try to use that IP address, it will not connect to RDP. When I view RDP settings in the VM, they are are unchanged from before. It says I should be able to connect by its name (Proteus). Any suggestions as to why this is no longer working? I went into device mangler and updated the network drivers, no dice. I can mount devices that host on my unraid server, but am unable to mount any non-unraid network storage to the VM. Any suggestions? Quote Link to comment
Solution ghost82 Posted November 13, 2022 Solution Share Posted November 13, 2022 You are probably using virbr0 network looking at your ip. Just change network from virbr0 to bridged br0. Quote Link to comment
TimV Posted November 14, 2022 Author Share Posted November 14, 2022 That was the problem. I saw it earlier when I was fiddling with my settings, but wasn't sure. It works like a champ now. THanks. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.