High Speed Internet (DSL) and Dial-Up

[#1]

Hello Elizabeth,

I originally wrote a different post but was happy to delete it after discovering a message from Anthony. 

It is evident Verizon has looked into the Landzdown connection issue and has determined the problem lies elsewhere.  Although the issue continues to exist, Verizon has reSolved their part.  Therefore I believe the Solved checks should remain.

Many thanks to everyone involved.

Cora

Tracing route to landzdown.com [74.55.178.34]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dslrouter [xxxxxxxx]
  2   879 ms   902 ms   949 ms  10.32.145.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.

The above trace route was done today, September 27, 2011.

[#2]

Softlayer suggested adding the following information to the ticket::

You may also want to request a few more tests from your client if he/she is still unable to access your server. Here are some details we will need to help us try to locate the cause of this problem.

- (Windows)WinMTR or (Linux)mtr

If your operating system is Windows, then you may use WinMTR. You may get WinMTR from the URL below:

http://winmtr.net/

From a Linux operating system, you may run the following command:

mtr -r -c 100 -n <IP or Domain Name>

- (Windows)tracert or (Linux)traceroute

If your operating system is Windows, then you may run the tracert command from the windows command prompt, example:

Start > Run > cmd(click ok) - Type tracert <IP or Domain Name>

From a Linux operating system, you may run the following command:

traceroute <IP or Domain Name>

 These tests should be conducted from your location or your clients that are having trouble accessing our network. Once the tests have completed, please paste those details directly into the trouble ticket, or you may attach them as a file or image.

If anyone is willing to provide the results of WinMTR and tracert, please post both sets of information in a reply.  (LandzDown IP 74.55.178.34)

Thank you and my thanks to Verizon for allowing us to continue working on this problem in this thread.

[#3]

I'm not sure how long WinMTR is supposed to run... I stopped it after 50+ packets were sent to non-responding hosts:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  279 |  279 |    1 |   12 |  340 |    7 |
|                             10.32.187.1 -    0 |  278 |  278 |   33 |   46 |  432 |   41 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   51 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

And here is the TraceRt:

Tracing route to landzdown.com [74.55.178.34]

over a maximum of 30 hops:



  1     2 ms     1 ms     2 ms  192.168.1.1

  2    41 ms    34 ms    35 ms  10.32.187.1

  3     *        *        *     Request timed out.

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10     *        *        *     Request timed out.

 11     *        *        *     Request timed out.

 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.



[#4]

Thank you, ky331! 

[#5]

Hi, ky331.  Can you send me your IP address please to be added to the other information (either via message here or message at the other location )

[#6]

Thank you Corrine and Ky331 for your continued efforts in this matter. Many Verizon customers who use Landzdown.com, including me, will certainly benefit from all you have done in this matter.

[#7]

Since there's no point running MTR since it turns up with the same results regardless, I will just send you my IP address to give to Softlayer.

[#8]

Thank you, Smith6612.  I've passed along the information from both you and ky331 to be added to the ticket. 

@Cora, we're all hopeful that this will be resolved sooner rather than later!  Thanks to everyone for your support.

[#9]

I just got through!    Hopefully, this is a "permanent" fix..

For what it's worth, here's a "good" Trace:

Tracing route to landzdown.com [74.55.178.34]

over a maximum of 30 hops:



  1     1 ms     1 ms     1 ms  192.168.1.1

  2    35 ms    34 ms    34 ms  10.32.187.1

  3    42 ms    35 ms    35 ms  P0-0.NYCMNY-LCR-07.verizon-gni.net [130.81.46.214]

  4    44 ms    36 ms    66 ms  so-5-3-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.28.154]

  5    42 ms    36 ms    37 ms  0.xe-3-0-0.BR3.NYC4.ALTER.NET [152.63.2.241]

  6    42 ms    35 ms    36 ms  204.255.168.194

  7    91 ms    90 ms    85 ms  The-Planet.TenGigabitEthernet2-3.ar2.HOU1.gblx.net [64.214.196.58]

  8    88 ms    83 ms    79 ms  e3-2.ibr02.hstntx2.networklayer.com [70.87.253.169]

  9    91 ms    86 ms    84 ms  te2-6.dsr01.hstntx2.networklayer.com [74.55.252.42]

 10    84 ms    86 ms    86 ms  po15.dsr01.hstntx1.networklayer.com [70.87.253.110]

 11    80 ms    86 ms    82 ms  po1.car05.hstntx1.networklayer.com [207.218.223.18]

 12    88 ms    80 ms    80 ms  server01.manageyourpc.com [74.55.178.34]



Trace complete.



[#10]

Yippee!!!

Aaron is still at work so I don't know if it is something SoftLayer fixed or if Eric, how has still been working on this issue from the Verizon side, discovered something.