Windows Forum

Ask something
Discussion Locked

IP pinging

0 helpful
11 replies

by gridrunner

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Hi come across a system has 2 NICs in it, one is for adsl the other is for the LAN. I can ping from this system out, but I can't seem to ping back to this system from any other terminal on the network. This systems ip address is set at 192.168.0.2,as I said I can ping out and ping any terminal on the network, but when I try and ping it from any other terminal all I get is a timeout, Can any one help ?

11 replies

by jimandkathy

I do not have a full answer for you. What I do have is to see if the either or both of the NICs are stopping incoming pings. Remove a card and retest and see if the pings go both way. Next swap out the card still in and install the other one and retest.

Jim

by maelgwyn

Methinks that the problem is that the routing is not set up correctly on that machine. If it is running 2k, check the routing setup (routing and remote access in the admin group). In linux and NT, check IP forwarding is switched on. Other than that, id need to see the system. Also it could be the NICs... but see if you can ping from a terminal to their nic (ie the 192.x) then to the other. if the problems there, itll show

by gridrunner

System is running win98, have tried to ping from other terminals, but just keep on getting a time out. but I can ping all terminal from this system. Alsothe server is also running 98 and all workstations are runing win95

regrads, Ken

by gperrie

I think the problem is the default gateway.

Don't know the full explanation but its something like - when you ping the box(or send any request) it forwards all packets to it's gateway ie. the internet . These packets can never find a way back to the box doing the ping giving a timeout message.

Gavin

by nettek

Your problem is that when you ping the multihomed computer, that computer is responding to the ping out the DSL line instead of back on the LAN. Add a route statement to the dual-nic computer:
c:\route -p add 192.168.0.0 mask 255.255.255.0 192.168.0.2
The -p means persistent after reboot.
192.168.0.0 is the subnet
255.255.255.0 is the subnet mask
192.168.0.2 is the local nic
This tells the PC to respond to all request from you local subnet via the local nic.

This discussion is closed to new replies.