General > News

BeBot v0.6.6 released - The not so scary halloween edition

<< < (2/2)

Khalem:
I am unable to reproduce this and i can connect just fine.

Keep in mind that aoc-eu-um.live.ageofconan.com is a DNS round robin which in addition serves different views depending on where you are located, so it could be a case of a UM server being down, or your servers nameserver DNS caches being outdated.

I know Funcom have fairly strict firewall rules going as well which could be triggered by excessive connection attempts. But I am not certain if that happening would result in reject packages being sent (the sane thing from a DoS perspective would be not to)

In any case i can assure you this is beyond our control and is not influenced in any way by BeBot. It is attempting to connect to the IP it is given by your server when it asks for aoc-eu-um.live.ageofconan.com to be looked up on the correct port which is 7000.

WeZoN:
will test out the bot on my local machine to check..

WeZoN:
Ok. As i need to set up the database server and so on i will not check it here..

As everyone else seems to run the bot with no problems i must be a block.

Either Funcom or the company hosting my server.

Khalem:
If you server host allows remote database connections, there is nothing to stop you from running the bot from your local machine connected to the server host database just for testing purposes.

I would also check if the DNS entries are being resolved properly on your server.
For example you can use http://www.kloth.net/services/dig.php and enter the nameserver your server host provides, provided it allows remote queries from outside the facility or most likely the dig tool itself will be installed on the server.

WeZoN:
it's tested and the aoc connection on my server is indeed blocked...

Most likely by the company that hosts it. As the bot has spammed the login to aoc after the login changes made by funcom.

Navigation

[0] Message Index

[*] Previous page