Mohonk
asked on
Wired vs Wireless Tracert/Ping times much different
We have a wireless network with workstations running a web-based application off a server in our datacenter. We have a 4.5MB pipe going to the datacenter from our location. The application run off of our wireless network is sluggish.
When I do a tracert from a wired workstation vs a wireless I get some interesting results but I'm not sure why this would be.
Here is the output from the Wired workstation:
U:\>tracert ewebbridgem
Tracing route to ewebbridgem [172.28.122.111]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.24.128.1
2 <1 ms <1 ms <1 ms 172.24.128.2
3 15 ms 11 ms 6 ms 172.26.0.69
4 29 ms 12 ms 12 ms 172.26.0.1
5 31 ms 21 ms 26 ms 172.26.0.2
6 15 ms 19 ms 15 ms 172.28.8.250
7 15 ms 15 ms 15 ms ewebbridgem [172.28.122.111]
Trace complete.
Here is the output from the Wireless workstation:
C:\>tracert ewebbridgem
Tracing route to ewebbridgem [172.28.122.111]
over a maximum of 30 hops:
1 3 ms 4 ms 8 ms 172.24.49.3
2 2 ms 1 ms 1 ms 172.24.112.25
3 3 ms 2 ms 7 ms 172.24.128.2
4 13 ms 15 ms 14 ms 172.26.0.69
5 74 ms 69 ms 106 ms 172.26.0.1
6 151 ms 148 ms 127 ms 172.26.0.2
7 238 ms * 159 ms 172.28.8.250
8 150 ms 185 ms 93 ms ewebbridgem [172.28.122.111]
Trace complete.
The response times from my internal routers the 127.24 is resonable from both the wired and wireless networks.
Why would the response times from the route through the pipe to the data center be so different wired vs wireless? Its taking the same path once it gets to 172.24.128.2 but the wireless is very sluggish.
Thanks for the help!
When I do a tracert from a wired workstation vs a wireless I get some interesting results but I'm not sure why this would be.
Here is the output from the Wired workstation:
U:\>tracert ewebbridgem
Tracing route to ewebbridgem [172.28.122.111]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.24.128.1
2 <1 ms <1 ms <1 ms 172.24.128.2
3 15 ms 11 ms 6 ms 172.26.0.69
4 29 ms 12 ms 12 ms 172.26.0.1
5 31 ms 21 ms 26 ms 172.26.0.2
6 15 ms 19 ms 15 ms 172.28.8.250
7 15 ms 15 ms 15 ms ewebbridgem [172.28.122.111]
Trace complete.
Here is the output from the Wireless workstation:
C:\>tracert ewebbridgem
Tracing route to ewebbridgem [172.28.122.111]
over a maximum of 30 hops:
1 3 ms 4 ms 8 ms 172.24.49.3
2 2 ms 1 ms 1 ms 172.24.112.25
3 3 ms 2 ms 7 ms 172.24.128.2
4 13 ms 15 ms 14 ms 172.26.0.69
5 74 ms 69 ms 106 ms 172.26.0.1
6 151 ms 148 ms 127 ms 172.26.0.2
7 238 ms * 159 ms 172.28.8.250
8 150 ms 185 ms 93 ms ewebbridgem [172.28.122.111]
Trace complete.
The response times from my internal routers the 127.24 is resonable from both the wired and wireless networks.
Why would the response times from the route through the pipe to the data center be so different wired vs wireless? Its taking the same path once it gets to 172.24.128.2 but the wireless is very sluggish.
Thanks for the help!
It looks like 172.26.0.1 has a problem getting back to 172.26.0.69. Is it always like this?
ASKER
It is on a different subnet here at the main building. Both go through the same pipe out the building. Where the route hits 172.26 it is out external interface.
giltjr - when you say it is having problems getting back to .69 what are you refering to?
Thanks!
giltjr - when you say it is having problems getting back to .69 what are you refering to?
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks. Can you let us know what the problem was? This way others can benefit from it.
If it was a wireless problem I would expect to see the delay on the local end, not the remote end.
What is the difference from IPCONFIG/ALL from a wired vs a wireless client?