If you've had a problem keeping your clock accurate using network time, this tip may help out. Network time is controlled from the System Preferences, Date & Time pane, Network Time tab. Symptoms of the problem include:
The "Use a network time server" checkbox turning itself
off after a restart.
The clock drifting even though the "Set Time Now" button seems to work.
OS X has a confusing "feature" that makes diagnosing the problem difficult: After a restart or after disabling and enabling the "Use a network time server" checkbox, OS X attempts to synchronize the time using a different method than when you press the "Set Time Now" button. After a restart or enabling "Use a network time server," OS X sends Network Time Protocol (NTP) messages using the User Datagram Protocol (UDP) from port 123 of your machine to port 123 of the specified NTP Server. The server replies from port 123 to port 123 of your machine.
After pressing the "Set Time Now" button, OS X sends NTP messages from a very high port number
(about 49150) of your machine to port 123 of the NTP Server. The server replies from port 123 to the same high port number of your machine.
Read the rest of the article for information on diagnosing and repairing this problem...
I stumbled across the fact that QuickTime Player (and most any QuickTime capable application) can play Cisco IPTV streams. There is no built-in way in QuickTime to find and open them. However, if you have a .sdp file for the stream, QuickTime will open and play it. One way to get an sdp file is via the program MacTV.
Select the stream you want in the list and choose "Save SDP..." from the file menu. The default helper for .sdp files, as it happens, is QuickTime Player. So now you can just double click the document to play in QTP or perhaps you'd prefer to drag it onto BBEdit or....
What's the point? Why not just use MacTV? Perhaps little, but if nothing else, QuickTime Player has controls for brightness, contrast, bass, treble, etc (possibly only in QuickTime Pro - not sure) while MacTV doesn't. Also a handy thing about .sdp files is that you can schedule the opening of them via cron (try Cronnix for an OS X GUI to cron) or any other similar scheduling tool.
I recently purchased a new Airport Extreme Base Station, only to realize afterward that my printer was not listed on Apple's Airport Extreme Printer Compatibility webpage
I was even more disappointed to find sparse documentation inside the base station box for different ways that a printer could be configured through the base station. Fortunately, after plugging in the printer to the base station, the printer was visible in Print Center by setting up a new "Rendezvous" printer.
If your printer works in Jaguar 10.2.3, I'm guessing it will work with the new Airport Extreme Base Stations, even though Apple and its business partners would prefer you buy a new printer. I have an Epson Stylus Photo 750, and it works great, wirelessly now.
[robg adds: I don't have an Extreme unit to test with, so I can't verify this one...]
I've experienced that the Princenter.app's option "automatic installation" of a PPD is not a good way to configure a LaserWriter Pro 610 under Jaguar.
After a lot of unsuccessfully attempts - and a growing wish to come back to OS 10.1.x - finally I've tried the following way:
Remove the printer (that doesn't work at all!)
Select 'Other' in the pop-up menu of Installation window
Select the Laserwriter 630 PPD in 'Classic's System Folder -> Extensions -> Printers Description folder.
I used a second AirPort base station (version 1, grey) to extend the range of my first base station (or any other access point) for sharing my internet connection. With that, I'm able to access the internet with a remote computer that has no direct access to the first AirPort base station. Please don't tear me appart for the use of the word "repeater / bridge". I know, it's technically not correct, but I think it describes somehow what I was doing here. Here is how I set it up:
Base station 1 -> Computer 1 + Base station 2 -> Computer 2
I found this out when setting up my Wi-Fi network.
To access LocalTalk/AppleTalk printers through wi-fi TCP/IP connections (when using non-AppleTalk wi-fi routers), use LocalTalk Bridge to connect LocalTalk to Ethernet. Then use an OS X machine on the Ethernet to share the AppleTalk printer to TCP/IP. In more detail:
I have an iBook (OS X.2) connected to my home network through a Linksys Wi-Fi switch. I have a G4 (OS X.2) connected through 100bT. Also I have a PowerMac 7300 (OS 8.5) connected through 10bT. The 7300 is also connected to a LocalTalk/AppleTalk PostScript LaserWriter 4/600 printer.
Using the free Apple control panel LocalTalk Bridge, I could connect the LocalTalk printer to the Ethernet AppleTalk network. When I turned on Appletalk on the G4, I could print directly to this LaserWriter, as long as the 7300 was turned on. So far so good. But the Linksys Wi-Fi switch does not send AppleTalk packets to my iBook, so I could not print from the iBook.\
However when I turned on printer sharing on the G4/OS X machine, my iBook saw the LocalTalk LaserWriter as a shared printer of the G4. Now I can print directly from my iBook. The only drawbacks are that both my G4 and my 7300 need to be turned on. Also I found that direct printing from Appleworks would result in no fonts send to the printer. When exporting print jobs from Appleworks to PDF and printing the PDF, this problem is resolved.
For several months now, my automated nightly incremental backups to an NSF-mounted remote device have been failing. After many false leads, I finally traced the problem to the program automount in /usr/sbin.
This program causes the remote disk to disappear when you log out, and things like remote backups at 2am will then fail. They even fail if you are logged in but the screensaver comes on. This unfortunately is (now) the default behavior, and automount, without asking or warning you, hijacks your NFS mounting point, moves it to its own directory, and creates an alias. I wonder if Bill Gates wrote this? Anyway, you can turn it off by editing the file /etc/hostconfig and changing the line AUTOMOUNT=-YES- to AUTOMOUNT=-NO-.
This will take effect after a restart. If you currently have NFS devices that have been automouted, you will have to unmount them by hand, delete the alii created by automount, remake the corresponding directories for the local mount points and then remount.
This can all be done in NSF manager except for the last step, which now fails with a cryptic "system error 255". You can get around this by mounting with the root command mount -a.
Now my backups work at 2 am like they are supposed to.
I wanted to share my USB printer with my roommate's Mac. It wouldn't work - no printer would show up in the Rendezvous pane of the Add Printer dialog. It turns out the problem is with AT&T Cable; or rather, the way it does things.
AT&T Cable in San Francisco is an odd beast. Their central will hand out DHCP addresses to any host connecting to a cable modem - rather nice, since you get a mostly-static global IP address for each machine (at least four allowed per household), nor is a "router" required - a hub is plenty enough. Sadly, the IPs they hand out are rarely on the same class C (Subnet Mask 255.255.255.0) network - the network mask their DHCP server hands out! What this means is that Rendezvous will not work between machines in the same house.
The solution is to give the machines a secondary IP address which is on a shared IP subnet. My method is to use the command /sbin/ifconfig en0 alias 192.168.1.?, where ? is a number between 2 and 254 - different for each machine. The 192.168.?.? subnet is "private," which means it won't colide with any global addresses.
This solved the problem instantly. A little bit more work, and I had a startupItems script put together as well (contact me for details) that adds the alias every time the machine boots.
It is VERY cool to be able to share a USB printer between two Macs with nearly no effort.
I recently built myself a Redhat box (see this thread on the forum site) to take the development site serving workload off of my G4. I mount the Redhat's web server directory via SMB, so I can edit and test locally on my Mac with jEdit. Last night, I shut down the Redhat box without disconnecting the SMB share first. Bad bad move.
I had left jEdit running; it went spinning beach ball nearly immediately. So did the Finder. The terminal was open, so I headed there to try to see what was happening. I was pretty sure it would time out eventually, but I wasn't sure how long that would take. In the terminal, after typing cd /Volumes to see what was there, a simple ls crashed the Terminal.
A few minutes later, things tried to return to normal, but the Finder was still locked up, and even quitting and restarting it via the Terminal had no effect. Then the dock died. I finally wound up rebooting. I had a similar experience at work when I shut down my shared Windows machine before disconnecting the share on my iBook; you'd think I would've learned by now!
So if you're working with SMB shares (and perhaps other server types as well, I expect), be sure to disconnect them before shutting down the server! Also, if anyone has any workarounds to return the box to working order in a more timely manner (until Apple can hopefully fix this issue!), please post them here.
In 10.2.3, Appletalk is its own network port (which goes against my understanding of the term port, as it's really just a protocol over the ethernet port). As such, all three (Modem, Ethernet, and Appletalk) can be used simultaneously and Appletalk / Localtalk devices can be used and auto-detected while also accessing IP devices. Prior to 10.2.3, you had to choose either PPPoE or Appletalk in the Network Preferences, but could not access both over ethernet.
An example of how this can be useful: I've got an old TI printer connected to an Asante Ethernet / Localtalk bridge. My Internet connection is a DSL modem. I run the bridge and modem to a basic ethernet hub and out to my machine. Prior to this, I had to disconnect from my DSL modem to reconfigure my network settings using Location Manager and some scripts to connect to the printer (actually, it would randomly connect to both at times, but never reliably and it would reset on reboot). Now I can just print as you'd expect.