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.

Similar Messages

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.

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

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 is the better one, between AFP and SMB protocol for files' transporti

Hi,
I'm a newbie here and I have a question for MAC AFP protocol.
For files' transporting, MAC os has AFP protocol, and it also supports SMB protocol. Is there any difference between these two protocols?
Is the AFP protocol better than the SMB protocol , for files' transporting between two MACs, MACs and Windows,or two Windows?

AFP is preferred for Mac -> Mac transfers. It's the native Mac protocol and easiest to maintain.
Windows systems typically don't understand AFP so it's not an option for them. For Windows transfers you should use SMB.
The Mac can talk SMB, too, so if you had to choose only one, and you have Windows clients on your network, then SMB would be the way to go.
You are not limited to running just one, though. It's perfectly valid to have the server talk both AFP and SMB at the same time, letting each client use the protocol it prefers.

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.

How do I fix a broken SMB protocol so my Sonos sytem works again?

Hi,
I'm new to this, so bear with me.
I have been running a Sonos Play 3 since June 2013 without any problems. Two days ago I got a messsage on the Sonos Controller software saying;
"Unable to play ‘song name’ - cannot connect to //'my mac'/Music because the server cannot be found"
So I put in a ticket with Sonos Support and they've told me the following;
"The bug is not with Sonos, we see this problem a lot with Macs because SMB is broken. Sonos is able to play your music on your computer because your computer has to share the folder on the network. It does this with with a protocol called SMB.
If you don't want to upgrade I recommend you purchase a NAS(network attached storage) drive and move your music to it and share the NAS drive to Sonos."
I don't really want to run Mavericks because I'm used to Lion.
So my question is this - how to a fix a broken SMB? Can a borken SMB be fixed?
Any help would be greatly appreciated.

If you have Apple Care or your computer is still under warranty, call and get a case number. At least you will not have to pay for the repair if the crack is not "accidental" damage.
Do-It-Yourself Laptop Repair
Research YouTube's 'How To' video tutorials
FixYa

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.

Printing on windows xp network - smb protocol

keep getting error code 9786. printer is a mac friendly Canon Imageclass MF4150
using the below instructions not cutting it: any ideas???
Mac OS X v10.5 or later
Choose System Preferences from the Apple menu.
Choose Print & Fax from the View menu.
Click the + button to add a printer.
Press the Control key while clicking the "Default" icon (or any other icon on the toolbar), then choose Customize Toolbar from the contextual menu that appears.
Drag the Advanced (gear) icon to the toolbar.
Click Done.
Click the Advanced icon that was added to the toolbar.
Choose Windows from the Type pop-up menu.
In the URL field, type the printer's address in one of the following formats:
smb://workgroup/server/sharename
smb://server/sharename
Note: "workgroup" is the name of the Windows workgroup that the computer sharing the printer belongs to. "server" is the name of the computer sharing the printer (or its IP address). "sharename" is the shared Windows printer's share name. If the share name contains spaces, replace each space with "%20" (without quotation marks).
Tip: You don't need a "workgroup" when specifying the IP address of the computer (such as when the printer is on a different subnet), or if your Mac belongs to the same Windows (SMB) workgroup.
In the Name field, type the name you would like to use for this printer in Mac OS X.
Choose the appropriate PPD or printer driver from the "Print Using" pop-up menu.
Click Add.

Changing to Windows 7 won't help the matter. The limitation is with the UFRII driver on the Mac. It requires a direct connection to the printer so with it shared by a Windows computer it is unable to communicate correctly which results in the error you were getting.
And the driver is also not compatible with a print server - even the USB port of a Apple Airport device which normally allows other Canon printers to use the Canon driver is not a solution with this UFRII driver.
So without the workaround I don't believe you will be able to print while you have this device connected to Windows. This was the case with OS X 10.4 and is still the case with 10.6. The fault lies totally with Canon and the way they have made this UFRII driver. If the printer supported some other printer language, such as PCL or Postscript, then you would have some options. But with it only supporting the proprietary Canon UFRII language, you are restricted with how you can connect to any Canon printer that only supports this UFRII printer language.
If you want to have the Windows and Mac connected at the same time to the MF4150 then your options are;
1. Connect the printer to Windows and use the iHarder workaround (which as you mention is detailed but I have tried it and it works fine)
2. Connect the printer to the Mac and use Bonjour for Windows on the PC. This can be annoying if the Mac is a laptop but it all depends on how often you are going to print from Windows.
3. If the Mac and PC are not very far from each other you could use a USB hub.
4. If the Mac is a laptop, physically connect it to the USB port of the MF when you need to print.

