Printable View
I have tried variations of the "visionfs client" command until I'm
almost blue.
I have a share setup on a Maxtor terabyte NAS storage. It uses Win
networking for access, so i would like to get the SCO to be an
authenticate client to the share.
Does anyone know step-by-steo how to get this too work?
Thanks,
Bob
On 23 Aug, 09:29, Bob Meyers <oregon...@gmail.com> wrote:[color=blue]
> I have tried variations of the "visionfs client" command until I'm
> almost blue.[/color]
Bob,
An understand of what you have tried and how it has failed
might help in understand what the issue is.
[color=blue]
> I have a share setup on a Maxtor terabyte NAS storage. It uses Win
> networking for access, so i would like to get the SCO to be an
> authenticate client to the share.
>
> Does anyone know step-by-steo how to get this too work?[/color]
VisionFS (and OpenServer 5.0.6) are legacy products that
SCO no longer supports. While it may be possible to
access the NAS (if the Win networking you mention above
is not "too modern") I would suggest that you consider
upgrading your server to OpenServer 6, which is supported
and includes Samba 3.
John
----- Original Message -----
From: "Bob Meyers" <oregonbob@gmail.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Saturday, August 23, 2008 3:29 AM
Subject: visionfs access a WinNT share from SCO 5.0.6
[color=blue]
>I have tried variations of the "visionfs client" command until I'm
> almost blue.
>
> I have a share setup on a Maxtor terabyte NAS storage. It uses Win
> networking for access, so i would like to get the SCO to be an
> authenticate client to the share.
>
> Does anyone know step-by-steo how to get this too work?
>
> Thanks,
> Bob[/color]
I know it's possible because I've done it. But it was way back in '99 on a 5.0.5 box, and I played with visionfs at that time enough over the course of about a year to decide that I would rather use samba or facetwin for those times when I absolutely must use netbios file sharing. And really, I generally successfully avoid needing to use netbios file sharing at all.
The most common use for me for any form of windows file/print sharing is printing, both directions.
Windows since win2k can both print to and share via lpd so there's not much need for for using netbios to print to a windows share or to let windows print to a sco share. Though I do ebd up using facetwin a lot simply because almost all the stand-alone customers have it _anyways_ and unlike samba or visionfs, facetwin very fast/easy/simple to set up printers and have them actually work, either way (server or client), first time, every time.
For file-transfer, there are soooo many ways to skin that cat that that so far it's just never been the case that I actaully _needed_ to do it specifically the way you are asking about. (mount a windows share like any other disk or nfs filesystem). But it's worth mentioning and knowing that that is the one possible reason _to_ use visionfs in my opinion.
It's the only netbios client on open server that can mount a windows share like an nfs share or like smbmount does on linux.
I've never needed it, but I concede situations could exist where it may be the only or the best way to handle some job.
(I don't know whether to consider/include/count AFPS)
Usually I almost always can use the web server and the end result is all 3 of, simpler, more robust/reliable/self-maintaining, more portable.
The closest to needing to mount a share was really more accurately phrased as needing the two boxes to have access to a common area, and it didn't really matter if the sco box mounted a windows share, or if the windows box munted a sco box share. So far, for me anyways, it always was just as good to have the windows box mount a share on the sco box instead of the other way around.
In a few other odd cases where the sco box really does want to reach out to a win box and drive the operations, I was able to do it with the ftp-client-like utils fct_client or smbclient.
I'd be happy to help suggest or explore other possible approaches if you describe the actual need, in leue of dredging up visionfs docs that I have no where to test on anyways.
--
Brian K. White [email]brian@aljex.com[/email] [url]http://www.myspace.com/KEYofR[/url]
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
This is a bit of a shot in the dark - it's several years since the last
time I used VisionFS, and that was as a server, not as a client.
One issue that I used to run into had to do with packet signatures.
VisionFS didn't support them; some versions of Windows by default required
them (I think 2000 and above, though I'm not 100% sure), while others
considered them optional.
Is it possible that your NAS requires them by default, and therefore
can't be connected to by anything that doesn't support them? This wouldn't
cause problems with any Windows version from at least the last decade or
so, as I think even 95 and 98 supported it (but didn't require it), but
would cause problems with VisionFS.
--
Stephen M. Dunn <stephen@stevedunn.ca>[color=blue][color=green][color=darkred]
>>>----------------> [url]http://www.stevedunn.ca/[/url] <----------------<<<[/color][/color][/color]
------------------------------------------------------------------
Say hi to my cat -- [url]http://www.stevedunn.ca/photos/toby/[/url]
On Aug 23, 2:29*am, Bob Meyers <oregon...@gmail.com> wrote:[color=blue]
> I have tried variations of the "visionfs client" command until I'm
> almost blue.
>
> I have a share setup on a Maxtor terabyte NAS storage. It uses Win
> networking for access, so i would like to get the SCO to be an
> authenticate client to the share.
>
> Does anyone know step-by-steo how to get this too work?
>
> Thanks,
> Bob[/color]
I no longer have any clients using VisionFS, having switched everybody
that needed it to Samba, warts and all. It's no longer installed so I
can't really look at it in real time. But after jogging my memory for
a bit, I have two pieces of advice.
1. You may be using the wrong command. Look at the 'clientadmin'
command. Not sure about this, it's been a while.
2. The man pages for VisionFS are essentially worthless from the SCO
side. I never could figure out a way to filter the output so I could
view a screen at a time. So go to a Windows box at which you can view
the VisionFS manual, then print the pages. Some of these commands
have dozens of switches, and seeing the syntax printed in a graphical
context with bold and italics will help.
Mark
On Aug 27, 2:38*pm, mbennett <mbenn...@claritysoftwaresystems.com>
wrote:[color=blue]
> On Aug 23, 2:29*am, Bob Meyers <oregon...@gmail.com> wrote:
>[color=green]
> > I have tried variations of the "visionfs client" command until I'm
> > almost blue.[/color]
>[color=green]
> > I have a share setup on a Maxtor terabyte NAS storage. It uses Win
> > networking for access, so i would like to get the SCO to be an
> > authenticate client to the share.[/color]
>[color=green]
> > Does anyone know step-by-steo how to get this too work?[/color]
>[color=green]
> > Thanks,
> > Bob[/color]
>
> I no longer have any clients using VisionFS, having switched everybody
> that needed it to Samba, warts and all. *It's no longer installed so I
> can't really look at it in real time. But after jogging my memory for
> a bit, I have two pieces of advice.
>
> 1. You may be using the wrong command. *Look at the 'clientadmin'
> command. *Not sure about this, it's been a while.
>
> 2. The man pages for VisionFS are essentially worthless from the SCO
> side. *I never could figure out a way to filter the output so I could
> view a screen at a time. *So go to a Windows box at which you can view
> the VisionFS manual, then print the pages. *Some of these commands
> have dozens of switches, and seeing the syntax printed in a graphical
> context with bold and italics will help.
>
> Mark[/color]
try enabling plain text passwords in NT ..