- Joined
- Jan 24, 2011
- Messages
- 5
- Reaction score
- 0
- Points
- 1
- Location
- Sydney Australia
- Your Mac's Specs
- Which one? I have ten. Current one is MacBook Air (late 2013)
Gday All,
Sorry if this has been asked before. I've a bit of a look but cannot find anyone else with the same problem although look similar.
Most days; after about 30 minutes our Airport network drops out and users lose contact with the network. Why?
Our network consists of a desktop (2.66GHz Intel Core 2 Duo running 10.5.8) connected to the internet by a standard ADSL modem and connected to the three laptops in the house by Airport using the desktop as a 'host/server'. At the end of each day we completely shut down the desktop for the night and reboot it next morning.
The laptops are
MacBook 2.4 Ghz Core 2 Duo with AirPort Extreme (0x14E4, 0x8D) running 10.5.8
MacBook 2.26 Ghz Core 2 Duo with AirPort Extreme (0x14E4, 0x93) running 10.6.4
iBook G4 1.07 GHz PowerPC G4 with AirPort Extreme running 10.3.9
None of the other macs are on the network (most are too old)
Sometimes simply restarting airport on the host computer and the laptop clients can reconnect but this is never a reliable connection if it works. It is more than likely to drop out again.
Most times it goes straight to staying dropped out. Restarting the host fixes the problem for the rest of the day almost every time.
My son is a bit of a hacker and has discovered that if we force quit these processes:
bootpd
mDNSResponder
nmbd
ntpd
configd
in this order we can regain AirPort connection without rebooting the host. This also fixes the problem for the rest of the day almost every time.
To me this seems like the electronic equivalent of kicking it in the gonads - hard. Seriously I am concerned that we are fiddling around with activities best left alone.
What do these processes do and are we destabilising the system by terminating them?
Sorry if this has been asked before. I've a bit of a look but cannot find anyone else with the same problem although look similar.
Most days; after about 30 minutes our Airport network drops out and users lose contact with the network. Why?
Our network consists of a desktop (2.66GHz Intel Core 2 Duo running 10.5.8) connected to the internet by a standard ADSL modem and connected to the three laptops in the house by Airport using the desktop as a 'host/server'. At the end of each day we completely shut down the desktop for the night and reboot it next morning.
The laptops are
MacBook 2.4 Ghz Core 2 Duo with AirPort Extreme (0x14E4, 0x8D) running 10.5.8
MacBook 2.26 Ghz Core 2 Duo with AirPort Extreme (0x14E4, 0x93) running 10.6.4
iBook G4 1.07 GHz PowerPC G4 with AirPort Extreme running 10.3.9
None of the other macs are on the network (most are too old)
Sometimes simply restarting airport on the host computer and the laptop clients can reconnect but this is never a reliable connection if it works. It is more than likely to drop out again.
Most times it goes straight to staying dropped out. Restarting the host fixes the problem for the rest of the day almost every time.
My son is a bit of a hacker and has discovered that if we force quit these processes:
bootpd
mDNSResponder
nmbd
ntpd
configd
in this order we can regain AirPort connection without rebooting the host. This also fixes the problem for the rest of the day almost every time.
To me this seems like the electronic equivalent of kicking it in the gonads - hard. Seriously I am concerned that we are fiddling around with activities best left alone.
What do these processes do and are we destabilising the system by terminating them?