Sorry. Sent that too soon. What is the ip of the device? On Fri, Feb 12, 2010 at 10:30 AM, Richard Stovall <[email protected]> wrote:
> There shouldn't be a hop. > > http://jodies.de/ipcalc?host=192.168.0.0&mask1=22&mask2= > > <http://jodies.de/ipcalc?host=192.168.0.0&mask1=22&mask2=>What kind of > device is it? Do you have any sort of console access? > > > On Fri, Feb 12, 2010 at 10:25 AM, John Aldrich < > [email protected]> wrote: > >> Either that or whatever is on the first hop is blocking / dropping ICMP. >> >> >> >> [image: John-Aldrich][image: Tile-Tools] >> >> >> >> *From:* Benjamin Zachary - Lists [mailto:[email protected]] >> *Sent:* Friday, February 12, 2010 10:15 AM >> *To:* NT System Admin Issues >> *Subject:* IP gurus .. >> >> >> >> 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/> ~
<<image001.jpg>>
<<image002.jpg>>
