Anonymous_User Absent Member.
Absent Member.
1163 views

Welcome to 2010

My first IT problem of the year:

Sometime early Saturday (Jan. 2) afternoon, the domains I control (websites
and POP3 email) became unreachable. I confirmed that DNS was working and
the web host had not gone bankrupt, then determined that the domains were
oddly reachable through Comcast, yet unreachable through Verizon.

Verizon support was very weak. The first tech did not even have access to
the Internet, but she could test my line, and confirm that it was working.
She seemed surprised that I could reach other websites, just not the ones I
needed to reach.

The tech and supervisor I spoke with were not familiar with PING and
TRACERT, and did not understand the special significance of a 10.x.x.x
unrouteable IP address.

They insisted that Verizon doesn't block anything, and in an accusing tone,
wanted to know if this web site was a "VPN page" (it is not). They finally
suggested it could be a "whitelist" problem with my web host.

Hopefully, others are reporting problems, and someone knowledgeable will
come back to work today at Verizon.

Anyone have any suggestions? We already tried FDISK, but just on one
machine. 🙂

-Bob Carroll



Labels (1)
0 Likes
12 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Welcome to 2010

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

First, support is not offered in the 'chat' forum so it may be worthwhile
to post elsewhere. Also, when you do, outline (in detail) what was done
to determine what could and could not be reached and what "reachable"
means, preferably with a LAN trace and traceroute output.

Good luck.




Wallgames.com wrote:
> My first IT problem of the year:
>
> Sometime early Saturday (Jan. 2) afternoon, the domains I control (websites
> and POP3 email) became unreachable. I confirmed that DNS was working and
> the web host had not gone bankrupt, then determined that the domains were
> oddly reachable through Comcast, yet unreachable through Verizon.
>
> Verizon support was very weak. The first tech did not even have access to
> the Internet, but she could test my line, and confirm that it was working.
> She seemed surprised that I could reach other websites, just not the ones I
> needed to reach.
>
> The tech and supervisor I spoke with were not familiar with PING and
> TRACERT, and did not understand the special significance of a 10.x.x.x
> unrouteable IP address.
>
> They insisted that Verizon doesn't block anything, and in an accusing tone,
> wanted to know if this web site was a "VPN page" (it is not). They finally
> suggested it could be a "whitelist" problem with my web host.
>
> Hopefully, others are reporting problems, and someone knowledgeable will
> come back to work today at Verizon.
>
> Anyone have any suggestions? We already tried FDISK, but just on one
> machine. 🙂
>
> -Bob Carroll
>
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLQjU+AAoJEF+XTK08PnB5R4kQAIIvp2u8cStQqdzQUUBHXfxA
sp5BMYrL0VJettABNdUXMTQhSwD41mwF5/SHH92EhLYfrxcs0jhy7FERUufucuAF
AWKd466CPhBnkDDlI+ZanPjZXu2LTigiY0GSy6KJgBmrziJMrJNO63tkIgRkoPwn
W1LDpyEl27MdFdEtr8Wwks/56msHji5I6wFgigN5o4BhhZpCXnGRmD2xx4ikFYCk
0OEM3xJnf4TPfKhJXgNZsCAaH0MR5Y9lPyiM5biAUVvZqrxHbayWu8ldPHL4e5SF
QuIR3gJG9JKB7dPFPcXHihCUpY0KP5nke3oAKfRx0xvEcRhuEgoIetm6Fno4uQHV
QDVc0goMFU/LhvWX0haZYVD3N9VBJ1tayfjooFSkxAtA/Dw4mCBwUj3/7MxaA8tk
aqlg59zdDf9WitbFqLRiVWP54uQAPJ8xvHGokMfGGaFGBHp5th8z5tsBCeNYSh7e
epU3L5FE3N3HLe5/cMW4YXV+LVne0u3R4GpzYMKYXtypPTAFWoXNIq97fCmgzQMl
WF2nlFqmdRjpIBj32OmKYJ0pLDTG0ckcvwTcBEFujO4dmonE8rH+NCT+yO1mcX5R
GuTz0u9jxr5IQSVqaANFqh2Rhek89EdA0BssdlNQTENLJ2Qdgoe20H/UKiQ8Bsnf
viE2QNeQ5EMHK+CZoLfD
=QLr/
-----END PGP SIGNATURE-----
0 Likes
jmarton2 Absent Member.
Absent Member.

