• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 633
  • Last Modified:

Ping Packet loss

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
westone
Asked:
westone
  • 3
  • 2
1 Solution
 
PapertripCommented:
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
 
westoneAuthor Commented:
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
 
PapertripCommented:
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
 
westoneAuthor Commented:
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
 
PapertripCommented:
In that case then you are probably correct in that the device is just not responding to pings.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now