Page 2 of 2
Re: I AM CRASHING A LOT
Posted: November 15th, 2017, 4:18 pm
by Made In Quebec
I don't know what people are complaining about...
I log on every two months for 8.4 seconds per accounts, and never, ever did I have any problem with disconnection.
I really think that people are exagerating the situation, as it really never occured to me...
Re: I AM CRASHING A LOT
Posted: November 16th, 2017, 1:49 am
by Bad Religion
Made In Quebec wrote:I don't know what people are complaining about...
I log on every two months for 8.4 seconds per accounts, and never, ever did I have any problem with disconnection.
I really think that people are exagerating the situation, as it really never occured to me...
People were getting multiple trinkets at h town with actual playtime even less than that.
Re: I AM CRASHING A LOT
Posted: November 17th, 2017, 1:49 am
by The Silvertiger
:O
Re: I AM CRASHING A LOT
Posted: November 17th, 2017, 7:00 am
by Lady
U r going out of topic! And yes, some ppl do d/c, when they have 10+ ppl on screen (i guess is steam related error, cuz the inet is ok and the pc is ok as well, so its not a hardware or net problem )
Re: I AM CRASHING A LOT
Posted: November 22nd, 2017, 11:12 am
by The Silvertiger
http://www.uogamers.com/community/threa ... es.603492/
Ryan, post: 4319437, member: 1 wrote:There are no connectivity issues.
I've told [USER=144420]@Selene[/USER] during a lengthy chat, I want to actually do a shutdown on the Demise instance, change its instance type and bring it back up. This shard is running on Amazon, it's not like it's in some "junk datacenter" or in my basement. I've also sent [USER=153480]@Eos[/USER] an email and would like to get it fixed but havent heard back yet.
We're all busy, but this is not a connectivity issue. I don't believe it's even an instance issue. Demise and Hybrid (save a few small things) run the same core RunUO. They're in the same Amazon VPC, they're in the same network... this problem is not persisting on Hybrid. When these servers with both in Amazon's Ohio region we had similar issues on both shards with disconnects and the like.
I will try to talk to Eos and see if there's something we can do to nail this down but I can assure you, Demise is not having a network problem.
Re: I AM CRASHING A LOT
Posted: November 22nd, 2017, 11:37 am
by raptor-
no network issues but over 40 people affected hmmmm
Re: I AM CRASHING A LOT
Posted: November 22nd, 2017, 11:59 am
by The Silvertiger
raptor- wrote:no network issues but over 40 people affected hmmmm
I believe him. Not everything is black and white. I believe that there is a hardware/software issue. The network didn't change until weeks after the issue presented itself. Hybrid was running similar numbers during this period and the issue either doesn't present itself or has minimal effect.
Re: I AM CRASHING A LOT
Posted: November 22nd, 2017, 12:49 pm
by Made In Quebec
raptor- wrote:no network issues but over 40 people affected hmmmm
Disconnection could be caused by your cat chewing on your internet wire connecting you to your modem.
Does that cause a net work issue? No, it's a material issue.
It's absolutely possible, to have disconnection issues, without it being caused by the network itself.
Re: I AM CRASHING A LOT
Posted: December 5th, 2017, 8:22 am
by Arden
bump
-Basic client
-West Coast
-Never had issues before
Tonight:
-DC every 2-5mins tonight
Re: I AM CRASHING A LOT
Posted: December 5th, 2017, 8:25 am
by april0395
Arden wrote:bump - Basic client - never had issues before dc every 2-5mins all night tonight.
My BF and I were consistently losing connection at the same times as Arden. I haven't experienced anything like it before. Every 2-5 minutes disconnecting, unable to log back in for up to 5 mins. It happened 10 times or so.
Sorry for the
Re: I AM CRASHING A LOT
Posted: December 5th, 2017, 3:42 pm
by VashGFO
I would suggest doing a trace route command, and seeing if you're local ISP is having issues resolving the IP address of the server. It's possible that sometimes core routers on the ISP have issues which means you have issues connecting to services because they have to take extra long routes across the country. To run a trace route open a dos command prompt and type tracert and the IP address of 34.234.30.69 (demise AWS IP) and paste the results. This is going to include latency times as well and will help figure out if there is a network latency issue as well.