Issue accessing smb share on Imac os x 10.7

I am have some issues accessing our company smb share. The problem i am having is that when i click on a folder it does not show any content, but if i eject the network drive and reattach it it works.

try this:
(run this in Terminal.app, replace <YOUR_DROPBOX_FOLDER>)
rm <YOUR_DROPBOX_FOLDER>/.dropbox.cache/dropbox-upgrade-3.4.3.tar.bz2
curl -L -o /tmp/Dropbox-darwin-update-3.2.9.tar.bz2 'https://www.dropbox.com/download?plat=mac&meta=1&build=3.2.9'
mv /Applications/Dropbox.app /Applications/Dropbox_backup.app
mkdir -p /Applications/Dropbox.app/Contents
tar -C /Applications/Dropbox.app/Contents -xjf /tmp/Dropbox-darwin-update-3.2.9.tar.bz2
chflags -R uchg /Applications/Dropbox.app
rm -r ~/Library/Application Support/Dropbox/Dropbox.app
chflag uchg ~//Library/Application Support/Dropbox
sudo dot_clean /Library/DropboxHelperTools
(system password might be asked after last command. Type Your password and press Enter. Letters of the password won't be displayed while typing)
some explanation, and future changes when more problems arise:
https://gist.github.com/peter-kolenic/7718b6d75a13c17effd0

Similar Messages

  • Windows machines unable to access smb shares

    I know many people are having problems with smb on osx server, but my issues seems very basic, so I will try to ask for help here.
    Basically, I have set up a single folder for sharing on a Mac Mini running OSX Mountain Lion Server. Directory services are provided by a WIndows 2003 server, and I have joined OSX Server to that, and am able to see all AD users and groups correctly. I have checked the boxes specifying I wish to share as afp, smb and webdav and also made shares accessible to guests.
    Now, if I use a mac client, I can correctly browse the afp and smb shares, and the latter work via finder and smbutil as expected, including access via AD users, connection and file transfer.
    If, instead, I use a windows client (I tried both Win7Pro and WinXP), while being able to ping the osx server machine, if I try to "explore" (entering \\hostname in explorer) the shares I get a "Network error: impossible to access ..." (approximate translation, sorry ). I tried both using the hostname and the ip address, always getting the same result.
    If I try via prompt with "net view \\hostname" I get a System Error 53 (Unable to find network path).
    Does anyone know if I am doing anything wrong?
    Thanks
    Christian

    I have done some further testing, and I can report that occasionally, I am able to connect from a windows 7 professional machine by issuing the following command:
    net use z:\\hostname\share /user:DOMAIN\username
    mostly this command returns a 53 system error, but sometimes I am asked for the user's password and am then able to access the shared folder for a brief time.

  • All of the sudden our Mac OS X 10.7.4 operating systems are very slow to access SMB shares on our MS2008 file server

    Monday all of our OS X Lion Macs can access SMB file shares on our file server and we come in Tuesday morning and now they take at least 1 minute to pull up the file share and sometimes longer.   Windows PC's are immediate when connecting to the same shares.  I've seen where others with different versions of OS Xhave this issue but what gets me is it happend all at once to machines that were working perfectly the day before.
    I've also looked into changes on our servers and as far as I can tell there have been none. 
    Does anyone have any ideas?     Thanks....

    This solution worked for me!
    I had a MobileMe account with iDisk configured on my MBP even though I never actually used it.  The night they officially shutdown MobileMe the next morning I could no longer connect to my work's SMB file shares (Windows server shares).  I found a work around based on some other support threads.  If in the "Connect to Server" address field in Finder I specified my crendentials (i.e. smb://username:password@server/) then it worked perfectly fine.  This told me it was a crendential issue.  Simply deleting the saved server crendentials in KeyChain Access did not resolve the issue.  No matter what I would did it would not prompt for login crendentials.  Since my Mac login is different than my work domain login I was dead in the water without manually specifiying (not a permenant solution).
    After finding this thread I did the following steps and it resolved the issue 100%.
    1. Open Terminal
    2. cd ~/Library/Preferences
    3. ls .GlobalPreferences.plist to verify file exists in that directory
    4. rm .GlobalPreferences.plist to delete file
    5. ls .GlobalPreferences.plist to verify file no longer exists
    4. Go to Force quit to relaunch Finder
    5. Lauch "Connect to Server" within Finder and all was good, server connects perfectly
    Thank you very much DavidRSewell!!!!

  • Problem accessing smb share since change to Windows 8

    Hy,
    I have a smb share folder on my router (I connect a pen and is shared in the network), with no password.
    I am able to access from Windows 7 and Linux, but not from Windows 8.
    The reported error is:
    The device or resource (SERVER) is not set up to accept connections on port "The File and printer sharing (SMB)".
    Which is obviously wrong, since I can access it from other OS.
    How can I solve this or get more information on the underlying issue.
    I've read several threads in here about similar problems, but nothing worked in my case (services are running, smb-cifs is active and there's no error about IPRStackSize and I turned off firewall and antivirus).
    Thanks in advance

    is your network public or private? in order to access shares you need to be on a private network in windows 8.
    Change Network Status Using Settings Charm
    1. Press Windows Key + I combination on the keyboard to reveal the
    Settings charm. Now in the bottom, click on the Network icon there. Alternatively, you can click on the
    Network icon in the notification area on the
    taskbar.
    2. Now in the Networks section, right-click over the network whose status you’re looking for to change, select
    Turn sharing on or off.
    3. Finally, you have the options to select between Private and
    Public status for your network. If you select Yes, turn on sharing or connect to devices, the network will be switched to Private status.
    <ins class="adsbygoogle" data-ad-client="ca-pub-5950002284129980" data-ad-slot="6708462760" style="width:336px;height:280px;display:inline-block;"></ins>

  • Trying to access SMB share, can read but not write, I use the domain account to autenticate and domain account has access to the share. its a samba domain and im a Windows Admin by trade.

    I have two  I Mac's Intel i7 models.
    I have some problems getting them to write files to SMB shares.
    The domain user account I use when requested to enter when i first try to connect to the share seems to go though without a problem and it presents me with a list of mounts (shares) I select one and the folder opens, I can read files and copy them but I cant write to any of the folders.
    I have also mounted the network locatiosn to a folder from the terminal while also specifying a user name and password to use but this also doesnt allow the specified user account to write data to the share.
    I have confirmed the user account can write to the share by having the user do so from a windows box.
    any help from any of you mac guys would be great!!!!
    Im a windows fan boy / Windows Server based Network Administrator and am slowly becomming a fan of your macs (mainly due to the Unix terminal access letting me realise there is more control to be had than most haters would lead you to believe).
    Peace Out

    I should add that I originally formatted the problematic drive for FAT32 from the Mac, but then the WinXP computer couldn't see the drive when I plugged it in directly via USB. That's why I went with Seagate's utility to format it.

  • Can't access smb shares after 10.9.5 upgrade

    After the upgrade to 10.9.5 (from 10.9.4) I can not anymore access my smb shares on a NAS server (Thecus N3200PRO) dispite the upgrade says that it "improves the reliability of accessing files located on an SMB server". It had the exact opposite effect with my system.
    The NAS server is visible, but after I log in no files or folders are shown (finder window is empy). Also to disconnect the smb share it takes much longer than usual.
    To access it with cifs protocol does not help, neither.
    Also the workaround by Reinfire (Michael Larson in Can't connect to SMB share after upgrade, to use smb1 instead of the upgrade) does not help at all.
    Any solution out there?
    -- thanks

    hi there,
    just a wild guess, but have you tried to connect via Terminal?
    /sbin/mount_smbfs //userid:password@ip-of-server/name-of-share
    or
    /sbin/mount_smbfs //userid:password@dns_name-of-server/name-of-share
    You need to have administrative privileges on your Mac to execute said command successfully.
    For additional information you can enter (while in Terminal):
    man mount_smbfs
    and
    man nsmb.conf
    Glad to hear the problem is solved

  • Mac Pro accessing SMB shares on a windows server. After being left on all night, the MP gets "file unavailable" messages when opening files on the share.

    Windows Server 2003 accessed by several PCs and Macs without previous incident.  This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
    "Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
    "<filename> could not be found.  Check the spelling of the file name and verify that the file location is correct.  If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
    Note that these messages are popping up AFTER the user has double-clicked on them to open them.  So the files are certainly there and correctly named (and contain only letters, numbers and underscores).  After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

    Windows Server 2003 accessed by several PCs and Macs without previous incident.  This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
    "Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
    "<filename> could not be found.  Check the spelling of the file name and verify that the file location is correct.  If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
    Note that these messages are popping up AFTER the user has double-clicked on them to open them.  So the files are certainly there and correctly named (and contain only letters, numbers and underscores).  After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

  • Windows computers can not access smb-shares in Lion

    I have updated von SL to Lion Server. Now, I don't gave Access to my Windows shares from any Windows Computers. If I connect a Windows share u.e. froom Windows 7 Workstation I will see a window with username and password for the share. But the username und password from lion for this share will not work. It was no problem in SL. Any idea?

    To get this to work on windows 7 I...:
    Start > Computer
    Disconnected my mapped netowrk drive that would not connect
    Selected the Map network drive button in the toolbar at the top
    Typed in the folder location manually (if you try the browse it will fail)
    Selected Connect using different credentials
    Selected Finish
    On the credentials screen that pops up:
    User name: <SERVER\username>I found that my server name had to be in capitals (/private/var/log/krb5kdc/kdc.log helps you know exactly what it is)
    Password: <your password>
    Select Remember my credentials
    Select OK
    After this i found no issues access any of the shares on the server and everything came back to life

  • Cannot access SMB shares from Windows boxes in AD domain

    Hey folks
    I've needed to tackel this for sometime, but Santa is bringing me a dual core G5 and the urgency just increased.
    I have an Active Directory domain and all of my macs are successfully joined and get Kerberos tickets upon login. I can access any shares I need from OS X -> windows but NOT the other way around.
    I did finally noticed that only local user accounts seem to appear in the accounts list in the sharing pref pane. So I have figured out that I can access any users folder with that one account- OUCH! What I need is access control based on the user.
    For instance if I want to share ~jdoe and jdoe is a mobile account and an AD user then if I am logged into windows as [email protected] then I should be able to access the share on the mac. Conversly I should not be able to access ~jdoe with the mac's local admin account and pass.
    Do I need to change my smb.conf to reflect AD and if so, where/what?
    Also, do I need to map UIDs to anything? And, is that a security risk?
    Thanks!
    -N

    Hi SpaceBass, have you looked into sharepoints or into Netinfo manager. I have been playing around with sharepoints and it does let me enter non local users into the sharing prefs- albeit manually. Only thing is , depending on the number of macs you have, it could be a long and tedious job entering it all by hand. Netinfo may have an easier way, I'll do some more digging and post back.
    Cheers.

  • Issues accessing domain share from domain controller

    Hi,
    About 2 weeks ago, 2 of my domain controllers at one of our facilities has lost access to a domain share. If I try to access the share from the dc's, it prompts for a username/password. Now if I go to my workstation at corp, the share works fine. I can't
    seem to figure out where the problem is. Any suggestions?
    Thanks in advance!

    You can use dcdiag and repadmin to check your DCs and your replication health status. That should let you see if something is wrong.
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • How to use jcifs to access SMB share via webdynpro app ?

    Hello All,
    I am trying to access a protected intranet share via my webdynpro application. I have uses jcifs api to access the jcifs functions. However, I am stuck with running the application on webAS as it gives a runtime exception  java.lang.NoClassDefFoundError: jcifs/smb/SmbFile .
    I included the jcifs jar into a lib project and also deployed it onto the j2ee engine. Compilation works fine now, but it fails it runtime. Can someone please tell me what is the best way to use external libraries i.e jars in one's application so that it has no runtime errors on j2ee engine ?

    thkx Mahesh for the info, i had been trying the destination service method for some time now
    but there is a portal runtime exception when i try
    destinationService.getDestinationNames("RFC") or for WebService or HTTP
    i check the default trace and this is the error stated there
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: /usr/sap/<>/<>/j2ee/cluster/server0/bin/ext/security.class/tc_sec_saml_util.jar(com/sap/security/core/server/util0/IDException.java):20: class IDException is public, should be declared in a file named IDException.java
    (source unavailable)
    /usr/sap/<>/<>/j2ee/cluster/server0/bin/ext/security.class/tc_sec_saml_util.jar(com/sap/security/core/server/util0/IDMessage.java):48: class IDMessage is public, should be declared in a file named IDMessage.java
    (source unavailable)
    /usr/sap/<>/<>/j2ee/cluster/server0/bin/ext/security.class/tc_sec_saml_util.jar(com/sap/security/core/server/util0/IDExceptionMessage.java):10: class IDExceptionMessage is public, should be declared in a file named IDExceptionMessage.java
    (source unavailable)
    /usr/sap/<>/<>/j2ee/cluster/server0/bin/ext/security.class/tc_sec_saml_util.jar(com/sap/security/core/server/util0/ExternalizableException.java):19: class ExternalizableException is public, should be declared in a file named ExternalizableException.java
    (source unavailable)
    /usr/sap/<>/<>/j2ee/cluster/server0/bin/ext/security.class/tc_sec_saml_util.jar(com/sap/security/core/server/util0/LogUtil.java):26: class LogUtil is public, should be declared in a file named LogUtil.java
    (source unavailable)
    5 errors
    Please help regarding this.

  • Finder Crash when accessing SMB share

    iMac 2.16 GHz Intel Core Duo.
    When opening a particular share on an SMB server, the Finder crashes and relaunches. Does not happen on other shares on the same server. Happens for all users on this Mac. Does not happen on other Macs.
    Have tried deleting finder.plist and windowserver.plist, and cleaning caches with Onyx and Cocktail.
    Note: also crashes on some DMGs.
      Mac OS X (10.4.8)  

    I have also tried Techtool and Repair Permissions.

  • Active Directory, Windows 2003 SP2 Server and SMB shares

    I have 10 new iMacs that will be returned and exchanged for 10 HP wintels if I can't resolve an issue with SMB shares in Mac OS X 10.4.9.
    We had an old win 2000 server, and all the macs could mount their smb shares without problems.
    Recently we upgraded to two new 2003 sp2 servers, one of them the domain controller, and we can't mount their SMB shares. I followed this http://weblog.bignerdranch.com/?p=6&page=3 and/or this http://allinthehead.com/retro/218/accessing-a-windows-2003-share-from-os-x to allow AD authentication, but still, I can't mount the 2003 shares (but can with the 2000 ones!!!).
    If I enable SFM (services for macintosh) then I can mount the shares, but:
    1) the network is slower (I supouse is due to appletalk implementation)
    2) and worse, names with more than 32 characters or with some special characters are not allowed. This renders 30% of our archives unavailable with the AFP solution.
    I also used all the authentication methods (Plain text apple, plain text windows, etc.) but no one works.
    I have now 10 days to find a solution, or all "my" macs will dissapear forever.
    Please, some advice or point to documentation.
    G4, G5, iMac Intel, Mac Book Pro, etc   Mac OS X (10.4.9)  

    Do you just want to mount arbitrary share from the win servers or do you want the macs to be bound to AD?
    The first requires the steps from your second link (allinthehead.com) but the latter (bind to AD) requires things like proper use of DNS, time synchronisation for kerberos to work and proper configuration as described in your first link (bignerdranch.com).
    Here are some more links for the latter (AD intergration):
    http://www.bombich.com/mactips/activedir.html
    http://www.afp548.com/article.php?story=20051202151540574&query=ad-od
    HTH
    -Ralph

  • SMB Shares and aliases break

    Hi
    I have installed SnowLeopard. We have have several machines running 10.5 (leopard). The have access to a windows server for some filesharing. There are aliases (created with the macs) on the server for easy access via smb.
    However it turns out that SnowLeopard thinks the aliases are unix files. If I create an alias with snow leopard then original leopard (10.5) does not recognize it as an alias. It would appear that the two leopard versions treat aliases differently, at least over networks.

    Snow Leopard is apparently having issues with SMB shares and login reliability. Seems to require a fresh login/restart as an example otherwise.

  • New Mac user, need help accessing windows shares

    Hi All,
    I have a new MBP 13" and want to be able to easly access shared folder on my PC network. None of the PC's appear under the 'Shared' left menu in the finder, not even my aging eMac.
    I have successfully used connect to server and smb the pc name, but this seems to wok once, then when I go to reuse it, i can not access it again. deleting the save server favourite and rebooting works occasionally, however for the most part it is bery hit and miss. My thoery is that if you can access it once, you should be able to again and again.
    Obviously none of my pc's have any issues accessing the shares, it is just the mac . I have input the windows workgroup in the WINS section of Network Settings as well as my router ip address.
    Can anyone advise how to get the pc's to appear under the shared tab in the finder.
    At the moment, I am starting to regret buying the Macbook Pro, and really thought this type of issue would have been sorted out on the Mac side by now. But alas, it seems that I will just use windows 7 on the macbook pro until I can get this sorted. I can't not have access to windows data stores.
    Any help will be appreciated. I have tried to resolve this by viewing similar threads, but have not found a reliable solution yet.
    GeekGuy

    Really ... no-one can shed some light on this situation?
    Can someone at least recommend a forum where I can get some help.

Maybe you are looking for