On Jun 23, 11:06 pm, "soup_or_po...@yahoo.com"
<soup_or_po...@yahoo.com> wrote:
> On Jun 23, 2:03 pm, Lew Pitcher <lpitc...@teksavvy.com> wrote:
>
>
>
> > In comp.os.linux.networking, soup_or_po...@yahoo.com wrote:
> > > Hi
> > > I am trying to ping a host by IP and getting DUP. The man page says it
> > > is a hardware problem.
>
> > Typically, a DUP comes as a result of more than one node using the target IP
> > address. Yes, this is a hardware problem, in that only one of those nodes
> > can legitimately "own" the IP address, and all the other responders suffer
> > from some misconfiguration.
>
> > Recognize that, if more than one destination claims a specific IP address,
> > the underlying network (i.e. Ethernet) often cannot properly route data to
> > the destination node.
>
> > > When I do wget with the host IP I am getting
> > > html response code 400. Apparently there is nothing wrong with the
> > > host. Can anyone help me figure this out? These are the commands I
> > > used at the linux command prompt.
>
> > > ping 198.252.230.11
>
> > > wget -drc
>
> >http://198.252.230.11:9504/VendorSSO...PartnerID=yyyy
>
> > > I also ran traceroute and didn't receive any hits. All the hops
> > > printed 3 asterisks.
>
> > Firewalled?
>
> That is very likely. I would like to rule out hardware failure in
> which case I will leave it upto the powers be in my org. Since ping
> has shown DUP's, how definitive is it that the problem is with
> hardware?
>
> Thanks for your help

It might just be the network driver issue if you are using custom
driver

-- Rohit