In addition to the advice from the others, make sure that the MAC address that's responding to the pings is the same as the MAC address of 192.168.0.1
Just sayin' On Fri, Feb 12, 2010 at 07:15, Benjamin Zachary - Lists <[email protected]> wrote: > Has anyone seen something like this before? > > > > I have a network with 192.168.0.x/22 (255.255.255.248.0) > > > > When we goto ping a device @ 192.168.0.1 the reply comes back in 1-3ms so > that’s okay, however a tracert yields: > > > > 1 * * * > > 2 1ms 1ms 1ms 192.168.0.1 > > > > This is happening only for this one device, I can tracert other devices in > the 192.168.0.x or anywhere else and get a simple 1 line response. > > The reason we are checking this is because our phone gateway is the > 192.168.0.1 and people are having some connectivity issues with it > > The vendor is claiming we have a routing issue even though everything is in > the same subnet so there is no ‘routing’ occurring. > > > > Im thinking the PBX has the wrong subnet on it but I cant see it until the > vendor comes onsite later today… > > My route table looks correct and even doing the tracert from a 192.168.0.x > server I get the same result. > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
