Yeah, you did this via the VMWare autoinstall thing. I still really suggest throwing it out and doing it via Ubuntu Desktop for Orca etc. though, and also doing it manually. I know you can get orca by installing a bunch of stuff through apt instead, but I don't know what. The version of the installer that comes with Desktop is accessible.
You need a screen reader in the vm to edit config files, both for when things go wrong and potentially for initial setup. I don't understand why I have to point out that trying to read highly technical information that needs to be accurate character for character through OCR isn't ever going to work, but apparently I have to.
I always forget how to check/edit hostname on Linux without just Googling it, but if you can work out the hostname of the vm, then Windows may already be able to see it if you ssh myuser@hostname. I have that working here, but I don't remember if I did anything special to set it up. Windows 10 implemented mdns which I think is what does it.
Now, the next thing is VMWare networking configuration. You want to just leave that as NAT. If it's not working and you think it should, then open an admin command prompt on the Windows side and do:
net stop vmnetbridge
net start vmnetbridge
Which can sometimes magically fix it. Yet another reason to have Orca on the vm is so that you can find out whether the mvm can reach the internet, because "the vm can reach the internet but Windows can't talk to it" and "the vm can't reach the internet" are very different problems with very different solutions.
If that's not good enough to get you access, you can put VMWare in whatever they call their network configuration that gives the VM a MAC address and direct access to your router (bridged, I think). Then you can go play with dhcp settings in the router and get it a fixed IP. There's a couple other ways to do that as well, but I don't remember them. Be aware that screwing up the router's dhcp settings will take the entire network offline. You'll have to reset the router to factory defaults and reconfigure from scratch. There's ways to fix it that don't require doing that, but they're probably beyond you and they're potentially router specific. "I screwed up my DHCP settings" is beyond my level of networking troubleshooting knowledge.
If all of this is confusing, you can go get Docker for Windows and read a Docker tutorial and every single step of the process will be 100% accessible. Only real difficulty with Docker is that content gets erased when the container stops by default, which most people just fix by embedding their content in the container at least at the newbie level. If you can write a bash script to do what you want, docker will work nicely for you as a learning platform and it also looks very good on a resume anyway.
My BlogTwitter: @ajhicks1992