Twilight Guild Forum

World of Warcraft => Warcraft Discussion => Topic started by: moonras on December 19, 2008, 03:19:44 PM

Title: Problems Staying Connected?
Post by: moonras on December 19, 2008, 03:19:44 PM
I've been having problems staying connected since I got home. Thought some of you might want to read this in case you are as well. Hopefully it will be fixed soon.

"We are attempting to gather information regarding the disconnect issues that began today. This mostly seems to be affecting Comcast and Verizon users.

Please follow the instructions below to post a trace route to your realm. Thanks!

Start WOW login to the realm you normally play on.
Press ALT-TAB to minimize WoW and return to the desktop.
Click Start then Run, then type "cmd"
In the DOS window type "netstat"
Wait until the command prompt appears again, approx 1 minute
You will see an IP address connected on port 3724. It will look like xxx.xxx.xxx.xxx:3724 this is your connection to Blizzard.
Now perform a trace route to that IP address to map the route you take to the realm.
Go to Start/Run
Type "cmd" to bring up the DOS window in the Run command box.
Type "tracert xxx.xxx.xxx.xxx > "C:\trace.txt" in the DOS window
Wait for the command prompt to appear again, about 1 minute.
Now the file called trace.txt should hold the trace route you took to the realm. Please reply to this thread with the recorded information. "


http://forums.worldofwarcraft.com/thread.html;jsessionid=06B60213740C153FAAAD2B4D9748B2D4.app23_03?topicId=13769837832&sid=1&pageNo=1
Title: Re: Problems Staying Connected?
Post by: Lynette on December 19, 2008, 05:20:10 PM
I had similar.  Decided to just log for awhile.
Title: Re: Problems Staying Connected?
Post by: TheGeneral451 on December 19, 2008, 07:28:49 PM
Yeah i logged also it was so annoying. 10 min max and then a disconnect.  :-[
Title: Re: Problems Staying Connected?
Post by: fiere redfern on December 20, 2008, 09:36:33 AM
I had the same thing most of yesterday - up and quit at one point and went off to do something else =P

Apparently the issue's been resolved (for me, at least). I've been hanging out in Dalaran for the past twenty minutes with no problem.