Issues with a clean Windows10 VM Setup

[roguedeus]

SUCCESS...

Straight out of the box, clean Win10 Pro (64), VirtualBox VM, with a bridged network adapter.

Everything unpacks fine.

Setup/Verified the eqemu_config.json and login.json files.

I can startup the server, see it's waiting for a client.

In the VM, I can access the internet fine, and I can ping my host PC's public IP (but not it's local one).

On the PC, I can not ping the VM's reported local IP (using ipconfig in VM), but I can ping it's bridged adapter.

I allowed all relevant Firewall settings during all installs. And even disabled both PC and VM Firewalls to see if it mattered. (It didn't)

eqhost.txt is updated with the same IP the loginserver is assigned. (port 5999 for RoF2)

eqgame.exe has a shortcut with the patchme addendum.

Besides the IP issue, it's all up to snuff.

...

At the moment, I am unable to even login. It tells me "A connection to the server could not be reached."

I've scoured what little there is related to this issue, and most seem to assume it's a eqhost.txt issue. However, if it is, it's not due to incorrect format.

[LoginServer]
Host=192.168.56.1:5999

Having said all that. Has anyone had similar issues and resolved them?

Any guesses? Possible VM setup incorrectly?

Anything might help, so please... I am on the verge of walking away from this.



Edit: So that you don't think I'm wasting your time. I have searched for any posts even remotely recent, regarding this, and some rather old ones. None suggest this is anything other than an incorrect eqhost.txt setup.

Perhaps I am using the wrong IP...
-- The ipconfig output from inside the VM shows a local IP (192.168.0.185), due to the bridge.
-- The ipconfig output from the host PC shows both its local IP (192.168.0.189) and the VM adapter (192.168.56.1)

The host PC, can't ping the VM's local IP, but can ping the adapter.
The VM, can't ping the host PC's local IP, but can ping it's internet IP.

Would the router be causing this?



Edit 2: Seems it was Windows interfering.

Solution was the go into Allow an app or feature through Windows Firewall, and enable File and Printer Sharing.

I can now log in and see the server listing.

However, something else seems to be preventing me from actually entering the server.

Will report when/if I find a solution.



Edit 3: Resolved...

The fix is to delete the redundant login servers... Only left "loginserver1" assigned to the VM's Local IP.

Dunno if it mattered, but I also added the "address" line some suggested.



SERVER IS UP AND CHARACTERS MADE...