SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 18 | September | 2006 ]

>> Next Message >>


Date: Mon, 18 Sep 2006 09:40:10 -0700
From: Ray Davison <raydav@charter.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: Networking

Content Type: text/plain

I may have missed the question, but isn't this an in-house network where
security is not an issue? That is my case and I just set every shared
drive for basic/read write. Those drives are now there for the taking
for any machine I connect.

The only thing I have had to do to get Win to connect was to get the
proper protocols on the Win side, nothing special on the OS/2 side.

And I have never had to fiddle with any configuration files, everything
was done in Connections. It should also show if things are working. As
you may have noticed, I barely know what a command line is.

Ray

Steven Levine wrote:
>
> OK you have NETBEUI installed. This means you should be able share files
> between the eCS boxes without any TCP/IP configuration. We can configure
> for sharing with the Windows boxes later.
>
> You can do a basic test of the install with
>
> net start peer
>
> from the command line.
>
> To start sharing files, you need to define the users and the shares to
> Peer. Find the LAN configuration folder in the Connections folder.
>
> LAN sharing permissions are user based. This means that each user must be
> defined on each machine that you wish to give the user access to. This
> user's password needs to be the same on each machine.
>
> When you installed eCS, you supplied an LAN administrator name and
> password. Login with this user id and password to get started. This user
> has permission to do anything.
>
> There's also a guest user, but it's better to delete this user once you
> have the other users configured.
>
> Define your users and your shares and you should be ready to go. The Peer
> configuration notebook is reasonable intuitive.
>
> Steven
>

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


>> Next Message >>

Return to [ 18 | September | 2006 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.