MArcomage

Free multiplayer on-line fantasy card game

Please log in

Glizorkulblorkul on 21:00, 8. Jan, 2012
Over the last week or so I've been having serious problems connecting to Arcomage.net. I know the site hasn't been down because I'm able to play from work, but at home I cannot connect to arcomage.net unless I restart my browser. This doesn't happen with any other websites, but I think it has to do with some of my browser settings that I recently changed. The problem is, I don't know which setting to reconfigure. Does anyone have any ideas or suggesstions?
DPsycho on 21:05, 8. Jan, 2012
Which browser and what version?
Mojko on 21:13, 8. Jan, 2012
And what error exactly does it produce?
Glizorkulblorkul on 00:56, 9. Jan, 2012
I am using chrome but the error replicates on firefox. If I restart firefox, it starts working on both browsers. The error I get is a standard 'page not found'.
Mojko on 06:53, 9. Jan, 2012
Please provide us with browser version, so I can test it properly.
Glizorkulblorkul on 05:53, 10. Jan, 2012
Chrome 16.0.912.75
Firefox 8.0.1

It says DNS something or other. My brother has an account on this cpu as well. He uses ff, i use chrome. When i get the error in chrome, closing firefox and reopening firefox and then putting the http://arcomage.net into firefox will make arcomage.net work for both browsers. very strange bug. I have to implement this fix several times a day in order to play.
Mojko on 06:35, 10. Jan, 2012
Strange... However, if it's DNS related it shouldn't be a browser issue. Is MArcomage the only site where this happens?
Glizorkulblorkul on 07:52, 10. Jan, 2012
Yes, this is the only site that this error happens on. I've played thousands of games error free but this bug has been happening for the past week.
Glizorkulblorkul on 07:21, 11. Jan, 2012
Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's DNS address.

This webpage is not available
The server at arcomage.net can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.
Here are some suggestions:
Reload this webpage later.
Check your Internet connection. Restart any router, modem, or other network devices you may be using.
Check your DNS settings. Contact your network administrator if you're not sure what this means.
Try disabling network prediction by following these steps: Go to the wrench menu > Options > Under the Hood and deselect "Predict network actions to improve page load performance." If this does not resolve the issue, we recommend selecting this option again for improved performance.
Add Google Chrome as a permitted program in your firewall's or antivirus software's settings. If it is already a permitted program, try deleting it from the list of permitted programs and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the wrench menu > Options > Under the Hood > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Mojko on 07:29, 11. Jan, 2012
Yeah, after running some test and searching for documentation on the error, I came to same conclusion. The error is most likely on your side, because DNS error means that you couldn't even reach our server, so the error is probably not on our side. I recommend to follow those instructions and hopefully it will resolve the error.
theultramage on 09:02, 11. Jan, 2012
It might be that your ISP's (or ours) dns servers are acting up - sometimes my ISP's servers just went down for an entire day and I had to temporarily switch to some other service (like google's 8.8.8.8) to be able to do anything.

You can run cmd.exe, run 'nslookup.exe', and start typing in some domain names you want to test. You can also type 'server ns1.krabica.net' to start asking our dns server directly. If the requests start failing then that should indicate something's wrong.

PS: When you say "until you restart the browser", that means it suddenly starts working after you do that. How long does it then take for it to break again?
Glizorkulblorkul on 18:45, 12. Jan, 2012
As I said, if it was an issue with my internet connection then it would affect all websites equally, it only errors on this website. All other pages work fine. It gives me the error about 5 times a day. Each time I have to restart firefox and load arcomage in firefox to get it to work in Chrome.
Glizorkulblorkul on 18:48, 12. Jan, 2012
Once its fixed, it lasts about an hour or more before I need to apply the fix again
DPsycho on 19:35, 12. Jan, 2012
Glizorkulblorkul wrote:
As I said, if it was an issue with my internet connection then it would affect all websites equally
That's not actually true. If you're experiencing an issue with the path your ISP takes to bring you the site (by which I mean physical lines and connections), then you would definitely experience the issue with this site and perhaps others that are physically located near its servers by extreme coincidence, and yet the rest of your web browsing would be entirely unaffected.
Glizorkulblorkul on 00:51, 18. Jan, 2012
Yeah, its probably a problem on my side, it's just very frustrating to have to reload both browsers essentially every 90 minutes or so. I'm just baffled by this one
theultramage on 14:51, 24. Jan, 2012
As an experiment, could you switch your system's DNS server to 8.8.8.8 (google)? (just so we can get that test out of the way)
Glizorkulblorkul on 10:52, 3. Feb, 2012
I disabled chrome from clearing all my data after each session and that seemingly fixed it
Glizorkulblorkul on 07:18, 18. Feb, 2012
Well after 2 weeks of uninterrupted play this error has resurfaced and essentially makes me reload a browser and, wait 60 seconds, and relog into arcomage every hour. Something with chrome,..
Mojko on 08:46, 18. Feb, 2012
You should check your browser settings. To be able to play without the need to log in every time, you have to keep the cookies (they must not be cleared). You should check for cookie related setting.
dimitris on 21:42, 18. Feb, 2012
It's most probably a firewall thing, or maybe an OS issue.
If you're using Windows 7 or Vista check point 1 at this page.

Oh and also you can't be logged in with multiple browsers and same user at the same time. I believe that's because only one live session per user is allowed.