06-04-2015
What Jim said, plus there is a mapping correlation between *nix and Windows.
The permissions on the 2008R2\AD needs to be set to allow *nix (probably root access from NFS, or whatever mapping is done) to read\write to that folder.
I had a similar problem a few years ago, I was getting the same thing, once Windows permissions was set to allow *nix to r+w the folder was no longer anon, it was seen correctly..
So this is definitely on the Windows 2008R2\AD side, but every environment is different, so it's difficult to say make sure folder XXX has rights.
You will also run into problems with Windows tech (they don't understand *nix \ windows mapping in NFS) so they may push back and say "permissions are set correctly".. which may be a true.. to a POINT.. but they just need to allow root access or anonymous access (for NFS) to access those folders as well.
This is an EASY fix, just not easy to describe the steps and folders that need to change.
10 More Discussions You Might Find Interesting
1. AIX
Hi Guys,
Autofs works fine on AIX 5.2, but the same thing is not getting mounted automatically on AIX 5.3..
Is there ant difference for autofs confiiguration between 5.2 and 5.3
Thanks & Regards
Manu (0 Replies)
Discussion started by: b_manu78
0 Replies
2. Solaris
Hi,
I want to permanently disable nfs and autofs in solaris 9, (2 Replies)
Discussion started by: manoj.solaris
2 Replies
3. Solaris
I've a sun server, 3 sun workstations and plan to do backup on certain directory in each workstations monthly.
As it's only require to mount as NFS on those workstations once a month. So I plan to configure such requirement using autofs.
What are the considerations need to take care in such... (4 Replies)
Discussion started by: KhawHL
4 Replies
4. Solaris
hi
tell me difference between direct automount and indirect automount.
thanks you (1 Reply)
Discussion started by: sijocg
1 Replies
5. Solaris
what are all the advantages of direct map and indirect map in 'AUTOFS' and which one is better for our usage (2 Replies)
Discussion started by: dinu
2 Replies
6. UNIX for Dummies Questions & Answers
I am running CentOS 6.3 as a VM on a host which has the same installation. I configured my NFS server and I am guessing it works. I say guessing because I can mount the desired folder with mount command on my client machine. So, when I run:
mount -t nfs -o vers=3 vm2.domain.com:/nethome /nethit... (7 Replies)
Discussion started by: bashily
7 Replies
7. Red Hat
I have an nfs at 192.168.1.10:/home/vm1/Desktop/nfs and will like to mount locally to /home/vm1/Desktop/nfs-mount using automounter...need help doing do
What i did
$cat /etc/auto.master
/home/vm1/Desktop /etc/auto.nfs
$cat /etc/auto.nfs
nfs-bind -fstype=nfs ... (3 Replies)
Discussion started by: nokia3310
3 Replies
8. Red Hat
Hi
I'm trying to use autofs to mount a directory structure. I have a directory with sub directories in it and all of them mounted on their respective filesystems
/dbname /dev/mapper/vg_dbname-Home
/dbname/oracle00 /dev/mapper/vg_dbname-Data00... (3 Replies)
Discussion started by: maverick_here
3 Replies
9. Red Hat
RHEL 7.1 client using autofs to mount a NIS map of home directories being exported by a Solaris 10x86 nfs server.
The owner and group are correct on the NFS server, but on the RHEL client, the owner and group end up being nobody nobody. The USERS and GROUPS are NIS maps as well. They are... (2 Replies)
Discussion started by: mrmurdock
2 Replies
10. Fedora
Hi all,
I'm having trouble getting autofs working on a new install of Scientific Linux 7.2.
I have the files /etc/auto.master, /etc/auto/homes and /etc/auto.misc and /auto.direct setup, and they are copies of files on a working SL 6 machine. I can include the contents of the files at the end... (0 Replies)
Discussion started by: HuntWilliamR
0 Replies
cr(1) General Commands Manual cr(1)
NAME
cr - converts text files between nix EOL and dos EOL
SYNOPSIS
cr - | + <input file> <output file>
DESCRIPTION
Text files, such as tle files, that come from a dos source usualy have the ^M symbol at the end of every line. Cr converts files between
the dos newline format and the normal *nix newline format by stripping the ^M to convert dos to *nix, using the '-' option, or adding ^M to
a *nix file to create the proper dos file when the '+' option is used.
Although this extra character is not often a problem, programs like seesat5, which are data driven will encounter parsing problems when the
extra character is present. It is these problems that cr is intended to repair.
Options
- | + One or the other of these options is required. The '-' option is used to remove ^M from all newlines found in the dos file. The '+'
option is used to add ^M to every newline found in a *nix file.
input file
Fully delineated path to the input file. As this program is used in the dos environment as well, standard input is not used.
output file
Fully delineated path to the output file. As this program is used in the dos environment as well, standart output is not used.
SEE ALSO
seesat5(1), seesat5(7), SEESAT5.INI(5), tle(5)
BUGS
Cr is not an inteligent program. It methodicaly replaces/removes the offending character when it finds it in the correct context. Newline
sequences found in contexts other than 'newline' will be replaced/removed just like those found in the proper context. Passing a binary
file through cr is not advised, for this reason. Send all inqueries to Dale Scheetz <dwarf@polaris.net>.
Debian Linux 2 April 96 cr(1)