The Quick Way to Connect to a Network Drive using Mac OS 10.5 Leopard

I’ve posted a few times about the problems I’ve had connecting to a network drive using Leopard. Previously I posted about how Leopard was able to connect to a network drive, but wouldn’t show the contents of the shared folder. After a lot of testing, and a bit of luck, I followed that up with a post on how I was able to browse the folders on my network drive. Now, I’ve found a way to connect to my network drive and browse the folders almost immediately. Although this method may sound a bit convoluted, there are just four steps. As I only have my MacBook to test with, I can’t guarantee that this will work for you, but I don’t see any reason why it shouldn’t.

Step One

Connect to your network drive in the usual manner. Either use the Command-K shortcut, or from the Menu Bar use Go -> Connect to Server. In either case, you’ll be presented with a Connect to Server dialog box. The server address should be specified as:

smb://network.drive.ip.address

Click the Connect button and wait for Finder to connect to your network drive. If you have more than one shared folder set up on the drive you’ll be prompted for the folder that you want to connect to. Once Leopard has connected to the shared folder a new Finder window should open.

Step Two

Open Terminal from Applications -> Utilities -> Terminal. At the prompt, type the following command:

sudo smbclient -L NETWORK_DRIVE_NAME

The NETWORK_DRIVE_NAME refers to the the Windows name for your drive and is usually set using the configuration interface for the drive - this may be a web interface or an application, the exact details will depend on your specific drive. When you press Return, you’ll be prompted for your password. Type your password and press Return again. When you run this command, you should get a response like this:

Receiving SMB: Server stopped responding
session request to NETWORK_DRIVE_NAME failed (Call returned zero bytes (EOF))
Receiving SMB: Server stopped responding
session request to *SMBSERVER failed (Call returned zero bytes (EOF))

Although the Samba Client returns with an error message, don’t worry, you’re still on track to be able to browse the drive contents.

Step Three

Restart the Finder. This is achieved by typing the following command in Terminal:

sudo killall Finder

Once this command has been entered, the Leopard Finder will restart. You’ll notice that your Desktop icons disappear, as will any open Finder Windows. Your Desktop icons should reappear almost immediately.

Step Four

Repeat Step Three:

sudo killall Finder

Open a Finder Window, and under the Shared section your network drive should be listed. Click the drive name, and then double-click the shared folder name. You should now be able to browse the contents of the drive.

Important Notes

  • I don’t know why, but the Finder has to be restarted twice for this work.
  • The Terminal commands must be run using sudo or as root (using su), even if you are logged in as an adminsitrator. If you are an administrator, you’ll be able to run the smbclient command and the killall command, but the process just won’t work.
  • I have no idea why this works, or how, I just know that it does work for me.
  • I’d recommend that you close all open programs while doing this, just in case. Using the killall command may have some strange effects on open programs, or lead to system instability.
  • Once again, I haven’t been able to test this on any other system other than my own, so your milage may vary.

If You Found This Post Interesting, Then You Might Also Like:

One Comment

  1. Rob CANADA Mac OS X Safari 523.10.6
    Posted Sunday, 24th February, 2008 at 20:46 | Permalink

    Weird… I used this procedure for a Mediasonic NAS HD9-SU2LAH. The device worked fine with SMB on Linux and Windows Vista (which was running on VMWare Fusion on my MacBook) but was not at all correctly with Go-> Connect to Server until I read your article. Man what a headache! Thanks for the info, you saved me a trip back to the store to return this crap enclosure!

6 Trackbacks

  1. By whatithink » My Network Drive Now Works with Mac OS X Leopard IRELAND WordPress 2.3.1 on Tuesday, 18th December, 2007 at 05:48

    [...] I’ve found an easier way to force Finer to recognise the contents of a network drive. You can read more about it here. [...]

  2. [...] I’ve discovered a better way to force Finder to browse the contents of a network drive. You can read more here. [...]

  3. By whatithink » Forcing Time Machine to Use a Network Drive IRELAND WordPress 2.3.1 on Tuesday, 18th December, 2007 at 12:59

    [...] I’ve discovered a better way to force Finder to browse the contents of a network drive. You can read more here. [...]

  4. [...] I’ve discovered a better way to force Finder to browse the contents of a network drive. You can read more here. [...]

  5. By whatithink » The Most Interesting Announcement at MacWorld? IRELAND WordPress 2.3.2 on Wednesday, 16th January, 2008 at 03:47

    [...] know that I, along with a large proportion of Leopard users, have been experiencing problems using Time Machine to backup to a NAS drive. This announcement confirms that using Time Machine to backup to a a network drive will be [...]

  6. By whatithink » Leopard Update 10.5.2 to be Released Friday IRELAND WordPress 2.3.2 on Wednesday, 23rd January, 2008 at 21:13

    [...] SMB support is fixed, so I won’t have to go through a convoluted process to get Leopard to recognise my NAS drive. Share and Enjoy: Share This [...]

Post a Comment

Your email is never shared. Required fields are marked *

*
*

CAPTCHA image

Submitting a comment on this site means that you've accepted the following rules: 1. Comments are owned by those who post them. By posting a comment you agree to allow your comment to displayed/ used on this site with attribution to your name and site. 2. You agree to be a grown up. This is the Internet and people will disagree with you. Argue your point of view rationally without resulting to childish name calling. 3. Inappropriate comments will be deleted. As to what constitutes "inappropriate" - here's a short list: I won't tolerate spam, comments that are created by a bot, or a comment that is written purely to troll, to disparage or to insult. At the end of the day, this is my site, so I decide what's appropriate. 4. Language: I'm not a prude, but strong language just for the sake of strong language is not acceptable. In other words, use sparingly.