freepooma-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [pooma-dev] Problem with configure on Linux/ia32: Red Hat 8.0


From: Jeffrey D. Oldham
Subject: Re: [pooma-dev] Problem with configure on Linux/ia32: Red Hat 8.0
Date: Fri, 27 Feb 2004 13:12:00 -0800
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Sullivan, Jeff wrote:
Thanks again for your help, but I am still having trouble checking out
the cvs sources. I also was unable to ping pooma.codesourcery.com (from
Linux).

% ping pooma.codesourcery.com
PING pooma.codesourcery.com (65.74.133.5) from .... : 56(84) bytes of
data.

--- pooma.codesourcery.com ping statistics ---
4 packets transmitted, 0 received, 100% loss, time 3017ms

% /usr/bin/cvs --version
Concurrent Versions System (CVS) 1.11.2 (client/server)

% cvs -d :pserver:address@hidden:/home/pooma/Repository
login
Logging in to
:pserver:address@hidden:2401/home/pooma/Repository
CVS password:
cvs [login aborted]: connect to pooma.codesourcery.com(65.74.133.5):2401
failed: Connection timed out

Could this be due to my corporate firewall or other security settings?
Is that the right IP address for the cvs server?

Pinging works for me from inside and outside codesourcery.com:

(outside codesourcery.com)
ping pooma.codesourcery.com
PING pooma.codesourcery.com (65.74.133.5) from 171.64.66.201 : 56(84) bytes of data. 64 bytes from voldemort.codesourcery.com (65.74.133.5): icmp_seq=0 ttl=243 time=11.402 msec 64 bytes from voldemort.codesourcery.com (65.74.133.5): icmp_seq=1 ttl=243 time=8.084 msec 64 bytes from voldemort.codesourcery.com (65.74.133.5): icmp_seq=2 ttl=243 time=7.647 msec 64 bytes from voldemort.codesourcery.com (65.74.133.5): icmp_seq=3 ttl=243 time=8.738 msec

--- pooma.codesourcery.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/mdev = 7.647/8.967/11.402/1.462 ms

Inside codesourcery.com yields similiar data.

--
Jeffrey D. Oldham
address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]