Here we go again

I am playing two characters on Teek.
I went to log on my second character on my laptop but got a message that my request was denied as the world only allows a certain mumber of accounts.
I looged out and logged the same character on my desktop, no problem. I restarted the laptop, and started the game, but same error message.
This is a server side problem, last truebox server I played on had the same problem. I brought the laptop to a repair place and had it reset to factory specs. I loaded only Firefox and Everquest, but no joy, I removed everquest and reloaded it, still nothing.
It's looking more and more as if I'll be buying F1 23.

True Box: 
This server starts with True Box enabled. You may have only 1 client per computer logged into the server at the same time. 
When Omens of War unlocks, the server switches to Relaxed True Box. You may have up to 3 clients per computer logged into the server at the same time. 
When The Buried Sea unlocks, True Box will be removed.

https://www.everquest.com/news/eq-teek-and-tormax-are-live

Yes I only had one client logged into my laptop.

Have you thought about redownloading game client on the laptop? Sounds like there might be some corruption, I would also keep zero files not even configs.

Alternative copy it over from your desktop but have it in a completely new folder and make sure the shortcut launching it executes and works from the new directory. Though I recommend a new client.

OH also assume they each have their own account? Each account can also only have 1 active character logged into, to any server it matters not.

Change the password to ensure it is secure as well.

It's not client side. I reformatted the laptop and loaded only firefox and everquest, the problem persisted.

With two accounts, I would be able to play on your desktop and laptop.

Not sure if this is what's causing it, but just in case - if you use the feature to kick an account off of one PC from the other PC that tends to confuse the servers about which accounts are logged in where and has caused this issue for me in the past. If you fully log off on the computer that's running an account before loading that account on another PC it gets around this.