SMB 3.0 support???

Hello all,
Does anyone know if SMB 3.0 is supported by WAAS?  If not, is there an expected date for support?
Thanks,
Kirk

Is there an expected time line when the SMB v3 would be rolled out for the WAAS product?
Getting more and more requests if the SMB v3 is supported and at this stage I cannot answer back.
Frits

Similar Messages

  • Which SMB router will support broadband at 60 Mbps download?

    Hello, we are trying to decide on which router in the SMB line would support the above speeds on the WAN?
    The datasheets provide NAT throughput info but I am not sure if that is enough to make a decision.
    The RV180 series seems to offer NAT throughput at 800Mbps. Services other than NAT will not be required.
    The RV042 also seems to be capable of supporting this speed but overall, it is not really clear if any of the RV's will work or not.
    Please help?
    Thanks!!

    According to this review RV180 won't support 60Mbps:
    https://supportforums.cisco.com/message/3618617#3618617
    Tibor Kiss 23-Apr-2012 12:26 PM
    In fact the NAT Throughput is far from reality... The real throughput is between 50-60 Mbps. We tried with a 120 Mbps ISP and also tried it with 2 PC (from WAN side to LAN side of course). We also tried with 2 different W type and a simple RV180 and the results are the same.
    Considering the 1 Gbps port capabilities (which are OK!) and the expectations of today's (for example the 120 Mbps internet packages) this is really ridiculous! We tried it with and without every feature (firewall), etc., but now I have to say that this is true for all first version of the RV180 series.
    I personally tested RV042 with a 60/3 Mbps cable modem connection without any slow down QoS activated. But make sure you put more than your connection for the max inbound/outbound.

  • Changes to SMB/CIFS? Support for Byte-Range Locking?

    Since upgrading to leopard I have noticed some significant change to the "SMB" protocol. I am trying to confirm if byte-range locking is now supported by "SMB" in Leopard. Can anyone verify this. Is there anywhere to see what changes have been made to SMB/CIFS in Leopard?

    Since upgrading to leopard I have noticed some significant change to the "SMB" protocol. I am trying to confirm if byte-range locking is now supported by "SMB" in Leopard. Can anyone verify this. Is there anywhere to see what changes have been made to SMB/CIFS in Leopard?

  • Best file manager with SMB and streaming support? Time Capsule access?

    Constantly having to jump through hoops it seems, because of no file manager in iOS. Another simple scenario: have 2 disks connected to my Apple Time Capsule. Can accesss them with Android phones, always in trouble finding a good app on iPhone. Any tips? Wish I could also stream my home videos, etc from these disks. Documents 5 (Readdle) can access them via SMB, but not stream, which is nasty for large videos.
    Thank you,
    Roman

    I was experiencing the same problem when I upgraded to a Time Capsule. To fix the problem remove all personal file sharing port mapping settings. Then make sure that the enable  file share, and enable over WAN is on and checked for the TC, then update the TC. While that's updating go into the server app and remove any old file sharing protocols from the TC on the server app. Next add a new custom protocol by hitting the + name it file share and set the port to 140. hit the update button and wait for it to finish. Once that's finish go back to the airport utility and find the newly made file share protocol by selecting it under port mapping for the TC. If you don't have the newly made one in there make a new one your self. Name it the same as you did in the server app and set the public TCP ports to 140 and the private TCP ports to 548, make sure the private IP address is set to the same as your server in the reserve. Update the time capsule and you should be able to access both by putting in the appropriate afp://www.yourserver.com:140 for the server and afp://www.yourserver.com:548  for the TC. Have fun, lion server can be a little fussy!

  • 10.7 SMB no longer supports Lexmark and other apps

    I understand that Apple has changed SMB -- and it is not incompatible with lots of applications and devices (e.g. Lexmark scanners than scan to Mac).  Short of going back to Snow Leopard, is there a way to get the "old" SMB to replace the 10.7.6 SMB -- or is there a prayer that Apple will "fix" this problem?
    Thanks,
    Jim

    There are reports that this problem can be solved by simply restarting, or by resetting the PRAM.

  • Error to Connect Oracle Files from Mac Os10  using smb protocol .

    I connect my MacOs10 to oracle Workspaces using smb protocol but when I try to copy a file into a folder the system show me "error -36".
    From the finder I type "apple -k" and then I write "smb://nomeserver". The system show me "User name" and "Password" and after the authentication I see "MyHome" resource on my desktop.
    I navigate into MyWorkspaces folders and than I copy a file from a local directory. After a few second the system show me "error -36" and the file is not transferred from local to server.
    Any idea?
    Thanks

    In OCS10g SMB protocol not supported, use FTP or WebDav.

  • Can't connect to SMB server

    Hi! I have trouble with connection to my smb server on debian. When I try to connect from "connect to server" menu, I get this error: URLs with the type "smb:" are not supported". Now I can connect only with bash command. But few days ago all worked from GUI.
    In system.log I got this (I try connect from PathFinder & Finder):
    Feb 25 00:30:37 macbook Path Finder[44402]: An error occurred while trying to mount "smb://sofico"., err: Error: -36
    Feb 25 00:30:41 macbook NetAuthAgent[72818]: inErrorInfo = {          AuthType = Server;          ErrorNumber = 45;          ErrorType = 4;          Scheme = smb;

    Fix this by reinstalling OS X

  • Itunes, Leopard and SMB

    My entire iTunes library is stored on a NAS - an Iomega Home Network Drive. It mounts under Leopard as SMB. It supports SMB and FTP.
    Browsing and writing files is possible, but flaky. I think this is a known bug in Leopard 10.5.1. I use FTP to transfer files. It's annoying, but it works.
    Importing the music library into iTunes went fine, but I am not able to play back any file. Nothing happens when I click "play" or doubleclick the mp3. Also, album art does not show up.
    Now it gets interesting. When I manually browse to the mp3 in the Finder and "get info" on it, suddenly iTunes sees it, the album art is displayed, and the mp3 plays. It also plays all the other mp3s in that album. This continues to works until I reboot.
    Considering how large my iTunes library is, getting info on every album I want to play back is not quite an option.
    I'm pretty sure this is a bug in Leopard, so I'm not expecting an answer - but is anyone else seeing behavior like this?

    This issue was not fixed in 10.5.2. I have deleted my iTunes library and imported it again, but no mp3s will play. Also, it now complains that it cannot locate the file even though the share is mounted.
    Anyone?

  • Setting up SMB to respect ACL

    Hi,
    I've setup my 10.6.3 server to use ACL and it works fine over AFP. However, I have a bunch of problems with the AFP service, so checked if SMB was giving me the same problem and it doesn't. So, I want to change my users to use SMB instead of the defacto AFP. All clients are macs (10.5.8 and 10.6.x). Using smb, right now, it looks like it uses the posix permission and just ignores the ACL on the share point. So how can I make SMB work like AFP when permission is concerned? I've changed the umask on each client machine and on the server so the default folder creation is 775 instead of 755, but if they copy something on the server that was done prior to that change, the files are read-write by the owner only and read only for the group and others.
    There is also the issue of special characters not supported by SMB that are supported by AFP. Is there a list of those characters, specifically for the OS X server SMB implementation?
    TIA
    Jeff

    You want to map oracle files to your windows client ?
    open up a command prompt and do the following:
    net use * \\hostname.domain\\MyHome
    What this does is map what you see in oracle files via the web interface :
    my private files
    my public files
    my workspaces
    to the next available drive letter on your pc. The various file sections (listed above) should appear as folders under that drive.

  • Can see shares but can't access them

    I have files located on a Mac OSX Server. I've enabled SMB file sharing support on that box.
    From my Arch desktop I can now list those shares with smbclient:
    smbclient -L 192.168.0.15 -U%
    Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.28a-apple]
    Sharename Type Comment
    IPC$ IPC IPC Service (Mac OS X Server)
    Unsorted Disk Unsorted
    Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.28a-apple]
    Server Comment
    MEDIA-SERVER Mac OS X Server
    Workgroup Master
    WORKGROUP
    That has taken me an hour because Apple had "available = no" in the smb.conf (despite all of their glossy UI's saying everything was enabled and accessible). I cannot seem to connect to the Unsorted share now though.
    smbclient //192.168.0.15/Unsorted -U%
    Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.28a-apple]
    At which point it just hangs. Are there any client side settings I can check? Otherwise I assume this is a server side issue and I should hit the Apple forums?

    I used NFS instead which was far easier to set up. Just created /etc/exports file and started NFS via the Apple Server Admin.

  • Mountain lion 10.8.2 can not connect to windows NAS server Dell Sentinel

    I recently upgraded to 10.8 OS My office is connected to a NAS server Dell Sentinel WD4000. Everything was working fine until the upgrade from 10.7 to 10.8 Now when I "connect to server" Not one of my accounts can connect. All I get is wrong password. The server connects to every computer on the network except the 10.8 The server shows up as an icon on Shared Devices.
    Someone please help me. Apple has been useless.

    I hope this helps.  But, Apple has confirmed a significant bug in 10.7.4 that breaks SMB.  Their support says they are working on it, but they do not know when the fix will be released.  It has broken SMB at all sites I support including my own location where Lion server has the updated version as well.  Only AFP works but not consistently.  The suggestion is to restore 10.7.3 from a backup or wait until the fix is released.  SMB does work - but only when admin authentication is used on Mac servers - don't know about Windows Servers.  I do know the client side of Mac's also are affected with SMB issues.  Good luck!

  • MAC OS 10.4.5 ACCESS AD W2K3

    PEOPLE,
    Please a need help.
    I can't access my w2k3 server using Mac OS X 10.4.5
    I tryied using: smb://ipofserver, smb://nameserver/user, smb://ipofserver, smb://nameofserver
    return the message user or password incorrect, and Alias error.
    PLEASE, PLEASE SOMEBODY HELP!
    regards,
    Fabiano Golfre
    [email protected]

    Hi Fabiano!
    Windows 2003 Server comes with a security policy enabled called "Digitally Sign Communications". Mac OS X's version of SMB does not support this.
    You will need to disable this policy on the server. Have a look at this page on MacOSXHints.com for details: http://www.macosxhints.com/article.php?story=20030922153448490.
    Hope this helps! bill
    1 GHz Powerbook G4   Mac OS X (10.4.5)  

  • [Forum FAQ] Troubleshooting Network File Copy Slowness

    1. Introduction
    The Server Message Block (SMB) Protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. The set of message packets that defines a particular version of the protocol is called a dialect. The Common
    Internet File System (CIFS) Protocol is a dialect of SMB. Both SMB and CIFS are also available on VMS, several versions of Unix, and other operating systems.
    Microsoft SMB Protocol and CIFS Protocol Overview
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa365233(v=vs.85).aspx
    Server Message Block overview
    http://technet.microsoft.com/en-us/library/hh831795.aspx
    1.1
    SMB Versions and Negotiated Versions
    - Thanks for the
    Jose Barreto's Blog
    There are several different versions of SMB used by Windows operating systems:
    CIFS – The ancient version of SMB that was part of Microsoft Windows NT 4.0 in 1996. SMB1 supersedes this version.
    SMB 1.0 (or SMB1) – The version used in Windows 2000, Windows XP, Windows Server 2003 and Windows Server 2003 R2
    SMB 2.0 (technically SMB2 version 2.002) – The version used in Windows Vista (SP1 or later) and Windows Server 2008 (or any SP)
    SMB 2.1 ((technically SMB2 version 2.1) – The version used in Windows 7 (or any SP) and Windows Server 2008 R2 (or any SP)
    SMB 3.0 (or SMB3) – The version used in Windows 8 and Windows Server 2012
    SMB 3.02 (or SMB3) – The version used in Windows 8.1 and Windows Server 2012 R2
    Windows NT is no longer supported, so CIFS is definitely out. Windows Server 2003 R2 with a current service pack is under Extended Support, so SMB1 is still around for a little while. SMB 2.x in Windows Server 2008 and Windows Server 2008
    R2 are under Mainstream Support until 2015. You can find the most current information on the
    support lifecycle page for Windows Server. The information is subject to the
    Microsoft Policy Disclaimer and Change Notice.  You can use the support pages to also find support policy information for Windows
    XP, Windows Vista, Windows 7 and Windows 8.
    In Windows 8.1 and Windows Server 2012 R2, we introduced the option to completely disable CIFS/SMB1 support, including the actual removal of the related binaries. While this is not the default configuration, we recommend disabling this older
    version of the protocol in scenarios where it’s not useful, like Hyper-V over SMB. You can find details about this new option in item 7 of this blog post:
    What’s new in SMB PowerShell in Windows Server 2012 R2.
    Negotiated Versions
    Here’s a table to help you understand what version you will end up using, depending on what Windows version is running as the SMB client and what version of Windows is running as the SMB server:
    OS
    Windows 8.1  WS 2012 R2
    Windows 8  WS 2012
    Windows 7  WS 2008 R2
    Windows Vista  WS 2008
    Previous versions
    Windows 8.1 WS 2012 R2
    SMB 3.02
    SMB 3.0
    SMB 2.1
    SMB 2.0
    SMB 1.0
    Windows 8 WS 2012
    SMB 3.0
    SMB 3.0
    SMB 2.1
    SMB 2.0
    SMB 1.0
    Windows 7 WS 2008 R2
    SMB 2.1
    SMB 2.1
    SMB 2.1
    SMB 2.0
    SMB 1.0
    Windows Vista WS 2008
    SMB 2.0
    SMB 2.0
    SMB 2.0
    SMB 2.0
    SMB 1.0
    Previous versions
    SMB 1.0
    SMB 1.0
    SMB 1.0
    SMB 1.0
    SMB 1.0
    * WS = Windows Server
    1.2 Check, Enable and Disable SMB Versions in Windows operating systems
    In Windows 8 or Windows Server 2012 and later, there is a new PowerShell cmdlet that can easily tell you what version of SMB the client has negotiated with the File Server. You simply access a remote file server (or create a new mapping to it) and use Get-SmbConnection.
    To enable and disable SMBv1, SMBv2, and SMBv3 in Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012, please follow the steps in the article below.
    Warning: We do not recommend that you disable SMBv2 or SMBv3. Disable SMBv2 or SMBv3 only as a temporary troubleshooting measure. Do not leave SMBv2 or SMBv3 disabled.
    http://support.microsoft.com/kb/2696547
    1.3 Features and Capabilities
    - Thanks for the
    Jose Barreto's Blog
    Here’s a very short summary of what changed with each version of SMB:
    From SMB 1.0 to SMB 2.0 - The first major redesign of SMB
    Increased file sharing scalability
    Improved performance
    Request compounding
    Asynchronous operations
    Larger reads/writes
    More secure and robust
    Small command set
    Signing now uses HMAC SHA-256 instead of MD5
    SMB2 durability
    From SMB 2.0 to SMB 2.1
    File leasing improvements
    Large MTU support
    BranchCache
    From SMB 2.1 to SMB 3.0
    Availability
    SMB Transparent Failover
    SMB Witness
    SMB Multichannel
    Performance
    SMB Scale-Out
    SMB Direct (SMB 3.0 over RDMA)
    SMB Multichannel
    Directory Leasing
    BranchCache V2
    Backup
    VSS for Remote File Shares
    Security
    SMB Encryption using AES-CCM (Optional)
    Signing now uses AES-CMAC
    Management
    SMB PowerShell
    Improved Performance Counters
    Improved Eventing
    From SMB 3.0 to SMB 3.02
    Automatic rebalancing of Scale-Out File Server clients
    Improved performance of SMB Direct (SMB over RDMA)
    Support for multiple SMB instances on a Scale-Out File Server
    You can get additional details on the SMB 2.0 improvements listed above at
    http://blogs.technet.com/b/josebda/archive/2008/12/09/smb2-a-complete-redesign-of-the-main-remote-file-protocol-for-windows.aspx
    You can get additional details on the SMB 3.0 improvements listed above at
    http://blogs.technet.com/b/josebda/archive/2012/05/03/updated-links-on-windows-server-2012-file-server-and-smb-3-0.aspx
    You can get additional details on the SMB 3.02 improvements in Windows Server 2012 R2 at
    http://technet.microsoft.com/en-us/library/hh831474.aspx
    1.4 Related Registry Keys
    HKLM\SYSTEM\CurrentControlSet\Services\MrxSmb\Parameters\
    DeferredOpensEnabled – Indicates whether the Redirector can defer opens for certain cases where the file does not really need to be opened, such as for certain delete requests and adjusting file attributes.
    This defaults to true and is stored in the Redirector variable MRxSmbDeferredOpensEnabled.
    OplocksDisabled – Whether the Redirector should not request oplocks, this defaults to false (the Redirector will request oplocks) and is stored in the variable MrxSmbOplocksDisabled.
    CscEnabled – Whether Client Side Caching is enabled. This value defaults to true and stored in MRxSmbIsCscEnabled. It is used to determine whether to execute CSC operations when called. If CSC is enabled,
    several other parameters controlling CSC behavior are checked, such as CscEnabledDCON, CscEnableTransitionByDefault, and CscEnableAutoDial. CSC will be discussed in depth in its own module, so will be only mentioned in this module when it is necessary to understanding
    the operation of the Redirector.
    DisableShadowLoopback – Whether to disable the behavior of the Redirector getting a handle to loopback opens (opens on the same machine) so that it can shortcut the network path to the resource and
    just access local files locally. Shadow opens are enabled by default, and this registry value can be used to turn them off. It is stored in the global Redirector variable RxSmbDisableShadowLoopback.
    IgnoreBindingOrder – Controls whether the Redirector should use the binding order specified in the registry and controlled by the Network Connections UI, or ignore this order when choosing a transport
    provider to provide a connection to the server. By default the Redirector will ignore the binding order and can use any transport. The results of this setting are stored in the variable MRxSmbObeyBindingOrder.
    HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
    Security Signature settings – The RequireSecuritySignature setting is stored in MRxSmbSecuritySignaturesRequired, EnableSecuritySignature in MRxSmbSecuritySignaturesEnabled, RequireExtendedSignature
    in MRxSmbExtendedSignaturesRequired, and EnableExtendedSignature in MRxSmbExtendedSignaturesEnabled. Note that the Extended Security Signatures assume the regular security signatures are enabled, so those settings are adjusted if necessary based on the extended
    settings. If extended signatures are required, regular signatures have to be required.
    EnablePlainTextPassword – Support for using plain text passwords can be turned on using this key. They are disabled by default.
    OffLineFileTimeoutIntervalInSeconds – Used to set the expiration time for timing out an Exchange (discussed later) when the exchange is accessing an offline file. This value defaults to 1000 seconds,
    but can be changed in the registry and is stored in the global Redirector variable OffLineFileTimeoutInterval
    SessTimeout – This is the amount of time the client waits for the server to respond to an outstanding request. The default value is 60 seconds (Windows Vista). When the client does not receive the
    response to a request before the Request Expiration Timer expires, it will reset the connection because the operation is considered blocked. In Windows 8, the request expiration timer for the SMB 2 Negotiate is set to a smaller value, typically under 20 seconds,
    so that if a node of a continuously available (CA) cluster server is not responding, the SMB 3.0 client can expedite failover to the other node.
    ExtendedSessTimeout – Stored in the ExtendedSessTimeoutInterval variable, this value is used to extend the timeout on exchanges for servers that require an extended session timeout as listed in the
    ServersWithExtendedSessTimeout key. These are third party servers that handle SMB sessions with different processes and vary dramatically on the time required to process SMB requests. The default value is 1000 seconds. If the client is running at least Windows
    7 and ExtendedSessTimeout is not configured (By Default), the timeout is extended to four times the value of SessTimeout (4 * SessTimeout).
    MaxNumOfExchangesForPipelineReadWrite – This value is used to determine the maximum number of write exchanges that can be pipelined to a server. The default is 8 and the value is stored in the variable
    MaxNumOfExchangesForPipelineReadWrite.
    Win9xSessionRestriction – This value defaults to false, but is used to impose a restriction on Windows 9x clients that they can only have one active non-NULL session with the server at a time. Also,
    existing session based connections (VNETROOTS) are scavenged immediately, without a timeout to allow them to be reused.
    EnableCachingOnWriteOnlyOpens – This value can cause the Redirector to attempt to open a file that is being opened for write only access in a manner that will enable the Redirector to cache the file
    data. If the open fails, the request will revert back to the original requested access. The value of this parameter defaults to false and is stored in the MRxSmbEnableCachingOnWriteOnlyOpens variable.
    DisableByteRangeLockingOnReadOnlyFiles – This parameter defaults to false, but if set to true will cause level II oplocks to automatically be upgraded to batch oplocks on read-only files opened for
    read only access. It is stored in the variable DisableByteRangeLockingOnReadOnlyFiles.
    EnableDownLevelLogOff – False by default, this value controls whether a Logoff SMB will be sent to down-level servers when a session is being closed. If this is false, and the server has not negotiated
    to the NT SMB dialect or does not support NT Status codes, the logoff will not be sent because we aren’t sure that server will understand the request. The value is stored in MrxSmbEnableDownLevelLogOff.
    HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\
    ResilientTimeout – This timer is started when the transport connection associated with a resilient handle is lost. It controls the amount of time the server keeps a resilient handle active after the
    transport connection to the client is lost. The default value is 300 seconds (Windows 7, Server 2008 R2, 8, Server 2012).
    DurableHandleV2TimeoutInSecond – This timer is started when the transport connection associated with a durable handle is lost. It controls the amount of time the server keeps a durable handle active
    after the transport connection to the client is lost. The default value is 60 seconds (Windows 8, Windows Server 2012). The maximum value is 300 seconds.
    HKLM\SYSTEM\CurrentControlSet\Services\SMBWitness\Parameters\
    KeepAliveInterval – This functionality was introduced for SMB 3.0 in Windows 8 and Windows Server 2012. The witness protocol is used to explicitly notify a client of resource changes that have occurred
    on a highly available cluster server. This enables faster recovery from unplanned failures, so that the client does not need to wait for TCP timeouts. The default value is 20 minutes (Windows 8, Windows Server 2012).
    HKLM\System\CurrentControlSet\Services\SmbDirect\Parameters\
    ConnectTimeoutInMs – Establish a connection and complete negotiation. ConnectTimeoutInMs is the deadline for the remote peer to accept the connection request and complete SMB Direct negotiation. Default
    is 120 seconds (Windows 8).
    AcceptTimeoutInMs – Accept negotiation: The SMB Direct Negotiate request should be received before AcceptTimeoutInMs expires. The servers starts this timer as soon as it accepted the connection. Default
    is 5 seconds (Windows 8).
    IdleConnectionTimeoutInMs – This timer is per-connection. It is the amount of time the connection can be idle without receiving a message from the remote peer. Before the local peer terminates the
    connection, it sends a keep alive request to the remote peer and applies a keep alive timer. Default is Default: 120 seconds (Windows 8).
    KeepaliveResponseTimeoutInMs – This attribute is per-connection. It defines the timeout to wait for the peer response for a keep-alive message on an idle RDMA connection. Default is 5 seconds (Windows
    8).
    CreditGrantTimeoutInMs – This timer is per-connection.  It regulates the amount of time that the local peer waits for the remote peer to grant Send credits before disconnecting the connection.
    This timer is started when the local peer runs out of Send credits. Default is 5 seconds (Windows 8).
    References:
    [MS-SMB]: Server Message Block (SMB) Protocol
    http://msdn.microsoft.com/en-us/library/cc246231.aspx
    [MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3
    http://msdn.microsoft.com/en-us/library/cc246482.aspx
    SMB 2.x and SMB 3.0 Timeouts in Windows
    http://blogs.msdn.com/b/openspecification/archive/2013/03/27/smb-2-x-and-smb-3-0-timeouts-in-windows.aspx

    3. How to Troubleshoot
    3.1 Troubleshooting Decision Tree
    1
    Is the slowness occurring in browsing a network shared folder or   copying a file, or both?
    Browsing, go to 1.1.
    Copying, go to 1.2.
    Both, go to 1.3.
    1.1
    Is the target a DFS path or not?
    Yes, go to 1.1.1.
    No, go to 1.1.2.
    1.1.1
    Is the client visiting the nearest DFS root server and file   server?
    Yes, go to 1.1.1.1.
    No, go to 1.1.1.2.
    1.1.1.1
    Browse the corresponding (Non-DFS) UNC path directly. Do you   still experience the slowness?
    Yes, go to 1.1.1.1.1.
     No,
    go to 1.1.1.1.2.
    1.1.1.1.1
    Issue is the particular file server responds to the share folder   enumeration requests slowly. Most probably it’s
    unrelated to DFS. Follow   1.1.2.
    1.1.1.1.2
    Issue is that client experiences delay when browsing the DFS   path, but no delay is visiting the target file server
    directly. Capture   Network Monitor trace from the client and study if the DFS path is cracked   down.
    1.1.1.2
    Use dfsutil.exe to clear local domain and referral cache. Then   visit the DFS path again and capture Network Monitor
    trace from the client to   study why the client goes to a wrong file server or DFS root server.
    1.1.2
    Not a DFS issue. Issue is the particular file server responds to   the share folder enumeration requests slowly. “Dir”
    the same share folder   from Command Prompt. Is it slow?
    Yes, go to 1.1.2.1
    No, go to 1.1.2.2
    1.1.2.1
    Check the number of subfolders and files in that share folder.   Is the number large?
    Yes, go to 1.1.2.1.1
    No, go to 1.1.2.1.2
    1.1.2.1.1
    Try to “dir” a different share folder on the same file server,   but with less items. Is it still slow or not?
    Yes, go to 1.1.2.1.1.1
    No, go to 1.1.2.1.1.2
    1.1.2.1.1.1
    Probably to be performance issue of the file server. Capture   Network Monitor trace from both sides, plus Performance
    Monitor on the file   server.
    1.1.2.1.1.2
    Probably to be performance issue of the file server,   particularly, of the disk. Capture Network Monitor trace from
    both sides,   plus Performance Monitor on the file server.
    1.1.2.1.2
    Same as 1.1.2.1.1.1. Probably to be performance issue of the   file server. Capture Network Monitor trace from both
    sides, plus Performance   Monitor on the file server.
    1.1.2.2
    Explorer.exe browses the share folder slowly while “dir” does   fast. The issue should lie in the particular SMB traffic
    incurred by   explorer.exe. It's a Shell issue.
    1.2
    Is the target a DFS path or not?
    Yes, go to 1.2.1
    No, go to 1.2.2
    1.2.1
    Is the client downloading/uploading against the nearest file   server?
    Yes, go to 1.2.1.1
    No, go to 1.2.1.2
    1.2.1.1
    Try to download/upload against that file server using the   Non-DFS share path. Still slow?
    Yes, go to 1.2.1.1.1
    No, go to 1.2.1.1.2
    1.2.1.1.1
    Not a DFS issue. Capture Network Monitor trace from both sides   to identify the pattern of the slowness.
    1.2.1.1.2
    This is unlikely to occur because the conclusion is   contradictory to itself. Start from the beginning to double
    check.
    1.2.1.2
    Same situation as 1.1.1.2. Use dfsutil.exe to clear local domain   and referral cache. Then visit the DFS path again
    and capture Network Monitor   trace from the client to study why the client goes to a wrong file server or   DFS root server.
    1.2.2
    Same as 1.2.1.1.1. It's not a DFS issue. Capture Network Monitor   trace from both sides to identify the pattern of
    the slowness.
    1.3
    Follow 1.1 and then 1.2.
    3.2 Troubleshooting Tools
    Network Monitor or Message Analyzer
    Download
    http://www.microsoft.com/en-us/download/details.aspx?id=40308
    Blog
    http://blogs.technet.com/b/messageanalyzer/
    Microsoft Message Analyzer Operating Guide
    http://technet.microsoft.com/en-us/library/jj649776.aspx
    Performance Monitor
    http://technet.microsoft.com/en-us/library/cc749249.aspx
    DiskMon
    http://technet.microsoft.com/en-us/sysinternals/bb896646.aspx
    Process Monitor
    http://technet.microsoft.com/en-us/sysinternals/bb896645

  • SL Server Permission Issues with Windows XP Clients

    I'm running into some permissions issues with Snow Leopard Server. I know it's specific to SL Server because I have two Leopard servers and neither one is affected. All servers are set up the same way.
    I'm using this SL server as a file server in the golden triangle approach: AD for Users, OD for Groups that supply AD User membership. I have one volume per OD group, and that group has read/write privileges to that volume via the default Server Admin read/write ACL. POSIX permissions are 770 on the top level directory, and ownership is set to the AD user who owns the volume, and the OD group the volume belongs to.
    The client is XP SP3. When the client accesses a share on the SL server, their access is correctly granted and they can browse the share and read any files inside the share. They can copy files to the share from wherever. They can open, edit, and save files. However, they cannot rename or delete files within the share. They cannot rename folders, but can delete them. This affects all AD users regardless of the OD group they're in.
    I have a few Windows 7 and Vista clients on the network, and these two OS's are not affected by this so the problem is limited to XP. If I create a user in OD, and auth to the sever from the XP client as that user, the problem goes away, so it's something to do with AD and SMB.
    I do have a ticket in with Apple support, which was escalated to Engineering. Still waiting on that.
    Things I have tried that have not worked/helped:
    -Modify the ACL to Full Privileges
    -Tried removing/re-adding user to OD group.
    -Remove darwin_streams from vfs_objects in smb.conf
    stream support = no
    ea support = yes/no (tried both ways)
    darwin_streams:brlm = no
    -Added nt acl support = no to smb.conf
    per http://bit.ly/6aYycW
    -Animal sacrifice..... ??
    Help?

    I need to do more testing, but I think the fix is to add "acl check permissions = no" to the bottom of /etc/smb.conf:
    ; Site-specific parameters can be added below this comment.
    [global]
    acl check permissions = no

  • XL Report Error

    Hi
    I have a problem in XL Report, when i try to generate a report based on a query made in composer or even when i try to generate through the report organizer.
    The error that happens is:
    An error occurred during the process "Report Initialize". Description: (666) Error! Unable to get document! Cause: Automation error. XL report startup failed!
    I look in Excel and it seems that an add'in should be installed and there isn't any, so the toolbar of XL Report doesn't appears.
    Best Regards

    I found it,
    First, Damien - I still get the error with a power user too.
    My SAP consultant and I found an obscure mention of the problem at the SAP Marketplace www.service.sap.com/smb in the support notes database with the seach XLR. We found an explination about the error and it stated to also add a config file for Microsoft Excel called “excel.exe.config” to the directory where “excel.exe” is,
    with the contents of the config file are :
    <?xml version="1.0"?>
    <configuration>
         <startup>
              <supportedRuntime version="v1.1.4322"/>
              <supportedRuntime version="v1.0.3705"/>
              <requiredRuntime version="v1.0.3705"/>
         </startup>
    </configuration>
    Keep in mind that if you are using DotNet Framework 2.0 with Excel in another application you may run into problems because <b>you cannot add</b> the line
              <supportedRuntime version="v2.0.50727" />
    XL Reporter will not work.
    Hopefully they will fix this in future releases of XL Reporter.

Maybe you are looking for