• Subject: Re: TraceRoute
  • From: Scott Klement <klemscot@xxxxxxxxxxxx>
  • Date: Fri, 12 Jan 2001 14:06:10 -0600 (CST)

I've seen stuff similar to this happen when

       a) two computers have the same ethernet (MAC) address.
       b) two computers have the same IP address, one is responding to
               pings, one is not.
       c) routing is screwed up (subnets and routes aren't properly
       d) network card is dying.  

Of these, I'd say (d) is the most likely/common unless you're setting up
your LAN for the first time, now.

On Fri, 12 Jan 2001, John Hall wrote:

> hmm... couple of clarifications about my situation.
> If I ping using a name or the direct IP the same thing occurs.
> No other systems (NT, linux, 98, 95) experience this problem.
> I doubt that it is a time-out issue since the problem occurs with our
> local internet router.  A successful ping will return in 3 to 4 ms
> typically.  Pinging external internet addresses yield times of 100 to
> 180 ms.  Both will fail on pings # 2 & 4
> > Chris Bipes wrote:
> > 
> > Sounds like you are handing out multiple IPs for your system.  DNS
> > will give out 1 then 2 then 1 then 2....
> ping resolves the DNS prior to sending the packet.
> The firewall logs show 5 ping attempts to the same address.
> Oh well I'll keep looking

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.