11-13-2011 10:07 AM - edited 03-07-2019 03:21 AM
What would I be missing here to eliminate the 'request timed out' and high latency value.
TIA.
11-14-2011 02:15 AM
hi feisty,
what is the result if you ping the local GW from the laptop.(guess its across the w-lan link, right?)
and what is the result if you ping the local GW from the DNS-server?
cause if you are able to ping the local GW´s without any problem then L2 connectivity seems to work fine, then L3 might be a problem.
or is there a difference if you ping from laptop to dns-server, or from dns-server to laptop?
regards,
florian
11-15-2011 10:06 AM
Say we got a L3 problem, how can this be resolved?
11-16-2011 12:10 AM
hi feisty,
first i would try figure out where the problem really occurs.
what are the ping results if you ping from the dns-server to the core switch?
or what are the ping results if you ping from the dns-server the first network device?
try to isolate the problem as far as you can.
IF a L3 problem would be present, then you would need to check why it takes so long to route between the different subnets.
what kind of device is responsible for the routing?
can you tell me a bit more about your network setup?
florian
11-16-2011 12:39 AM
Can you post the traceroute?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide