An Accepted Solution is available for this post.
Re: Periodic Disconnects
Silentmiller
Newbie
‎06-09-2009 12:54 PM

Okay, according to people that know a lot more about this stuff than I do. It is working okay now.

http://www.dslreports.com/forum/r22504576-speedlatency-ConnectivityHigh-Latency-with-FIOS-NY-Area~start=80 

Also the World of WarCrafters have weighed in:

http://forums.worldofwarcraft.com/thread.html?topicId=17631614987&sid=1&pageNo=11 

0 Likes
An Accepted Solution is available for this post.
Re: Periodic Disconnects
marknazzal
Newbie
‎06-10-2009 10:21 PM

     Okay...here are the results of a longer trace route ran today while I had the internet going.


-http://profile.imageshack.us/user/marknazzal/images/detail/#197/3dtrace6.jpg

-http://profile.imageshack.us/user/marknazzal/images/detail/#192/3dtrace5.jpg

-http://profile.imageshack.us/user/marknazzal/images/detail/#145/3dtrace4.jpg

-http://profile.imageshack.us/user/marknazzal/images/detail/#140/3dtrace3.jpg

-http://profile.imageshack.us/user/marknazzal/images/detail/#197/3dtrace7.jpg

-http://profile.imageshack.us/user/marknazzal/images/detail/#191/3dtrace1.jpg

-http://profile.imageshack.us/user/marknazzal/images/detail/#13/3dtrace2.jpg

...Did i do that right? 😛  any thoughts?

--------------------

Non-3d Traceroutes still getting the same results:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>tracert 12.129.233.23

Tracing route to 12.129.233.23 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  myrouter.home [192.168.1.1]
  2     5 ms     5 ms     4 ms  L100.LSANCA-VFTTP-134.verizon-gni.net [96.247.3.
1]
  3     6 ms     7 ms     6 ms  G10-0-5-1934.LSANCA-LCR-09.verizon-gni.net [130.
81.138.110]
  4     9 ms     7 ms     8 ms  so-4-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.28.72]
  5     8 ms     8 ms     7 ms  0.so-6-3-0.XT1.LAX9.ALTER.NET [152.63.10.153]
  6     9 ms     8 ms     9 ms  0.so-7-0-0.XL3.LAX15.ALTER.NET [152.63.112.53]
  7    10 ms    10 ms     9 ms  192.205.35.161
  8    10 ms    10 ms     9 ms  cr2.la2ca.ip.att.net [12.123.30.134]
  9    10 ms     9 ms    10 ms  gar5.la2ca.ip.att.net [12.122.128.25]
 10    13 ms    12 ms    11 ms  12.122.255.74
 11    11 ms    12 ms    11 ms  mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.


Also keep in mind this is not just a WoW issue, but one that obviously manifests itself more clearly when gaming due to the constant connection etc.

0 Likes
An Accepted Solution is available for this post.
Re: Periodic Disconnects
prisaz
Legend
‎06-11-2009 04:07 PM

Here is a trace from my location. It looks like your trace times out right before it hits the server. Server not accepting more connections. Hardly a FIOS issue and time out is not on Verizons network so not much can be done short of the provider on the other end providing more connections to the server. If your connection is being dropped on the other end it is the server on the other end.


Target: 12.129.233.23
Date: 6/11/2009 (Thursday), 7:04:00 PM
Nodes: 20


Node Data
Node Net Reg IP Address      Location            Node Name
   1   -   - 192.168.0.5     39.171N,  77.273W   HOMENET1
   2   1   - 192.168.0.1     Unknown            
   3   1   1 192.168.1.1     Unknown             wireless_broadband_router.home
   4   2   - 10.1.41.90      Unknown            
   5   3   2 130.81.109.166  WASHINGTON D.C.     g15-0-6-192.washdc-lcr-01.verizon-gni.net
   6   3   2 130.81.29.216   WASHINGTON D.C.     so-0-1-0-0.lcc1-res-bb-rtr1-re1.verizon-gni.net
   7   4   3 152.63.32.141   WASHINGTON D.C.     0.ge-4-2-0.br2.iad8.alter.net
   8   5   - 204.255.168.30  WASHINGTON D.C.    
   9   6   4 12.122.135.14   39.044N,  77.489W   cr1.wswdc.ip.att.net
  10   7   4 12.122.4.53     Philadelphia        cr2.phlpa.ip.att.net
  11   8   4 12.122.2.209    Cleveland           cr2.cl2oh.ip.att.net
  12   9   4 12.122.2.125    Cleveland           cr1.cl2oh.ip.att.net
  13  10   4 12.122.2.205    Chicago             cr1.cgcil.ip.att.net
  14  11   4 12.122.31.85    Denver              cr2.dvmco.ip.att.net
  15  12   4 12.122.30.25    Salt Lake City      cr1.slkut.ip.att.net
  16  13   4 12.122.30.30    Los Angeles         cr2.la2ca.ip.att.net
  17  14   4 12.122.129.25   Los Angeles         gar5.la2ca.ip.att.net
  18  15   - 12.122.255.74   Los Angeles        
  19  16   5 12.129.193.246  Los Angeles         mdf001c7613r0004-gig-12-1.lax1.attens.net
  20  17   - 12.129.233.23   Irvine             

Message Edited by prisaz on 06-11-2009 07:09 PM
0 Likes