As Chris said, check to see if you're really a /21 or /22 Is that network pure voice or voice+data ? That's a pretty big network for both to operate in but manageable. It defintely doesn't suggest connectivity issues are related to "routing" but more so network congestion; packet loss; transmission delays, etc.
If only 1 device is reporting that issue, check the mask and gateway assigned to its NIC. On Fri, Feb 12, 2010 at 11:20 AM, Jay Dale <jay.d...@3-gig.com> wrote: > What is the mask set to on the device you're pinging? > > > > Jay > > > > *From:* Benjamin Zachary - Lists [mailto:li...@levelfive.us] > *Sent:* Friday, February 12, 2010 9: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/> ~
