Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Software update
- Thread starter zarzar555
- Start date
- Sort by reaction score
If you do one of the following in Terminal:
You should get "Bundy-Server.local" back. This means that you (or someone) have set this computer to look for updates from a local server, rather than from Apple's servers. Many organizations do this, for three reasons:
1) save on bandwidth to the outside world (this can be expensive)
2) speed up the download of updates (since LANs are typically much faster than general internet connections)
3) control the timing of updates, so IT has a chance to vet them before they go out
To unset this you need ONE of the following lines (in the same order as before):
Code:
defaults read /Library/Preferences/com.apple.SoftwareUpdate CatalogURL
defaults read com.apple.SoftwareUpdate CatalogURL1) save on bandwidth to the outside world (this can be expensive)
2) speed up the download of updates (since LANs are typically much faster than general internet connections)
3) control the timing of updates, so IT has a chance to vet them before they go out
To unset this you need ONE of the following lines (in the same order as before):
Code:
sudo defaults delete /Library/Preferences/com.apple.SoftwareUpdate CatalogURL
defaults delete com.apple.SoftwareUpdate CatalogURLFirst, make sure that it says that for both versions, one after the other.
The next check is about dns, if someone is spoofing Apple's software update servers to make you look at "Bundy-Server.local", this could also happen then. I don't happen to know the address that SoftwareUpdate uses, so you will have to track that down. But in the mean time I would look at you DNS services to see if something is up there.
The next check is about dns, if someone is spoofing Apple's software update servers to make you look at "Bundy-Server.local", this could also happen then. I don't happen to know the address that SoftwareUpdate uses, so you will have to track that down. But in the mean time I would look at you DNS services to see if something is up there.