Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 989
  • Last Modified:

Mac OS 10.6.4 having shared folder access issues on SBS 2003

We have a server running SBS 2003. We have 3 Macs in the office. Two of them do just fine, but the newest and best one has a very slow connection to shared folder areas and only has read privileges when it does connect. It's a MacBook Pro running OS 10.6.4. It's on a wired connection to the network. It connects to the server using the smb:// protocol.

The user is already a member of the Administrators group, so he should have complete access. On top of that, I have gone into the specific shared folder he's trying to access and added his username for complete access.

I don't know where else to go from here.
0
habakkuk3178
Asked:
habakkuk3178
1 Solution
 
Dave_ANDCommented:
Have you tryed allowing Everyone access for a test? just to see if its a permissions issue or a Mac thing? (do for both NTFS and share)
0
 
habakkuk3178Author Commented:
We have a small network, so it's actually already set up to allow Everyone full control.
0
 
Dave_ANDCommented:
ok, so we know its not that then.. it seems the latest OS X has some SMB sharing problems, have you read thru this page: http://www.macwindows.com/snowleopard-filesharing.html ?

Maybe a good idea instead of using everyone, use Authenticated users just to add a bit of security for file shares etc :)
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
roylongCommented:
Are all of your computers running the same version of the Macintosh OS?

I would start by going through and checking everything in the network system preferences to ensure all of your network settings are exactly the same and it's nothing on this side.

Have you tried connecting from one of the other computers with the same username?
0
 
maximus5328Commented:
try different ethernet connection - from one of the computers that are working normally
0
 
habakkuk3178Author Commented:
That article did the trick. Thanks for the link! Adding :139 to the smb:// connection protocol fixed the issue.

smb://servername:139
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now