Dude, lol, i used this in the first place. stop advertising it, please.

Idk what is wrong.

It has been sorted, yes.

Have you tried following this: http://ragrappy99.picturepush.com/showformat.php?image=5455015

Has this been fixed then, i still have the problem of every one of the servers ive tried to set up being misconfigured ... :3

Ive spent ages on this already and the port is definitely open, as confirmed by several different tests etc...

Egad. Well this explains it.

Just release a small v0.49.1 fix. So you don't use up the famous v0.50-number. ;)
And you could also think of getting yourself an auto-update module. There really are tons of open-source updaters. It shouldn't be too hard to integrate one to AoS.
I mean basically it's just checking one versionnumber, then hashsumming all files and comparing them against the server-stored hashsums. Then downloading and replacing those files. Since there are no services and no registering dll's and stuff it won't be too complicated to just replace a new "client.exe" for example.

mat, have you not read what i just said? hell i even used DMZPLUS mode, still nothing, im sure cuz i run minecraft and vent servers, so its a problem on THEIR side, not mine.

9/11 conspiracy

let's not forget:

http://ace-spades.com/forums/topic.php?id=769

http://ace-spades.com/forums/topic.php?id=911

Razor: If the server doesn't show up on the master server list, it's probably due to closed ports still ;)

This is again a serous problem.
As I tested this: I had all my ports forwarded, all firewalls and possible protection down, almost every service not required to connect to the INTERNET and run a server down, even windows explorer, the server does simply not show up on the list, i go to my friends house to host it, and it works fine, come back to my house, try every computer i have, no work.

Seroiusly, i LOVE hosting servers but your killin' mah thunder ben.

Bump

Um, sorry, but are you going to leave 50% of the servers unusable until the next update?

Ben, this problem has been ignored long enough. it should be your topmost priority and a fix should be released immediately. it has caused too much frustration for too many people. besides, the players are being denied half if not more the number of playable servers.

Thanks, I just implemented a fix but it's on the client. Server-side hotfixes are easy but a new client would need a totally new release and I'd like to do more tweaking and testing before that.

Made a server named Fix AOSserverIdentifierSeeforum

edit: Lol, someone else did too?

I would say this is very easy to fix, so it should be fixed ASAP (either on the master server or on the client).

Bump enough? ;)

Yeah, I'd like to have my server up and running again sometime.

Bump.

Ben, in case you're reading this: change "DWORD" or "uint32" to "int".

EDIT: someone bump

yes, please fix this because this is why so many servers with correctly opened ports don't work! all of my servers are configured exactly the same, the only difference being their IP ranges, yet only some work!

once again mat pulls through.

bump for much-needed immediate fix!

I was wondering what the fuck was happening.

Home of Lexsym's serverbot is down until it finds a new home, or this is fixed.

+2

Converting to little-endian and then to decimal is stupid anyway, I'd just use hexadecimal or 4 decimals. I can't find a reason for this.

Sounds pretty bad, bump for a good cause.

+1

Hi Ben. I already sent you an email in regards to this, but in case you ignored it (like it seems you did to a lot of my other mails) or don't check your mail, here's the bug report again.

I'm currently running a server called "pyspades WIP test", and the "Play" site gives the commandline aos://2252985183 - it's located at ledev.org (95.211.73.134).
For some reason, the master server happily connects to it, and it appears on the main site. However, when you click on the server on the site, it doesn't work,
and gives "misconfigured". I've debugged this, and it seems to give WSAEADDRNOTAVAIL on WSASendTo. The packet never leaves the client either (Wireshark says so),
so there's definitely something wrong with your client. I also made a local relay server on localhost that relays packets to ledev.org, and that works perfectly.

The bug is caused by your code - it uses a signed int on the client when making the server IP instead of an unsigned one, which is why the command-line "client.exe "aos://-2041982113"" works (it's just the server IP in a signed int-form).

What this means is that HALF the IP-range CANNOT make servers (which I am coincidentally a part of).

Fix this, Ben.