News Group Posts

Visionfs broadcasting

Visionfs actually had excellent documentation, but it seemed like most SCO admins were unaware of it. That's probably because the docs were available by accessing the Visionfs administration editor from a Windows machine, not from Unix. The command line configuration did offer some help, but it was nothing like what you could see from Windows.

From: Matt Schofield <mattsc@sco.deletethisbit.com>
Newsgroups: comp.unix.sco.misc
Subject: Re: Vision FS Broadcast - how to limit?
Date: Fri, 27 Aug 1999 17:16:34 +0100
Message-ID: <37C6B9E1.9BE10254@sco.deletethisbit.com> 
References: <37C6B57A.49E3871C@total.net> 

Stuart H wrote:
> 
> Hi,
> 
> I have recently upgraded to SCO 5.05 and am using Vision FS 3.0 to
> utilize the system for file and print sharing.
> Everything is running great except that the server broadcasts throughout
> our network and is resident in every workgroup.
> I would like this server to be present within the one workgroup. It has
> been specified which group the server belongs yet it still broadcasts
> throughout.

VisionFS can either broadcast on a network, or not broadcast at all. It
cannot be set up to only broadcast to a certain subset of machines i.e.
a workgroup. VisionFS can be configured to appear in a particular
workgroup by running (Profile Editor -> Server Properties ->
Identification.

The only surefire way of stopping VisionFS from broadcasting on a
network is to turn Windows naming off (Profile Editor -> Server
Properties -> Advanced -> Disable Naming). This will stop VisionFS from
appearing in any workgroup and will limit communications to TCP port 139
(nothing on UDP 138, 139). This will require all clients to have
VisionFS configured in their lmhosts file and users will only be able to
access the server by running '\\servername', or using premapped network
drives.

Hope this helps

Matt Schofield
-- 
Return email address junked

This is the opposite desire:

From - Thu Dec 23 05:45:16 1999
From: Matt Schofield <mattsc@sco.deletethisbit.com>
Newsgroups: comp.unix.sco.misc
Subject: Re: NT Workgroups
Date: Thu, 23 Dec 1999 09:51:20 +0000
Message-ID: <3861F098.1F9EF736@sco.deletethisbit.com> 

Andrew West wrote:
> 
> Can anyone explain to me what I have to do to get my SCO Unix 7.1 box to
> appear in my network neihborhood. I currently have NT Clients with NT Server
> authenticating and can only see my SCO box when I click on entire network
> and then I get my workgroup and the SCO Box. I would like to see it when I
> open network neihborhood along with everything else on the network.
> Any ideas would be appreciated.
> 
> SCO Novice

Assuming you're using VisionFS:


By default VisionFS will appear in domain/workgroup browselists if that
domain has a member master browser on the same subnet as VisionFS. 

It is possible to force VisionFS to appear in specific domains and
workgroups by taking the following steps:

1. Run the Profile Editor. In the Identification Tab select any entries
with a corresponding workgroup entry of (all) and Remove them.

2. Click New... Select an appropriate Server Name (default should
suffice). In the workgroup  box type the name of the domain/workgroup
you wish VisionFS to appear in. Leave the CIFS entry blank.

3. Repeat 2. for all domains/workgroups you wish VisionFS to be
browsable in.

4. In the Advanced tab ensure that the 'Participate in master browser
elections' box is enabled.

5. From the Profile Editor menu bar select Profile -> Restart Server.

The VisionFS server will now appear in the specified Domain Browselists
though due to the nature of browsing it may take up to approx. 1 hour
for the browse lists to be propogated around the network.

Regards

Matt Schofield
-- 
Return email address junked

Comments?

More Articles by Tony Lawrence - Find me on Google+

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.