Musings and Mutterings

They are doing construction on interior of the office's back entryway several floors below me. They're using some sort of grinder to clean the floors before putting the tiles down, have been doing so all day.

It is driving me up a wall.

My office is directly above the entryway, and the sound (a pulsating squeeking noise) is resonating through the stairwell and into my office.

Hopefully this will be the only day it's running.

Had a nice talk with Rogers technical support. The problem was not resolved, but we concluded that the Airport was not hanging due to the DHCP updating the IP address assigned to the Airport's MAC address; that only takes place once every two weeks. Nothing is happening on the Rogers network that explains these types of periodic errors. This problem has only happened once in the past and they concluded that the problem was with the Airport, not the modem. They can only guess that something in the Rogers cable modem that is not in the DSL modem is causing problems with the Airport.

They suggest plugging the modem directly into the laptop for 24 hours and see if the connection drops. If it does, we record the light activity on the modem and the time we noticed it.

I tend to agree with the assessment. The modem (and ethernet cable) works consistently with the laptop (but a 24-hour connect test will confirm that), while the Airport works consistently with the DSL modem (based on more than a year of continuous use). When the Airport hangs, the modem still communicates happily with the Rogers network (their diagnostics indicated that the modem connected to the internet and functioning properly when I had no internet connection here), but the Airport communicates happily with computers on the wireless network (including piping music through to the stereo). All that happens, is the throughput of packets between the computer and the modem ceases to be managed by the Airport, an issue that is resolved by resetting the Airport.

A thought that came to mind is whether the NAT ceases to resolve packet readdressing correctly when it updates the internal IP address. One way to test this is to lock the laptop's and G5's MAC addresses to specific internal IP addresses. Problem is, I've watched the IP address change on the laptop while using it and the internet remains active.

I used to day this back in the days when I was a network administrator, but I say it again: intermittent problems suck for being solved!