Network works, as expected. VNC viewer from vmamdrivalinux apparently not installed or working.

My guess is same now. Windows 10 bug or something preventing these versions of Linux vnc from working. That is my best guess so far.

I have played with x11vnc between linux computers and use RDP to connect to Windows 10 versus tightvnc. Have you tried changing ports?

192.168.0.3:x where x as follows
0 = 5900
1 = 5901
2 = 5902

Origionally it failed to load from port 5900 or port 5901, as follows above. I am aware of that trick. Then, suddenly it started to work from port 1, so something changed. Unfortunately, we had a city wide brown out lasting for a second. But that was long enough to turn off both machines and every virtual machine. Now I got them all rebooted. It fails on both vmandrakelinux and vsuselinux on both ports 0 and 1.

I need them to either be on port 0, or 1, if it's on another it will not work for my setup properly. I have no idea what the differences were.

P.S. - Since I haven't always used Linux, sometimes I just need to pick a distribution and learn about it. Even if I use it longer than supported. Just so I can gain some real expertise that I can apply back to Linux in general and future versions of that distro.

With your virtual machines being a tad old the options may be different from current versions. A bit kludgy but vncserver --list would display your users vnc sessions which you could probe via ssh. You might be able to get the same info from running processes but would a bit complicated parsing that information.

With old distributions I would expect some sort of vncserver configuration script that includes username/port number. I assume vnc starts automatically upon boot. If neither port works that corresponds to your usernames then not sure what isn't working at the moment.

On both of these machines, vnc is started from boot. On vmandrakelinux it's a separate service. On vsuselinux I tweaked the startup files to add an equivalent of Windows autoexec.bat. Then I started vnc from there. On both it chooses ports automatically. The files I have been tweaking are when it's started on the wrong port. If they are tweaked it will reset them to port 0 if you do it right. Obviously that's not what is wrong now like usual. Do you know more about how they work under the hood? Are there any other configurations that might be corrupted? Meanwhile, I'll reset from the images again. Then I'll retry the ports. I might be able to do that tomorrow, but if not it'll need to wait til Wednesday if I can't do it remotely.

If I don't make progress soon I'll depreciate these servers. That would mean they are too old to run on my new windows and the new virtualbox. It was last working straight from the image on the old version of Windows 10. When it upgraded that's when it broke.

Well, I was just able to remotely restore the images. This time, on both machines, it made the vncserver work on port 1, which is okay for me. They work and now I'm happy. But I have no idea why they quit working and persisted over image installs.