Re: Welcome to 2010

On Mon, 04 Jan 2010 18:36:46 +0000, ab@novell.com wrote:

> First, support is not offered in the 'chat' forum


Only Novell support isn't allowed. 🙂


--
Joe
With great power comes great responsibility.

Joe Marton Emeritus Knowledge Partner
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

How many times do you say that per week? 🙂


"Joseph Marton" <jmarton@no-mx.forums.novell.com> wrote in message
news:Tzq0n.2233$q93.1322@kovat.provo.novell.com...
> On Mon, 04 Jan 2010 18:36:46 +0000, ab@novell.com wrote:
>
>> First, support is not offered in the 'chat' forum

>
> Only Novell support isn't allowed. 🙂
>
>
> --
> Joe
> With great power comes great responsibility.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

I've seen chunks of the internet go down before.

It seems to me that different providers yield different results, right? I'd
say some large privider between the failing provider and the destination has
a router problem.

We had problems once only getting back and forth to LA. Ginormous routing
error in San Jose, turns out due to fiber damage from construction. Their
auto-re-route ideas failed I reckon.

Another time we would connect for a while then disconnect, failing to route.
Comparing the tracerts I noticed different IPs for routers going through
Denver (I think?). Turns out that Level 3 has two ginormous routers there
and the failover had different routing tables than the first. The 2nd only
come online when the first failed or was saturated.

They corrected it, and then as a Tier 1 provider asked me which ISP I worked
for. Yoink! Too late...you fixed it for a plebe! 🙂


"Wallgames.com" <rpcarrollNOSPAMPLEASE@NOSPAMPLEASEwallgames.com> wrote in
message news:Ghq0n.2225$q93.1108@kovat.provo.novell.com...
> My first IT problem of the year:
>
> Sometime early Saturday (Jan. 2) afternoon, the domains I control
> (websites and POP3 email) became unreachable. I confirmed that DNS was
> working and the web host had not gone bankrupt, then determined that the
> domains were oddly reachable through Comcast, yet unreachable through
> Verizon.
>
> Verizon support was very weak. The first tech did not even have access to
> the Internet, but she could test my line, and confirm that it was working.
> She seemed surprised that I could reach other websites, just not the ones
> I needed to reach.
>
> The tech and supervisor I spoke with were not familiar with PING and
> TRACERT, and did not understand the special significance of a 10.x.x.x
> unrouteable IP address.
>
> They insisted that Verizon doesn't block anything, and in an accusing
> tone, wanted to know if this web site was a "VPN page" (it is not). They
> finally suggested it could be a "whitelist" problem with my web host.
>
> Hopefully, others are reporting problems, and someone knowledgeable will
> come back to work today at Verizon.
>
> Anyone have any suggestions? We already tried FDISK, but just on one
> machine. 🙂
>
> -Bob Carroll
>
>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

Thanks for the great story, Craig.

Perhaps the Internet is being clogged with those 50MB attachments headed
your way...

🙂


