Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mounting WIN shared directory

Status
Not open for further replies.

josel

Programmer
Oct 16, 2001
716
US
Howdy dudes!

First of all - wish you all a very merry christmas and happy new year to you all!!!

I am trying to mount a shared directory in my window box to my SCO OpenServer box. I named the directory UNIX and set it to be shared as UNIX; permissions are all open.

From the UNIX server, I then typed

mount -f NFS 192.168.0.138:/UNIX /mypc

and I got
mount: 192.168.0.138:/UNIX server not responding (1)
: RPC: Port mapper failure - RPC: Timed out

As far as not responding, I thought PC was not reachable but I am able to ping it ...

Can you please offer some trouble-shooting points and possibly a solution? Please!!!!

Thank you all in advance.

Regards;

Jose Lerebours KNOWLEDGE: Something you can give away enlessly and gain more of it in the process! - Jose Lerebours
 
Sounds like the NFS server is not running on the Windows box.
I'm not a Windows expert but does sharing a directory as UNIX mean that Windows runs NFS server software? Maybe you can check in the Services to see if the NFS server is running. Just a guess.
 
NFS does not come standard with all versions of windows. You may need to purchase and install an NFS server package for your windows box before you can make this work.

You should define the machine you are trying to mount in your /etc/hosts file. You should then be able to manage this filesystem using the scoadmin filesystem manager.
 
OK, I'm back!

I have purchased and installed Windows Services for Unix 3.0. I am now able to mount my shared directory.

I noticed that everytime I ran `l` in the mounted directory, I got a couple of warnings which went away when I ran `nfs start`. Now, my `l` are clean.

The problem I am facing now is permission problems. I have Gateway for NFS running in my window server and have setup the shared directory to full control permissions to all users. I set the octal settings to 777 and I still cannot copy from UNIX local directories into WINDOWS shared (mounted) directory.

To mount shared directory I used:
mount 192.168.100.5:/unixshare /appl/unixshare

I tried:
cp /appl/rpts/report01 /appl/unixshare and I get

cp: unable to create file /cd/wholock: Permission denied (error 13)

The UNIX local directory is set to full, wide open, permission as well.

What am I doing wrong or missing here?

Thank you all in advance!

Regards;

Jose Lerebours KNOWLEDGE: Something you can give away endlessly and gain more of it in the process! - Jose Lerebours
 
This error does not make sense, why is the cd command trying to write to the file /cd/wholock ?


What is /cd/wholock ? have you had a look at this file ?



Strange ?


Regards,
UkWizard.
 
My bad!

In troubleshooting the problem, I unmounted /appl/unixshare and mounted /cd ... When I posted the error, I was mounted to /cd thus the error show cd instead of /appl/unixshare.

If I mounted /appl/unixshare, I still get the same error.

Sorry for the mix up!


Jose Lerebours KNOWLEDGE: Something you can give away endlessly and gain more of it in the process! - Jose Lerebours
 
Is it possible you have mounted the filesystem as read-only?

What happens if you copy a file to the folder in windows? Can you then see or read the file from the unix machine?

I usually use the scoadmin filesystem manager to mount my nfs filesystems. You might be able to get some hint to the problem if you look at the mount status from there.

Another possibility, is that your NFS password and group files on the Windows box are not set up correctly to allow access.

One more possibility, I have seen some cases where 777 permissions on the unix box is translated to system read only on a windows machine, causing a permissions conflict.
 
apeasecpc,

Thank you for taking the time and replying.

I copied a file to the share resource within windows but cannot see it in unix (it does not list). When I run `l`, I get zero files.

The command I used was mount -f NFS 192.168.100.5:/unixware /cd

192.168.100.5 is the Windows 2000 server. In the same server, I have /unixware set to share with read/write properties.

I have not been able to figure out how to map the users. I can't get the SFU to find my UNIX box ... (This is bad, isn't it?).

Well, if 777 is bad, then that could be part of the reason. /appl is a mounted filesystem. This is where we keep application related files and have a good % of unused space. appl mod is set 777 filepro:group. /appl/unixshare mod is set to 777 root:sys.

Only root will be copying into mounted shared resource.

I am inclined to remove SFU and reinstall - Take it from the top!

Do I have to install anything in the UNIX end? If so, what is it? I have not added a thing in my UNIX server other than run `nfs start`.

Thanks;


Jose Lerebours

KNOWLEDGE: Something you can give away endlessly and gain more of it in the process! - Jose Lerebours
 
If you aren't getting any errors when you mount, My first guess is that you have a user mapping problem on the windows side, which is causing access to be denied.

With NT 4.0 the user and group settings are defined in the passwd and group files located in c:\winnt\system32\drivers\etc on the server. For the contents of these files I basically copied them from my SCO machine and then deleted any lines referring to users or groups I didn't want included. Your system probably has something similar. Your NFS software for windows should have documentation on how to map users.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top