AMIA ARCHIVE • View topic - Screwy Server (previously known as "Incoming downtime")

NWNcx, I think

I need some info to nail down what's the issue exactly. If you can't login, post

* the error,
* the time (best to do it in the format "1,5 hours before I posted this message", so I don't have to figure out your timezone) and
* if you managed to get in a few hours earlier or not.

If you can get in later you can best edit your older post and make addendums as the play unfolds.

O, and can somebody give me the ports nwn uses for multiplayer? It's somewhere on the internet, but I don't have the time for a search.

Once I got some info I will contact the hoster to see if they block anything.

O, and I am also interested to know if you CAN log in. Perhaps country is also a good thing to know in both cases.

Last edited by Raif on Thu, Oct 03 2013, 10:11 AM, edited 1 time in total.

servers both just crashed about 10 mins ago. cant log in
the error.. just says attempting to find server, connection to the server has failed, server is not responding (timed out)

dont know if that helps?

Australia gmt +10

Last edited by Dakotaen on Thu, Oct 03 2013, 12:32 PM, edited 1 time in total.

Yep, can't log in since around 15 minutes before this post. Servers don't show up in the History tab and Direct Connect doesn't work either.

EDIT: Oh right, Denmark here.

I haven't been able to connect to the server for about two hours now (although it might have had some uptime since the first "crash" today, it's gone now). Same situation as yesterday; "attempting to find server, connection to server failed, server is not responding (timed out)."

I'm in Australia, GMT +8.

can no one force a reboot?

server was due to auto reset but that has not worked.

Just up in the US here (EST)

Server's showing as up on the forums with 2 in on A, 1 in on B, but when I try to connect, I get the
Attempting to find server
Connection to Server has Failed
Server is not responding (Timed out)
error.

Also, Disco: This it?
Application: NWN Port range: 5120 - 5129 Protocol: TCP/UDP

Application: NWN1 External port: 6667 Internal port: 6667 Protocol: TCP/UDP

That is odd, I noticed yesterday Amia A and B were 0/65 all day. But at night when I got home from work it all worked just fine.

bobofwestoregonusa wrote:

That is odd, I noticed yesterday Amia A and B were 0/65 all day. But at night when I got home from work it all worked just fine.

Yeah, it was down most of yesterday. Much time was spent console gaming. >.>

People seem to be timing out when trying to connect via Direct Connect. Check your history tab. I'm in game right now with one other person, but I understand a heap of people are trying to get in and cannot due to timeouts. I was able to get in through the history tab, but not able to get in through direct connect, etc.

... It's greyed out in my history tab, though thanks for the tip, anyways.

Eastern Australia, by the way, for location.

I just logged in at 18:55 GMT +5. Everything seems fine.

So very Random this.

I tried to log in just now and can't
History tab is greyed and direct connection shows connection time out.

UK

It appears most of the connection issues are happening morning through mid-day EST times.

Person I'm playing with currently is from US, south east. They added Amia to favourites, then used that method to log in.

On the west end of Australia and the server is appearing offline still!

South Central Australia, getting Timed out and failing to connect and have been for around 3ish hours!

how are you doing this favourites thing?

since reinstalling the game the server list pane is blank, history blank, well everything is blankety blank!

One of the .ini files contains the information used in History/Favourites. Just a matter of finding where it goes, and slotting in the server's IP. For those people who time out, try and ping the server, see if you can get a response?

Raif wrote:

how are you doing this favourites thing?

since reinstalling the game the server list pane is blank, history blank, well everything is blankety blank!

That'd be because Gamespy stopped hosting NWN servers a year (or two?) ago. They still exist, but there's no longer a server list in the core game; you need mods to connect to an alternative server list, or use the list here.

Gobbledygook wrote:

One of the .ini files contains the information used in History/Favourites. Just a matter of finding where it goes, and slotting in the server's IP. For those people who time out, try and ping the server, see if you can get a response?

Favourites are stored in nwnplayer.ini, under [Favorites Page] as Server0=/1=/2=/etc. Unfortunately, while I can add the Amia IPs to the list, they remain greyed out in the in-game favourites list and direct connect still doesn't work.

How do you ping the server, exactly? The most I know about Neverwinter Night's server browser is that opening and closing the direct connect option makes the list refresh.

Last edited by Hudson on Thu, Oct 03 2013, 15:03 PM, edited 1 time in total.

P Three wrote:

Server's showing as up on the forums with 2 in on A, 1 in on B, but when I try to connect, I get the
Attempting to find server
Connection to Server has Failed
Server is not responding (Timed out)
error.

Same for me a moment ago in Holland.

Direct connect doesnt work. Amia is greyed out in the history tab.

Cannot get in via Direct Connect.

However, I can log in using either the History or the Favorites tabs in Gamespy.

Southeast US here.

I can connect through both Favorites & History tabs, as per usual.

Northern Europe.

Can't get in through Favourites/History, or Direct Connect.

Nothern Europe as well.

History and favorites are greyed out, direct connect is times out.

Central Europe

Any chance this is a problem with NWN itself and not Amia? It is a 12 year old game though I suspect that isn't the issue since you have to host the server anyway. NWN just allows you to connect to them via all being the same game, but is there any more reliance on Bioware hosting the game itself?

*caveman questions*

It's strange that some people can connect via the history and favourites tabs, yet others can't.

Assuming it's a playerside difference, do you guys have some mod for improved multiplayer connectivity? Like say, the mod which adds a working server list and removes the wait on connecting to the (now dead) Gamespy servers?

Can't get in via Direct Connect or History/Favorite tabs, as of moments ago and the past hour.

