Unable to setup local server (POL-0033)

[JeremiahFaust]

Been trying to setup LSB for the last few weeks as time permits but have been unable to get it to work. I have gotten as far as getting xiloader to launch, it successfully connects to my instance of LSB but after I hit accept on the PlayOnline MMO "Rules of Conduct" dialog, it takes me to a error POL-0033.

The Details of my setup:
DualBoot EndeavorOS (Arch Linux based)/Windows11
128Gb Ram
2 Tb nVME storage per OS
Intel i9-13900k (I know, should have gone AMD)
Nvidia RTX 4090

there should be no issues with the specs of my build, and everything I will detail below as my troubleshooting steps I attempted on both EndeavourOS and Windows 11, as well as a Windows 10 VM. I have also tried to get this to work on an ancient Lenovo laptop with integrated intel gpu, 16 Gb Ram and Running EndeavourOS... same results. I even tried a Raspberri Pi 5 8 Gb although I couldnt even get it to compile and didnt want to waste time figuring that out since i don't have plans to run my server off on an ARM CPU in the long run anyway.

Initially, I tried something custom thinking the configurations looked simple enough so I tried Docker, even built out a new dockerfile, and Docker-compose based off of what I learned from the sample provided in the wiki, this obviously didnt work.

When my attempt to get a docker container failed, I decided to try a bare metal install of the server, from here, I decided to follow the instructions from the Wiki to the letter, only changes I made were in the Sql_Port, I changed from 3306 to 9306 This shouldnt be an issue since I can confirm that xiloader was able to create the account without issue when i queried the [accounts] table. I will note that even my Docker install was able to get this far.

I did not want to deviate at all from the docs as I just wanted to see a working install, and could modify things after that. So I left the SqlLogin, SqlPassword and SqlDatabase configs as is. zoneip in the zone_settings table is set to 127.0.0.1 for all zones, although I have also tried setting it to the machines local IP and 0.0.0.0

When this failed to get me connected, still getting the POL-0033 error, I figured xiloader must be using the wrong ports, and me not knowing what a correct ports to pass into xiloader would be I wrote a very simple C# program that took every single port in the network.lua config and printed out a command I could just paste into a terminal/powershell window to test... I did this for every single possible port configuration which... was a lot... of the ones that actually got me into the PlayOnline Viewer, I was always blocked by that pesky POL-0033 error...

so at this point I am at a loss with no idea what else I could possibly do other than to reach out for assistance (btw I did try searching for help on POL-0033 error but everything I found online were very unhelpful with stuff saying its very rare, or just reboot and it should go away...).

I tried the release version of xiloader as well as self-compiled.

I am attaching a copy of my network.lua file (had to change the file extension to .txt because github wouldn't accept .lua), I also wiped my logs, ran a single test with this network.lua so that the logs I am attaching should be trimmed down to just a single attempt. I also enabled TCP and UDP debugging and sql logging in the logging.lua, so the map logs are actually kinda long, but I always waited for it to say: "The map-server is ready to work!" before I ran any tests.

also note, in the connect-server logs, the "async_read_some error in from IP {}:" showed up after I hit confirm on the POL-0033, so the error I am encountering is occurring first.

connect-server - Copy.log
map-server - Copy.log
search-server - Copy.log
world-server - Copy.log
network.txt

[zach2good]

Hi there,

If you can avoid it, try and run everything while changing NO settings. We run the default settings in GitHub's Windows and Ubuntu cloud machines multiple times a night and they all work all the time, so your issues will be through deviation from the regular settings before you have things working, or through your general network layout.

From your logs:

[12/07/24 16:14:33:415][map][warn] You are running as the root superuser or admin. (usercheck:207)
[12/07/24 16:14:33:415][map][warn] It is unnecessary and unsafe to run with root privileges. (usercheck:208)

To my knowledge POL-0033 is a generic network error. The old Nasomi forums list this as a fix: https://web.archive.org/web/20191009050410/http://nasomi.com/wiki/index.php?title=Config:troubleshooting

POL-0033

Restart your network adapter and try connecting again.
Go to your network connections and right click the one your using, and try "repair".
Try power cycling your modem, this can clear on connection issues as well.

[JeremiahFaust]

Appreciate the quick response!

the running as root was a more recent attempt on my part, and I was getting this issue prior.

I am using an older HP 10Gb Ethernet card I bought aftermarket, I also use the the built in 2.5Gb Ethernet on the motherboard as a failover , I can see how that could cause some issues with the network.

I will unplug the 10Gb card, and trying the repair. Will see if that resolves things before resetting the modem as I don't want to kill the internet for everyone in the house before I can warn them.

[nacky-tiger]

hi there
zoneip does not edit the database directly.

Execute the following
cd server/tools

$python3 dbtool.py
Select “t. Maintenance Tasks” and change “2,Set zone IP addresses”. Set the IP address of the server you want to make public.

Perhaps a firewall is getting in the way
Turn off all Firewalls on the server side and the client side.
If OK, restart the Firewall and leave only the necessary ports open.

[JeremiahFaust]

I tried disabling the firewall... that didnt help.
I disconnected my 10Gb NIC and it also didnt help.

Currently setting up a clean install of Windows 11 on an old machine that has no extra NICs and will set it up to run both server and client.

really cool to know that the dbtool.py can set the zoneip, I was worried I might be setting that incorrectly, I will need to dig through the options in that tool more closely, so far I only used it to initialize the DB.

[nacky-tiger]

I hope it works out for you.I built my server on ubuntu. I had no trouble with the procedure other than ”zoneip".

[JeremiahFaust]

Alright, with a complete clean format of Windows 11 on an old PC with only 1 NIC, I was able to get it running, I also at the same time setup the server on an Ubuntu 24.04 server that is also an old PC I have that only has 1 nic.

after I confirmed it worked completely local on 1 machine I tried to connect to the instance hosted on Ubuntu from the new Windows 11 machine and that also worked, at least up to character creation, failed at actually loading into Windurst, but I believe that to be the zoneIp's that @nacky-tiger mentioned... so at this point I think I am able to get up and running.

Seems my past few weeks issues were simply a case of my unique development setup interfering with trying to setup this system.

I plan on keeping the server running on the Ubuntu instance, as for running the client... I can just rely on this old Windows 11 machine. Appreciate the help @zach2good for helping me break out of my tunnel vision.

[JeremiahFaust]

forgot to mention, I did setup the server previously on an old laptop that should mirror the successful Ubuntu setup... so it seems to me that it would be xiloader that was unhappy with my unique system setup, and not the server... since xiloader is what I was running from my dev machine with 2 nics.