News Group Posts

visionfs over internet

See also Using Visionfs or Samba across subnets.

I did this once over a VPN to a branch office back in the days of very poor and very asymmetric internet connections. It was just this side of unbearable, but I guess most VPN access was just as bad so they got used to it.

Newsgroups: comp.unix.sco.misc
From: Bob Willey <bob@ccs.COM>
Subject: Re: VisionFS access thru the internet
Date: Tue, 28 Dec 1999 05:46:16 GMT
Message-ID: <4.1.19991228004006.00ad0a70@consult> 

Just got finished testing this, and setting up TCP port 139 so that it is
passed in/out of the Firewall, allows VisionFS to work over a WAN/Internet.
 Won't show us in Network Neighborhood, but doing a Start / Run
//machinename   (and having the machine name listed in the
\Windows\lmhosts  file)
and voila  VisionFS shows up.  Make sure the user/machine name is defined
in the VisionFS users, and also that WIN98 is setup for PlainTextPasswords
or else you will get the infamous  "password incorrect" even though it is a
correct password.
Go to www.sco.com/ta  and look up  Windows 98   and you will see the article

Pretty slick actually.  
I setup our firewalls on both sides to filter and only allow certain IP's
on port 139, thus giving an extra level of security.

Bob Willey -   http://www.ccs.com/happyherbal.html


At 08:36 PM 12/25/1999 +0000, Aldert van der Laan wrote:
>On Fri, 17 Dec 1999 08:09:59 +0000, Matt Schofield
><mattsc@sco.deletethisbit.com> wrote:
>
>
>>> 
>>> I am running VisionFS 3 locally, but have not opened any ports to the Wan
>>> yet.
>>> There is no full time systems admin, my customer has outsourced this to the
>>> company I work for.
>>> 
>>
>>It's certainly possible. The issues you should be aware of:
>>
>>1. The satellite office PC's will need some way of resolving the
>>server's name to an IP Address e.g. WINS, lmhosts files. VisionFS won't
>>appear in their Network Neighbourhood. You should set up shortcuts or
>>mapped drives on the user's PC's.
>>
>
>I setup an Lmhosts file as well as a hosts file.
>I am unable to connect to the main office, although I have enabled the
>Netbios port 139 and read over the "manual" a thousand times.
>
>I almost seems that the service is not bound to the dialup connection.
>Could it be that the ISP is filtering out these connections?
>As stated the people can telnet in and I even tried rlogin (which I
>enabled before and disabled after the test).
>
>I am using PPP from Morningstar on the server, could that cause a
>problem maybe?
>
>I can't seem to find any leads on the TA site of SCO.
>
>It simply states it is possible.
>
>Ah... well better get some Christmas dinner.....
>
>Happy holidays,
>
>Aldert
>
>
>>2. You should set VisionFS up to filter connections to only allow access
>>from designated ranges of IP Addresses. See p88 of the VisionFS manual
>>on the CD or from http://www.sco.com/vision/eval/manuals.html. You
>>should also set the firewall to filter connections.
>>
>>3. You should only need to open port 139 on the WAN as 137 and 138 also
>>used by VisionFS are for UDP packets and hence unneccessary over the
>>WAN.
>>
>>4. You should set up VisionFS to use encrypted passwords (default)
>>otherwise clients may send UNIX passwords in plain text (as does telnet
>>and FTP). See p84-86 of the manual. 
>>
>>Regards
>>
>>Matt Schofield

->      Bob Willey  -  bob@ccs.com       <-
           CCS Enterprises, Inc. 
      PO Box 35   Linkwood MD  21835
http://www.ccs.com    Come Visit Us !!
http://www.intercom.net/user/consult
-> (410) 228-9211 -- FAX: (410) 901-1105 <-

From - Thu Feb 24 04:51:19 2000
From: Roberto Zini <fred@strhold.it>
Newsgroups: comp.unix.sco.misc
Subject: Re: PPP Connections
Date: Thu, 24 Feb 2000 10:20:01 +0100
Message-ID: <38B4F7C1.65CFED86@strhold.it> 
References: <38B46841.782A3A73@home.com> 

Peter T. Corgan wrote:
> 
> Hello Everyone,
> 
> I have read so much information I think I am getting
> myself confused. My goal is to connect a PC in one of
> our branches to the corporate server in another county.
> Because it is a long distance call, the PC is going to
> call a computer (SCO box) in our second branch, which
> will have a connection to the main server at our
> corporate office.
> 
> The PC in branch one O/S is Windows98.
> The SCO box in branch two O/S is SCO Unix 5.05...
> The SCO box at corporate is SCO Unix 5.05...
> 
> Do I configure the SCO box in branch two as a Gateway?
> Do I create IP addresses to be on the same network? Or
> Do I create routes?
> The staff in branch two has no computer experience at all.
> What would be the simplest way to make the connection
> from branch two to the corporate server?
> 
> I thank you in advance for any feedback that you can give
> me. I have allot to do any no time to do it...
> 
> THANKS!!! Pete Corgan

Well, unless you're using some sort of 'Proxy ARP' (detailed
in the 'SCO OpenServer Networking Guide' manual), it's better
to have the SCO box in branch two acting as a gateway (configure
it by using the 'netconfig' interface). Next, configure an
incoming PPP connection by either using SCO PPP or MorningStar
PPP and assign a different network ID to this network (eg,
Win98=192.168.0.1 <-PPP-> SCO OS5=192.168.0.2); the same OS5
box could have a LAN connection to a router BUT with a
different network ID (eg, SCO OS5=192.168.1.1 <-LAN-> Router=
129.168.1.2).

For additional info see Tony Lawrence's web site at

        

Best,
Roberto
-- 
---------------------------------------------------------------------
Roberto Zini                                  email : fred@strhold.it
Technical Support Manager -- Strhold Sistemi EDP Reggio Emilia(ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"                
        (Pete "Maverick" Mitchell - Top Gun)

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.