August 4th, Login Issues

[cnynridr2]

I want to do a Tracert and know the cmd part but what do I put for Turbine? It isn't Turbine.com or DDO..com.

[moomooprincess]

But 100% of the time I will crash on an instance change within 40 minutes.

1. Go from House K to Market? "The connection to the server has been lost!"

2. Try to enter the Crystal Cove? "The connection to the server has been lost!"

3. Try to exit a COMPLETED quest? "The connection to the server has been lost!"

4. Try to enter House K Cannith Crafting Hall? "The connection to the server has been lost!"

5. Try to teleport from Smuggler's Rest to avoid instance change? "The connection to the server has been lost!"

6. Change instance in the market from Market 1 to Market 2? "The connection to the server has been lost!"

7. Try to enter the tavern in Smuggler's Rest? "The connection to the server has been lost!"


Is it consistent? No. But within 40 minutes I GUARANTEE it will happen to me.

This is probably the most frustrated I have been. Since I can get in but I never know when it will fail.

All last week I played fine. I had family obligations all day Saturday, so I could not play until after 6:30 PM when the problems began.

Right now, I am very negative over the entire situation. And no one knows what is going on.

[die]

now unable too put in a ticket I get a fail "saying u need a valid email? when in fact the email that is in the mms is vaild ive had it for 15 yrs or so now?

[Gchrisberry1]

For those that are following me on this; can you double check your dndclient log file and see if the IP address your failing on is 74.201.106.23 or something different. If different see if it goes to the same dead-end.

Thank you.

000000047.519: Connection failed (0x00000004:0x00CD0B73) to server 0, addr 74.201.106.23:9003

[Rakuda13]

Your way ahead of me. I can't even get to the portion of the launcher where you log in.

Im with you,stuck on initializing,couldnt log in all day yesterday,but finally could late last night,now this morning back to being stuck at initializing.

[moomooprincess]

I want to do a Tracert and know the cmd part but what do I put for Turbine? It isn't Turbine.com or DDO..com.

Use these addresses

74.201.102.41

74.201.102.19

74.201.102.7

74.201.102.43
74.201.102.42
74.201.102.11
74.201.102.13
74.201.102.14

example
tracert 74.201.102.43

[Zephyrelli]

OK just did a cove run on Argo and everything fine. As of this morning, had the 33% could not connect to patch server error. Did nothing special, only waited it out. Using Verizon DSL. Hope everyone elses luck changes soon.

[cnynridr2]

Microsoft Windows [Version 6.1.7601]

Tracing route to 74.201.102.43 over a maximum of 30 hops

