View Single Post
  #10   Spotlight this post!  
Unread 02-12-2013, 15:46
techhelpbb's Avatar
techhelpbb techhelpbb is offline
Registered User
FRC #0011 (MORT - Team 11)
Team Role: Mentor
 
Join Date: Nov 2010
Rookie Year: 1997
Location: New Jersey
Posts: 1,624
techhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond reputetechhelpbb has a reputation beyond repute
Re: ping and tracert networking question

Quote:
Originally Posted by Ether View Post

Guys:

My internet connection has been working flawlessly for the past 11 days (ever since I changed the DNS server setting in my router as suggested by Jared). So that seems to be a pretty strong indicator that the problem I was experiencing is not the link between my radio and the local tower. Would a WireShark capture of several tracert or WGet transactions shed any light?
Tracert probably not, the wget might.

The point I was making is that wireless has a habit of concealing subtle issues that might be temporary or recurring. TCP/IP is a pretty reliable protocol it'll generally cover for quite a bit before a total link failure.

On a long distance link you'll quite commonly loose link quality and never really notice it because the protocol will retry the delivery.

A prime example is a highly directional link I inherited from someone. It would only fail on windy days in the summer because there were trees that grew high enough that when the wind caught them and they were full of leaves it made strange interference. The link would rarely go completely down. People would start experiencing performance issues on large downloads and partially loaded pages (most of the page would load but a few large images would fail).

Quote:
I did notice something weird though. In the router's "Connection Status" window it always shows the "Lease Expires" data/time equal to the "Lease Obtained" date/time. It was not like this in the past. Is this normal?

Lease Obtained Mon Dec 02 19:24:21 2013
Lease Expires Mon Dec 02 19:24:21 2013


24 hours is a common DHCP lease but that appears to be in a permanent state of assigning an IP.
Have you tried to power the computer off and on again (props to the "IT Crowd")?

In the big picture, on the other hand, if it's working for now it might be better to leave it be.
Plug and pray

Last edited by techhelpbb : 02-12-2013 at 15:58.