SMB Protocol Version on Zfs

Hi,
It's seens that smb shares created with zfs share command are using smb 1.0; after some wireshark on Windows Machines, the protocol used is smb not smb2.
On previous versions, I could set this on /etc/samba/smb.conf (max protocol = SMB2). "- The Oracle Solaris 11 OS introduces a new method for sharing and managing SMB and NFS shares. The zfs command has been enhanced to manage shares and share properties on Solaris ZFS file systems. The zfs command now supports SMB and NFS sharing by means of the share, sharesmb, and sharenfs properties"
Is there a way to force zfs smb shares to exported on smb2?
Regards
M

cindys wrote:
My very limited view is that if you create an SMB share of a Solaris ZFS file system, then the share should be available on Windows system running SMB or SM2. SMB and SM2 should interoperate, like different versions of NFS do. What is the actually problem?
Thanks, CindyHi Cindy,
I am able to connect to the shares.
Windows Client can mount the share and after some time:
Exception message: Failed to start monitoring changes to '\\sol11-zfs-01\mypool-fs0001\076\home' because the network BIOS command limit has been reached.
I've created a linux box with smb2 and this error won't occour (samething happens on smb1-linux). I am not sure which feature exactly fixes this error.
Using a cmdlet on win2012,
PS C:\Windows\system32> Get-SmbConnection
ServerName ShareName UserName Credential Dialect NumOpens
10.133.24.23 pool server\user server\uh-user 1.50 2
Dialect is 1.5.