Sync prob of updatin info from WDM to smb.conf using smb protocol

Hi,
I would appreciate if somebody could help me as i'm trying hard to solve my server's problem but could not find any solutions. My Mac OSX Server is running as a Dual 2.3GHZ PowerPC G5 and the current version is 10.4.11. When i tried to create a new sharepoint volume which is located at the XServe Raid or editing the permissions of the existing sharepoint volume, it was not able to update the smb.conf and i was not able to view the volumes using 'smb' command. I'm not sure if this lies with the synchronization problem between the workgroup manager and smb.conf file. From the Server Admin under the Window service, there's an error message displayed as follow:
/SourceCache/samba/samba-100.12/samba/source/smbd/service.c:make_connection(805)
Is there any way where i could fix the files as I have no idea of where the files reside in the system?
Thank you!
Cheers,
Stephanie

Don't know what your issue has to do with 'Using Mac OS X Tiger'. That is the forum you've posted in but I see you are running 10.5 Leopard. Perhaps posting in the 'Mac OS X Server' forum would help.
http://discussions.apple.com/category.jspa?categoryID=96

Are there any compatibility issues with Mavericks and EMC Celerra File shares, particularly with the SMB protocols?

Our company uses a EMC Celerra file share, but most of our users are Windows based. We have a small production department of 7 macs. Starting with Snow Leopard, we noticed some issues with SMB. We were able to resolve those issues, but had to wait to upgrade to Lion because there were additional SMB or permissions concerns with the Celerra file share and Lion. Now, we are again waiting to upgrade to Mavricks because of the way it handles user permissions. Does anyone using Mavericks now also connect to a EMC Celerra file share? Thanks!

Our company uses a EMC Celerra file share, but most of our users are Windows based. We have a small production department of 7 macs. Starting with Snow Leopard, we noticed some issues with SMB. We were able to resolve those issues, but had to wait to upgrade to Lion because there were additional SMB or permissions concerns with the Celerra file share and Lion. Now, we are again waiting to upgrade to Mavricks because of the way it handles user permissions. Does anyone using Mavericks now also connect to a EMC Celerra file share? Thanks!

Creating a folder on an SMB share using a Mac

Hi everyone,
This is more of a question than a problem I'm trying to solve, really. Though the answer might help me better explain the issue to our security team.
Our environment has multiple Windows file servers, both 2003 and 2008. If one of these SMB shares is accessed from a Mac and the user creates a folder, will the ACLs on the share that are set to cascade actually cascade to this newly created folder? We've had issues in the past where ACLs that are supposedly set to cascade on a shared folder are not present on sub-folders created from Macs.
Next question: if the share resides on a netapp device, do the same rules apply? The Macs are still connecting to these shared folders using the SMB protocol.
All Macs are bound to our 2008 AD domain and use network accounts with local homefolders. The issue seems to happen when one or both of the following things happen:
1. A Mac user copies/creates a folder on a Netapp share and for some reason it doesn’t inherit rights correctly
2. We move the folder from one share on an actual Windows server to the Netapp and it doesn’t take permissions correctly.
Please let me know if you need any other information.

Let's put it this way: I'm asking on a Mac site because the people on non-windows support sites are WAAAAY more interested in talking about problems and solutions involving things other than Windows.
I'm fairly certain that the windows servers ARE respecting their own inheritance rules, barring any major bugs and the like which someone may know about...
The isue isn't with Macs moving shares to a netapp, it's with a share being moved to a NetApp that has folders created by a Mac. Talking with our security team further, it seems the problem may be limited to shares resident on a NetApp or moved from a Windows server to a NetApp.
I was primarily asking to see if anyone knew of any issues with these particular situations or had experienced something similar and had dug into it any deeper with F5 (NetApp vendor).

Performance problems with DFSN, ABE and SMB

Hello,
We have identified a problem with DFS-Namespace (DFSN), Access Based Enumeration (ABE) and SMB File Service.
Currently we have two Windows Server 2008 R2 servers providing the domain-based DFSN in functional level Windows Server 2008 R2 with activated ABE.
The DFSN servers have the most current hotfixes for DFSN and SMB installed, according to http://support.microsoft.com/kb/968429/en-us and http://support.microsoft.com/kb/2473205/en-us
We have only one AD-site and don't use DFS-Replication.
Servers have 2 Intel X5550 4 Core CPUs and 32 GB Ram.
Network is a LAN.
Our DFSN looks like this:
\\contoso.com\home
   Contains 10.000 Links
   Drive mapping on clients to subfolder \\contoso.com\home\username
