10-30-2001
NFS is a viable solution when Samba is not possible.
My suggestion would be to set up a Linux box and make sure you can do NFS between the UNIX server and the Linux box. When you can sucessfully do this; then proceed to a UNIX-->W2K configuration. First, try UNIX<--->UNIX NFS.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am a real newbie to linux/unix and need alot of help. I have been trying to find through books and internet , how to change the network properties(ip address,subnet mask, protocols,ect..)But I cant seem to find out how.Also do I need to install samba to network to other windows machines on a peer... (2 Replies)
Discussion started by: scotte
2 Replies
2. UNIX for Dummies Questions & Answers
I have successfully installed Slackware 8.0 on a disk and Windows 2000 on the other. The win-disk being the master and linux-disk the slave. I do multi booting via LILO and everything works great.
But recently I've decided to remove the harddrive with linux on and put it in another computer.... (6 Replies)
Discussion started by: J.P
6 Replies
3. UNIX Desktop Questions & Answers
I want to know if there is any problem that install windows2000 and unix or linux on same computer.I partition my harddisk to 4,
3 of 4 are NTFS, 1 is FAT32, I want to install unix or linux on this partition.how should I do??? (6 Replies)
Discussion started by: sw_water
6 Replies
4. Linux
Hi All,
I was trying to ftp multiple files from my windows to my linux box, everything gets transfered but unfortunately some of them are corrupted.
I found out that some of the files are in Ascii and some are binary, but since most of the files I'm trying to send are Ascii...the big ones... (2 Replies)
Discussion started by: 3rr0r_3rr0r
2 Replies
5. Solaris
Hello!
I have a Linux nfs server (called server100 below) with a export nfs. My problem is that the Solaris client (called client100 below) doesn't seems to like it. In the Solaris syslog I got following messages (and after a while the solaris client behave liked its hanged/to buzy). Also see... (3 Replies)
Discussion started by: sap4ever
3 Replies
6. UNIX for Dummies Questions & Answers
How can i create a nfs share in Windows? (4 Replies)
Discussion started by: proactiveaditya
4 Replies
7. Solaris
Hello,
I have a centos as nfs server, its name is centos_A.
After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/*
But,
My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies
8. AIX
Hi 2 ALL,
try to run NFS Server in AIX 7.1 :
1. Step by step on NFS Server node
mkdir /tmp/test
chgrp staff /tmp/test
chmod 775 /tmp/test-- create export directory (fs)
mknfsexp -d /tmp/test -t ro
exportfs -va
show mount -e
:/# exportfs -av
exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies
9. Solaris
Only for testing/learning I have setup a windows 2000 server with active directory
I connect to it a Solaris 10 machine "client".
I want Solaris10 take users from AD
I have follow this guide..
a)Setup active directory environment+services for UNIX
OK
b)I have created two users,one for... (2 Replies)
Discussion started by: Linusolaradm1
2 Replies
nfssec(5) File Formats Manual nfssec(5)
NAME
nfssec - overview of NFS security modes
DESCRIPTION
The mount_nfs(1M) and share_nfs(1M) commands each provide a way to specify the security mode to be used on an NFS filesystem through the
option. mode can be either or These security modes may also be added to the automount maps. Note that mount_nfs(1M) and automount(1M) do
not support at this time.
The option on the share_nfs(1M) command line establishes the security mode of NFS servers. If the NFS connection uses the NFS Version 3
protocol, the NFS clients must query the server for the appropriate mode to use. If the NFS connection uses the NFS Version 2 protocol,
then the NFS client uses the default security mode, which is currently NFS clients may force the use of a specific security mode by speci-
fying the option on the command line. However, if the filesystem on the server is not shared with that security mode, the client may be
denied access.
If the NFS client wants to authenticate the NFS server using a particular (stronger) security mode, the client wants to specify the secu-
rity mode to be used, even if the connection uses the NFS Version 3 protocol. This guarantees that an attacker masquerading as the server
does not compromise the client.
The NFS security modes are described below. Of these, the modes use the Kerberos V5 protocol for authenticating and protecting the shared
filesystems. Before these can be used, the system must be configured to be part of a Kerberos realm.
Use authentication. The user's UNIX user-id and group-ids are passed in the clear on the network, unauthenticated by the NFS server
. This is the simplest security method and requires no additional administration. It is the default used by HP-UX NFS Version 2
clients and HP-UX NFS servers.
Use a Diffie-Hellman public key system
which is referred to as in the forthcoming Internet RFC).
Use Kerberos V5 protocol to authenticate users before granting access
to the shared filesystem.
Use Kerberos V5 authentication with integrity checking (checksums) to
verify that the data has not been tampered with.
User Kerberos V5 authentication, integrity checksums, and privacy protection
(encryption) on the shared filesystem. This provides the most secure filesystem sharing, as all traffic is encrypted. It should
be noted that performance might suffer on some systems when using depending on the computational intensity of the encryption
algorithm and the amount of data being transferred.
Use null authentication
NFS clients using have no identity and are mapped to the anonymous user by NFS servers. A client using a security mode other
than the one with which an HP-UX NFS server shares the filesystem has its security mode mapped to In this case, if the filesystem
is shared with users from the client are mapped to the anonymous user.
WARNINGS
lists the NFS security services. Do not edit this file. It is not intended to be user-configurable.
FILES
NFS security service configuration file
SEE ALSO
automount(1M), mount_nfs(1M), share_nfs(1M), rpc_clnt_auth(3N), secure_rpc(3N), nfssec.conf(4).
nfssec(5)