SMB.conf file is used to configure the server end of samba, not necessarily the client. I am aware of this, however, smb.conf was the only samba-related configuratin file I found. As smbclient turned out to actually use it, I hoped it would influence the other samba-clients as well - it does not.

Our question to you might be: what kind of server are you connecting to via SMB? All of them, makes no difference really.

It was later ported to Mac OS X. Thursby's DAVE, ADmitMac and ADmitMac PKI products include both an SMB client and an SMB server, and support Microsoft's DFS. An iPhone application named Flash Files has an SMB server implementation. Aug 27, 2010 - You could easily achieve this using mount_smbfs (which is, actually, a wrapper for mount -t smbfs ): mount_smbfs //user@SERVER/folder.

Optimize a pdf in adobe for mac. The producer is Adobe PDF Library 7.0 and the file is Acrobat 6.x. I do this all the time and have never had a problem optimizing a PDF before. It goes through all the steps and if I check the file info before I close it, it states that it is in the older format, but when I come back and reopen the file later it says it is Acrobat 6.x again. I have a PDF created in InDesign CS2. I'm trying to optimize the file to be compatible with Acrobat 4.x, but the optimize does not 'take'.

All work flawlessly, if I connect from Windows or from Linux, but none works, if I connect from Mac OS X. (if Windows, what version of server software, please) Windows 2003 Server. And when you enter the servername/IPaddress, end it with ':445) I'll try this. So far, I put the:445 at the end of the server name - it had no influence: SMB://[Server_IP]:445/[Share]. Also, putting it to the end has no effect. It still tries to port 139. Like: SMB://[Server_IP]/[Share]:445 Is that what you are trying?

Yes, this exactly - and the same in Finder. The above just does not work, mount_smbfs stubbornly tries to connect to the port 139 and so does Finder. There might be some clues here. Ecurity/index.html This is actually a nice link for all sorts of other stuff, but did not help much in this case. Near the bottom, search for 'Manual firewall configuration', then 'Kernel Twaeking', (yes, it's misspelled). Now, I have tried this as well with Mac OS X Server as the client allowing much more flexibility to the firewall rules without the need to resort to manual tweaking.

Result: mount_smbfs hangs and gets a timeout after a while. This is obvious, as I have now closed the port 139 to both ways - so, no answer -> timeout. Bottom line: mount_smbfs does not work on the kernel level, so tweaking the kernel does not help much here. There should simply be some way to instruct mount_smbfs to use the port 445 and then everything would work.

Firewall settings do not work, so maybe there is some kernel variable to set the samba port? Not in the documentation, though. This looks very bad, from the Darwin 8.8 kernel source tree: /* * Common definintions and structures for SMB/CIFS protocol */ #ifndef NETSMB_SMB_H #define NETSMB_SMB_H #ifndef PRIVSYM #define PRIVSYM _private_extern_ #endif #define SMB TCPPORT 139 /* * SMB dialects that we have to deal with. */ which indicates the port 139 has been hard coded.

Apple Footer • This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Free iso softwre for mac os. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site.

All postings and use of the content on this site are subject to the.

Microsoft Windows 3.11, 9x, and NT have built-in support for the SMB protocol, so systems running these operating systems can easily access your Samba server's resources. Under Microsoft Windows 9x and NT, you can access Samba resources by using the Windows Explorer. Log on using a userid that's authorized to access Samba resources.

Then click on Network Neighborhood and you should see a subtree that corresponds to your Samba server. By expanding the subtree, you can see the browseable file and printer shares that are available. You can easily drag and drop files to and from a shared directory, assuming your userid is permitted the necessary access. To use a shared printer, click on Start Settings Printers and then double click on Add Printer. The wizard will guide you through the setup procedure.