Windows 7/CIFS

have some new Windows 7 64 bit workstations that cause the following
problems:
Most of my Netware is gone, but the server that remains runs CIFS.
Without the client, file access is slow and can't run executables from the
shares.
With the client, users get frequent account lockouts.
Client is 2 SP1.
Any ideas?

Thanks! I'll check those out.
"Marcel Cox" <[email protected]> wrote in message
news:[email protected]..
>
> I don't know what NetWare version and support pack level you are using,
> but for reliable operations with current Windows versions, it is quite
> essential that your CIFS has to be up to date. For NetWare 6.5 theis
> means that you must be on SP8 and have the following oatch installed:
>
> 'NOVELL: Downloads - NSS Update for NetWare 6.5 Support Pack 8 2.0'
> (http://download.novell.com/Download?...d=tMWCI1cdI7s~)
>
> For the Novell client, the situation is similar. The V2 SP1 client had
> many quirks and issues and for reliable operations, you really need the
> latest patched client (which is v 2 SP1 IR2) available here:
>
> 'NOVELL: Downloads - Novell Client 2 SP1 for Windows (IR2)'
> (http://download.novell.com/Download?...d=OsMcJFYBh54~)
>
> One strange thing however is the account lockouts you report. That
> typically sounds like an issue where a server supports both NCP and
> CIFs, but you are not using universal password and the passwords for the
> user are not synchronized.
>
>
> --
> Marcel Cox
> ------------------------------------------------------------------------
> Marcel_Cox's Profile: http://forums.novell.com/member.php?userid=8
> View this thread: http://forums.novell.com/showthread.php?t=414395
>

Similar Messages

  • Accessing Windows CIFS Shares via Nautilus

    Hi,
    I've recently installed and configured Solaris 11, am having problems accessing Windows CIFS shares via Nautilus.
    I've installed both samba (needed for CUPS to print to printers connect to a windows pc) and smb/client. The smb/client and samba services are running. The smb/server service is not installed.
    I can print to any printer on the windows PC I'm trying to access via Nautilus, so I know my username/password for accessing the pc are correct.
    I can also manually mount any share on the windows PC via the cli (eg mount -F smfs -o user=elin //elink/users /mnt), and browse the files directly that way, except the file permisssions don't seem to align with any unix user. Again this just shows that the username/password combination is ok.
    For Samba, I'm using the default smb.conf file as /etc/samba/samba.conf. Workgroup is set to WORKGROUP in smb.conf.
    On the Windows pc, in the security event viewer, I can see the auth request, however is failing with bad password (event ID 4776, error code 0x006a). In the default group policy object for networking, I've set to accept "LM & NT, NTLMv2 when neogiatated", as this allows legacy clients to connect. (Legacy meaning NT4, Win95, etc, and also has the benefit of allowing other OSes to connect as well).
    I'm also able to access the WIndows PC CIFS shares from an Arch Linux based setup (running GNOME 3.2 w/ Nautilus 3.2), so I doubt it's the Windows side of things causing the problems. Additionally, when I was running Solaris 10u9 (just before upgrading to Sol11), I was able to access the shares via Nautilus as well.
    So my question is:
    1. Does Nautilus use Samba or the Oracle smb/client service to handle mount windows CIFS shares?
    2. What log files or configuration files do I need to looking at to help with this error?
    As a side question,
    I've found that on a clean installation running the "Print Manager" accesses CUPS fine, but once you install a printer, it'll no longer connect to CUPS, unless run from the cli "sudo system-config-printers". So this is a permissions issue, where's the best place to fix/handle that one.

    Replying to my own thread, as I have a possible but very-hackish solution.
    To add some further details to my original post.
    There are 4 PCs on the LAN.
    1. Hellfire - OS = Solaris 11 11/11
    2. Brimstone - OS = Arch Linux
    3. Elink - OS = Win7 Pro x64 SP1
    4. IsaacPC - OS = WinXP Home SP3
    Attempting to connect to Elink from Hellfire, accessing CIFS shares via Nautulis fails. (Mounting shares via Nautulis fails, but works fine from CLI using 'mount' command which to my understanding uses the smb/client service to work). Elink also hosts all the printers on the LAN, a HP LJ1200 and an Epson Fax/Printer/Scanner.
    Helfire does attempt to authenticate, as listed in the event logs on the Win7 PC (elink), but is returning bad password when using Nautulis. (but printing from hellfire to either printer on elink works fine, as does mounting CIFS shares using 'mount').
    Booting the live CD of Solaris 11, also exhibits the same non-working behaviour when attempting to mount CIFS shares in Nautulis.
    Attempting to access CIFS shares on elink from Brimstone (via Nautulis 3.2 within GNOME 3.2), or from IsaacPC works fine.
    Hellfire configuration.
    Samba is installed, but NOT running (samba is needed for accessing the printers on elink, as CUPS needs smbspool which is part of the samba package), and the native smb/client service is also running.
    smb.conf is a direct copy of the default *.conf file, except the WORKGROUP is set to 'WORKGORUP'. There is a symlink to smb.conf in /etc/sfw/smb.conf -> /etc/samba/smb.conf
    Onto the hackish-fix.
    I've noticed that there are 2 copies of libsmbclient.so installed on the system, one in /usr/sfw/lib (part of the "libsmbclient" package) and another in /usr/lib/samba (part of the "samba" package).
    "libsmbclient" appears to be based on samba 3.5.8 codebase, and is linked to the gvfsd-smb daemon (this is the software that Nautulis uses to talk SMB to access CIFS shares).
    "samba" is based on the samba 3.5.10 codebase, and it's installation has nothing to do with GNOME or Nautulis in any manner.
    Using any of the samba included tools to test SMB/CIFS functions, work with 1 minor exception (which I'll list below). eg, using smbclient I can list all shares on any PC on the LAN, etc.
    So as a hunch, I renamed the libsmbclient.so.0 in /usr/sfw/lib, and symlinked /usr/sfw/lib/libsmbclient.so.0 -> /usr/lib/samba/libsmbclient.so.0 (so that gvfsd-smb is linked against the slightly newer version of the libsmbclient.so as included in the samba package located in /usr/lib/samba).
    I rebooted Hellfire, and now I'm able to access CIFS shares via Nautulis, provided that some form of authentication is needed (that is a username and password is needed - guest access and blanks passwords don't work - but these IMO should be disabled immediately as part of a baseline security package in regards to Windows - so no harm there).
    Now to the minor exception I noted earlier. When using smbclient to actually connect and transfer files, I get:
    ld.so.1: smbclient: fatal: relocation error: file /usr/lib/libreadline.so.5: symbol tgetent: referenced symbol not found
    As far as I know, tgetent is part of libtermcap.so, so I guess when building smbclient or libreadline.so, the link reference to termcap was left out? (or something like that). Anyway, that's another issue...

  • Error -36 connecting to Windows 2000 Server

    I'm trying to connect to a windows 2000 server that appears in my Network browser but I can't authenticate using the Network browser or via smb://.
    I have been able to connect in the past no problem and I can login to the server on another machine using my user and password.
    I get two errors:
    If I go via Network browser I can click and get a username and password dialog box. When I enter my details and hit return I get - 'The alias (servername) could not be opened because the original could not be found'
    If I go via Connect to Server i get a "can't connect to server blah blah (-36 error)" and I can cancel or try again.
    I've searched high and low for a solution but can't find anything like this.
    I suspect I need to trash some preference or other, like you could do in OS9, but I have no idea where to start with OS X.
    Can anyone help?
    Al
    G5   Mac OS X (10.3.9)  

    See the following article
    http://docs.info.apple.com/article.html?artnum=301580
    Basically the steps are as follows:
    Follow the steps below to configure your computer to use plain text passwords to make SMB/CIFS connections when the specified Samba or Windows (SMB/CIFS) server does not support encrypted passwords. (You must be an administrator to do these steps.)
    Make sure that you are not currently connected to any Samba or Windows (SMB/CIFS) servers and that you do not have any Samba or Windows-related error messages open.
    Open the Terminal (/Applications/Utilities/).
    At the prompt, type: sudo pico /etc/nsmb.conf
    Press Return.
    Enter your password when prompted, then press Return again.
    You should see an empty file and a "New File" notice at the bottom of the pico window. If you do not see the "New File" notice, this file already exists.
    Enter the following into the file so that it appears as follows:
    [default]
    minauth=none
    Save the file (press Control-O), press Return, then exit pico (Control-X).
    Type: sudo chmod a+r /etc/nsmb.conf
    Press Return.
    Restart your computer.

  • I can't connect to my Windows machine from my G4 Others Can

    Hi,
    I'm new here, I'm sure this has come up before, but I couldn't find a solution in the forum.
    I'm trying to connect a G4 running 10.3.8 to a Windows 7 PC unsuccessfully. However I can connect to it and share with both an Intell based PowerMac and a newer Power PC G5.
    The G4 sees the other computer on the network, but when I enter its username and password I get the message,
    "The alias named xxxxxxxxxxx could not be opened because the original item can not be found."
    Also, the error message on the console reads,
    "mount smbfs: unable to list resources: syserr=function not implimented
    I can however successfully ping it through the terminal.
    I've pretty much run out of ideas, so if anyone would be able to help I'd really appriciate it.
    Thank you,
    Eric

    Hmmm, link works here...
    Archived -  Mac OS X 10.4: Error -36 alert displays when connecting to a Windows server
    This article has been archived and is no longer updated by Apple.
    Symptoms
    Mac OS X 10.4: Error -36 alert displays when connecting to a Samba or Windows server
    After upgrading from Mac OS X 10.3.x to Mac OS X 10.4, you may get an error message when you try to connect to a Samba or Windows (SMB/CIFS) server. A Samba or Windows (SMB/CIFS) server includes servers operating on Microsoft Windows and other operating systems that use Samba for SMB/CIFS services.
    If the connection is unsuccessful, the following error message may appear:
    The Finder cannot complete the operation because some of the data in smb://........ could not be read or written. (Error code -36).
    If you check the Console (/Applications/Utilities/), you will also see this error message:
    mount_smbfs: session setup phase failed
    Resolution
    This error can occur if your Mac OS X 10.4 client is trying to connect to a Samba or Windows (SMB/CIFS) server that only supports plain text passwords. If you do not see the above message in the Console, you are not experiencing this issue and should try normal troubleshooting
    Unlike Mac OS X 10.3, the Mac OS X 10.4 SMB/CIFS client by default only supports encrypted passwords. Most modern Samba or Windows (SMB/CIFS) servers use encrypted passwords by default, while some Samba servers might have to be reconfigured.
    You should consider contacting the owner or system administrator of the Samba or Windows (SMB/CIFS) server to which you are trying to connect and encourage them to disable plain text passwords and start using encrypted ones. If the server cannot be reconfigured to support encrypted passwords, you can configure Mac OS X 10.4 SMB/CIFS client to send plain text passwords.
    Warning: If you configure your computer to allow connections to Samba or Windows (SMB/CIFS) servers using plain text passwords, when you attempt to make any connection to such a Samba or Windows (SMB/CIFS) server, your password will be sent "in the clear". This means that it is possible for someone who is monitoring your connection to see your password. This could lead to someone compromising the Samba or Windows (SMB/CIFS) server. We strongly recommend that you configure your Samba or Windows (SMB/CIFS) servers to exclusively use encrypted passwords.
    Follow the steps below to configure your computer to use plain text passwords to make SMB/CIFS connections when the specified Samba or Windows (SMB/CIFS) server does not support encrypted passwords. (You must be an administrator to do these steps.)
    Make sure that you are not currently connected to any Samba or Windows (SMB/CIFS) servers and that you do not have any Samba or Windows-related error messages open.
    Open the Terminal (/Applications/Utilities/).
    At the prompt, type: sudo pico /etc/nsmb.conf
    Press Return.
    Enter your password when prompted, then press Return again.
    You should see an empty file and a "New File" notice at the bottom of the pico window. If you do not see the "New File" notice, this file already exists.
    Enter the following into the file so that it appears as follows:
    [default]
    minauth=none
    Save the file (press Control-O), press Return, then exit pico (Control-X).
    Type: sudo chmod a+r /etc/nsmb.conf
    Press Return.
    Restart your computer.
    Important: Information about products not manufactured by Apple is provided for information purposes only and does not constitute Apple’s recommendation or endorsement. Please contact the vendor for additional information.
    Also, does the PC connect to that Mac if you enable Windoes Sharing on the Mac?

  • CIFS/SMB difference

    If I try to access my windows share on my network using smb://servername/sharename - it cannot find the box.
    If I use CIFS://servername/sharename it works like a charm.
    What is the difference between CIFS and SMB?
    [the above holds true for accessing only some of the windows machines on the network... but is consistent... same servers never can be see, other can always be seen]

    CIFS (Common Internet File System) is a refinement of SMB (Server Message Blocks). SMB is the term for Microsoft's file sharing technology as used in Windows. CIFS was proposed by them as an "open" version of SMB for filesharing over the Internet and is used by other platforms such as Unix.
    If you're having trouble with SMB then something in your setup related to Windows file sharing, perhaps WINS server settings or authentication, is not quite right, whereas the more generic CIFS is able to connect.

  • Connecting to A Windows XP Shared Folder

    I looked around and I must not be good at searching because this seems like it had to have been asked before. so my apologies up front if it was.
    We recently moved and I lost my shared folder connection from my Mac to my windows xp machine and I haven't been able to reset it. I found articles describing how to connect, but I keep getting an error.
    http://www.mac-connect.com/winfrommac.php
    When I do that, my mac can not find my pc on the network whether I browse, use ip address or computer name. It looks for a while and then I get an error message that says "The Finder cannot complete the operation because some data in smb://ip address could not be read or written. (Error Code - 36).
    I have disabled all firewalls I know about and set up the "My Documents" folder to share. But I still can not figure it out. I have Windows OS X (10.4.1).
    Message was edited by: gremmie
    Message was edited by: gremmie

    Hi
    I feel for you - I've been having the same problem except that I AM able to connect to my Mac via my PC - just not the other way around.
    The really annoying thing is I'm not interested in connecting from my PC to the Mac, I just want to connect from the Mac to the PC.
    There is an answer in Mac help, but it hasn't solved my problem. I'm not an IT expert at all, so I haven't the faintest idea what the solution is. Mac help says this occurs when upgrading from Mac OS X 10.3 to 10.4 but I've always had 10.4 and for me it only happened after I uploaded security updates - although I'm not sure which update caused it.
    This is from Mac help, maybe it will work for you:
    Symptoms
    Mac OS X 10.4: Error -36 alert displays when connecting to a Samba or Windows server
    After upgrading from Mac OS X 10.3.x to Mac OS X 10.4, you may get an error message when you try to connect to a Samba or Windows (SMB/CIFS) server. A Samba or Windows (SMB/CIFS) server includes servers operating on Microsoft Windows and other operating systems that use Samba for SMB/CIFS services.
    If the connection is unsuccessful, the following error message may appear:
    The Finder cannot complete the operation because some of the data in smb://........ could not be read or written. (Error code -36).
    If you check the Console (/Applications/Utilities/), you will also see this error message:
    mount_smbfs: session setup phase failed
    Resolution
    This error can occur if your Mac OS X 10.4 client is trying to connect to a Samba or Windows (SMB/CIFS) server that only supports plain text passwords. If you do not see the above message in the Console, you are not experiencing this issue and should try normal troubleshooting
    Unlike Mac OS X 10.3, the Mac OS X 10.4 SMB/CIFS client by default only supports encrypted passwords. Most modern Samba or Windows (SMB/CIFS) servers use encrypted passwords by default, while some Samba servers might have to be reconfigured.
    You should consider contacting the owner or system administrator of the Samba or Windows (SMB/CIFS) server to which you are trying to connect and encourage them to disable plain text passwords and start using encrypted ones. If the server cannot be reconfigured to support encrypted passwords, you can configure Mac OS X 10.4 SMB/CIFS client to send plain text passwords.
    Warning: If you configure your computer to allow connections to Samba or Windows (SMB/CIFS) servers using plain text passwords, when you attempt to make any connection to such a Samba or Windows (SMB/CIFS) server, your password will be sent "in the clear". This means that it is possible for someone who is monitoring your connection to see your password. This could lead to someone compromising the Samba or Windows (SMB/CIFS) server. We strongly recommend that you configure your Samba or Windows (SMB/CIFS) servers to exclusively use encrypted passwords.
    Follow the steps below to configure your computer to use plain text passwords to make SMB/CIFS connections when the specified Samba or Windows (SMB/CIFS) server does not support encrypted passwords. (You must be an administrator to do these steps.)
    Make sure that you are not currently connected to any Samba or Windows (SMB/CIFS) servers and that you do not have any Samba or Windows-related error messages open.
    Open the Terminal (/Applications/Utilities/).
    At the prompt, type: sudo pico /etc/nsmb.conf
    Press Return.
    Enter your password when prompted, then press Return again.
    You should see an empty file and a "New File" notice at the bottom of the pico window. If you do not see the "New File" notice, this file already exists.
    Enter the following into the file so that it appears as follows:
    [default]
    minauth=none
    Save the file (press Control-O), press Return, then exit pico (Control-X).
    Type: sudo chmod a+r /etc/nsmb.conf
    Press Return.
    Restart your computer.

  • Creating a symlink directory on a network share to a path below a mapped drive letter, local path, or UNC path does not work

    Am I correct in assuming I can not create a `symlinkd` to a network share, local path, or a UNC path on a network share that will be accessible by clients?
    ###Mapped drive letters don't work:
    1) navigate to a network share:
    pushd \\windows2008server\share\
    2) make a hardlink:
    mklink /d test_sharedir t:\directory\
    dir .\test_sharedir
    #Directory of Z:\test_sharedir
    #File Not Found
    UNC paths don't work:
    1) navigate to a network share:
    pushd \\windows2008server\share\
    2) make a symlink:
    mklink /d test_dirunc \\windows2008server\share
    dir .\test_dirunc
    #Directory of Z:\test_dirunc
    #File Not Found
    I can create a functional `symlinkd` on a local drive to a mapped drive letter or a UNC path.
    Are my assumptions above correct?
    We are in the middle of a migration and have created two symlinkd to UNC paths for shared DLLs, one below c:\windows\system32\ (directing to a share containing 64-bit DLLs) and one below c:\windows\syswow64 (directing to a share containing 32-bit DLLs).
    On the file server, we have had a path to 32-bit DLLs (from Windows 7 clients: s:\dll\).  I am attempting to rename this directory so that it is accessible via "s:\dll32\" and would like to create a symlinkd that links "s:\dll" to
    "s:\dll32" [again where S: is a mapped drive on a Windows 2008 server].  How do I do this?
    Thanks,
    Matt

    Hello Mandy,
    The link you sent me is for Netapp CIFS server daemon contained within DataOnTap (the Netapp OS) to follow symlinks.  I am inquiring about the Microsoft products Windows Server and Windows 7.
    To gain a better understanding of the Microsoft Windows Server and client (Windows) CIFS stacks and interaction of the stacks, I have referred to Figure 6 "Server Message Block Server Model" within the following (albeit older) document: http://download.microsoft.com/download/2/8/0/2800a518-7ac6-4aac-bd85-74d2c52e1ec6/tuning.doc
    You will see the following:
    I assume that the Windows Server CIFS server service must be "smart enough" to determine that a CIFS client is attempting access to a SYMLINKD and actually fill the request by following the SYMLINKD.  The CIFS server service does not appear
    to operate like this.
    1) Am I correct in my assumption that the CIFS client (redirector) and the CIFS server (server) do not following symbolic links (whether they be file or directory)?
    2) If not, how do I submit a feature request for this so that it can be reviewed and approved or not approved for inclusion/hotfix release?
    Thanks for your time,
    Matt Brown
    [UPDATE]
    Note that you can use a `directory junction` instead of using a SYMLINKD, to link to LOCAL resources (source). However, `directory junctions` do not allow access to resources over UNC.

  • Multiple finder crashes on brand new MBP

    I just purchased the 2.53 GHz MacBook Pro two three ago and have had a ton of finder crashes and restarts. It's not been anything worse than annoying, but it's still very disconcerting to have the desktop disappear for a few seconds. At least it always comes back.
    I can not reproduce the crashes reliably. However, they do seem to happen almost exclusively when I'm navigating through a network drive. The mounted drive doesn't have to be from the same machine, either. It can be from my Windows desktop (CIFS mount), my OpenBSD server (Samba/CIFS mount), or my Airport Extreme with my 750 GB Seagate FreeAgent Pro drive attached to it's USB port (formatted on this Mac).
    The crashes don't seem to occur when finder is in the background; only when I'm actively using it.
    I've also had a few other applications crash, but nothing nearly as much as finder (11 finder crash logs so far...)
    Anyone have any experiences like this?
    I've not yet run Apple's diagnostics, but will be doing so tonight.

    Well, I got the Apple store to swap out the MacBook Pro due to a scratch on the display's case. The store Genius didn't know why the finder was crashing. He didn't find anything in his internal support system, either. I also spoke to an enterprise support tech, who just happened to be there for another reason, and he wasn't sure either. Both techs did say that the build of OS X for the new MacBook/MacBook Pro is different than their normal one. I assume this is due to the new hardware and new driver requirements.
    They looked at the crash logs I have and weren't able to determine the cause. We all agreed that the hardware wasn't likely the cause, but couldn't be 100% certain.
    Well, after the swap, I've already had one finder crash, and as such expect many more over time. I figure this is an OS bug and Apple will eventually fix it. My past experience with OS X (pre 10.5) shows that this feature should be stable.
    The store Geniuses suggested I keep sending the crash reports to Apple, as I have been. So, I'm closing this issue and will just deal with the finder crashes for now. At least none of the crashes has actually brought down OS X.

  • Reversing Configuration to allow SMB connections using plain text passsword

    I could not logon to a SMB Winows server - repeatedly getting a error -36. I found Apple Article 301580 "Mac OS X 10.4: Error -36 alert displays when connecting to a Windows server". After checking about the possibility of the server being configured to accept an encrypted password - I was resigned to following the directions in 301580 to configure your computer to use plain text passwords to make SMB/CIFS connections when the specified Samba or Windows (SMB/CIFS) server does not support encrypted passwords:
    1. Make sure that you are not currently connected to any Samba or Windows (SMB/CIFS) servers and that you do not have any Samba or Windows-related error messages open.
    2. Open the Terminal (/Applications/Utilities/).
    3. At the prompt, type: sudo pico /etc/nsmb.conf
    4. Press Return.
    5. Enter your password when prompted, then press Return again.
    6. You should see an empty file and a "New File" notice at the bottom of the pico window. If you do not see the "New File" notice, this file already exists.
    7. Enter the following into the file so that it appears as follows:
    [default]
    minauth=none
    8. Save the file (press Control-O), press Return, then exit pico (Control-X).
    9. Type: sudo chmod a+r /etc/nsmb.conf
    10. Press Return.
    11. Restart your computer.
    My question is how can I reverse this confuiguration to the previous setting where only encrypted passwords are used ?
    Thanks!

    The solution in my situation was to insert the code below at the top of the file and that took care of the problem.
    AddType image/svg+xml svg
    AddType image/svg+xml svgz

  • SSH in Termianl

    is there a way without installing any software on the mac or pc to access files from my mac from a pc. For example if i am at school, can i ssh into my mac. At home i have a PC laptop that i confiured to have a folder named 'iMac' and when i click it it will ask for authentication. Can i do that through command prompt, or could i have like a shortcut on my flashdrive to somehow get into my Mac securly with authentication to my machine to access my files (just files no screen sharing or anything)

    I know nothing about what comes with Windows, so if Windows has ssh, with its scp and/or sftp file transfer commands, then yes. Otherwise, you might need PuTTY or Cygwin (or some other package with ssh support).
    On the Mac, you need to enable System Preferences -> Sharing -> Remote Login
    You need to configure your router so it port forwards port 22 from the internet to your Mac. PortForward.com has documents providing step-by-step guides on how to setup port forwarding for a huge list of routers
    <http://portforward.com/>
    The HARD part is that you now need to find out the IP address assigned to your router by your ISP. At home you can most likely query your router, or access a web site such as <http://whatismyip.com>, then take that IP address with you.
    If you are willing to install a dynamic DNS updating utility on your home Mac, you can get a free dynamic DNS name from No-IP.com or DynDNS.org. This will make finding your home system much easier, but it does break your rule that no software may be installed.
    If you have enabled Windows (SMB/CIFS) file sharing on the Mac, then you could also create an ssh tunnel for SMB/CIFS traffic.
    ssh -L 22445:localhost:445 -L 22139:localhost:139 [email protected]
    Now you would need to figure out how to tell your PC that it should connect to the file server 'localhost:22445' (or localhost:22139). Of course I'm making the major assumption that Windows knows about the 'localhost' concept.
    I'm making some major assumptions, as I do not really do much with Windows, and very little at this level of detail. Of course if by PC you really meant you are running Linux on a generic PC laptop, then this is very doable.
    Of course if you are going to allow installing software, then I would suggest using TeamViewer.com on the Mac and PC, which will give you both screen sharing and file transfer over a secure connection.
    By the way, Terminal, Unix, and command line command questions are best asked in the Mac OS X Technologies > Unix Forum
    <http://discussions.apple.com/forum.jspa?forumID=735>

  • Worth upgrading to Lion Server?

    Not trying to be snarky, geniunly curious.
    Currently have a Snow Leopard server for a small business office. It's being used as an Open Directory master, network share, web server, and Time Machine backup. No mail/calendar/wiki (use Kerio for that). In reading about Lion server I'm not sure if any of the new features are worth the upgrade for me. We went from 10.5 to 10.6 server mostly for the speed boosts and Spotlight searching, but I can't seem to find any "must have" Lion features for my use case.
    Anyone care to share their decisions over why they are planning an upgrade, and why?

    I will add to what was said above. Do not under any circumstances upgrade.
    I recently setup a clean Lion server, pre-installed on an iMac, with the lion server add-on from the App Store. So, totally clean machine, starting from scratch, Lion pre-installed.
    It's been a nightmare. The Server tool is unusable. It is buggy as ****. User and Group assignments just up and dissapear. They are still present, but you can't see them from the Server Tool. The only way to manage them is to use the Users and Groups Preference Pane, which is a pain also, but at least it works.
    The UI for setting permissions (yes, the standard Command-I interface), is screwed up also. It cannot handle simple tasks whithout failing. You never know what it its going to do. You add a group. But it doesn't take. You add it again. It might work. Hevean forbid you want to add a group, assign it read-write, and then apply to all subfolders. LOOKS like it works, but it doesn't. I confirmed this using the command line tools.
    I finally gave up trying to use the UI for permissions, and now I am doing everything from the command line using "chmod" commands. These always work. As soon as I can figure out how to manage users and groups from the command line, that's what I'm going to do.
    Windows SMB/CIFS sharing is a nightmare. It mostly works. Except when it doesn't. And it doesn't a whole lot of time. You think it's fine. But for no apparent reason, the Mac starts dropping the connection if it idles for too long. You can have a document open on a Windows machine, and go back to save it or work further, and the connection has dropped. Repeatedly you will work on a file, and for no apparent reason, when you try to save it, you are told that the file is already open by another user. But it's not. You are the only user, and in fact you are only using one single application to edit the file.
    I could not get our Debian-Linux based RIPs (for our large format printers) to connect using SMB at all. I finally gave up after numerous attempts trying every possible combination, and switched to using NFS exports. Thankfully, NFS still works in Lion, and the NFS Manager app (google for it) has been updated to manage them if you are uncomfortable doing it from the command line / text editor.
    We are hobbling along. It ain't pretty. I wish we had another option at this point.
    FYI: We didn't have a choice but to make this move now. Our old fileserver, a linux box, could no longer keep up with our growing user base and our very large file systems (we are a medium-sized printing company). Linux is great as a Mac server for smaller networks, but it can't handle either Samba or AFP connections once the filesystem grows too large. It bogs down horribly due to the inherent limitations of Samba and Netatalk. So our only options were a Mac Server or Windows+Extreme-Z IP. We chose to roll the dice on an iMac + Promise Pegasus disk array on Thunderbolt + Lion Server.
    I wish I had the option to install Snow Leopard. But you can't install it on this iMac. The only machines that support Thunderbolt AND Snow Leopard are laptops. Unless we spent gobs of money on a Mac Pro + Fiber Channel (which would have been almost triple the price), our only choices were the new Mac Mini Server, or the new iMac, either of which supports Thunderbolt, but neither of which supports Snow Leopard.

  • Need advice on file locations / storage

    Hi,
    I was wondering if I should store all of the LR data including the DNG/RAW files outside of LR on an external RAID 1 eSATA CalDigit VR drive... it's wicked fast and since it's RAID 1 it's its own backup.
    I was wondering which datafiles produced by lightroom take up the most space? I am pretty sure it will be the DNG/RAW files with imbeded adjustment data...
    Any thoughts on using Mac's Time Machine to BU LightRoom data?
    Thanks

    Hi there again!
    Here, in this new company I have a little more time to make some testing... and so made a few and... thats just a problem with "older" software. I've just downloded the indesign CS3 demo from Adobe website and made a test.
    I've made a new freehand MX doc and a Indesign CS3 doc and place on both an image that it is stored in a PC with Windows XP (cifs:// share) and an image on other Mac running OS X. Saved the files and close the apps. Unmount both shared volumes and then mount again.
    When opening the freehand MX doc it did find the image stored on the other Mac but not the one stored on the PC.
    When opening the Indesign doc everything was fine. It opened both linked images without loosing the "path" to the files.
    I remember that I've done this test (freehand only) in the previous company I was wich had an Windows 2003 server with a smb/cifs share. I ask the IT guy to make a afp share for the macs using the "services for macintosh" but he couldnt get there so I was stucked with that "solution".
    There we used mostly freehand... it was a everyday nightmare. We had a folder with the logos from all the companies in the groupe in one folder in tiif, jpeg and eps format to link to projects and dont have repeated files all over the place, so every time we opened a freehand file that had a link to those logos I sometimes have to find the path for every single files linked to that one...
    I'm trying to convince everyone here to go CS3 exclusively and put freehand away. It aint gonna be developed any further so... but until than we have lots of projects already done with it and will continue for some time more
    eMac   Mac OS X (10.3.7)  

  • Firefox cannot load a directory content using file:///...

    I'm currently using Firefox 3.6.12 on Windows server 2003 64 bits.
    When browsing a smb share mounted on windows with an URL like:
    file:///L:/dossiers_techniques/bugs/I18n_Ndmp/dir-utf8/Mus-%F0%9D%84%9E
    (NB: it's displayed without the %xy stuff but using the appropriate font and glyph)
    I simply obtain the following error page:
    XML Parsing Error: reference to invalid character number
    Location: file:///L:/dossiers_techniques/bugs/I18n_Ndmp/dir-utf8/Mus-%F0%9D%84%9E
    Line Number 184, Column 76:<title>Index of file:///L:/dossiers_techniques/bugs/I18n_Ndmp/dir-utf8/Mus-&#xd834;&#xdd1e;</title>
    ---------------------------------------------------------------------------^
    NB: I've crafted this folder and its content for I18N test purposes in the applications I'm working on.
    And this specific Firefox test was triggered by a more complex configuration involving Flex and Java which thrown an exception (java.io.UTFDataFormatException).
    As a matter of fact, using Firefox 3.0.8 running on linux, I can browse the same directory (shared and mounted through nfs) with just the small graphical issue that the single G CLEF glyph is displayed as two unknown glyphs:
    Index of file:///usr/people/lps/dossiers_techniques/bugs/I18n_Ndmp/dir-utf8/Mus-��
    I've uploaded the same "dir_utf8" content on a web server, (see URL given in the "URL of affected site" which is NOT affected): it works pretty find, if the character encoding is manually set to "Unicode (UTF-8)".
    Hence it does seem that this issue is Windows or cifs or file: protocol related.

    Clear the cache and the cookies from sites that cause problems.
    "Clear the Cache":
    * Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
    "Remove Cookies" from sites causing problems:
    * Tools > Options > Privacy > Cookies: "Show Cookies"
    Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
    *Don't make any changes on the Safe mode start window.
    *https://support.mozilla.com/kb/Safe+Mode

  • Incorrect Folder Count (-63) report from TechTool Pro

    I've gotten this message a couple times. I can't find any info on what the -63 error message is (I assume it's an incorrect folder count).
    The last time it happened I booted off the startup disc and ran disc utility, which found two extra folders. I repaired the disc and it was fine for about a week, now it's back. Any ideas what might be causing this?

    +I can't find any info on what the -63 error message is+
    "This error can occur if your Mac OS X 10.4 client is trying to connect to a Samba or Windows (SMB/CIFS) server that only supports plain text passwords"
    http://docs.info.apple.com/article.html?artnum=301580

  • Windows 7 and CIFS

    I've seen a few people bring up the topic already - but no useful answers yet. Has Novell found a way to make Netware CIFS work with Windows 7 yet?
    I've been experimenting with Windows 7 - worked perfectly, almost at what I'd use for production on one test computer... Loading Novell Client 2 IR1a blew it to hell. I decided not to try that again, and simply try CIFS. That didn't work, and Googling the issue brought up countless references to the fact that they (Win7 & CIFS) still can't talk to each other.
    ...This test computer is running Windows 7 Home Premium.
    ...Any answers other than "no clue" would be appreciated!

    Originally Posted by JSwart
    I've seen a few people bring up the topic already - but no useful answers yet. Has Novell found a way to make Netware CIFS work with Windows 7 yet?
    I've been experimenting with Windows 7 - worked perfectly, almost at what I'd use for production on one test computer... Loading Novell Client 2 IR1a blew it to hell. I decided not to try that again, and simply try CIFS. That didn't work, and Googling the issue brought up countless references to the fact that they (Win7 & CIFS) still can't talk to each other.
    ...This test computer is running Windows 7 Home Premium.
    ...Any answers other than "no clue" would be appreciated!
    no clue...Just kiding.
    Do the following:
    - select "start" -> "run"
    - type "secpol.msc" to open your local security policy
    - then got to "local policies" -> "security options" and set the "Network Security: LAN Manager" from "Send NTLMv2 response only" to "Send LM & NTLM -- use NTLMv2 session security if negotiated. "
    https://forums.openfiler.com/viewtopic.php?id=2004

Maybe you are looking for