OT -- seeking a knowledgable AS 701 technical contact.

Thu Nov 17 01:13:52 UTC 2011

sorry grant :( (gmail user fail)

On Wed, Nov 16, 2011 at 8:12 PM, Christopher Morrow
<morrowc.lists at gmail.com> wrote:
> On Wed, Nov 16, 2011 at 8:12 PM, Christopher Morrow
> <morrowc.lists at gmail.com> wrote:
>> what are you trying to do with ftp.uu.net? is it broken in some way?
>>
>
> is it possibly that no login info works on it?
>
> $ ftp ftp.uu.net
> Connected to ftp.uu.net.
> 220 FTP server ready.
> Name (ftp.uu.net:morrowc): anonymous
> 331 Guest login ok, send your complete e-mail address as password.
> Password:
> 530 Login incorrect.
> Login failed.
> ftp> quit
>
>
>> On Wed, Nov 16, 2011 at 5:51 PM, Grant Ridder <shortdudey123 at gmail.com> wrote:
>>> Hi,
>>>
>>> If i remember right, Verizon Business has 3 or 4 different help desks.
>>>  From my experience, none of the help desks know anything about the others.
>>>  I dont have any numbers off hand unfortunately.
>>>
>>> -Grant
>>>
>>> On Wed, Nov 16, 2011 at 4:35 PM, Robert Bonomi <bonomi at mail.r-bonomi.com>wrote:
>>>
>>>>
>>>> Apologies for the noise, but I have been absolutely unable -- despite
>>>> literally *hours* of trying --to contact anyone at _any_ of the published
>>>> Verizon Business phone numbers who has any comprehension of what I am
>>>> talking about -- to wit:
>>>>
>>>>  "I am looking for someone with _any_ awareness/knowledge of Verizon
>>>>   Business's public-access anonymous FTP server, with the hostname
>>>>   'ftp.uu.net'."
>>>>
>>>> The published Verizon Business technical contact number -- both in 'whois'
>>>> for uu.net, and Jared's NOC contact list is only the 'ticket center', and
>>>> won't open a ticket for someone who is not Verizon customer.
>>>>
>>>> "Customer service" doesn't know what 'ftp' is, and vacillates between
>>>> thinking it is a circuit problem, or  that I am having a problem with -my-
>>>> domain.
>>>>
>>>> Call-transfer to 'technical support' was answered by someone handling
>>>> 'delinquent payments'.  Another transfer attempt ended up on somebody's
>>>> cell phone.
>>>>
>>>>
>>>>
>>>>
>>>
>>
>