Re: Can't ping router.

In message <4f12635360nospam@xxxxxxxxxxxxxxxxxxxxx>
David <nospam@xxxxxxxxxxxxxxxxxxxxx> wrote:

In article <c2535f124f.davehigton@xxxxxxxxxxxxx>,
Dave Higton <davehigton@xxxxxxxxxxxxx> wrote:
In message <4f11ebcf66nospam@xxxxxxxxxxxxxxxxxxxxx>
David <nospam@xxxxxxxxxxxxxxxxxxxxx> wrote:

*ping 192.168.0.101
Ping 192.168.0.101: 56 data bytes
64 bytes from 192.168.0.101: icmp_seq=0.

That shows the RPC's internet stack is working.

At least that bit's okay then.

[Snip]


----192.168.0.2 Ping Statistics----
1 packets transmitted, 0 packets received, 100% packet loss

Hmm, no communication outside the box.

I don't have any direct experience of the DG834, but Netgear's
information on the web suggests it has 4 LAN ports and one
Internet port. I take it your RPC is connected to one of the
LAN ports?

Yes. they're numbered 1 to 4. I did have the 2 Macs on 1 & 2 with the
RPC on 3 but since I swapped cables between a Mac and the RPC, the RPC
is now on port 2, the Macs on 1 & 3.

The router's recognising the RPC as a 10Mb connection but that seems as
far as it goes.

Immediately after pinging the router from the RPC, on the RPC issue
the command

arp -a

That will list the IP and hardware addresses of any system it has
started a negotiation with in the last 15 minutes.

If the router shows up, it means that the RPC has asked who owns IP
address 192.168.0.1, and the router has replied with its own hardware
address. This is an essential step in sending a message, such as ping,
to the router. All messages on ethernet are actually sent to hardware
addresses.

The only times I've seen ARP work, when ping doesn't, are when pinging
a system whose security settings forbid a reply to ping, such as the
Windows firewall, or a wireless interface with the wrong encryption
key.

If arp hasn't worked, then the failure is at a very low level- usually
hardware, e.g. cable, port etc.

At that stage I would be trying a crossed cable directly from the RPC
to a Mac. With that it should be possible to ping the RPC from the Mac
(but not the reverse for the same reason the Macs won't ping each
other - they are set not to respond to pings. You WILL want to change
that setting on each Mac, so you can do this sort of testing.)

It will only work with a crossed cable, which I don't suppose you
have. They are about 7 pounds from PC World, if you want to explore
that route further.

If that test also fails, I would suspect the RPC ethernet hardware.

Another test - does the router's web interface allow you to ping other
systems from the router? If so, try pinging the RPC from the router.
If it works, then your problem is a security setting in the router.
(You won't be able to ping the Macs from the router - security
settings on Macs again.)


--
Alan Adams, from Northamptonshire
alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
.

Relevant Pages

  • Re: Cant ping router.
    ... packets transmitted, 0 packets received, 100% packet loss ... and the router has replied with its own hardware ... ping, to the router. ... Mac (but not the reverse for the same reason the Macs won't ping ...
    (comp.sys.acorn.networking)
  • Re: Network Internet Connection Problems
    ... router would seem to be choosing not to reply. ... That suggests that you tried to ping something by name. ... on the RPC, the XP-PC and the LAN side of the router. ... Hosts file is listing both computers and router correctly. ...
    (comp.sys.acorn.networking)
  • Re: Separate IP address for VPC and MAC
    ... > my Powerbook to my wireless router then everything works fine and I ... > can now ping the MAC and the router from the DOS prompt. ...
    (microsoft.public.mac.virtualpc)
  • Re: Cant ping router.
    ... field - I mean on the router's own settings. ... RPC with the IP address used by the RPC. ... That is indeed the Media Access Control address, abbreviated to MAC ... When you ping the router, does the light on the router flicker? ...
    (comp.sys.acorn.networking)
  • Re: Damned MBP to Winblows wireless networking issue
    ... If it's a router, there will be - it'll be NATting, which is ... Network Neighborhood browser? ... First check whether the PC can ping its OWN ip address. ... Now try the same test on the Mac. ...
    (uk.comp.sys.mac)