I saw this hint you have about sharing a PC's Internet with a Mac over Bluetooth. That's great, but it involves too much configuration and a terminal window login every time. Here's an alternative that "just works," mainly for owners of Symbian based phones.
The PC Suite software supplied with those phones has a server that hosts such connections over Bluetooth (and also IR and cables) for the phones, but it also works with other devices, like Palms and Macs. To make it work, do the following:
On the PC:
Right click on the mRouter tray icon and make sure Bluetooth serial ports are enabled.
On the Mac:
Make a new Bluetooth serial port, called something like Bluetooth-mRouter. Pair it with the Bluetooth Serial Port service on your host PC. Then set it to Outgoing and RS232 mode. Then load up the Network prefs panel, and configure the new port. Make sure it's using PPP. Under PPP options, you can safely deselect "Disconnect if idle." Under Modem, select Null Modem 115200 and deselect "Wait for dial tone."
Now use the Internet Connect menu, select the port you just made, and then select Connect. Hey presto, Internet sharing over Bluetooth. The only limit seems to be that although mRouter can handle up to 460000bps, the Mac Null Modem driver is capped at 115200, so if anyone wants to make a better Null Modem driver, please respond.
Finally, non-Symbian phone owners can download the PC Suite freely from Nokia or SonyEricsson, too. Install them and then remove everything except for the mRouter executable from their startup menu, and they're good to go.
I am sharing files with a colleague at the office over Bluetooth. We both have the same Mac, and are up to date with all software.
When he tries to look at a folder that contains files whose name contain an ampsersand sign, the folder just appears empty. It took some time to track that down, but we could eventually easily reproduce the behavior just by adding or removing the ampersand from a file name.
I could not find any reference to this issue describing it as normal, so, to me it's a bug.
When changing locations in Network via System Preferences and the DHCP service does not provide directly a new IP address, one does not need to restart the computer. A network reset suffices. This can be given via the terminal:
I'm sure there are many other ways of doing this, but ... after hours of frustration trying to get a new Toshiba laptop running WinXP Home Edition to see our Linux Server and my OS X Ti-Book on our office network through the Network Neighborhood, I finally called in a UNIX guru friend of mine who suggested the following.
Open the Registry on the Windows machine (just type "regedit" from the "Run" command"). Then adjust the following Entry:
Change the default "Value Data" field from 0 to 1. Restart Windows and Voila! The Linux and OS X machines show up in the Windows network neighborhood.
[robg adds: In order to get my machine to show up at work, I just used Directory Access (in /Applications -> Utilities) to set a matching Workgroup name, and all was good from that point. But I have heard that this hasn't worked for others, so maybe this hint will help.]
I've tried for quite some time to get my files to print from my wife's iBook (clamshell) running OS 9.2 to the Epson Inkjet or HP Laserjet 4 on our network. The HP is directly connected to the ethernet hub and the Epson is connected to the OS X iMac via USB. I've tried using this hint, but it doesn't work, and I scoured the internet with no result. Yet, there is a simple, if not particularly elegant, way.
I've written a very simple AppleScript and attached it to my drop box folder on the OS X machine. I've placed an alias of the drop box on the desktop of the OS 9 machine (set to appear on start up). When the user of the OS 9 machine drops a file into the drop box, the Applescript is activated and the finder prints the file to the default printer.
Finding your WiFi/Airport connection broken after your machine wakes from sleep?
It appears that, with some non-Apple base stations where the Mac is using DHCP, it can forget its IP address during sleep, but does not request a new one. The best solution is to switch to using a fixed IP address, as even turning AirPort off then reconnecting to the network has little effect.
I use the following AppleScript to share my broadband internet connection with my USB-attached irDA adapter. This allows my Palm to use my network connection so I can sync AvantGo (modem sync) and download emails direct from my POP account on the net.
First you need to share your ethernet connection (don't know about modem dial-up) by pressing Start in the Internet tab of the Sharing control panel. Then edit the script below and insert the following details (all are needed):
Your Mac OS X password (you must be an administrator)
The name of your IrDA device. In a terminal window type ls /dev/tty*. Copy the one that starts tty.IrDA.
The IP address of your primary DNS server (for your internet connection)
The IP address of your Mac
An invented IP address for your remote device (e.g. Palm) that is not being used by anything else. Often just take your Mac IP Address and add 1 to the last number.
I have set up a G4 with OS X to serve as a file server in a mixed environment. For PCs with Win98, XP and NT to access the server, I had quite some config work to do with the Samba setup. Everything was smooth, but some PC users could still not authenticate with the OS X Samba server. While investigating the problem, I discovered some discrepancies with the generic Samba docs and the OS X Samba version with respect to password handling. Effectively, I had three options to change passwords for users on the OS X server:
Directly change the Unix password from a telnet session with asswd
Using the samba tool smbpasswd
Using an external Mac(!) with AppleShare and using the "change password" dialog there.
It turns out that the smbpasswd command had no effect at all, even if a /var -> db -> samba -> smbpasswd was there, it was ignored.
The method via AppleShare changed the Unix password and the Samba password stored as a hash code in /var -> db -> samba -> hash -> Username. It is this hash-file (and not the smbpasswd file) which controls the access to the server. The command smbpasswd however, does not change this hash file, only the AppleShare dialog was successful.
[robg adds: I haven't tested Samba connectivity from anything other than Win2K and WindowsXP boxes, so I can't verify these claims, but thought they might be useful to someone.]
I was looking at some of the previous hints and did not find anything useful as far as printing to a shared printer (CUPS) in Linux. I have an old Pentium that is set up as my Samba / share / printer / etc. Currently, Windows can print to it fine via Samba (check the docs - with newer Samba versions, it requires adding two lines to the smb.conf file). As far as adding the printer to your Mac (OS X 10.2.6), it's really easy (after you figure it out). Start by going to http://localhost:631/ with your favorite browser. Go to the Administration section and click on Add Printer. On the first screen with Name, Location, and Description, most of this is irrelevant. Pick a name, enter some descriptive info, and click Continue.
On the next screen, click the Device pop-up menu and select "Internet printing protocol (http)" and click continue. On the next screen, for the Device URI, enter http://192.168.1.1:631/printers/deskjet. Of course, you'll need to change the IP and name of the printer (mine is deskjet) to match your setup.
Then, make sure you select a driver that matches up with your printer, so you can change some of the printing options. I'm using a DeskJet 3420. Really inexpensive and works great.