My iMac G4 800 MHz Flatpanel does not have an original (and now practically unobtainable) AirPort card. Even if you find one for 100 euro or more, and it turtns out not to be a scam, you still only have 802.11b, not g, wireless. That is a problem! Here's the fix. I purchased a Belkin Wireless G Gaming adapter (F5D7330). The adapter is hooked up to the UTP ethernet port and it draws power from a USB cable (of which it has two, but one is enough). So you do not need the power adapter, and there are no net cables involved.
This has allowed me to connect to my AirPort Express router. It feels great making an 802.11g connection with a machine that is deemed not AirPort Extreme Ready.
Of course, I want to secure my network. I can set up my Base Station using the AirPort Assistant, but how do I setup the adapter correspondingly? AirPort software only works with the original unobtainable AirPort card. After I tried everything else, I read the manual. Go to System Preferences » Network » Configure and switch to manual IPv4 (or set it up as a new location). Type 192.168.2.220 for the IP address, etc. Follow the instructions in the manual which are intended for Windows. Use the reset buttons on your Base Station and adapter in case things do not work out; even unplugging the USB may be required. Success!
[robg adds: Note that this is not really a portable solution in terms of size; it's more like a typical wireless router, not a cardbus solution.]
OS X 10.5's screen sharing feature works nicely on local networks. But to control your computer over an internet connection is easy, too.
Use SSH to establish a tunnel to the computer you want to control. Be sure to use a local port other than 5900 -- otherwise the screen sharing app will complain about controlling the local screen is not possible. A good example is:
ssh -L 1202/192.168.10.10/5900
...where 1202 is the local port, and 192.168.10.10:5900 the remote destination.
Go into Safari and type in the URL vnc://localhost:1202, if you're using the local port 1202 as in the above example.
Now drag the URL to your desktop to create a link to this URL
Rename and/or change the icon for the URL link with the Get Info window.
If the tunnel is established and you click the generated link, the screen sharing app will start and show your remote computer.
[robg adds: A comment on the queue site notes "To ensure this is secure, you should ssh to the target host and forward to localhost. e.g: ssh -L 1202:localhost:5900."]
There have been several hints in the past about the contents of ARD and the networksetup command line utility. It is a very nice tool, and in OS X 10.4, it was found in /System » Library » CoreServices » Remotemanagement » ARDAgent » Contents » Support » networksetup. It is no longer there, but now instead, it is stored in /usr/sbin/networksetup.
So, if any of you were using scripts to push out network settings via ARD or a third party app like Casper, you should adjust your scripts accordingly. This change is only in Leopard, so all previoius versions of OS X can use the contents of the ARDAgent package.
So I updated our little network to 10.5, and the ability to share volumes and foelders is just great. However, I had a problem with how to enable a given group's read - write - delete - execute access to a given shared volumes: for all files that exist in that folder today, and for all files that might be created in the future. There are some hints on this problem, including cron jobs and default permission flags (umask), but none of them really worked out, especially in 10.5.
The answer lies in the advanced Access Control Entries (ACE) handling of file permissions. This involves Terminal, but Michael Watson has coded a front end for this. I asked him, and he will update the code for Leopard as soon as he finds a minute. Thus, we have to use the Terminal for now.
I've just upgraded my son's Mac Mini to 10.5, and turned on the Screen Sharing and ssh server after the initial install. In 10.4, I had long ago configured the "hidden" ARD VNC server, though alas I now find I've forgotten the password I set at that time. My son's gone to bed, but I want to play on his Mac -- what to do?
It seems that the "new" screen sharing feature is basically the same as 10.4's, and the VNC password is in the same place: /Library » Preferences » com.apple.VNCSettings.txt. The password is obfuscated by XORing it with a fixed key, so you need a little perl magic to view / set it.
[robg adds: Read on for the how-to. Please note that this isn't a security concern, as it assumes you've got ssh access to the machine in question, as well as the ability to execute root privileges on that meachine -- and if you've got both of those things, well, you've pretty much got the machine anyway.]
In 10.4, if you had a custom firewall config running, the built-in firewall configuration was greyed out in the System Preferences. Now in Leopard this is not the case ... I haven't worked out what happens when you use both configurations, built-in and custom, but here's how you get your custom firewall back:
Set the firewall option in the Security System Preferences panel to "Allow All Incoming Connections," just to make sure that the built-in settings don't conflict / interfere with your custom settings.
Create an entry in /Library/LaunchDaemons, mine is called ipfw_firewall.plist, and it looks like this. Customize to meet your needs.
If you, like me, want your separate firewall log file in /var/log, then you need to modify /etc/syslog.conf like this:
With those changes, you get your firewall logs in /var/log/ipfw.log.
The actual scripts and firewall rules here are the result of research I did on ipfw on OS X and BSD, and are the result of other people's work, for instance, Dru Lavigne. I just used their stuff and modified it to fit my requirements.
This one will definitely fall into the "the answer was so simple I'm glad nobody knows I was having the problem" category. I've read many of the posts about the disappearing WINS settings, and the inability to find Windows shares on a LAN. Here's how I got it to work.
First, your workgroup info is now in the Networking pane of System Preferences, which is most likely where it should have been in the first place. Second, if you have the default setup and attempt to change your WINS info, it will revert to default. It seems that in 10.5, the 'Automatic' location has a rigid template for WINS that cannot be changed.
So, the painfully simple solution. Make a new template, then change your WINS information so that your NetBios name is something more fitting than Macintosh, and your workgroup is ... well, your workgroup. Apply, save changes, etc. Voila!
After upgrading to Leopard, whenever I would try to mount SMB shares on my company's network, the Finder would hang interminably on the "Connecting to Server" progress dialog (the network is Active Directory-based).
My password, like many that of many people, contains some extended characters. Today I tried URI-escaping the password, and it worked! I was able to connect immediately to all shares. To URI escape a password, try the following:
When you select a server or shared computer in a 10.5 Finder window, a button appears saying Connect as. This allows you to enter a username and password for the server you are trying connect to. Under 10.4, in the case of Windows servers, this dialog also has a text field that allows you to enter the domain your username belongs to. Under 10.5, this text field is missing.
The solution is simple: enter the domain as part of the username, just as you would in the comparable Windows dialog, separating the domain from the username with a back slash ('\').
Leopard includes a fast VNC viewer for its Screen Sharing feature. You can browse other Leopard machines in the Finder and click "Screen Share..." to see their screens. You can also connect to Windows and Linux VNC servers with "Connection, New" and entering the host address.
But on Lin
ux you can go one step further. Install the Avahi software (avahi-daemon package under Debian) and create a service file in /etc/avahi/services/vnc.service, with these contents: