Quote:
Originally Posted by Ether
The above does not fit the facts of my case:
My internet was flawless for the first three years (see post #19), and I still have the exact same line-of-sight access to the local tower (no new structures erected in the vicinity).
The problems I had been experiencing recently (the subject of the thread) are not correlated with weather conditions (see post #22). Downpour, dense fog, freezing rain, blizzard, gale force winds, electrical storm: no correlation. |
It's possible you could still be experiencing problems either from weathering of the assemblies, the cables or equipment issues.
For example: when motherboard capacitor start to fail the computer may start exhibiting random instability.
That very same computer probably worked for years before the issues presented.
Unfortunately the state of 'working' in wireless IP links comes in many shades.
It is even possible that over time you've inherited a little mechanical slippage and the antenna pointing is slightly off.
Anyway it is really neither here nor there, if you are happy with the performance what's the sense of worrying about it?
Just as a matter of sanity when I start to have issues like this with links I try to put myself into a position where I can see clearly if there are link level issues so usually I deal with that when the urgency is low.
Quote:
|
So having identical "expires" and "obtained" timestamps is definitely abnormal? For example, it's not a synonym for "no expiration"?
|
If you go to a command prompt and do an:
ipconfig /all
Does that also report the same obtain and release timestamp for that network interface?
It should because those values are stored in Unix timestamps in the registry.
I looked at 3 different Windows systems: XP, 7, 8
All pointing at DHCP servers with infinite leases.
The obtained time reports from the last update.
The renew time reports when the lease expires.
However the IP handed back to that MAC address is the same.
The servers are Windows 2003 and Windows 2008.
There is a single exception I could find:
Microsoft Remote Access Service (RAS) will clone the timestamps because it hides from the client that the assignment is DHCP and it's handing it off from a pool at startup.
In that case it should be dated: Jan 1st, 1980
This happens because RAS hands back an incomplete DHCP handshake and if you look at the DHCP server side the actual time stamps are there.
In all likelihood your equipment is NATing your public IP and some piece of equipment is handing out DHCP internally to your side of the connection (which facilitates the NAT process). Perhaps there's something a little off with how the DHCP has been implemented. However again if it's working you may as well leave it alone till it doesn't but so far as I can see generally what you see there is not normal.
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.
Might just be the result of your router and nothing else.