Sharing folders

Hello,
I have messaging server 7 installed on solaris 10 x86 machine.
In comm Express I was trying to a share folder.
ex.
user 1 and user 2 are able to share folders
user3 and user 4 are able to share folders
however user3 or user4 are not able to share folder with user 1 and user2 ...and same in reverse.
folder is shared still while searching for shared folders it says no shared folders found for this user.
the difference here is that user1 and user2 are on same mail host and user3 and user4 are no another.
Does this make any difference? or should I check something else also?
regards,
sumant.

mr.chhunchha wrote:
the difference here is that user1 and user2 are on same mail host and user3 and user4 are no another.
Does this make any difference? or should I check something else also?The behaviour you have described is expected. Enabling shared IMAP folders for users on different mail-stores requires that you configure distributed shared folder on each of the mail-store systems. This is all documented in the manual:
http://docs.sun.com/app/docs/doc/819-4428/bgawd?a=view
Regards,
Shane.

Similar Messages

Windows 2008 R2 SP1 (64bit) shared folders no longer work with Windows 7 Pro but do work with WindowsXP & Windows 2003

As of last week, our Windows 7 Pro workstations can not map or browse the Windows 2008 Server shares. They can ping the Windows 2008 server. The Windows 7 Pro machines can still access the Windows 2003 Server Shares. The older workstations running Windows
XP can still map to the both the Windows 2003 & Windows 2008 Servers. All the servers can browse to each others shared folders (2 windows 2003 server & 1 windows 2008 server).

Ok, now you're down to network or permissions issues. An unedited ipconfig /all
of server and problem workstation may help. You could also try setting up some auditing.
https://technet.microsoft.com/en-us/library/dn311489.aspx
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

My Macbook Air does not show up on my network to any of my other computers, Other computers on my network appear and disappear, some shared folders are not accessible

