SCIENTIFIC-LINUX-USERS Archives

November 2007

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Maxim kovgan <[log in to unmask]>
Reply To:
Maxim kovgan <[log in to unmask]>
Date:
Fri, 30 Nov 2007 01:57:33 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (89 lines)
Taylan Yetkin wrote:
> Both ping and traceroute  the host from fermi machines returns  
> success.  I need some time to understand the use of tcpdump.
> thanks,
> Taylan

can you post your ifconfig of the listening interface ?


a routing table would be nice too:
netstat -nr

you can of course scramble the IP addresses.



> 
> Maxim kovgan wrote:
>> John Summerfield wrote:
>>> Maxim kovgan wrote:
>>>> John Summerfield wrote:
>>>>> Taylan Yetkin wrote:
>>>>>> Hi,
>>>>>> I installed a cvs repository in my local SL machine and trying to 
>>>>>> connect
>>>>>>  it
>>>>>> from fermi machines. I get the following error:
>>>>>>
>>>>>> [cmswn085> cvs login
>>>>>> Logging in to 
>>>>>> :pserver:[log in to unmask]:2401/var/lib/
>>>>>> cvsroot
>>>>>> CVS password:
>>>>>> cvs [login aborted]: connect to
>>>>>> neutralino.physics.uiowa.edu(128.255.34.167):2401 failed: No route 
>>>>>> to hos
>>>>>> t
>>>>>
>>>>> This is a routing/firewall problem. the cvs command asks for the 
>>>>> password before trying to connect.
>>>>>
>>>>> 07:02 [summer@numbat ~]$ cvs  -d 
>>>>> :pserver:anoncvs@localhost:2401/var/lib/ login
>>>>> Logging in to :pserver:anoncvs@localhost:2401/var/lib
>>>>> CVS password:
>>>>> cvs [login aborted]: connect to [localhost]:2401 failed: Connection 
>>>>> refused
>>>>> 07:03 [summer@numbat ~]$
>>>>
>>>> It's most probably tcpwrappers
>>>
>>> No. That allows a connexion, then rejects it. You don't get "no 
>>> route" or "refused messages."
>>
>> AFAIK tcpwrappers refuse too.
>> but I somehow missed the no route to.. :)
>> and you're right! it needs some investigation:
>>
>> 1. ping to the host
>> 2. traceroute to the host.
>>
>> if you sporadically get the no route problem, it means you have ... a 
>> routing problem :)
>>
>> after you finished up with it, you can continue and trouble shoot.
>> routing problem can be cause by your university/enterprise firewall too.
>>
>>
>> you can also investigate with tcpdump, which is a great sniffer.
>>
>> Good luck!
>>
>>
>>
>>>
>>> "reset" is more probable.
>>>
>>>
>>
>>
> 


-- 
Maxim Kovgan,
Distributed Systems and Data Mining Laboratory
Computer Science, Technion
http://dsl.cs.technion.ac.il

ATOM RSS1 RSS2