HELP! Using Samba in Panther

SpiicyTuna · 10-31-2003, 01:10 PM

I have no choice but to use a windows share in my job position. 10.2.8 worked wonderfully with Samba. Now that I have upgraded to 10.3 (Panther), I cannot access any windows shares. I get the error: "The Finder cannot complete the operation because some dats in "smb://<<Share Nam>>/" could not be read or written. (Error code -36)." When I tried to mount manually from the command line using mount_smbfs, I got the error "mount_smbfs: SMB filesystem is not available"

Has anyone else encountered any erros? Does anyone have any ideas? I really do not want to downgrade to 10.2 again....

SpiicyTuna · 10-31-2003, 05:59 PM

My Fix:

Fresh install while archiving my user account. When install gets to the part asking which disk to install on, choose options, then you have the archiving choices.

tncook · 11-11-2003, 08:57 AM

I'm having the same problem on a fresh install of 10.3. I can mount volumes using mount_smbfs, but not through the finder. It gives me the "smb://<<Share Nam>>/" could not be read or written. (Error code -36)" error. It worked fine in 10.2.x

edit: apparently if i specify a specific share when mounting it works, but if just trying to connect and then pick a share it doesn't.

bciesq · 11-12-2003, 08:34 AM

I came across the following at

http://www.macwindows.com/panther.html#reader

Quote:


	November 3, 2003 Darrell Kienzle has a fix based on the NetInfo Manager: I read your discussion of problems with access to SMB shares in Panther. Here's something I discovered when working with one of the betas. Fire up NetInfo Manager and browse to /users/yourname/passwd. The passwd _should_ be "****". This is a representation of a shadow password (a feature added in Panther). If you see something like "YW3273hhs," that's a standard hashed Unix passwd (which Jaguar used). If you have a hashed passwd, use System Preferences to change your password (you can give it the same value it used to be). Reload NetInfo Manager and you'll see it has changed to "****" I found that this helped enormously when trying to connect to Windows and SAMBA shares. November 3, 2003 Sean Sperte points to the Directory Access utility: One thing that helped my painful SMB browsing experience in Panther was to set the correct workgroup in the Directory Access utility app (found in the Utilities folder in the Applications folder). Once I did this, problems accessing "folders" (or drives) more than one time were solved. November 3, 2003 Dave de Groot offered the same idea, but called it a partial solution: I found that you need to add your domain to the SMB WorkGroup on your Mac. You can do this by opening the "Directory Access" app in the Applications:Utilities folder, clicking on the lock to authenticate, clicking on SMB, clicking on Configure, and then typing your workgroup (or domain) into the WorkGroup field. After doing this, you should be able to browse for servers in that domain. Furthermore, your servers will show up in the Network area of the Finder. The only drawback is that if you have a home network, you need to change that workgroup setting again when you get home.

Things still are not perfect, but at least I am back to 10.2.8 levels of SMB browsing.

osxpounder · 12-10-2003, 11:55 AM

I've tried each of these suggestsions -- so far, I still can't get logged into my PC via Samba. I'm going to post a new thread requesting help and giving the details -- thanks for posting these tips, though.

bkhuonk · 12-11-2003, 05:18 PM

i am have the same problem. Was a solution ever found?

bri

osxpounder · 12-15-2003, 10:59 AM

http://www.macosxhints.com/article.p...31203172256827

"By default Workgroup in the Windows domain does not equal my login Workgroup. I found that you can specify Workgroup (along with user ID) in the SMB connect to string. For example:
smb://WORKGROUP;machine.somewhere.com/Share

This works to specify WORKGROUP for login. This can be expanded ...."

Read the rest of the hint for details that might just be what you need. Hope this helps!

Niels · 12-19-2003, 03:24 AM

This worked for me too. Thanks.

gdsgds · 01-02-2004, 08:59 AM

I had the same problem and just found a solution thanks to different posts. What I did : I went in my Keychain Access application and saw there were two entries for USERNAME (the username I use on our windows network) that apparently were used each time I try to connect using smb and despite I each time entered my password manually. I deleted the two entries and closed Keychain access. Then I tried to reconnect :

smb://192.168.0.1

the username/password window was showed and I entered my password and yes, it worked.

Let me know if this works for you.

radag87 · 07-02-2004, 04:15 PM