Northeast US.

bobofwestoregonusa wrote:

Any chance this is a problem with NWN itself and not Amia? It is a 12 year old game though I suspect that isn't the issue since you have to host the server anyway. NWN just allows you to connect to them via all being the same game, but is there any more reliance on Bioware hosting the game itself?

*caveman questions*

Its not. Other servers have no trouble. I am pretty sure its the server who may have a firewall too much or something.

Hi!

I have the same problem as the others. It's gone from my history tab and direct connect does not work(it times out).

The Silent Whisper wrote:

It's strange that some people can connect via the history and favourites tabs, yet others can't.

Assuming it's a playerside difference, do you guys have some mod for improved multiplayer connectivity? Like say, the mod which adds a working server list and removes the wait on connecting to the (now dead) Gamespy servers?

No idea. But if Disco wanted to ask me some specific questions about, uh, anything I might have related to my computer or system that might enable me to get in and not others, I could try to find out for him.

Well, I am clueless... we didn't change anything, and suddenly stuff goes bonkers in a random fashion. Sent a mail to the hoster, perhaps they're doing some maintenance.

Dev Disco wrote:

Well, I am clueless... we didn't change anything, and suddenly stuff goes bonkers in a random fashion. Sent a mail to the hoster, perhaps they're doing some maintenance.

that would make sence that its on their end, because both servers just crashed together, everyone disconnected because i noticed both servers where at 0/65 for a good few minutes

then 2 people managed to get in (assuming thats goobledygook and the other) then he posted about the history tabs and favourites, and since then several other have been successful that way.

A just went weird for me. I got disconnected, and now while the server appears in my history, it says No Module instead of AmiaA. B still works fine.

Yups, my mistake. Was doing some experiments.

Talking to two friends who live in the same town as me. One has the same ISP as I do and he can connect just fun. The other one has a different ISP and can connect T_T
Mine does not work however.

Poorsod wrote:

Can't get in through Favourites/History, or Direct Connect.

Nothern Europe as well.

Same

Well, I did the history trick as well. Now I see the servers in the server list and I can log in.

This is really weird... when I add these servers to my favourites I get these two ip addresses in my nwplayer.ini:

AmiaA: 185.29.203.8:5986
AmiaB: 185.29.203.8:12125

And Io and behold: these work with direct connections...

There's some pretty weird rerouting going on.

I'm not a whiz, but if it's of any relevance, I seem to have a wildly dynamic IP because my wireless connection doesn't like giving me the same address for too long. In other words, I have to reset it multiple times a day.

I'm one of the few who can connect to both servers just fine.

When I looked at the server details in the history list it gives me this.
AmiaA: 185.29.203.8:26936
AmiaB: 185.29.203.8:26109

The Amia Web Site shows the IP is 185.29.203.11
Why the change from 11 to 8?

Also: US here, can connect via History page.

As of this moment, still greyed out in history, and DC doesn't work.

Disco, the IPs you gave don't work either, for me.

(Eastern US)

SE USA here. No ping to 185.29.203.8, no connectivity on 5121 or 5986.

Copy of tracert to server, first hops omitted.

5 12 ms 13 ms 16 ms 67.111.23.82.ptr.us.xo.net [67.111.23.82]
6 * 39 ms 39 ms ash-bb4-link.telia.net [213.155.134.132]
7 105 ms 105 ms 106 ms ldn-bb2-link.telia.net [213.248.65.209]
8 166 ms 114 ms 113 ms adm-bb4-link.telia.net [213.155.136.79]
9 114 ms 113 ms 132 ms adm-b7-link.telia.net [213.155.133.35]
10 129 ms 166 ms 174 ms netrouting-ic-152752-adm-b7.c.telia.net [80.239.
193.134]
11 157 ms 130 ms 129 ms ar1.spk.nl.netrouting.net [178.239.63.34]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

From where I am on the internet, you guys are dark.

The website, at 185.29.203.11, is obviously still visible to me. Tracert to webserver shows:

5 12 ms 12 ms 13 ms 67.111.23.82.ptr.us.xo.net [67.111.23.82]
6 41 ms 40 ms 40 ms ash-bb4-link.telia.net [80.91.248.138]
7 107 ms 107 ms 106 ms ldn-bb2-link.telia.net [213.248.65.209]
8 116 ms 116 ms 141 ms adm-bb4-link.telia.net [213.155.136.83]
9 115 ms * 115 ms adm-b7-link.telia.net [80.91.246.43]
10 162 ms 138 ms 158 ms netrouting-ic-152752-adm-b7.c.telia.net [80.239.
193.134]
11 131 ms 131 ms 131 ms ar1.spk.nl.netrouting.net [178.239.63.34]
12 131 ms 131 ms 131 ms 185.29.203.11

Trace complete.

That is about as local a problem as I've ever seen. Firewall or router typos, or server thinking it's a firewall, are top culprits.

Just relaunched nwn client. When I looked at the server IP address again that time it gave a differnt set of numbers for AmiaA: 185.29.203.8:14339. Almost like it's picking and chossing random ports or something? I am not sure not a comp wiz.

A and B address in the top left corner of forum now read:

Server IP: 185.29.203.11:5121 (and 5122)

Address doesn't work though

I logged in just fine. Must mean I'm the safe and datable option.

Can't get in through Favorites/History, or Direct Connect.

Mid USA, CST

Just logged in I was direct connecting with those numbers Disco posted and all of the sudden both servers appeared in my history tab. Corrected itself?

Screwy Server (previously known as "Incoming downtime")

Who is online