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.
habakkuk3178Asked:
Who is Participating?
 
Dave_ANDConnect With a Mentor Commented:
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
 
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
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
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
All Courses

From novice to tech pro — start learning today.