I tried the two options shown here for netinfo manager and keychain access. Removing the entries from the keychain access proved to be the fix in my case.

bkhuonk · 07-02-2004, 04:36 PM

I finally achieved access. The address supplied by my tech guy was a vurtual address. He gave me the actuall address of the machine and it worked like a dream. Hope this helps someone else.

10-31-2003, 01:10 PM	#1
SpiicyTuna Prospect Join Date: Oct 2003 Posts: 12	HELP! Using Samba in Panther I have no choice but to use a windows share in my job position. 10.2.8 worked wonderfully with Samba. Now that I have upgraded to 10.3 (Panther), I cannot access any windows shares. I get the error: "The Finder cannot complete the operation because some dats in "smb://<<Share Nam>>/" could not be read or written. (Error code -36)." When I tried to mount manually from the command line using mount_smbfs, I got the error "mount_smbfs: SMB filesystem is not available" Has anyone else encountered any erros? Does anyone have any ideas? I really do not want to downgrade to 10.2 again....

11-11-2003, 08:57 AM	#3
tncook Triple-A Player Join Date: Jan 2002 Location: Ann Arbor Posts: 145	I'm having the same problem on a fresh install of 10.3. I can mount volumes using mount_smbfs, but not through the finder. It gives me the "smb://<<Share Nam>>/" could not be read or written. (Error code -36)" error. It worked fine in 10.2.x edit: apparently if i specify a specific share when mounting it works, but if just trying to connect and then pick a share it doesn't. Last edited by tncook; 11-11-2003 at 08:59 AM.

12-10-2003, 11:55 AM	#5
osxpounder Major Leaguer Join Date: May 2002 Location: atl, ga, usa Posts: 356	Doesn't work for me, though. I've tried each of these suggestsions -- so far, I still can't get logged into my PC via Samba. I'm going to post a new thread requesting help and giving the details -- thanks for posting these tips, though.

12-11-2003, 05:18 PM	#6
bkhuonk Prospect Join Date: Dec 2003 Location: Bloomington Posts: 12	Same problem i am have the same problem. Was a solution ever found? bri

12-15-2003, 10:59 AM	#7
osxpounder Major Leaguer Join Date: May 2002 Location: atl, ga, usa Posts: 356	Solution? Yes, I found one that worked for me ... http://www.macosxhints.com/article.p...31203172256827 "By default Workgroup in the Windows domain does not equal my login Workgroup. I found that you can specify Workgroup (along with user ID) in the SMB connect to string. For example: smb://WORKGROUP;machine.somewhere.com/Share This works to specify WORKGROUP for login. This can be expanded ...." Read the rest of the hint for details that might just be what you need. Hope this helps!

10-31-2003, 05:59 PM	#2
SpiicyTuna Prospect Join Date: Oct 2003 Posts: 12	My Fix: Fresh install while archiving my user account. When install gets to the part asking which disk to install on, choose options, then you have the archiving choices.

12-19-2003, 03:24 AM	#8
Niels Prospect Join Date: Dec 2003 Posts: 13	This worked for me too. Thanks.

01-02-2004, 08:59 AM	#9
gdsgds Triple-A Player Join Date: Aug 2002 Posts: 59	I had the same problem and just found a solution thanks to different posts. What I did : I went in my Keychain Access application and saw there were two entries for USERNAME (the username I use on our windows network) that apparently were used each time I try to connect using smb and despite I each time entered my password manually. I deleted the two entries and closed Keychain access. Then I tried to reconnect : smb://192.168.0.1 the username/password window was showed and I entered my password and yes, it worked. Let me know if this works for you. Last edited by gdsgds; 01-02-2004 at 09:20 AM.

07-02-2004, 04:15 PM	#10
radag87 Prospect Join Date: Jul 2004 Location: Ft Worth TX Posts: 1	Using Samba in Panther I tried the two options shown here for netinfo manager and keychain access. Removing the entries from the keychain access proved to be the fix in my case.

07-02-2004, 04:36 PM	#11
bkhuonk Prospect Join Date: Dec 2003 Location: Bloomington Posts: 12	Another solution I finally achieved access. The address supplied by my tech guy was a vurtual address. He gave me the actuall address of the machine and it worked like a dream. Hope this helps someone else.