
Originally Posted by
jackpenn
Hi Guys
I Have what I think might be be hopefully a minor issue. I'm running a 131 and 136 in virtualbox with an MX linux host. 16gb ram, i7 cpu 2.7ghz,
4gb nvidia. Not ideal I know running client on the same machine but it's what I got and it runs ok.
I am using a PC with very similar specs to set up the servers before moving them to my VM host, so it should be good.
Forgot to mention that I am using a bridged network in vbox.
This is the correct way.
Everything is cool for a few weeks then I get a changed IP from my ISP. So got that fixed up, server running again and website up, but when I launched the client it seems to be not finding the server. I made sure I had the address right in server.txt. I also tested the 136 client with the same result. The last thing I tried was a clean install of a new client. Same result. Am hoping one of you guys can cast some light on what's going on.
Normally you're supposed to use your internal IP addresses which don't change if your ISP changes anything - you have a local network and the IP addresses start with 10. or 192. or 172. (it's more specific but in 99% cases it's enough), are you saying you are using the public IP address (such as the one you see on whatsmyip.org)?
Why am I not using the client in Windows? Because I'm tired of all the constant issues with windows 10. The latest issue I had was no matter what I tried I could not create a working network with vbox so I finally threw the towel in and went back to linux. Shame really because when it is running in windows it's ok.
I'm quite sure 343 will be very much on your side here, although I have done setup with vbox on Win10 without issues with the bridged option. I have had some weirdness when I first picked NAT and then changed it to bridged, it doesn't seem to like that very much - you have to use bridged from get go. Or at least try redoing your setup from scratch and see it works. But you should in any case use internal IP adresses.
Pete