\\contoso.com\group
   Contains 2500 Links
   Drive mapping on clients directly to \\contoso.com\group
On \\contoso.com\group we serve different folders for teams, projects and other groups with different access permissions based on AD groups.
We have to use ABE, so that users see only accessible Links (folders)
We encounter sometimes multiple times a day enterprise-wide performance problems for 30 seconds when accessing our Namespaces.
After six weeks of researching and analyzing we were able to identify the exact problem.
Administrators create a new DFS-Link in our Namespace \\contoso.com\group with correct permissions using the following command line:
dfsutil.exe link \\contoso.com\group\project123 \\fileserver1\share\project123
dfsutil.exe property sd grant \\contoso.com\group\project123 CONTOSO\group-project123:RX protect replace
This is done a few times a day.
There is no possibility to create the folder and set the permissions in one step.
DFSN process on our DFSN-servers create the new link and the corresponding folder in C:\DFSRoots.
At this time, we have for example 2000+ clients having an active session to the root of the namespace \\contoso.com\group.
Active session means a Windows Explorer opened to the mapped drive or to any subfolder.
The file server process (Lanmanserver) sends a change notification (SMB-Protocol) to each client with an active session \\contoso.com\group.
All the clients which were getting the notification now start to refresh the folder listing of \\contoso.com\group
This was identified by an network trace on our DFSN-servers and different clients.
Due to ABE the servers have to compute the folder listing for each request.
DFS-Service on the servers doen't respond for propably 30 seconds to any additional requests. CPU usage increases significantly over this period and went back to normal afterwards. On our hardware from about 5% to 50%.
Users can't access all DFS-Namespaces during this time and applications using data from DFS-Namespace stop responding.
Side effect: Windows reports on clients a slow-link detection for \\contoso.com\home, which can be offline available for users (described here for WAN-connections: http://blogs.technet.com/b/askds/archive/2011/12/14/slow-link-with-windows-7-and-dfs-namespaces.aspx)
Problem doesn't occure when creating a link in \\contoso.com\home, because users have only a mapping to subfolders.
Currently, the problem doesn't occure also for \\contoso.com\app, because users usually don't use Windows Explorer accessing this mapping.
Disabling ABE reduces the DFSN freeze time, but doesn't solve the problem.
Problem also occurs with Windows Server 2012 R2 as DFSN-server.
There is a registry key available for clients to avoid the reponse to the change notification (NoRemoteChangeNotify, see http://support.microsoft.com/kb/812669/en-us)
This might fix the problem with DFSN, but results in other problems for the users. For example, they have to press F5 for refreshing every remote directory on change.
Is there a possibility to disable the SMB change notification on server side ?
TIA and regards,
Ralf Gaudes

Hi,
Thanks for posting in Microsoft Technet Forums.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Regards.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

After upgrade my MBP from snow leopard to mountain lion all my smb connections stop to work.

After upgrade my MBP from snow leopard to mountain lion all my smb connections stop to work.
Now iám using mac os 10.8.2
I can see the server, I can choose the drive, but when try to open a folder the message on Finder is: You don't have permissions to see the content.
I already delete the key and try to connect again, but the problem persist. Already try change the ip from file server. Already try differents users. (admin, guest, etc...)
I have a windows server 2008 and a NAS working with SMB protocol. Both with the same problem.
That problem occurs only on Finder, if I try see the folder by Terminal, is possible to see my files.
Any Solution ?
Any Tip ?
Any Question ?

Not knowing how much RAM is installed in your iMac, your iMac can take a total of 8 GBs of RAM.
Before upgrading to Mountain Lion, I would strongly suggest installing the maximum 8 GBs of RAM.
Correct and reliable Mac RAM can be purchased from online Mac RAM sources Crucial memory or OWC (macsales.com).
Here is OWC's link to your model iMac and the RAM modules you will need.macsales
http://eshop.macsales.com/item/Other%20World%20Computing/8566DDR3S8GP/
You can purchase and download OS X 10.8 Mountain Lion from the Mac App Store in the OS X dock.
Before installing, it would be prudent to make a backup copy of all of your important data or your entire current system. Either using, optical discs, USB flash drives or external hard drives.
This is too insure protection of your data in case something goes wrong with the install of OS X Mountain Lion.
Good Luck!

SMB Protocol Broadcast

Similar Messages

Maybe you are looking for