[nylug-talk] Re: Ubuntu Problem: No Longer Able to Make Certain Connections

[James Keenan]

On Oct 21, 2006, at 8:09 AM, nylug-talk-request at nylug.org wrote:

>
> Message: 4
> Date: Fri, 20 Oct 2006 21:30:28 -0400
> From: James Keenan <jkeen at verizon.net>
> Subject: [nylug-talk] Re: Ubuntu Problem: No Longer Able to Make
> 	Certain	Connections
> To: nylug-talk at nylug.org
> Message-ID: <D918C5DE-7822-4C1E-91F9-CE85AF296762 at verizon.net>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Sep 12, 2006, alex at pilosoft.com wrote:
>
>> Subject: Re: [nylug-talk] Re: Ubuntu Problem: No Longer Able to Make
>> 	Certain	Connections
>> To: NYLUG Technical Discussion <nylug-talk at nylug.org>
>>
>> On Mon, 11 Sep 2006, James Keenan wrote:
>>
>>> [Documents] 517 $ ip route list
>>> 192.168.6.0/24 dev eth0  proto kernel  scope link  src 192.168.6.94
>>> default via 192.168.6.1 dev eth0
>>> [Documents] 518 $ traceroute nntp.perl.org
>>> bash: traceroute: command not found
>>> [Documents] 519 $ tracepath nntp.perl.org
>>> 1:  192.168.6.94 (192.168.6.94)                            0.144ms
>>> pmtu 1500
>>> 1:  no reply
>> What does 192.168.6.1 run?
>>
>
>
> Just getting back to this problem.  I'm afraid I didn't understand
> what you meant by "192.168.6.1 run" in this context.
>
> This problem has a number of different symptoms.  Not only can I no
> longer use AIM; yesterday I discovered that I can't 'rsync' either.
> And I can't get my system clock to synchronize with Internet clocks
> via the Ubuntu Date and Time feature, either.
>
> I was able to discuss this with one of the sysadmins late this
> afternoon.  He, too, advised me to run:
>    iptables -L -v -n
> He showed me what he characterized as "normal" output when he ran it
> on his Linux box -- and the output was much more detailed than mine.
> But I didn't get a chance to discuss it further with him.  He could
> rsync to the site to which I failed to rsync -- and that's a site I
> had no problem rsynching to from home.
>
> Any further diagnostic suggestions, ladies and gentlemen?  TIA
>
> jimk
>


This problem has been fixed.  It ultimately had nothing to do with  
'iptables', 'tracepath', etc.  A kindly sysadmin looked into the  
company's network settings and discovered that my IP address was one  
of the few that lacked certain network permissions.  (I can't  
remember *which* permissions; I'll post a follow-up.)  When he  
corrected that, I got my rsync, AIM and time synchronization all back.

Thank you very much.
Jim Keenan