"Craig" <elrushbo@eib.net> wrote in message
news:NJq0n.2238$q93.1626@kovat.provo.novell.com...
> I've seen chunks of the internet go down before.
>
> It seems to me that different providers yield different results, right?
> I'd say some large privider between the failing provider and the
> destination has a router problem.
>
> We had problems once only getting back and forth to LA. Ginormous routing
> error in San Jose, turns out due to fiber damage from construction. Their
> auto-re-route ideas failed I reckon.
>
> Another time we would connect for a while then disconnect, failing to
> route. Comparing the tracerts I noticed different IPs for routers going
> through Denver (I think?). Turns out that Level 3 has two ginormous
> routers there and the failover had different routing tables than the
> first. The 2nd only come online when the first failed or was saturated.
>
> They corrected it, and then as a Tier 1 provider asked me which ISP I
> worked for. Yoink! Too late...you fixed it for a plebe! 🙂
>
>
> "Wallgames.com" <rpcarrollNOSPAMPLEASE@NOSPAMPLEASEwallgames.com> wrote in
> message news:Ghq0n.2225$q93.1108@kovat.provo.novell.com...
>> My first IT problem of the year:
>>
>> Sometime early Saturday (Jan. 2) afternoon, the domains I control
>> (websites and POP3 email) became unreachable. I confirmed that DNS was
>> working and the web host had not gone bankrupt, then determined that the
>> domains were oddly reachable through Comcast, yet unreachable through
>> Verizon.
>>
>> Verizon support was very weak. The first tech did not even have access
>> to the Internet, but she could test my line, and confirm that it was
>> working. She seemed surprised that I could reach other websites, just not
>> the ones I needed to reach.
>>
>> The tech and supervisor I spoke with were not familiar with PING and
>> TRACERT, and did not understand the special significance of a 10.x.x.x
>> unrouteable IP address.
>>
>> They insisted that Verizon doesn't block anything, and in an accusing
>> tone, wanted to know if this web site was a "VPN page" (it is not). They
>> finally suggested it could be a "whitelist" problem with my web host.
>>
>> Hopefully, others are reporting problems, and someone knowledgeable will
>> come back to work today at Verizon.
>>
>> Anyone have any suggestions? We already tried FDISK, but just on one
>> machine. 🙂
>>
>> -Bob Carroll
>>
>>
>>

>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

I just started blocking the 50 gb attachments!


"Wallgames.com" <rpcarrollNOSPAMPLEASE@NOSPAMPLEASEwallgames.com> wrote in
message news:vft0n.2296$q93.627@kovat.provo.novell.com...
> Thanks for the great story, Craig.
>
> Perhaps the Internet is being clogged with those 50MB attachments headed
> your way...
>
> 🙂
>
>
> "Craig" <elrushbo@eib.net> wrote in message
> news:NJq0n.2238$q93.1626@kovat.provo.novell.com...
>> I've seen chunks of the internet go down before.
>>
>> It seems to me that different providers yield different results, right?
>> I'd say some large privider between the failing provider and the
>> destination has a router problem.
>>
>> We had problems once only getting back and forth to LA. Ginormous
>> routing error in San Jose, turns out due to fiber damage from
>> construction. Their auto-re-route ideas failed I reckon.
>>
>> Another time we would connect for a while then disconnect, failing to
>> route. Comparing the tracerts I noticed different IPs for routers going
>> through Denver (I think?). Turns out that Level 3 has two ginormous
>> routers there and the failover had different routing tables than the
>> first. The 2nd only come online when the first failed or was saturated.
>>
>> They corrected it, and then as a Tier 1 provider asked me which ISP I
>> worked for. Yoink! Too late...you fixed it for a plebe! 🙂
>>
>>
>> "Wallgames.com" <rpcarrollNOSPAMPLEASE@NOSPAMPLEASEwallgames.com> wrote
>> in message news:Ghq0n.2225$q93.1108@kovat.provo.novell.com...
>>> My first IT problem of the year:
>>>
>>> Sometime early Saturday (Jan. 2) afternoon, the domains I control
>>> (websites and POP3 email) became unreachable. I confirmed that DNS was
>>> working and the web host had not gone bankrupt, then determined that the
>>> domains were oddly reachable through Comcast, yet unreachable through
>>> Verizon.
>>>
>>> Verizon support was very weak. The first tech did not even have access
>>> to the Internet, but she could test my line, and confirm that it was
>>> working. She seemed surprised that I could reach other websites, just
>>> not the ones I needed to reach.
>>>
>>> The tech and supervisor I spoke with were not familiar with PING and
>>> TRACERT, and did not understand the special significance of a 10.x.x.x
>>> unrouteable IP address.
>>>
>>> They insisted that Verizon doesn't block anything, and in an accusing
>>> tone, wanted to know if this web site was a "VPN page" (it is not).
>>> They finally suggested it could be a "whitelist" problem with my web
>>> host.
>>>
>>> Hopefully, others are reporting problems, and someone knowledgeable will
>>> come back to work today at Verizon.
>>>
>>> Anyone have any suggestions? We already tried FDISK, but just on one
>>> machine. 🙂
>>>
>>> -Bob Carroll
>>>
>>>
>>>

