Harry Putnam wrote:
> I get somewhat confused trying to go through the mount_smbfs man page.
>
> Operands
> The mount command supports the following operands:
>
> resource //[workgroup;][user[:passwo...@]server/share
>
> The name of the resource to be mounted. In addition to
> its name, you can specify the following information
> about the resource:
The resource is the way you specify the
share you want to mount. The format of
the resource is as follows:
//[workgroup;][user[:passwo...@]server/share
> What is an example of a `resource' in the cmdline above?
Gordon already sent you resource
examples.
> Are they just referring to the fs type (in this case smbfs)?.
>
> Is the semi-colon at //[workgroup;]
> ^ here
>
> supposed to be a colon? It appears to cause the command to fail if
> actually included in the command.
The semicolon is required when you specify
a workgroup name. See the following
description in the man page:
o workgroup is the name of the workgroup or the
Windows domain in which the user name is
defined.
If the resource includes a workgroup, you must
escape the semicolon that appears after the
workgroup name to prevent it from being inter-
preted by the command shell. For instance, sur-
round the entire resource name with double
quotes: mount -F smbfs "//SALES;geo...@rserver"
/mnt.
> I'm thinking some thing like this is what is meant (except for the
> `resource' part - wrapped for mail - passwd x'ed out):
>
> mount -F smbfs resource?? //HOME;reader:xxx...@mob1/mob1-c\
> /mnt/mob1-c
>
> mount -F smbfs //HOME;reader:xxxx...@mob1/mob1-c /mnt/mob1-c
> mount: Mount point cannot be determined
> bash: reader:xx...@mob1/mob1-c: No such file or directory
Try this instead:
mount -F smbfs "//HOME;reader:xxx...@mob1/mob1-c" /mnt/mob1-c
Cathleen.
> It also fails if I make the semi-colon a colon.
>
> mount -F smbfs //HOME:reader:xxxx...@mob1/mob1-c /mnt/mob1-c
> mount: session setup phase failed: syserr = authentication failed
>
> I don't really understand what I'm doing as must be obvious but are
> those command lines at least close?
>
> The user has accounts on osol server and in the case above what would
> be the windows server. The users passwd has been in place for ages.
>
> I've been able to mount these shares with no problesm from a linux
> machine with mount.cifs.
>
> So whats the problem above, can anyone tell?
>
> I've posted an attachment in a companion thread:
>
> Subject: osol cifs server windows xp clients no network neighbor
>
> showing every detail known to man about my cifs setup. if anyone
> cares to look but cifs isn't being served in this scenario.. the osol
> machine is client.
>
>
> _______________________________________________
> cifs-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
