Login timed out – running on virtual machine
Posted: Wed Mar 11, 2020 5:59 am
Hi,
I am running RoR through a virtual machine (Parallels) running Windows on my Mac laptop. I have been able to play with my roommate on the same network yesterday and most of today. Now, while he is able to log in and play, my log in consistently gets stuck and returns "login timed out" when selecting the server within the RoR client. Researching in the forums I tried the following:
-Downloading VPN
-Deleting these files: patchui.dll, patchui_win.dll, UserSettings, UserSettings.xml.Legacy1
-Unchecking read only
-Following the sticky as closely as I could
-Disabling firewall on Windows and Mac
-Restarting Mac, Parallels, and Windows
-Reconnecting internet via laptop and router
-Waiting some time (a few hours) and watching my roommate play for a while
-deleting my launcher and running RoRUpdater
Please help. I will bet on myself making a few mistakes here and there on any of these listed workarounds. Open to suggestions.
Thanks,
-g
**UPDATE. I guess the launcher fix did not work the second time around. Still looking for a solution to this.
I am running RoR through a virtual machine (Parallels) running Windows on my Mac laptop. I have been able to play with my roommate on the same network yesterday and most of today. Now, while he is able to log in and play, my log in consistently gets stuck and returns "login timed out" when selecting the server within the RoR client. Researching in the forums I tried the following:
-Downloading VPN
-Deleting these files: patchui.dll, patchui_win.dll, UserSettings, UserSettings.xml.Legacy1
-Unchecking read only
-Following the sticky as closely as I could
-Disabling firewall on Windows and Mac
-Restarting Mac, Parallels, and Windows
-Reconnecting internet via laptop and router
-Waiting some time (a few hours) and watching my roommate play for a while
-deleting my launcher and running RoRUpdater
Please help. I will bet on myself making a few mistakes here and there on any of these listed workarounds. Open to suggestions.
Thanks,
-g
**UPDATE. I guess the launcher fix did not work the second time around. Still looking for a solution to this.