My Macbook Air with Lion does not show up on my network to any of my other computers (PC's) , even though it is connected to my wifi and does access the Internet. In addition, my other computers sometimes show up in Finder and sometimes they're not there. Sometimes they do show in Finder and when I click on them, I get "Connection Failed", other times, they connect. Also some shared folders on those other computers, which are PC's are not accessible, even though fully shared. My network is Apple Airport Extreme and works perfectly otherwise, including all PC's being able to see each other. Help would be much appreciated

I got the same problem. I want to access my shared folder on my home windows7 from my MBA. Tried many suggestions on the web but all to no avail. I thought that should be very trivial. Maybe a Lion bug?

I can't use shared folders feature in VMware

Arch Linux is the guest system. Windows 7 is the host OS. I'm using VMware Workstation 10.0.1. After installing vmware tools (the original ones) I can't mount my shared folder. It says
~ mount -t vmhgfs .host:/ /mnt
Error: cannot mount filesystem: No such device
I've already searched the forum but I didn't find any solution to my problem.
[Update]
I think that it has something to do with the fact that vmware module sources are not compatible with the new UID and GID types:
uid_t -> kuid_t
gid_t -> kgid_t
I admit that I have no idea about patching sources. I've found this thread. It helped me with patching the vmhgfs module. Unfortunately the vmci module is still failing to compile because it's not patched yet. I have no idea how to fix this problem.
[Workaround]
Well I gave up. I've chosen the easiest way - Samba.
Additional information:
~ lsmod |grep -i vm
kvm_intel 134316 0
kvm 419974 1 kvm_intel
vmw_balloon 6258 0
vmwgfx 167331 2
ttm 66913 1 vmwgfx
vmw_vmci 53487 0
drm 242043 3 ttm,vmwgfx
~ vmware-hgfsclient
E
~ vmware-config-tools.pl
Initializing...
Making sure services for VMware Tools are stopped.
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
sh: : command not found
sh: : command not found
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/bin/gcc".
The path "/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers at "/lib/modules/3.14.3-2-ARCH/build/include".
The path "/lib/modules/3.14.3-2-ARCH/build/include" appears to be a valid path
to the 3.14.3-2-ARCH kernel headers.
Would you like to change it? [no]
make: Entering directory '/tmp/modconfig-jMh2Db/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.14.3-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.14.3-2-ARCH/build'
CC [M] /tmp/modconfig-jMh2Db/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-jMh2Db/vmci-only/linux/driver.o
In file included from /tmp/modconfig-jMh2Db/vmci-only/linux/vmciKernelIf.c:57:0:
/tmp/modconfig-jMh2Db/vmci-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
#define DEPRECATED(_fix) do {} while (0)
^
In file included from include/linux/kernel.h:13:0,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/percpu.h:44,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/preempt.h:5,
from include/linux/preempt.h:18,
from include/linux/spinlock.h:50,
from include/linux/mmzone.h:7,
from include/linux/gfp.h:5,
from include/linux/mm.h:9,
from /tmp/modconfig-jMh2Db/vmci-only/linux/vmciKernelIf.c:38:
include/linux/printk.h:96:0: note: this is the location of the previous definition
#define DEPRECATED "[Deprecated]: "
^
In file included from /tmp/modconfig-jMh2Db/vmci-only/./shared/vmware.h:39:0,
from /tmp/modconfig-jMh2Db/vmci-only/linux/driver.c:62:
/tmp/modconfig-jMh2Db/vmci-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
#define DEPRECATED(_fix) do {} while (0)
^
In file included from include/linux/kernel.h:13:0,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/percpu.h:44,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/current.h:5,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/processor.h:15,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/atomic.h:6,
from /tmp/modconfig-jMh2Db/vmci-only/linux/driver.c:24:
include/linux/printk.h:96:0: note: this is the location of the previous definition
#define DEPRECATED "[Deprecated]: "
^
/tmp/modconfig-jMh2Db/vmci-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/modconfig-jMh2Db/vmci-only/linux/driver.c:740:12: error: incompatible types when assigning to type ‘VMCIHostUser’ from type ‘kuid_t’
user = current_uid();
^
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-jMh2Db/vmci-only/linux/driver.o' failed
make[2]: *** [/tmp/modconfig-jMh2Db/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:1274: recipe for target '_module_/tmp/modconfig-jMh2Db/vmci-only' failed
make[1]: *** [_module_/tmp/modconfig-jMh2Db/vmci-only] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.3-2-ARCH/build'
Makefile:130: recipe for target 'vmci.ko' failed
make: *** [vmci.ko] Error 2
make: Leaving directory '/tmp/modconfig-jMh2Db/vmci-only'
The communication service is used in addition to the standard communication
between the guest and the host. The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the VMCI feature, you can install the driver by running
vmware-config-tools.pl again after making sure that gcc, binutils, make and the
kernel sources for your running kernel are installed on your machine. These
packages are available on your distribution's installation CD.
[ Press Enter key to continue ]
make: Entering directory '/tmp/modconfig-paCEZs/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.14.3-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.14.3-2-ARCH/build'
CC [M] /tmp/modconfig-paCEZs/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-paCEZs/vmci-only/linux/driver.o
In file included from /tmp/modconfig-paCEZs/vmci-only/./shared/vmware.h:39:0,
from /tmp/modconfig-paCEZs/vmci-only/linux/driver.c:62:
/tmp/modconfig-paCEZs/vmci-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
#define DEPRECATED(_fix) do {} while (0)
^
In file included from include/linux/kernel.h:13:0,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/percpu.h:44,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/current.h:5,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/processor.h:15,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/atomic.h:6,
from /tmp/modconfig-paCEZs/vmci-only/linux/driver.c:24:
include/linux/printk.h:96:0: note: this is the location of the previous definition
#define DEPRECATED "[Deprecated]: "
^
In file included from /tmp/modconfig-paCEZs/vmci-only/linux/vmciKernelIf.c:57:0:
/tmp/modconfig-paCEZs/vmci-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
#define DEPRECATED(_fix) do {} while (0)
^
In file included from include/linux/kernel.h:13:0,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/percpu.h:44,
from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/preempt.h:5,
from include/linux/preempt.h:18,
from include/linux/spinlock.h:50,
from include/linux/mmzone.h:7,
from include/linux/gfp.h:5,
from include/linux/mm.h:9,
from /tmp/modconfig-paCEZs/vmci-only/linux/vmciKernelIf.c:38:
include/linux/printk.h:96:0: note: this is the location of the previous definition
#define DEPRECATED "[Deprecated]: "
^
/tmp/modconfig-paCEZs/vmci-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/modconfig-paCEZs/vmci-only/linux/driver.c:740:12: error: incompatible types when assigning to type ‘VMCIHostUser’ from type ‘kuid_t’
user = current_uid();
^
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-paCEZs/vmci-only/linux/driver.o' failed
make[2]: *** [/tmp/modconfig-paCEZs/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:1274: recipe for target '_module_/tmp/modconfig-paCEZs/vmci-only' failed
make[1]: *** [_module_/tmp/modconfig-paCEZs/vmci-only] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.3-2-ARCH/build'
Makefile:130: recipe for target 'vmci.ko' failed
make: *** [vmci.ko] Error 2
make: Leaving directory '/tmp/modconfig-paCEZs/vmci-only'
The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and
host. The rest of this software provided by VMware Tools is designed to work
independently of this feature. If you wish to have the VSOCK feature you can
install the driver by running vmware-config-tools.pl again after making sure
that gcc, binutils, make and the kernel sources for your running kernel are
installed on your machine. These packages are available on your distribution's
installation CD.
[ Press the Enter key to continue.]
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[yes]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.15.1
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Starting Virtual Printing daemon: done
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
Guest operating system daemon: done
The configuration of VMware Tools 9.6.1 build-1378637 for Linux for this
running kernel completed successfully.
You must restart your X session before any mouse or graphics changes take
effect.
You can now run VMware Tools by invoking "/usr/bin/vmware-toolbox-cmd" from the
command line.
To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.
Enjoy,
--the VMware team
Last edited by Skitter (2014-05-14 16:51:50)

Hi.
I managed to compile open-vm-tools and the kernel module against 3.14.5 kernel. Here is the tarball with the all the files.
I still have an issue : With vmware-player 6.0.2, I can't acces my shared folder :
root@P146S011b ~ # lsmod | grep hgfs
vmhgfs 41622 0
vmw_vmci 47960 2 vmw_vsock_vmci_transport,vmhgfs
root@P146S011b ~ # vmware-hgfsclient
R
D
C
root@P146S011b ~ # mount -t vmhgfs .host:/R /mnt
Could not add entry to mtab, continuing
root@P146S011b ~ # tail -1 /etc/mtab
.host:/R /mnt vmhgfs rw,relatime 0 0
root@P146S011b ~ # cd /mnt
cd:cd:6: not a directory: /mnt
1 root@P146S011b ~ #
Forgot to add an install file with a depmod -a inside. You will have to run it by yourself

What happens to shared folders/mail when I disable/remove a mailbox in Exch2010 and which is better to get space back?

We have a number of old mailboxes taking up room. The users are long gone and I looked into removing them. The clients of these users have been moved to others. The users had shared folders that held this info. I have a few questions
about the removal.
1. Is there a difference in time before space is given back if I disable versus remove the user in EMC?
2. If an ex-employee had folders that others are sharing, what happens when I do the remove/disable? Will the folders still be out there on the people who had it shared or will it vanish from them too?
Thanks for your help.

"Best practice" is going to be defined by each company. I worked for Microsoft for 13.5 years, assisting over 100 large companies deploy either Windows or Exchange, and none had the same definition for their "best practice".
If you need access to a mailbox for a time period, you figure out a way to keep it. If you want any terminated employee's mailbox gone tomorrow, it is gone tomorrow.
I am a fan of having some sort of process that runs periodically to clear out unnecessary mailboxes and accounts, but if there are business reasons for keeping them around, that needs to be defined into the process. In my current company, terminated
accounts are kept for 30 days, mailbox included. We give mailbox access to a different employee if required and tell them that if they need anything, they need to pull it into their own mailbox. Then, when the account disappears, the mailbox goes
into the dumpster. So, if someone forgot to pull a message, they tell their boss and live with the consequences.
But again, that's just another example of how it might be handled. You get to define what will work for you, including pulling your business units in to help with the definition.

Shared Folders in mail

I'm running a OS X Leopard Server mail server. Since a few days a folder called "Shared Folders" appeared in all mailboxes. Within this shared folders folder there are several folders with strange names:
._-Dong-seeiuqi
._-Jolie-seignora
.-seer1990
._-seetrus2005
.-seeun1990
._-seiklab
There are now users with these names on my server. I would like to know how this could happen and what it is, and eventually how to remove them.

http://discussions.apple.com/thread.jspa?messageID=5732065&#5732065
http://discussions.apple.com/message.jspa?messageID=7809674#7809674
http://discussions.apple.com/thread.jspa?messageID=3921745&#3921745
http://discussions.apple.com/thread.jspa?messageID=3869994&#3869994

Sharing folders for 2 users on the same mac

Hey
I have a Vista Virtual Machine (VM) created in VMware fusion and it is stored on a partition on my Bay 2 HDD in my mac pro. it all runs fine when i log in since i am the admin on the box.
I created a Standard user account for my wife. I want my wife to open up VMware Fusion and launch the Vista VM as she pleases to do her work under her account. So i went to sharing in system preferances and selected the folder that contains the VM in "Shared folders" and under "Users" i gave her account read & write permissions. When i log in as my wife and try to launch the VM it says she does not have permissions. I can browse to the folder without any issues. I get the same message if i were to double click the VM also.
I then logged in as the admin and gave her account admin privileges to see if that will fix the issue. when i log in under her account i still get don't have permissions. If she has admin privileges should't she able to have access to any folder on my mac?
The goal is to leave my VM on my Bay2 HDD and have both of us launch Vista VM using VMware fusion successfully from this location under both our accounts
What am i doing wrong here?
Thanks
Rpk

Admin permissions does not give you blanket rights to any file. It only gives you the ability to give yourself permission to access a file.
doogald is correct to observe that you have to give your wife permission to read and write to the files inside the folder, and not just read and write permissions on the folder itself. In addition, if your wife doesn't have at least read permission on the folders in which the VM folder is contained, all the way up to the root folder, then she may continue to have problems.
If VM Fusion will allow this, it might be best to move the folder which contains the VM to /Users/Shared. You will still need to ensure that your wife has read and write permission for the folder +and its contents+ but the purpose of /Users/Shared is to share files and folders. This way you won't need to manipulate your permissions beyond making sure the shared folders and files themselves are read-writable by you and your wife.

Server 2003: make user template with read-only access for shared folders

I have need to make a type of user (like Administrator, Power User, Mobile User, User, etc.) that has read-only acess to shared folders. So when I make a new user and assign the "read-only user" template I wish to have, the user can open files
in the shared folders on the server, but not edit, save or delete files. Other users can and should remain able to edit, save & delete.
Before I dig in, is this even possible?

You could create a Group called ReadOnly, and set that to have Read on the ACLs of the relevant files or folders.
Make that template user a member of that group.
As long as they are not also a member of another group that gives them higher permissions, this would work.
Otherwise set the ReadOnly group to deny Write, which would over ride any other permission set.
So,
Folder A
ACL:
ReadOnly : R
Users: Read/Write
If a user is a member of Users & ReadOnly, they would get read/write to Folder A. As permissions are cumulative.
If you did the following:
Folder A
ACL:
ReadOnly : R
ReadOnly: Deny Write
Users: Read/Write
The users in ReadOnly would be denied write, as it overrides the cumulative permissions.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Map a drive to the Remote Web Access - Shared Folders

All companies love Remote Web Access. No need for VPN for access to remote desktop and the "private skydrive" Shared Folders.
Is there anyway to map a drive to these "private skydrive" Shared Folders? you can map a drive to the real skydrive and to Sharepoint so surely it is possible?

The trick that I found was to upgrade my file server to server 2012 R2 and configure iSCSI Target for the resource I wanted to access by RWA. On my RWA Server I then used the iSCSI initiator to connect to that Target. This makes the shared drive appear
as if it is a native drive on the RWA server. Once this was done I configured that drive, or a folder within that drive for access with RWA. It has worked perfectly ever since.
Trust but verify!

Upgraded 2 macs to Mavericks, can no longer access shared folders/files.

So I upgraded my Macbook Pro, and Mac Mini to Mavericks today, and previously when they were both on mountain lion I could access the shared folders/files and screen share with absolutely no issue whatsoever.
But upon updating to Mavericks today it all broke.
Both computers were running the OS X Server software on Mountain Lion, and I went ahead and purchased/installed the new edition of server that came out today.
I can see the other mac under the "Shared" option in Finder's sidebar, but when I try to open the other mac it says connection failed and offers to "connect as"
As I usually do, I connect as and it asks for the login credentials. I put in the same credentials as before, 150% sure they're right, in the text boxes that I used before, but it won't allow me to connect to the mac.
I know beyond a shadow of a doubt that they're the right credentials.
I thought it may have been just a wonky permissions error so I unshared the folders and reshared using the same permissions that had worked before.
I've been working on it for about 3 hours now so any help would be appreciated.

I upgraded my two machines - now when I access files on the "shared" storage array (a thunderbolt, pegasus array) across the network (ethernet) if I modify the file (for instance, a jpg) and then go to save I get a "you don't have permissions to etc...." and then when I just close the file without saving - it disappears from my file server permanently! even if I go to the machine hooked up to the array the file is "gone" - unbelievable. I have updated permissions where I can, deleted and added the sharing for users, tried SMB and AFP, and even downgraded the "sharing" machine back to OSX 10.8 where it was working fine but the client machine still is doing this where it can connect, see all the files, but as soon as I modify a file I get the warning and bam, it's gone forever....
Wow - this is a doozy. I don't have a fix but WARNING - watch out as you are working on this problem that your files are being vanished permanently.

Mountain Lion will no longer connect to my Homeserver shared folders

Yesterday I did a complete system wipe of my Mabook Pro and intalled a fresh copy of Mountain Lion, all has gone well apart from the fact that I can't connect to my Homeserver shared folders or stream from it using Plex, it can remote desktop into it though. All other devices can still connect to the server and the laptop can connect to all other just fine, any idea what might be causing this problem? Many thanks in advance.

I found if you connect to the shares themselves it's a slight work around but not ideal, so instead of doing this:
smb://servername
you do this
smb://severname/sharename
Then if you add them to your favourites by clicking the plus icon in the server connect dialogue box (⌘+k) its liveable with, hopefully this gets sorted in the next OS update.

Shared folders (Windows file shares) show access denied and do not prompt for credentials

Scenario:
Like other admins, I log on and work as a 'standard user' (usera) with no admin rights anywhere in the domain, to perform admin tasks I have another account (userb) which I authenticate with as and when required. userb has been allocated/delegated permissions
as required.
Problem:
When trying to connect to shared folders on servers (2008 R2) using a UNC patch via Windows Explorer (Win 7 Ent.), I see an access denied error and do not get an option to supply alternative credentials.
If I try to connect to the admin shares on the same server (\\server\C$ or \\server\e$) I get an access denied message AND get prompted for credentials. I supply my admin account and gain access as expected.
If I check share and storage management when attempting to connect, I see that Windows is trying to connect me to each share as usera (which has no access). I understand why I get access denied at this point, but not why it can't just prompt me to supply an
account that does have access. When trying the admin shares I also see the usera account, but I get a prompt to supply a user who does have access.
Share permissions on the folders are for example 'Everyone' Full Control. NTFS permissions are 'userb' has modify (read, execute, list, traverse etc) via a 'Server Admins' AD Universal security group.
Note: If I do a NET USE from CMD and use the /USER switch, I can access the shares fine. But this is not great for accessing shared folders on the fly from various computers.
How can I get the other shares on the server to prompt me, rather than just say access denied?
Many thanks.

Try to disable guest user from the server
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY
suggestion in a test environment before implementing!

Cannot open files created in shared folders by Windows 7

Hi.
I've been having issues with my shared folders.
My scenario is that I primarily work on my Windows 7 machine and save a copy on my MacBook so I can work on the same file when I'm out and about. I have no issue saving the files, or even browsing the shared folders on my MacBook. I can create, edit, save and delete files in the shared folder from my Windows machine without problem. The issue is that I'm unable to open any of the files created by Windows on my MacBook; it shows a prompt saying "You do not have permission to open document (filename)." I can't even see the thumbnails of image files created by Windows.
On the MacBook there is only one Standard user account which I use to login, and one Sharing Only account which I use to connect from the Windows machine with Read/Write permissions granted on my shared folders. The WINS workgroup has also been set to the same value as on the Windows machine.
I am able to move the files to Trash, but that's all I can do to them, which defeats the entire purpose of me having a portable computer. My shared folders were setup when I was still on Snow Leopard and had no issues before.
It's a hassle to have to bring a USB drive around to my meetings, and I'm completely clueless on what actions I must take to rectify this issue. Anyone out there ever have this issue? Any and all help is appreciated.
Thanks.

CR 8.5 is not supported on 64 bit OS's or ANY Terminal Servers.
The location for 32 bit applications on a 64 bit OS is \windows\syswow64.
Good luck
Don

[SOLVED] Samba: Can browse shared folders, but can't open files

Hi all, I've been using Samba to share some folders from my Arch box over the local network, and have not had any issues until just now. As the title says, I am able to browse (via Samba, both on a different device and from the Arch box itself) the folders being shared as well as see their contents, but trying to open a file fails, as does attempting to create a file in one of the shared folders. Accessing the files from the computer itself directly (not via Samba) works fine.
The error given by Thunar when trying to create a file is simply:
Failed to create empty file "test file".
Invalid argument.
Trying to read a file results in the same "invalid argument" error being given by the app that should open the file.
I've removed Samba and reinstalled, following the steps on the wiki to get it set up. Still have the issue.
Further, I only seem to be able to add shares via the smb.conf file - previously I was able to share folders via Thunar or the net usershare command, but now those also give an error:
$ net usershare add tmp /tmp "tmp" everyone:F guest_ok=y
net usershare add: cannot convert name "everyone" to a SID. Undetermined error.
Any ideas on what could be causing the problems would be greatly appreciated!
edit: my smb.conf file:
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = yes
usershare owner only = False
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = archpc
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = /etc/printcap
load printers = yes
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
; printing = bsd
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user
# Use password server option only with security = server
; password server = <NT-Server-Name>
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; username level = 8
# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
; encrypt passwords = yes
; smb passwd file = /etc/samba/smbpasswd
# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
# Unix users can map to different SMB User names
; username map = /etc/samba/smbusers
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /etc/samba/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Use only if you have an NT server on your network that has been
# configured at install time to be a primary domain controller.
; domain controller = <NT-Domain-Controller-SMBName>
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no
#============================ Share Definitions ==============================
[homes]
; comment = Home Directories
; browseable = no
; writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /home/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /home/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
# This one is useful for people to share files
[tmp]
comment = Temporary file space
path = /tmp
read only = no
public = yes
writable = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; read only = yes
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
Last edited by m00se (2014-05-26 11:35:28)

It seems your Samba is denying access to these files & dirs. My best guess would be that either the Samba user is not allowed to write (and read) those (in which case you'd have to modify the permissions accordingly) or Samba sets, when the share is mounted, the permissions such that your user is not allowed to read and write (you may in this case try to just set permissions for you to allow you what you want to do; or use "create mask" or "directory mask" or "writable" in your samba config. ).
Also, what do the logs say about this? According to your samba conf they are in /var/log/samba/%m.log where %m is the hostname or IP.

Server 2008R2 mapping to shared folders fails users of Windows 8.1 but seems OK on Windos 8.0 and no problems for Windows 7

Having read what I could from the related questions, the answers still elude me. This issue apparently is specific to Windows 8.1.
First, a little background.
1: The server is not on a domain, The system runs Server 2008-R2 standard with all folders shared across a standard "Workgroup" type network. They would prefer to
leave this layout intact.
2: The shared folders are nothing but Data files. There are no active system folders or anything used in an "active" environment. They are mostly Word doc, excel
files, pdf, txt, etc. However, due to the requirements of the software that needs to access these files, they Must
reside on a mapped network drive letter. Nothing else works due to the way the SQL database program stores the reference points back to the data.
I have had some success using what amounts to a “simulated” mapping using WebDAV to access the server. But access speed is a lot slower ad file size is limited.
3: The system has been configured as-is for the past 3 years with Users all on Windows 7 x64 (mixed OS, some Home Premium, some Professional) and the only problems that come up are when
access is through an ISP that blocks port 445. This was the original reason for finding a WebDAV/Cloud method just for those Users since they were unable to Map drives to anything on the Office Servers from their Home Internet even when using a VPN.
When Windows 8.0 became the only version available, I added a few users whose new laptops came with 8.0 from the vendors. While there were a very few minor problems, for all practical
purposes, I was still able to provide access to the mapped folders.
As the Windows 8.1 roll-out progressed, some users were successfully upgraded while others are still stuck in Windows 8.0. The issues with this seem to be hardware related and vary
depending on the Make and model of the laptop. I have been assured that eventually all of these will be able to advance to 8.1. But this delay has given me an excellent mixed OS environment for testing.
On the users who have not yet purchased new equipment and who are still using Windows 7. There has been no change. Their drive mapping is stable and they can always connect as usual.
Those blocked from lack of port 445 or still blocked. Systems inside the Office and those with ISP's who allow port 445 can use all mapped drives as normal.
Users who had Windows 8.0 and who have not yet been able to upgrade to 8.1 also have been unaffected. Same results as Windows 7.
Users who got the Windows 8.1 upgrade as well as those that came factory loaded with Windows 8.1 seem to be a never-ending list of problems. The ones that came native with 8.1 are worst
of all. The list of error codes runs through everything that has to do with “communication with the server”. As far as I have seen, this appears to be the issue.
Whether they are in the office on a wired network connection or at home on a Wi-Fi connection, the issues have the same results but the actual error codes may vary slightly. All of
them refer back to an inability to communicate with the server.
Nothing on the server has changed in any way. Users with Windows 7 continue to have zero problems, Users with Windows 8.0 seem to be doing fine as well. Only those with Windows
8.1 are affected and their problems are dramatic with everything from a total loss of drive mapping to misdirected data when the maps are active.
I have tried to make the drives automatically remap on reboot. I have tried registry modifications. I have done everything I can think of to make a difference but the results are the same
for every system using 8.1. The mapped drive letters invariably disappear. Sometimes while the system is in use ( I think I have been able to trace this to times when the system enters Sleep or Hibernate) but always when the system reboots.
One detail that might point to somewhere is that the "time to connect" when mapping the drive is so long that I believe some of the original failures were due to not waiting for a
minimum of 3 or 4 minutes to give time for the Shares to show-up in order to map them. Once the mapping is successful, the file access speed seems normal. But invariably, the drive becomes "unmapped" repeatedly each day.
I know this was a long question but I have tried to provide every possible detail for anyone who has experienced events like this who may already have a solution. I would even be glad
to purchase a 3rd party application if that is what it takes to get this to work. My next planned effort is to try using Server 2013 but I am afraid that might open another can of worms for those who still use Windows 7.
I have also been told that this is in some way related to the push to "Cloud" support in Windows 8.1 OS but I do not see where this would come in. I can say that this was the
one place where things continued to work as before. People who had Windows 8.1 and who had to use the CLOUD copies of our data are still able to connect to it with no problems.
Any suggestions appreciated. Preferably those that would not need extensive changes to the basic network structure. This "workgroup" consists of less than 25 users and any
extreme measures would be hard to justify

Hi，
I sugget you try to ping server so that we can verify the connectivity.
Can windows 8.1 access Windows Server 2008R2?
Also,please check the event viewer to see if some error log appeared when the issue occurred.
Regards,
Kelvin Xu
TechNet Community Support

Network shared folders appear as 'sharepoint'

Hello
I have 1 iMac and 2 windows 7 computers on my local small office network.
From the Mac I can see and access all shares on one PC, on the other, when I access via finder, the shared folders appear as 'sharepoint' and I cannot see any sub folders. I have checked settings on both PCs in the network centre and they seem identical.
Thanks if you can help. Regards

Hi, just an update...some of the problem is related to extensions. Some files have explicit extensions and others not. When I change the file extensions to an explicit extension (eg .pdf) then the file is fine.
However, there are no extensions on folders or folder aliases.
I've tried using chmod -x + file location/file name but that makes no difference to the alias, meaning that the Snow Leopard does not recognize the item as a short cut to another folder. Snow Leopard will only recognize the item as an alias if it's been created on a workstation running Snow Leopard OS. Very odd.
Phil

Sharing folders

Similar Messages

Maybe you are looking for