1 1 ms <1 ms <1 ms home [192.168.1.254]
2 47 ms 22 ms 22 ms 99-153-252-2.lightspeed.irvnca.sbcglobal.net [99
.153.252.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 26 ms 31 ms 24 ms 12.83.38.145
7 25 ms 25 ms 24 ms 12.122.82.245
8 24 ms 25 ms 24 ms 192.205.35.162
9 95 ms 95 ms 114 ms 0.ge-3-1-0.XL3.BOS4.ALTER.NET [152.63.20.217]
10 95 ms 94 ms 95 ms 0.xe-8-0-0.GW15.BOS4.ALTER.NET [152.63.24.26]
11 95 ms 95 ms 94 ms internap-gw.customer.alter.net [152.179.134.214]

12 96 ms 96 ms 96 ms border1.te8-1-bbnet2.bsn003.pnap.net [63.251.128
.107]
13 94 ms 96 ms 95 ms turbine-7.border1.bsn003.pnap.net [64.95.76.202]

14 95 ms 96 ms 97 ms 74.201.102.154
15 95 ms 95 ms 95 ms 74.201.102.43

Trace complete.

Hope this helps. Interesting that I got timed out and alter.net

[Trillea]

I don't know if this helps but I was able to log in once, tried to teleport from the Cove to the Harbor, got disconnected and have not been able to reconnect. This is on my main Selee on the Thelanis server.

[PuppiesAndRainbows]

000000047.519: Connection failed (0x00000004:0x00CD0B73) to server 0, addr 74.201.106.23:9003

Connection failed (0x00000004:0x00CD0B73) to server 0, addr 74.201.106.60:9003

[Rafal]

If I have just one character stuck out of more then 10 on my primary account and about 10 on my other 5 accounts I would say it's not a network problem. Even if the error message says "server connection timed out".

It's a DDO problem on a Turbine side.

Mac client crash might be exactly the same as windows crash but just an error message is missing. And this error message is not actually helpful.

So another interesting thing.

I had problem to log my stucked character in House P. I logged once but was never able to move it. Then I logged my other toon and went to House P, logged off and now I am alive on my stuck toon and at least for now can move around.
I really can not see how it's a network issue....

[ComicRelief]

So another interesting thing.

I had problem to log my stucked character in House P. I logged once but was never able to move it. Then I logged my other toon and went to House P, logged off and now I am alive on my stuck toon and at least for now can move around.
I really can not see how it's a network issue....

Dude, when it comes to electronics, I could write a book about the things I've seen that should have been "impossible", and yet it happened. Trust me - it's possible.

{Not saying it "is", just that it's possible...}

[PNGameAcct]

I really can not see how it's a network issue....

Same here - but assuming it IS somehow ISP related, it would seem to be TURBINE'S ISP that's having the issue, and not the hundreds or thousands of ISPs scattered across the US and around the world.

[BOgre]

So another interesting thing.

I had problem to log my stucked character in House P. I logged once but was never able to move it. Then I logged my other toon and went to House P, logged off and now I am alive on my stuck toon and at least for now can move around.
I really can not see how it's a network issue....

I'm not sure EXACtly how it's a 'net issue, but I do recall back when we were having some dev discussion about the crashing on zone in to Sands, that there was talk about how some network re-routing was taking place and if a timeout occurred at that time, it could cause a disconnect. So yeah, DC on changing zones could be 'net related.

[BOgre]

Same here - but assuming it IS somehow ISP related, it would seem to be TURBINE'S ISP that's having the issue, and not the hundreds or thousands of ISPs scattered across the US and around the world.

Well, again, when we were discussing where to put the blame regarding lag issues, we were able to point squarely at turbine's PNAP (if I remember right). So not an in-house Turbine problem, but still a turbine problem... Now if this current thing is being caused by Comcast or some other backbone-type issue, then no, not directly Turbine's fault, but could easily be a reason many are affected, and others are not.

[moomooprincess]

That's what we're trying to determine. At the moment it's very odd because even though it's on particular toons/"main" server, it's not DDO specific. The AC players are reporting the exact same behavior. It is very strange.

Star Trek is not a Turbine product.

This means it is a internet backbone problem and one of the big boys needs to fess up.

Maybe it was a male dominance game to cause pain over the weekend when many of the rivals customers were sure to be using the internet and the wannabe dominant male decided to cram the pipes and slow the load for the rival.

[Kadriel]

Seens neverwinter got their issues corrected. Apparently it was related to the web server that hosted the launcher page, and it had to be redirected.

Maybe this info helps with our issues?

[ComicRelief]

Star Trek is not a Turbine product.

This means it is a internet backbone problem and one of the big boys needs to fess up.

Maybe it was a male dominance game to cause pain over the weekend when many of the rivals customers were sure to be using the internet and the wannabe dominant male decided to cram the pipes and slow the load for the rival.

Maybe it was plot; a Romulan ploy...

[enochiancub]

Maybe it was plot; a Romulan ploy...

GASP!

You're a terrible genius. Sela has made her move.

[Cyndder]

Well, again, when we were discussing where to put the blame regarding lag issues, we were able to point squarely at turbine's PNAP (if I remember right). So not an in-house Turbine problem, but still a turbine problem... Now if this current thing is being caused by Comcast or some other backbone-type issue, then no, not directly Turbine's fault, but could easily be a reason many are affected, and others are not.

From the vast amount of posts, I've seen comcast, Verizon, att, and couple of other smaller carriers talked about...so it is not likely to be just one of these ISP's and the issues being found go from plain connectivity to connectivity to but a singe (primary) server used by most people.

So the problem is complex and I fear will not be fully resolved until more people can break apart the mound of information the users have been providing from around the world. I suspect some internal network routing..potentially from a piece of faulty hardware in addition to some ISP issues outside of Turbine's ready control...and some of the issue may very well be issues with Turbines ISP...but it will take time to untangle this ball of yarn.