View Single Post
  #43   Spotlight this post!  
Unread 02-12-2013, 19:10
Ether's Avatar
Ether Ether is offline
systems engineer (retired)
no team
 
Join Date: Nov 2009
Rookie Year: 1969
Location: US
Posts: 8,120
Ether has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond reputeEther has a reputation beyond repute
Re: ping and tracert networking question

Quote:
Originally Posted by techhelpbb View Post
It is even possible that over time you've inherited a little mechanical slippage and the antenna pointing is slightly off.
If there was sufficient signal degradation to cause the DNS issue, I would expect to see problems correlated with weather conditions (dense fog, sleet, blizzard), but I do not.


Quote:
Anyway it is really neither here nor there, if you are happy with the performance what's the sense of worrying about it?
To each his own I guess, but that's not the way I approach life. If there's something amiss I want to get to the bottom of it. This has served me well time and time again over the years.


Quote:
If you go to a command prompt and do an ipconfig /all
Code:
Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
        Physical Address. . . . . . . . . : [redacted]
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.33
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 192.168.1.1
        Lease Obtained. . . . . . . . . . : Monday,  December 02, 2013 11:47:30 AM
        Lease Expires . . . . . . . . . . : Tuesday, December 03, 2013 11:47:30 AM
As you can see, the lease assigned by the router to the PC is for 24 hours. Maybe that's because the router software doesn't know what to do with the lease it's been assigned with the "expired" timestamp the same as the "assigned". As I mentioned in post #39, it has not always been the case that the router lease obtained/expires timestamps are identical. I didn't make a note in my journal when I first noticed they were equal. But for the first couple of years or so they were not equal.


Quote:
If you are game: Remove your router from the connection and use the computer directly connected.
Reboot your computer and see what your DHCP reports.
Easy enough to do. I'll queue it up for later. Debugging some software right now.