Solved

Ping Packet loss

Posted on 2011-09-20
5
628 Views
Last Modified: 2012-05-12
Hi,
I am attempting to figure out why Internet access is slow on our Server 2003 domain with a dozen XP Pro SP3 clients. Internet is slow for the clients but normal on the server. The average of several bandwidth tests at different sites along the east coast is 5Mbs down and 600Kbs up and the internet browsing from the server is normal. At the clients it is slow.

I ran "Pathping yahoo.com" from the server and from a client. In both cases all hops experienced 0 packet loss except hop #2, which experienced 100% packet loss. Hop #1 went to our gateway at 10.0.0.254, hop#2 goes to 10.254.128.1 which is a private address I am unfamiliar with. IPCONFIG /All shows the IP configuration to be correct with no mention of 10.254.128.1. Our Server (for DNS) is 10.0.0.1, gateway is 10.0.0.254, client IPs are 10.0.0.xxx.

Is this hop#2 normal or a problem? How do I find out where this 10.254.198.1 address came from? Any other suggestions?

Thanks,
Bill
0
Comment
Question by:westone
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 21

Expert Comment

by:Papertrip
ID: 36568472
Going to need to check routes on 10.0.0.254

I would give more details but I don't know what you are using for a gateway.
0
 

Author Comment

by:westone
ID: 36568537
The gateway is just a wireless broadband router.

Tracert 10.0.0.254 returns one hop directly to 10.0.0.254.

Pinging anything beyond 10.0.0.254, the second hop is always 10.245.128.1. That's a private address, but outside of our network I suppose since it is always after the gateway address in the route to a public address. In that case we have no control over it. I got concerned with it because it shows 100% packet loss with "Pathping". Maybe it just doesn't reply to ping requests.
0
 
LVL 21

Expert Comment

by:Papertrip
ID: 36568558
You definitely should have control over it if you manage the network, or know what is at that IP at the very least.  Did you look through the router configs?  What is the gateway on the router?  What is the WAN IP showing?
0
 

Author Comment

by:westone
ID: 36568756
You make my point exactly: This is a private IP address, yet not one that conforms to our network setup. And, in a tracert to an outside address it is always after our gateway, so no, we do not have control over anything beyond the gateway. That is our ISPs territory and beyond.

We have a static Public IP address. This address of 10.245.128.1 is not even close to the IP configuration for our static address.
0
 
LVL 21

Accepted Solution

by:
Papertrip earned 500 total points
ID: 36568821
In that case then you are probably correct in that the device is just not responding to pings.
0

Featured Post

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Remote Apps is a feature in server 2008 which allows users to run applications off Remote Desktop Servers without having to log into them to run the applications.  The user can either have a desktop shortcut installed or go through the web portal to…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have. In this…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question