I have never had a problem with Samba and networking. The only thing that irritated me was when in Windows, my laptop would be seen as "Samba 2.2.3a (build 26) iBook (IBOOK)." This is long and silly. I wanted for it to just say the name of the computer. After reading a few other hints on Samba, I got started. I figured the clue would be in the /etc/smb.conf file (which it is). The first step is to back up the conf file. In terminal type:
% sudo cp /etc/smb.conf /etc/smb.conf.bak
Second Step. Edit it. Open it up and you'll find there are a few categories each in [brackets]. The first one is called "global." This contains all the settings for Samba in general. The default is this:
Note that there maybe an extra line if you have changed the name of the workgroup. After encrypt passwords = yes, simply add another line which says server string = %h - this will mean (after saving and restarting Samba) that Windows will just see your Samba server by the name of the computer. Alternativley, replace the %h with any text you like and that will be the name of the server.
By the way, Windows XP lists the computers by the name, and then the address in brackets afterwards. So now my iBook in windows looks like iBook (Ibook). Still, it doesn't confuse the people on my network that doesn't know who Samba is anymore!
Although not advertised, it is possible to connect your Mac to the Internet through a Bluetooth Access Point. I suppose here the access Point provides PPP LAN access.
0n 10.2.5, use the Bluetooth Serial utility (installed in Utilities folder) to create a new port. Give it a name like "BTAccessPoint" (name is one word). Hit "Outgoing," and pick the desired Bluetooth access point by clicking on the "Select Device" button. Discovering your access point services, select "LAN access using PPP." Note: to be able to discover the access point, make sure the access point is properly set up, and that, in particular, it does not filter out your MAC address...
Select the "Show in Network Preference" option, and eventually other encryption or authentification settings your Access Point may require (not tested with that option on on my setup).
Select RS232 on Port type. Close the setup window. Now the newly created port should show up in the port list (with BT AP name) and be selected. Quit BT serial port utility.
Go into Network preferences. On opening, it should show a newly detected port (BTAccessPoint). The TCP-IP tab should be set to "Using PPP." On the PPP tab, leave the phone number blank. Eventually fill in username and password info if your Access Point PPP settings require them. On the Modem tab, select "Null Modem 115200" modem profile.
You are done! Make sure this nework port is *before* other eventual network interfaces, since this order is the load order. Select the port in Internet access app (or menu), hit connect, and there you go! Good luck.
[robg adds: I haven't tested this one, as I have no Bluetooth enabled phones.]
Finally I can print from Acrobat to my PostScript printer connected to my Linux file server. I was always wondering why certain applications could, and yet others could not, print. Among those that couldn't were Photoshop and Acrobat - very annoying!
This nice page resolved all trouble by exchanging a small part of CUPS 1.15 with the latest 1.2 updates (yes, an uninstaller is included!). Thanks a lot to the author!
[robg adds: There was a previous hint that discussed other issues related to Linux printers...]
I just created a tutorial on setting up Mac OS X to print to the "Windows only" print server attached to the D-Link 713P home router/access point. The D-Link contains a parallel port and serial port which can be used for a printer and a modem, respectively.
I tell ya, there is nothing like being able to create a print job from the living room and picking it up in the computer room.
Switching to Mac and have tons of MP3s, Word docs, and other vital files that you really need on your Mac? Of course, you can buy Move2Mac, or any other file transfer software/special cables, but of no one wants to pay anything when it can be done for free. There's also the "Connect to Server" feature on Macs in which you can mount your PC's hard drive on your Mac's desktop, when both computers are on the same LAN and drag files onto your Mac. However, this feature is still very unstable for me a large majority of the time. It was consistently freezing up both machines in the process of transferring files. About 15 tries later, a hard reset did more than make me ill, it left my 17" PowerBook completely unbootable. I was left with no option but to completely reformat and reinstall OS X, rendering all my previous set up work on the machine.
So after reinstalling, spending countless hours awake re-setting up everything and getting over my anger, I was still back to the drawing board relative to transferring files from the PC to the Mac. So after racking my brain, I thought of something to try, and lo and behold, it worked 98% seamlessly, was absolutely free, and never once caused my Mac any trouble!
So what is this magical solution? You'd probably never think of it, actually: Yahoo Messenger. The latest versions of Yahoo Messenger for PC and Mac have something amazing built-in: when two users are logged on and sending messages and files (the files is the key here) over the same LAN, it automatically defaults to sending those messages/files via the LAN rather than the internet. This allows for speeds up to 100Mbps for file transfers between the machines connected via Yahoo Messenger on the same LAN!
I have not understood why people were not able to use iChat's Rendezvous mode to communicate with me. People stated they sent me a message, but I would never receive it. Turns out it was, in fact, my Apple built-in firewall blocking incoming iChat messages. This does not seem like it would be a hidden hint, but you would have thought Apple would have set iChat as one of the "common ports."
To allow incoming iChat connections, go to the Sharing System Preference panel, click on the Firewall tab, then click the "New" Button. Click on the Port drop down menu and select "Other." Enter 5298 for the port number. Optional, but recomended, enter "iChat" for the description.
[robg adds: I have changed the port number (it was 5289) and any references to Rendezvous, as this is really an iChat hint (see the comments below).]
If you are running into problems using Apple Remote Desktop (for example, you can't see anything but a black screen when you try to control a remote host), and have checked for UDP connectivity over the oft-cited port 3283, try this as well...
Check to see if the intervening routers and firewalls are allowing fragmented packets. Disallowing fragments is a serious show-stopper for ARD.
Hope this helps someone who may be frustrated by the problem...
When pointing the Finder or Print Center at an SMB (Windows) file share or printer (see this hint), NetBIOS names don't seem to do the trick. Mac OS X wants DNS names or IP addresses. So, a share that you "map" on MS Windows clients as MYSERVERMYSHARE has to get translated to something like smb://myserver.company.com/myshare in order for the Finder to understand it in the Connect to Server box. The problem I've found is that these mappings aren't always obvious.
Fortunately, Jaguar comes with some Samba UNIX tools that can help out with this problem, but they're kind of obscure. After much headache and stumbling through web tutorials, I wrote the following AppleScript to make them easy to use for name/address translation.
After much taking, I'm happy to be able to give something to the community!
This relates to a previous hint, where some Macintoshes do not auto-negotiate properly with the networking hardware. The current solution is to run a terminal command, sudo ifconfig en0 media 100basetX mediaopt full-duplex, which then correctly sets the media type and speed (in my case, 100basetX and full-duplex). Unfortunately for some of us, these settings don't 'stick' after a restart (the adapter goes back to autoselect), and must be re-set manually each time.
What is needed here is a process that does this type of thing for us on startup, even before reaching the login screen. This is accomplished by creating a StartupItem, and putting it in /Library -> StartupItems. StartupItem is really a folder containing two parts: A shell script of the same name as the folder, and an XML file called StartupParameters.plist.
Create a folder called setDuplex in /Library -> StartupItems, and create a file inside with the same name. The file should contain the following text:
# forces 100baseTX and full-duplex
ifconfig en0 media 100basetX mediaopt full-duplex
Make it executable by typing chmod a+x setDuplex. Note that you do not need a sudo command in the script, because it is already being run as root.
Next, create another file called StartupParameters.plist, containing the following text:
It appears that SCSI disks initialized with HFS or HFS Extended mount fine on a local machine with a SCSI card installed. However, HFS disks cannot be mounted across a local network ... but HFS Extended disks are seen and mounted by OSX and OS9. Hmmmmm.
[robg adds: If anyone can confirm this, I'd appreciate it. I don't have a SCSI drive...]