Similar Messages

  • SMB protocol

    who knows if the SMB protocol will be supported in the future release of CMSDK (after 9.0.4.2.0) ?
    Gérard

    It is supported in 90422 (personal experience), and in talking to support and sales people from Oracle it is part of OCS. I think as long as you have a UNIX version of the software they will have to support it. Otherwise, how would Windows clients talk to the software.

  • 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.

  • Smb protocol problem after upgrading to IOS 8

    Hi,
    I use SMB protocol to connect to Windows share folders in our company.
    Using IOS 7 on the iPad was working great until i upgrade one iPad to IOS 8.
    I can't connect using SMB protocol on the iPad with IOS 8. With an iPad with IOS 7 still works great.
    The settings are the same. I tested Goodreader v3 and v4 and FileExplorer program on the iPad with IOS 8 and on the iPad with IOS 7.
    The problem is only on the iPad with IOS 8. It does not matter which program I use. All are not working.
    On the iPad with IOS 7 all the programs works just fine.
    It seems that after upgrading to IOS 8, I have problem connecting to the share folders in Goodreader v3, v4 and in FileExplorer.
    It seems the problem is not on the settings of the server, account etc, also not program related but with the IOS 8.
    Does someone have this problem or now how to fix this?

    Hi all,
    I have run some more test and the problem is not with the SMB protocol but to connect to a DFS server.
    One share name like company.local and behind this we have some servers.
    The problem is with the DFS name (routing) When I connect directly to one server share location, it works fine.

  • Transport protocol version error in Integration Directory API

    Hi All,
    I am trying to create SOAP receiver communication channel using Java-only PI 7.31 directory APIs. I have passed all the required parameters to the CommunicationChannelIn service, but it's throwing error - "Enter at least one object key for operation 'create'".
    When I tried to test the service through WS Navigator, it's giving exception - "Enter a value for attribute 'Transport Protocol Version'" which doesn't exists in case of SOAP adapter creation.
    Has anybody come across this issue? If the adapter metadata does not specify any transport protocol version, then shouldn’t the validation checks in  CommunicationChannelIn service provider proceed without errors on a blank value for this attribute?
    Note: I have gone through all the SCN blogs, discussion threads we have on topics related to Integration Directory API.
    Thanks in advance for all the help and suggestions.
    Regards,
    Yashu Vyas

    Hi All,
    I am trying to create SOAP receiver communication channel using Java-only PI 7.31 directory APIs. I have passed all the required parameters to the CommunicationChannelIn service, but it's throwing error - "Enter at least one object key for operation 'create'".
    When I tried to test the service through WS Navigator, it's giving exception - "Enter a value for attribute 'Transport Protocol Version'" which doesn't exists in case of SOAP adapter creation.
    Has anybody come across this issue? If the adapter metadata does not specify any transport protocol version, then shouldn’t the validation checks in  CommunicationChannelIn service provider proceed without errors on a blank value for this attribute?
    Note: I have gone through all the SCN blogs, discussion threads we have on topics related to Integration Directory API.
    Thanks in advance for all the help and suggestions.
    Regards,
    Yashu Vyas

  • Question about ssh login warning: Bad protocol version identification

    I set up ssh on my computer according to Tim Haigh's suggestions given here:
    http://discussions.apple.com/thread.jspa?threadID=1674968&tstart=0
    But when I log in from my iPhone, secure.log shows this:
    sshd[534]: Bad protocol version identification 'GET / HTTP/1.1' from 208.54.83.51
    Although I do log in successfully, how can I resolve this error?

    GET / HTTP/1.1
    Looks more like a Web browser handshake, than ssh.

  • Unable to connect to the server with smb protocol

    I have recently upgraded to Lion. On Snow Leopard I was able to access my work server using SMB protocol. Since the upgrade I am not able to do that and not able to login to my personal folder located on the network server.
    Any help is much appreciated
    Thanks

    Hi Sir,
    >>The week before it work perfectly and we have had nothing changed since then except for the fact that we have changed the RD web access public IP to the same as the RD Gateway's
    Is it possible to change the public IP back for troubleshooting ?
    Beset Regards,
    Elton Ji
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • Incompatible protocol versions

    I am attempting to run an iphone application on an iphone 4.3 simulator. I have confirmed that I can talk to the Unwired Server by seeing that my client is contacting the server in the logs. However, I am getting the following message in the xcode console:
    [INFO] [CallbackHandler.m:46] =============================
    [ERROR] [CallbackHandler.m:47] Message Exception
    [ERROR] [CallbackHandler.m:48] SUPPersistenceException: Device and server are not using compatible protocol versions: client protocol version = 1, server protocol version = -1.
    [INFO] [CallbackHandler.m:49] =============================
    I saw a similar question regarding this in the context of a blackberry app in the forums, but the error was a bit different and the solution (simply resetting the simulator) did not work for me. Has anyone encountered this issue before? If so can you explain what is going on here and how you got past it?
    Thanks!
    Jesse

    Please check the MBO deployed in the server is same as what you were using in the client side development.
    Regards,
    Ram

  • The vm and host networking components failed to negotiate protocol version '4.0'

    Hi,
    I have the problem that when I start a VM with windows server 2012 on a hyper-v v2 host, it takes very long till the VM get bind the static or dynamic ip adress. I tried both, static and dynamic. In every case I see at the event viewer the following error:
    the vm and host networking components failed to negotiate protocol version '4.0'
    After a few minutes the VM gets bind the IP an everything works fine. But at the next time I reboot the machine the same failure appear.
    Trying to use legacy network adapter results in the same problem. After this I tried to export the vm to a hyper-v v3 host. At first boot time
    the problem didn't appear and the vm get's bind the ip adress without problems. Then after upgrading the integration services to hyper-v v3
    version the same problem appears but without register it in the event viewer.
    Does anybody know how I can fix this problem?
    Kind Regards,
    Marcus

    Hi,
    A MS KB records an issue when you run Windows 8 or Windows Server 2012 based Virtual machine in Windows Server 2008 or in Windows Server 2008R2:
    http://support.microsoft.com/kb/2744129
    There is a Microsoft update in this KB, you may install this KB in your Windows Server 2008 R2 and check the result.
    While about this issue after you migrate the guest VM to Windows Server 2012 host, will it still has such error message after you remove all network adapters of the guest VM?
    Install Windows update for the Hyper-V host, after that upgrade Integration service for the guest VM again to check the result.
    For more information please refer to following MS articles:
    "Unsupported configuration" warning when you run a Windows 8-based or Windows Server 2012-based virtual machine in Windows Server 2008 R2
    http://support.microsoft.com/kb/2737297
    Hyper-V Overview
    http://technet.microsoft.com/en-us/library/hh831531.aspx
    Lawrence
    TechNet Community Support

  • SMB Protocol disconnect (deadtime) setting

    We are implementing an Xserve G5 as a NAS, and Apple has confirmed that using the SMB protocol (which we must use due to connections from Windows clients) has a default setting to disconnect after a certain time of inactivity.
    I was told to modify the /etc/smb.conf file to include the setting:
    deadtime = 0
    After doing this and restarting the server, we are noticing clients are still getting disconnected after being idle. I am certain other people have needed to do this, so wondering if anyone has any experience setting this up properly? Thank you,

    Haha,
    I figured it out, although I don't pretend to know exactly why it works.
    Here is what I did.
    Instead of "smb://servername/share", I put in "smb://servername.mycompany.com/share".
    On the WinXP computer, typing in "\\servername.mycompany.com\share" also worked.
    I'm thinking it has something to do with DNS, but I'm not sure exactly. I'm just glad that it worked. I got the idea from this link here. http://hints.macworld.com/article.php?story=20080307092123215
    Thanks all,
    Ck

  • Which protocol version is really used?

    In the JSSE reference guide, Appendix A: Standard Names, is said, that the protocol name passed to the getInstance method of the SSLContext class maybe one of the following: SSL, SSLv2, SSLv3, TLS, TLSv1. But it does not specify which protocol version will actually be used, it is always said that it supports one or some specific protocols, but it may support other protocol versions as well.
    And what does the setEnabledProtocols method of the SSLSocket class do? May an application specify here exactly, which protocols should be used?

    JSSE currently supports SSL v3.0 and TLS v1.0 (SSL v3.1).
    The protocol agreeded with the server depends on your client/server configuration, and always is the lower protocol supported by both of them.
    For example:
    Server -> TLS v1.0
    Client -> SSL v3.0
    The shared protocol will be SSL v3.0.
    About the getEnabledProtocols() method, give a look here:
    http://java.sun.com/j2se/1.4/docs/guide/security/jsse/JSSERefGuide.html#NewMethods
    Hope this helps.

  • The VM and host networking components failed to negotiate protocol version '5.0'

    I have been searching for a fix for this issue for sometime.
    The VM and host networking components failed to negotiate protocol version '5.0'
    and
    The VM and host networking components failed to negotiate protocol version '4.0'
    this error have been posting on the host server 2008 R2, with a hyper-V running server 2012 R2, which is the eval version vhd from Microsoft.
    I have tried the patch on the server 2008 R2 host and the nic delete and rescan option with varied reboots and such between each step of the process just to try every possible combination.
    The error persists. Are there any other suggested solutions for fixing this problem. Also the drivers have all been updated along with the system firmware.
    thanks,

    The hotfix states Server 2012 in the VM. You stated Server 2012 R2 in the VM.  MSFT is very precise in this language - Server 2012 != Server 2012 R2.
    Two distinctly different releases of Windows Server.
    In this case the N = the running release of Hyper-V.  In this case your Hyper-V Server at release version 2008 R2.
    The +2 = the current version of Windows.  In this case that is 2012 R2.  Two releases ahead of the version of the hypervisor you are running.
    I tossed in the link to Ben Armstrong's blog article as that is the ONLY (and still definitive statement) support statement regarding this configuration.  He posted that article at my request after many folks posting in this forum with strange behavior
    in this configuration.
    "supported" in this context means that if you call CSS, you will be told the following: 'yes, you have errors in the event log.  We will not fix that.  This is an unsupported configuration.  But that does not block the OS in the
    VM running.  If you want the errors to go away, we suggest you upgrade your Hyper-V Server to 2012 R2.  That configuration is supported.'
    That said, it can impact other functionality of the VM that rely on Integration Components in the VM and the Services of the hypervisor.  There is most likely small things that will not work.
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

  • SMB Protocol Broadcast

    Hi,
    Does SMB protocol in linux really broadcasts more? because recently in my network there was a broadcasting probz occured, i was suspecting that looping would hav formed juz bcoz HSRP is running between 6509 & 3750, after trouble shooting, i juz disabled the SMB services in linux machinez. the network was perfect.

    When SMB moved to NetBIOS (and thus TCP/IP), finding remote resources became a bigger problem. Machines needed a new way to locate each other, besides sending broadcast packets?this was the only way to successfully handle spanning across multiple subnets.

  • Is HLS protocol version 6 is supported in IOS 6.x and IOS 7.x ?

    Is the latest HLS protocol version (version 6) is supported in IOS 6.x and IOS 7.x players ?
    If it is supported can you please provide a sample m3u8 with EXT-X-START tag ?

    I use native player and start play from web page in Safari
    Master playlist
    #EXTM3U
    #EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="WebVTT",NAME="Main",DEFAULT=NO,AUTOSELECT= NO,URI="http://172.18.0.81:8080/mediaserver/download/2/service.523/item.m3u8?playlist=we bvtt"
    #EXT-X-STREAM-INF:BANDWIDTH=16777216,SUBTITLES="WebVTT"
    http://172.18.0.81:8080/mediaserver/download/2/service.523/item.m3u8?playlist=da ta
    segmets playlist
    #EXTM3U
    #EXT-X-VERSION:4
    #EXT-X-TARGETDURATION:1
    #EXT-X-MEDIA-SEQUENCE:2280
    #EXT-X-ALLOW-CACHE:NO
    #EXTINF:1
    http://172.18.0.81:8080/mediaserver/download/2/service.523/item.ts?chunk=1
    #EXTINF:1
    http://172.18.0.81:8080/mediaserver/download/2/service.523/item.ts?chunk=2
    #EXTINF:1
    http://172.18.0.81:8080/mediaserver/download/2/service.523/item.ts?chunk=3

  • OCI/UPI Protocol Versions

    Hi,
    I need to know what OCI/UPI Protocol Versions my Application uses. Where can i see that? Who helps me ?
    Thanks

    Please reread your post with the following questions in mind:
    1. What application are you talking about? Does it have a name?
    2. Does this have anything to do with Oracle the database? If so describe how?
    3. What version of Oracle, the database, to a minimum of 3 decimal places?
    4. Why do you need this information? What is the purpose?

Maybe you are looking for