> Are you logging on with Safari first? Safari has a habit of > disconnecting and I've found almost immediate disconnects if I first > open Safari rather than Mail.app. I've also added SafariNoTimeout > which lets me select what timeout period for Safari, I think I set 10 > hours. Safari is still wierd, sometimes disconnecting while pages are > downloading saying the other side is not responding which indicates to > me that A) safari drops the connection and then tells me there is no > connection or B) when a site doesn't respond, Safari disconnects which > isn't a good thing. This seems to assume that he is using "Connect automatically" setting, which he may not be using. Even still, it does not really make that much sense -- e.g. a 10 hour timeout? That seems extreme. Safari uses whatever the internet connection is. If there is no response from the server in 60 seconds, or if the server data transmission stops for 60 seconds, it will timeout. Safari does not have the "power" to disconnect an internet connection, regardless of the connection method. Or maybe I am misinterpreting what Jack is saying? The most important thing is to look at the connection log. SIGHUP is a hangup signal -- just as the "English" message indicates, the modem hungup; it can be due to local or remote issues. A verbose connection log might tell more of the story, but it is important to note what was going on at the time of the hangup ... because it might not. An unstable connection could be a "local" problem, it could be a problem at the ISP's end ... Peter, would you be willing to run a script for me? (It will require using Terminal; I will give you exact instructions.) It gathers networking information. It will not reveal private information, nor will it change any settings. The info it will provide might be helpful in diagnosing the problem, along with some details about when this happens, and when it started happening. leigh :) (left iBook team for Core OS Networking)