Hi! First of all thanks for this site.:)
I drop these few lines to provide some help, if needed, about a issue i've read here some weeks ago. To make a long story short, i have made a startup script to enable the network hacks you posted here to encrease the TCP receive windowsize:
sudo sysctl -w net.inet.tcp.recvspace=64960
(i've increased a little the original size...eh!). and the one that deals with the delayed ack:
sudo sysctl -w net.inet.tcp.delayed_ack=0
The problem with these commands is that they reset to default on every restart (if you have to restart a machine with OS X on it, eh eh!). So, i've made a little folder to put into your StartupItems folder (/System/Library/StartupItems) and you're set. This little script enables these tricks on every restart. Download it here. You have to su to root to copy it to the desired folder (of course!).
Hope it helps!
[Editor's note: I have not tried this on my machine.]
Living in Europe, the mobile is my daily companion and so are my needs to connect remotely to my office. All the messages I read about the support of IrDA have been negative, telling me that the IrDA is not strategic any more for Apple anyway.
What a surprise when I did a new installation with the Mac OS X 10.1.1 CD coming with the new PbTi 550MHz: IT WORKS! I can choose the infrared connection using the Network Preferences and just by copying the Nokia modem scripts from Mac OS 9 I'm able to connect remotly to my office again. One big step to MacOS X in my daily business for me.
[Editor's note: I'm not sure if this is news or not, but everything I've seen has certainly indicated that IrDA was not supported on the newer Macs in OS X.]
We've had the ability to create share points when using personal file sharing for quite some time. Simply click a folder and select File -> Sharing, set your options, and go. With OS X, that functionality seems to have disappeared. According to Apple, we need OS X Server for this, but that is not so. Here's how you can create your very own share points in Mac OS X:
Open NetInfo Manager and authenticate.
Create a new subdirectory in /config/SharePoints/ (click on config, then on SharePoints, then select Directory -> New Subdirectory).
Set the name value to be what you'd like the share to be called (double-click on the Value column next to name).
Add a new property (Directory -> New Properyt) and name it directory_path.
Add a new value for directory_path. The value needs to be the path of the folder or volume (for example, /Users/username/Pictures).
Save your changes in NetInfo.
In the Finder, set the privileges on the folder or volume you'll be sharing. Do Show Info, then Privileges, and pick what you like -- Drop Box, Read Only, etc.
Stop and restart the AFP Server from the Sharing preferences panel.
Connect from a client and they will see the new share.
Notes: Users with admin privledges may not see the new share point, since they can see all volumes from the top anyway. Also, if you share items with spaces anywhere in the path, do not quote or otherwise escape the spaces when you add the directory_path into netinfo. If the volume being shared is read only (a CD ROM, for example), then just skip step seven.
[Editor's note: This is probably the most useful tip I've seen in quite a while! I just tried it, and it worked exactly as described - my "Pictures" folder became available as a read-only volume to the AppleShare network - slick!. I wonder how difficult it is to wrap a GUI application around updating NetInfo?? That would be a killer OS X app!]
I was having some odd connection problems with my Apple powerbook internal v90 modem. Random connection failures and disconnections. So I started looking at the modem script (inside /library/modem scripts). I read somewhere that with modems it's better to start simple so I commented out the existing init string and replaced it.
(Note: The exact line in the script may be different from that shown above, there are several versions of it. In the apple script it is below "label 3")
I seem to have had fewer connection problems. Although I can't say for sure that this alteration is the cause, and I'd be interested to see if this changes things for other Apple modem users. The side effect is that you cannot see the connection speed anymore.
[Editor's note: I'm unable to test this myself. You should probably make a backup of your script file before changing it.]
Depending on your kind of connection to the Internet, you may be able to improve your network performance under OS X by tweaking the TCP receive window size. In my case, I was downloading the OS X 10.1 Developer Tools, which consists of 19 segments, 18 of which are 10 MB in size (the last being around 7 MB). A typical segment download took me 8 minutes, but after the tweak it was cut in HALF! Needless to say this is an immense improvement, considering that I was still using the same connection. You can tweak the TCP receive window size by doing this:
%sudo sysctl -w net.inet.tcp.recvspace=40960
In this example I'm changing the size to 40960, or 40 KB. OS X defaults to 32 KB which is adequate for most connections, but since you have better knowledge of network conditions, you can make use of it to get results like I did. Experiment with other values to find the optimum.
Mac OS 10.1 with Samba built-in is a life saver. But without 3rd party CIFS clients, such as Sharity, I can't browse the resoruces on Windows servers. I have Sharity student license but have found it's inconvenient when dealing with many Windows servers -- only 2 connections allowed at a time. In order to check the resource on the third server I have to get into Sharity and disconnect one of the logged in servers. A few days ago I found something interesting: .nsmbrc and smbutil.
.nsmbrc is the configuration file for the Samba connections. The personal configuration file is in your home directory ~/.nsmbrc (don't forget the dot), and the global configuration file is at /usr/local/etc/nsmb.conf. For example, you can have this in your personal .nsmbrc file:
Now when you connect to a Windows server via Finder's Connect to Server command, the Workgroup field in the login panel is automatically filled in. Settings in .nsmbrc can also be used by smbutil.
smbutil is an interface to SMB requester. It has many functions for Samba file systems and logging in/out to the Windows server. However, the ability to browse Windows resource is the most useful one.
% sudo smbutil view //Account_Name@Server_Name
You'll be asked for your local password, then your windows password. For servers in different workgroup, use this:
I still can't figure out why smbutil only allows administrators to view resources. If you execute smbutil without sudo, you'll simply get an error. Please refer to the man pages of smbutil and mount_smbfs for more information.
Mail.app doesn't support SSL or TLS. I don't like sniffable passwords in general and really don't like them when the system has a wireless connection. Here's how to make it easy to use tunnel IMAP or POP3 through SSH. As a bonus, SSH supports compression (-C), which
may improve your transfer speeds.
SSH tunneling requires a remote server with SSH. This does not need to be the same server you're retrieving mail from - you might ssh into a
login server on the same network as your mail server. MAILSERVER and SSHSERVER refer to the IMAP/POP3 and SSH servers respectively.
Read the rest of this article if you'd like a detailed how-to on setting up secure mail transfer.
Curious - changed the "Options.." for "AppleShare Client" for Mac OS X and not know how to return those settings to the defaults?
If you have played around with the options found behind the "Options.." button on the login screen for a server when using the Mac OS X Client, and can not log onto a server any more, or received the error message "-5002 Bad UAM," then you might find this helpful.
The options that can be changed in the Options dialog are:
Add Password to Keychain
Allow Clear Text Password
Warn when sending password in cleartext
If any options are changed, and you are unable to return to this dialog to undo those changes, you can try the following. Go to your Keychain Access application, and remove your keychain entry for that and other volumes for that server.
If that does not work, please read the rest of this article for a couple of other options to restore the full functionality of the Connect to Server dialog box.
I found that I was able to mount CIFS (Windows, for example) shares on some servers, but not others, and the cause turned out to be that the hostname of my computer was just too long.
During the OS 10.1 setup the hostname for my computer was automagically set to "Bennett Hendry's Computer" (without the quotes), which showed up in DNS as bennett-hendry-s-computer. I opened the Sharing preferences panel and changed it to bhendry-mac.
Now I am able to mount CIFS shares on any server without trouble. I also don't need to specify the longer syntax mentioned in previous hints. The syntax "smb://server/share" works perfectly every time in the Connect To Server dialog box.