>>
>>

>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

Wallgames.com wrote:
> The tech and supervisor I spoke with were not familiar with PING and
> TRACERT, and did not understand the special significance of a 10.x.x.x
> unrouteable IP address.
>
> They insisted that Verizon doesn't block anything, and in an accusing tone,
> wanted to know if this web site was a "VPN page" (it is not). They finally
> suggested it could be a "whitelist" problem with my web host.


Many T1 ISPs have a history of "de-peering" with each other when they
are hoping the link is important enough to the other ISP that they will
pay them to put it back on.

The Cogent/Telia de-peering incident was a wakeup call for the entire
industry.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

Good point.

As an update, the problem has not yet been resolved.

Comcast reaches my websites, Verizon does not.

Thanks for the comments.


"David Howe" <DaveHowe@email.not.shown> wrote in message
news:1Gm1n.2991$q93.587@kovat.provo.novell.com...
> Wallgames.com wrote:
>> The tech and supervisor I spoke with were not familiar with PING and
>> TRACERT, and did not understand the special significance of a 10.x.x.x
>> unrouteable IP address.
>>
>> They insisted that Verizon doesn't block anything, and in an accusing
>> tone,
>> wanted to know if this web site was a "VPN page" (it is not). They
>> finally
>> suggested it could be a "whitelist" problem with my web host.

>
> Many T1 ISPs have a history of "de-peering" with each other when they
> are hoping the link is important enough to the other ISP that they will
> pay them to put it back on.
>
> The Cogent/Telia de-peering incident was a wakeup call for the entire
> industry.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

I have an idea....what if you install a RAS server at your Comcast site,
then dial in from your VZW site?

🙂


"Wallgames.com" <rpcarrollNOSPAMPLEASE@NOSPAMPLEASEwallgames.com> wrote in
message news:ahn1n.3002$q93.2747@kovat.provo.novell.com...
> Good point.
>
> As an update, the problem has not yet been resolved.
>
> Comcast reaches my websites, Verizon does not.
>
> Thanks for the comments.
>
>
> "David Howe" <DaveHowe@email.not.shown> wrote in message
> news:1Gm1n.2991$q93.587@kovat.provo.novell.com...
>> Wallgames.com wrote:
>>> The tech and supervisor I spoke with were not familiar with PING and
>>> TRACERT, and did not understand the special significance of a 10.x.x.x
>>> unrouteable IP address.
>>>
>>> They insisted that Verizon doesn't block anything, and in an accusing
>>> tone,
>>> wanted to know if this web site was a "VPN page" (it is not). They
>>> finally
>>> suggested it could be a "whitelist" problem with my web host.

>>
>> Many T1 ISPs have a history of "de-peering" with each other when they
>> are hoping the link is important enough to the other ISP that they will
>> pay them to put it back on.
>>
>> The Cogent/Telia de-peering incident was a wakeup call for the entire
>> industry.

>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

Craig wrote:
> I have an idea....what if you install a RAS server at your Comcast site,
> then dial in from your VZW site?


Because if he can't reach his sites, customers can't either - not a good
state of affairs if you are paying for web hosting.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

I was kidding! Who uses RAS any more?

🙂


"David Howe" <DaveHowe@email.not.shown> wrote in message
news:EbE1n.3176$q93.234@kovat.provo.novell.com...
> Craig wrote:
>> I have an idea....what if you install a RAS server at your Comcast site,
>> then dial in from your VZW site?

>
> Because if he can't reach his sites, customers can't either - not a good
> state of affairs if you are paying for web hosting.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Welcome to 2010

Craig wrote:
> I was kidding! Who uses RAS any more?
>
> 🙂

VPN is the new RAS 🙂
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.