
                  OS/2 Lan discussion              (Fidonet)

                 Saturday, 04-Sep-1999 to Friday, 10-Sep-1999

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   04-Sep-99 13:04:23
  To: all                                               04-Sep-99 19:14:10
Subj: OS/2 networking & Linux

I'm trying to get Samba configured properly on the Linux box here,  and am a
bit confused about the OS/2 side of things.  Which of the products in the Warp 
Connect stuff is what's needed to be able to map resources on other machines
and similar stuff?

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: David Calafrancesco                               04-Sep-99 22:45:10
  To: Roy J. Tellason                                   05-Sep-99 06:44:28
Subj: OS/2 networking & Linux

Roy J. Tellason wrote in a message to all:

 RJT> I'm trying to get Samba configured properly on the Linux box
 RJT> here,  and am a bit confused about the OS/2 side of things. 
 RJT> Which of the products in the Warp Connect stuff is what's
 RJT> needed to be able to map resources on other machines and
 RJT> similar stuff?

File and print sharing using NetBios over TCPIP. 

Dave Calafrancesco, Team OS/2
dave@drakkar.org

... They got the library at Alexandria, they're not getting mine! 
--- 
 * Origin: Druid's Grove BBS - (914)/876-2237 (1:2624/306)
278/111
724/10

+----------------------------------------------------------------------------+

From: Peter Knapper                                     05-Sep-99 15:04:01
  To: Roy J. Tellason                                   05-Sep-99 08:14:15
Subj: OS/2 networking & Linux

Hi Roy,

 RJT> I'm trying to get Samba configured properly on the 
 RJT> Linux box here,  and am a bit confused about the OS/2 
 RJT> side of things.  Which of the products in the Warp 
 RJT> Connect stuff is what's needed to be able to map 
 RJT> resources on other machines and similar stuff?

SAMBA (for *nix) is the equivalent of PEER SERVICES (for OS/2). PEER Services
consists of both the SERVER and CLIENT code. You need PEER SERVICES running to 
be able to connect an OS/2 CLIENT to resources served from a SAMBA Server.

One point to watch out for is that the PEER SERVICES machines is configured in 
the SAME DOMAIN (or WORKGROUP) as the SAMBA machine. If they are in different
DOMAINS, then they will not be able to see each other... Then you need to
consider the User profiles you are going to login in with...

Cheers........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Kenneth Duke                                      05-Sep-99 08:43:16
  To: All                                               05-Sep-99 16:29:09
Subj: A OS/2 machine to linux box

Maybe someone here can help me out abit with a problem I'm having...

I've setup a Linux Mandrake 6.1 box with cablemodem and a extra network card.
The Linux box is running fine.  I've added IP MASQ to the system, so, I'm able 
to connect to the Internet via my other 2 Win98 boxes...
I've tested the connections on the Win98 boxes, and everything runs fine.
However, on the OS/2 box, it won't run any Internet app...
I can however PING the outside world with the OS/2 box.

HELP me!


--- Telegard/2 v3.09.g2-sp3/mL
 * Origin: telnet://pcnashville.dhs.org (1:116/158)

+----------------------------------------------------------------------------+

From: MIKE RUSKAI                                       04-Sep-99 18:31:00
  To: ROY J. TELLASON                                   05-Sep-99 16:29:09
Subj: OS/2 networking & Linux

Some senseless babbling from Roy J. Tellason to All
on 09-04-99  13:04 about OS/2 networking & Linux...

 RJT> I'm trying to get Samba configured properly on the Linux box here, 
 RJT> and am a bit confused about the OS/2 side of things.  Which of the
 RJT> products in the Warp Connect stuff is what's needed to be able to map
 RJT> resources on other machines and similar stuff?

NetBIOS.  You can also get a version of GNU Samba for OS/2, but it's a pain 
to set up.

Mike Ruskai
thannymeister@yahoo.com


... Americans call it fast food because it speeds them to the grave.

___ Blue Wave/QWK v2.20
--- Platinum Xpress/Win/Wildcat5! v3.0pr2
 * Origin: FIDO QWK MAIL & MORE!  WWW.DOCSPLACE.ORG (1:3603/140)
278/111
724/10

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   05-Sep-99 12:08:09
  To: David Calafrancesco                               05-Sep-99 18:25:25
Subj: OS/2 networking & Linux

David Calafrancesco wrote in a message to Roy J. Tellason:

 DC> Roy J. Tellason wrote in a message to all:

 RJT> I'm trying to get Samba configured properly on the Linux box
 RJT> here,  and am a bit confused about the OS/2 side of things. 
 RJT> Which of the products in the Warp Connect stuff is what's
 RJT> needed to be able to map resources on other machines and
 RJT> similar stuff?

 DC> File and print sharing using NetBios over TCPIP. 

I've got both TCP/IP and NetBIOS configured as protocols,  and had thought
that you didn't need NetBIOS _over_ TCP/IP if stuff didn't need to be routed
to other lan segments.  No?

In the network stuff is "Peer logon",  "Lan server logon",  and some other
stuff.  That's where the confusion is.  I think I need to look at the
username/password issue,  too.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   05-Sep-99 12:10:12
  To: Peter Knapper                                     05-Sep-99 18:25:25
Subj: OS/2 networking & Linux

Peter Knapper wrote in a message to Roy J. Tellason:

 PK> SAMBA (for *nix) is the equivalent of PEER SERVICES (for OS/2). 
 PK> PEER Services consists of both the SERVER and CLIENT code. You 
 PK> need PEER SERVICES running to be able to connect an OS/2 CLIENT 
 PK> to resources served from a SAMBA Server.

Now _that_ is the bit that I was looking for...

 PK> One point to watch out for is that the PEER SERVICES machines 
 PK> is configured in the SAME DOMAIN (or WORKGROUP) as the SAMBA 
 PK> machine. If they are in different DOMAINS, then they will not 
 PK> be able to see each other... Then you need to consider the User 
 PK> profiles you are going to login in with...

Yes,  I was aware of the domain issue,  and have stayed on top of that.  The
user login is another matter,  and one that I'd suspected I was going to have
to deal with here.

There are an awful lot of different "bits" of stuff in the networking part of
this,  and I'm not real clear as to just which ones I need to be using.  It
doesn't help much that everybody calls things by different names,  either. <g>

Firing up the OS/2 box as I type this,  I see "net start req" going by,  and
it's attempting to start network messaging too (how do I stop that?).

In my network folder there's "LAN Svcs" (which is also on the desktop for some 
reason),  "LAN Server and OS/2 Peer Resources",  "Network SignON
Coordinator/2", and "UPM Services".  Do I need _all_ of that?

Clicking on that second one,  I get prompted for a login,  and trying one with 
a username/password that I know is valid on the other box,  I get "access
denied". It also says in that "Login" box that the Network is "LS",  dunno
where that came from or how to change it.  The domain name does show up
properly in another part of that,  though.

Clicking on the third and fourth items won't let me get past a password
prompt, I'm not sure what I need to configure to fix this.

Under "LAN Svcs" there's a whole bunch of stuff.  What the difference is
between "LAN Server Logon" and "Peer Workstation Logon" isn't clear to me.
Both of these get as far as a user/password prompt,  and appear to be doing
some stuff over the network (judging by the flickering lights on my hub) but
the former comes back with "The remote node or domain server is not currently
available" (which suggests that I don't have something configured right) and
the latter won't let me get past the user/password prompt.  In either case I'm 
trying a login that's valid on the Linux box.

One last thing -- if I click on "Sharing and Connecting" it shows me some
stuff that's on the w95 box,  but that's about it,  nothing on the Linux box
shows up in here (though I can see that stuff on the w95 box!)...

Suggestions?  I could use some help here...  :-)

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: LEE ARONER                                        05-Sep-99 08:28:00
  To: ROY J. TELLASON                                   05-Sep-99 20:21:26
Subj: OS/2 networking & Linux

RJT> I'm trying to get Samba configured properly on the Linux box here,  and
am a
   > bit confused about the OS/2 side of things.  Which of the products in the 
Warp
   > Connect stuff is what's needed to be able to map resources on other
machines
   > and similar stuff?


   Samba makes Linux see and understand SMB (Server Message Block) 
   protocol, which is what the PC Lan boxes are using to exchange 
   file and directory information. You don't need to make any 
   changes on the PC side, except that you must enable NetBios over 
   IP, as that is the only NetBios that Samba knows.

   You also have to setup permissions on the Samba box, the docs 
   should explain that...

                                         LRA


 -- SPEED 2.01 #2720: "You can observe a lot just by watchin'." -- Yogi Berra
--- Platinum Xpress/Win/Wildcat5! v2.0
 * Origin: Memory Alpha - (253) 859-6200 (1:343/311)
3613/666

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   05-Sep-99 19:22:11
  To: MIKE RUSKAI                                       06-Sep-99 00:15:18
Subj: OS/2 networking & Linux

MIKE RUSKAI wrote in a message to ROY J. TELLASON:

 MR> Some senseless babbling from Roy J. Tellason to All

Oh fine,  you screw up once and people start talking like that about you...

 MR> on 09-04-99  13:04 about OS/2 networking & Linux...

 RJT> I'm trying to get Samba configured properly on the Linux box here, 
 RJT> and am a bit confused about the OS/2 side of things.  Which of the
 RJT> products in the Warp Connect stuff is what's needed to be able to map
 RJT> resources on other machines and similar stuff?

 MR> NetBIOS.

It's in there.  But I don't know which aspects of the OS/2 side of things I
need to fiddle with to get this working properly.

 MR> You can also get a version of GNU Samba for OS/2, but it's a 
 MR> pain to set up.

I don't know why I'd want to,  since the OS/2 box is going to be strictly a
client in this setup,  while the Linux box is a server.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Elvis Hargrove                                    05-Sep-99 20:47:05
  To: Roy J. Tellason                                   06-Sep-99 06:39:15
Subj: OS/2 networking & Linux

-> RJT> I'm trying to get Samba configured properly on the Linux box

Roy, my supplier tels me that you need to visit TUCOWS site for a thing
called a "Configurer" for Samba which makes it duck soup to set up.  I
just came from his place, and he's got W98, W95, WinNT and Warp all
runing in different windows on the Linux box. AND they all network with
the NT server nicely.

 ^..^
--- FidoPCB v1.5 beta-'j'
 * Origin: Personal Freedom is NEVER really FREE! (1:397/6.2)
278/111
724/10

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   05-Sep-99 23:02:13
  To: LEE ARONER                                        06-Sep-99 08:26:24
Subj: OS/2 networking & Linux

LEE ARONER wrote in a message to ROY J. TELLASON:

 LA> You don't need to make any     changes on the PC side, except 
 LA> that you must enable NetBios over     IP, as that is the only 
 LA> NetBios that Samba knows.

Oh?  I thought it talked just netbios,  as opposed to netbios over tcp/ip.  On 
the w95 box I have it working and that has tcp/ip and netbios installed as two 
separate protocols,  no netbios over tcp/ip there.

And,  my understanding of this stuff is that the _only_ time you need netbios
_over_ tcp/ip is when you want netbios stuff to cross from one lan segment to
another,  as it's routable while netbios by itself isn't.  Since I have only
the one lan segment here,  that's not an issue.

 LA>    You also have to setup permissions on the Samba box, the 
 LA> docs     should explain that...

Yep.  Now,  if I go to the w95 box and open network neighborhood,  I can see
the Linux box no problem.  Clicking on that shows me a printer icon and three
shares that I have set up,  which I can get into no problem.  On the OS/2 box
I have got nowhere near this far.  The "shares and connections" icon doesn't
seem to be able to see the Linux box at all,  though I had no problems with
this seeing the w98 box I used to run.

Domain names agree,  and the protocols and whatnot match up,  IP addresses are 
as they should be (all 192.168.x.n),  so what's the problem?  What else do I
need to fiddle with here?

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   06-Sep-99 01:47:28
  To: Elvis Hargrove                                    06-Sep-99 08:26:24
Subj: OS/2 networking & Linux

Elvis Hargrove wrote in a message to Roy J. Tellason:

-> RJT> I'm trying to get Samba configured properly on the Linux box

 EH> Roy, my supplier tels me that you need to visit TUCOWS site for 
 EH> a thing called a "Configurer" for Samba which makes it duck 
 EH> soup to set up.

For which platform?

 EH> I just came from his place, and he's got W98, W95, WinNT and 
 EH> Warp all runing in different windows on the Linux box. AND they 
 EH> all network with the NT server nicely.

Yeah,  Samba seems to have a lot of stuff in it to deal with NT servers,  if
you've got 'em.

I've heard of that site,  but no web access at this point in time.  I'll ask
around and see what I can do,  though.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     06-Sep-99 20:39:06
  To: Roy J. Tellason                                   06-Sep-99 11:36:04
Subj: OS/2 networking & Linux

Hi Roy,

 PK> SAMBA (for *nix) is the equivalent of PEER SERVICES (for OS/2). 
 PK> PEER Services consists of both the SERVER and CLIENT code. You 
 PK> need PEER SERVICES running to be able to connect an OS/2 CLIENT 
 PK> to resources served from a SAMBA Server.

 RJT> Now _that_ is the bit that I was looking for...

I forgot to add, the terminology changed slightly betweem Warp 3 and Warp 4.
With Warp 3 is it called "OS/2 Peer" and on Warp 4 its called "File and Print
Client", but effectively they are the exact same thing. If I remember
correctly you were using Warp 3, so my comments should make some sense without 
translation.......;-)


 RJT> The user login is another matter,  and one that I'd 
 RJT> suspected I was going to have to deal with here.

The easiest way to initially handle Users is to set up the SAME Userid on each 
machine as ADMINISTRATOR (an administrator is one who has access rights to
create and delete SHARES and CONNECTIONS), and also make sure that login has
the SAME password on each machine. Then perform a LOGIN on each machne. This
way you stand the best chance of getting things running.


 RJT> Firing up the OS/2 box as I type this,  I see "net 
 RJT> start req" going by,  and it's attempting to start 
 RJT> network messaging too (how do I stop that?).

The NET START command is starting up the 2 parts of OS/2 PEER. The SERVER part 
is ALWAYS required, even if you onyl want to SERV up resources to other
CLIENTS. The REQUESTOR is the CLIENT part that allows the OS/2 box to connect
to other SERVERS. I normally remove the Network Messaging icon from the
STARTUP folder and only start it if I need it, although it can be useful to
debug problems.


 RJT> In my network folder there's "LAN Svcs" (which is also 
 RJT> on the desktop for some reason),  "LAN Server and OS/2 
 RJT> Peer Resources", 

This is a dynamic folder that is updated as MACHINES are found in the network. 
I dont normally use it myself, its a bit slow for me, but it can be useful to
show me what is around ont he Network. Warning: It will show machines that
WERE visible on the LAN at one time but may not currently be connected to the
LAN (EG a laptop that is removed from the LAN). A useful tool for browsing
what is out there.

 RJT> "Network SignON Coordinator/2", and 

If you connect to Network resources spread over different machines and types
of systems, NSC can be VERY useful to co-ordinate your logon to each of these
platforms. Essentially it remembers the last login to each platform and allows 
you to re-activate each login automatically. 

When you change passwords on a platform, it remembers that change and handles
it too. It also allows you to change the password on ALL paltforms at once and 
remembers any password changes that DONT complete, a real help when you are in 
a large distributed envronment.  

If you only have 1 other machine you wish to log on to then its probably not
of much use. I used it to manage an NT Server, a Novell logon, and an seperate 
OS/2 Peer logon using just one login sequence.


 RJT> "UPM Services".  

User Profile Management. Allows you to manage the Users configured to access
your machine. What is useful about UPM is that I could access the User
profiles on an NT Server and manage them as well, however I could only access
a subset of the possible options.

 RJT> Do I need _all_ of that?

Possibly not, you need to decide. Put them away for a later time if you dont
wish to dig into them now,.

 RJT> Clicking on that second one,  I get prompted for a 
 RJT> login,  and trying one with a username/password that I 
 RJT> know is valid on the other box,  I get "access denied".

I am not sure which "second one" you mean, however to do ANY work with UPM or
managing resources you MUST already be logged in as an ADMINISTRATOR! See next 
bit...


 RJT> It also says in that "Login" box that the 
 RJT> Network is "LS",  dunno where that came from or how to 
 RJT> change it.  The domain name does show up properly in 
 RJT> another part of that,  though.

Somewhere under your OS/2 PEER Folder you will see 3 LOGINS. The Default
configuration for OS/2 PEER has 3 ways of handling Users, however there are
other ways and things can get really complicated (but extremely useful if you
know what you are doing and are aware of the implications). There is probably
no need for you to use anything other than the default options so -
 
 1. LOGON
        Requires the User to be defined on the LOCAL machine. 
        The Logon is validated only on the local machine. In 
        most cases, a user logged in as this cannot access 
        resources on other machines that requires user validation 
        for access to shared resources.
 2. PEER LOGON
        Similar to 1, the user is validated locally, but also allows 
        the User to access other OS/2 Peer (or Workgroups style) 
        machines (provided they are configured on those machines to        
have access). This is a true PEER environment, ALL machines         are of
equal status. This is the same style of Networking as 
        provided by W4WG 3.11 operation, HOWEVER it has advantages...;-).
 3. LAN SERVER LOGON
        This type of Logon REQUIRES a DOMAIN CONTROLLER to be used. 
        I doubt if you have one of these so this is of no use to you.
        If you do not have a Primary or Secondary Domain Controller 
        on your LAN, then you CANNOT USE THIS! Basically, your Logon
        is validated on the DOMAIN controller, the LOCAL user profile 
        is NOT used at all. If the Userid exists on the local machine, 
        then the user may have extra access as defined lcoally, but 
        this is NOT required.

From this you can see that the whole Networking world becomes a LOT more
complicated than you first thought, there are so many ways of doing things,
and you are only using the installation defaults! When you have a few spare
months you can get into Forwarded Authentication and all manner of fiddling
with Access rights, but for now, stick with a type 2 Logon.


 RJT> Clicking on the third and fourth items won't let me 
 RJT> get past a password prompt, I'm not sure what I need 
 RJT> to configure to fix this.

When you installed OS/2 PEER, 1 of 2 things happened. Either your FIRST
startup of the network asked for a Userid and Password that beccame the
OWNERof the mcahine, or the system asigned the DEFAULT values of USERID and
PASSWORD. That Userid is the OWNER of the Network environment on that machine, 
and that is what it is asking for. Basically you MUST be logged in as an
Administrator to be able to run the Administration utilities! Once you have
access you can assign a NEW user with FULL Access rights and remove the
default one.

If you have forgotten the Userid and/or the password that you set them to when 
you installed Networking, then you have no option but to reset the User
Accounts database. Doing this will also wipe ALL your OS/2 PEER configuration
settings and erase your shares and connections! If you have not yet set any of 
these up, then you are safe to reset them all. 

Its actually quite easy to do this, go into the INSTALL of PEER Services and
follow through the install process until it finds the existing Database and
asks if you want to RESET it. Reply YES and it isntalls tehe defaults again. 


 RJT> Under "LAN Svcs" there's a whole bunch of stuff.  What the difference is 

 RJT> between "LAN Server Logon" and "Peer Workstation 
 RJT> Logon" isn't clear to me.

See above, the Logon explaination should resolve this question.


 RJT> In either case I'm trying a login that's valid on the Linux box.

The Linux box is NOT a PDC so forget trying to use a DOMAIN Login, it will
never work without a PDC or BDC. If you CANNOT log in to the Local machine,
then you will NEVER be able to log into a remote machine using a PEER LOGIN! A 
PEER Login REQUIRES a LOCAL Login to suceed first!


 RJT> One last thing -- if I click on "Sharing and 
 RJT> Connecting" it shows me some stuff that's on the w95 
 RJT> box,  but that's about it,  nothing on the Linux box 
 RJT> shows up in here (though I can see that stuff on the 
 RJT> w95 box!)...

You are lucky, the problem is usually that you can't browse Windows resources
until you build manual entries somewhere...

Make sure ALL machines have NETBIOS over TCP/IP configured in them. You may
also have to set up some broadcast mappings in NB over IP, I dont know if
SAMBA needs these or not (I have never used SAMBA).

If the Linux box has an unprotected share available (IE a resource that does
NOT require a password to access it, such as a printer), then that is not
surprising. If the Linux box HAS an "open" resource, then it should be visible 
to you. if not, you have some sort of networking problem between the machines, 
probably at the SMB level, not at the physical cabling level.

I hope this helps to get some things resolved.

Cheers............pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Kari Suomela                                      06-Sep-99 10:51:14
  To: All                                               06-Sep-99 18:39:21
Subj: Telnet

Is there a decent telnet client for OS/2, which allows multiple sessions? I
tried ZOC, but if I open a new session, it closes the previous one. :(

 KS


---
 * Origin: *  telnet://bbs.karicobs.com * (1:2424/101)
278/111
724/10

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   06-Sep-99 13:19:22
  To: Peter Knapper                                     06-Sep-99 18:39:21
Subj: OS/2 networking & Linux

Peter Knapper wrote in a message to Roy J. Tellason:

 PK> SAMBA (for *nix) is the equivalent of PEER SERVICES (for OS/2). 
 PK> PEER Services consists of both the SERVER and CLIENT code. You 
 PK> need PEER SERVICES running to be able to connect an OS/2 CLIENT 
 PK> to resources served from a SAMBA Server.

 RJT> Now _that_ is the bit that I was looking for...

 PK> I forgot to add, the terminology changed slightly betweem Warp 
 PK> 3 and Warp 4. With Warp 3 is it called "OS/2 Peer" and on Warp 
 PK> 4 its called "File and Print Client", but effectively they are 
 PK> the exact same thing. If I remember correctly you were using 
 PK> Warp 3, so my comments should make some sense without 
 PK> translation.......;-)

Yes,  it's Warp Connect (blue,  if that matters).

 RJT> The user login is another matter,  and one that I'd suspected I 
 RJT> was going to have to deal with here.

 PK> The easiest way to initially handle Users is to set up the SAME 
 PK> Userid on each machine as ADMINISTRATOR (an administrator is 
 PK> one who has access rights to create and delete SHARES and 
 PK> CONNECTIONS), and also make sure that login has the SAME 
 PK> password on each machine. Then perform a LOGIN on each machne. 
 PK> This way you stand the best chance of getting things running.

Ok,  I can do that.

 RJT> Firing up the OS/2 box as I type this,  I see "net start req" 
 RJT> going by,  and it's attempting to start network messaging too 
 RJT> (how do I stop that?).

 PK> The NET START command is starting up the 2 parts of OS/2 PEER. 
 PK> The SERVER part is ALWAYS required, even if you onyl want to 
 PK> SERV up resources to other CLIENTS. The REQUESTOR is the CLIENT 
 PK> part that allows the OS/2 box to connect to other SERVERS. 

Why is it that the requester starting up seems to take so long?  Also on
shutdown it sits there on "Peer service is being stopped" for a while...

 PK> I normally remove the Network Messaging icon from the STARTUP 
 PK> folder and only start it if I need it, although it can be 
 PK> useful to debug problems.

I'll look in the starup folder next time I fire that up.  How would you use
that?

 RJT> In my network folder there's "LAN Svcs" (which is also on the 
 RJT> desktop for some reason),  "LAN Server and OS/2 Peer 
 RJT> Resources",

 PK> This is a dynamic folder that is updated as MACHINES are found 
 PK> in the network. I dont normally use it myself, its a bit slow 
 PK> for me, but it can be useful to show me what is around ont he 
 PK> Network. Warning: It will show machines that WERE visible on 
 PK> the LAN at one time but may not currently be connected to the 
 PK> LAN (EG a laptop that is removed from the LAN). A useful tool 
 PK> for browsing what is out there.

Hm.  (Firing up that box to see what's in there...)  Ok,  this is where it's
giving me a "Login" box to deal with.  And calling the "Network" LS?  Anyhow
it's not letting me in there,  so I obviously need to fix something there. 
But where?  It's making the lights flicker on my hub,  as if it's trying to do 
something over the network...

Heck,  it won't let me even change that "Network" name or "Description"
settings,  either.

 RJT> "Network SignON Coordinator/2", and 

 PK> If you connect to Network resources spread over different 
 PK> machines and types of systems, NSC can be VERY useful to 
 PK> co-ordinate your logon to each of these platforms. Essentially 
 PK> it remembers the last login to each platform and allows you to 
 PK> re-activate each login automatically.

That sounds like something that would come in handy,  particularly with using
another system as a fileserver.

 PK> When you change passwords on a platform, it remembers that 
 PK> change and handles it too. It also allows you to change the 
 PK> password on ALL paltforms at once and remembers any password 
 PK> changes that DONT complete, a real help when you are in a large 
 PK> distributed envronment. 

 PK> If you only have 1 other machine you wish to log on to then its 
 PK> probably not of much use. I used it to manage an NT Server, a 
 PK> Novell logon, and an seperate OS/2 Peer logon using just one 
 PK> login sequence.

What I have here at the present time are this (dos/dv) box that's eventually
going to also be running Warp,  the OS/2 box,  a w95 box,  and a Linux box
that's been given a fair pile of disk space and will probably be getting more
as I change things around.

I think that ideally I'd like to end up with a setup where any user (family
mostly) can go to any of these boxes and log on,  and use whatever resources
are available on the network as a whole.

 RJT> "UPM Services".  

 PK> User Profile Management. Allows you to manage the Users 
 PK> configured to access your machine. What is useful about UPM is 
 PK> that I could access the User profiles on an NT Server and 
 PK> manage them as well, however I could only access a subset of 
 PK> the possible options.

I wonder if I could fiddle with my own "user" in there?  Hm,  that's got a
"Logon" and "Logoff" pair of icons in there too.  Hm,  attempting to use the
User Account Management icon in there also wants a logon and won't let me in.  
I'm going to have to dig into this a bit...     <g>

 RJT> Do I need _all_ of that?

 PK> Possibly not, you need to decide. Put them away for a later 
 PK> time if you dont wish to dig into them now,.

 RJT> Clicking on that second one,  I get prompted for a login,  and 
 RJT> trying one with a username/password that I know is valid on the 
 RJT> other box,  I get "access denied".

 PK> I am not sure which "second one" you mean, however to do ANY 
 PK> work with UPM or managing resources you MUST already be logged 
 PK> in as an ADMINISTRATOR! See next bit...

 RJT> It also says in that "Login" box that the Network is "LS",  
 RJT> dunno where that came from or how to change it.  The domain 
 RJT> name does show up properly in another part of that,  though.

 PK> Somewhere under your OS/2 PEER Folder you will see 3 LOGINS.

In "LAN Svcs" there's a "LAN Server Logon" and "Peer Workstation Logon" and
"Logoff".

 PK> The Default configuration for OS/2 PEER has 3 ways of handling 
 PK> Users, however there are other ways and things can get really 
 PK> complicated (but extremely useful if you know what you are 
 PK> doing and are aware of the implications). There is probably no 
 PK> need for you to use anything other than the default options so 
 PK> -   1. LOGON
 PK>         Requires the User to be defined on the LOCAL machine.

That "user profile" stuff was trying to do a local logon.

 PK>        The Logon is validated only on the local machine. In     
 PK>      most cases, a user logged in as this cannot access 
 PK> resources on other machines that requires user validation for 
 PK> access to shared resources.

I could be mistaken about this,  but it appears that such a thing is possible
with Samba running on the Linux box -- that if the OS/2 machine can be
persuaded to hand over the user login and password it'll deal with things from 
there...

 PK>  2. PEER LOGON
 PK>         Similar to 1, the user is validated locally, but also 
 PK> allows the User to access other OS/2 Peer (or Workgroups style) 
 PK> machines (provided they are configured on those machines to 
 PK> have access). This is a true PEER environment, ALL machines are 
 PK> of equal status. This is the same style of Networking as 
 PK> provided by W4WG 3.11 operation, HOWEVER it has 
 PK> advantages...;-).  

What advantages are those?

 PK> 3. LAN SERVER LOGON
 PK>         This type of Logon REQUIRES a DOMAIN CONTROLLER to be 
 PK> used. I doubt if you have one of these so this is of no use to 
 PK> you. If you do not have a Primary or Secondary Domain 
 PK> Controller on your LAN, then you CANNOT USE THIS! Basically, 
 PK> your Logon is validated on the DOMAIN controller, the LOCAL 
 PK> user profile is NOT used at all. If the Userid exists on the 
 PK> local machine, then the user may have extra access as defined
 PK> lcoally, but this is NOT required.

This sounds to me like something that Samba would deal with on the Linux box
as well,  though I still have some work to do on that end.

 PK> From this you can see that the whole Networking world becomes a 
 PK> LOT more complicated than you first thought, there are so many 
 PK> ways of doing things, and you are only using the installation 
 PK> defaults! 

Well,  maybe.  I've done some fiddling around with this stuff although it's
been a few months since I was in here messing around,  and that's probably why 
I am having trouble getting into a few places!

I got a bonus with a book a while back,  in that the cdrom that came with it
had a "book" on networking included,  and yes,  it sure is a very complicated
subject!  Unfortunately,  a lot of what they talked about in there was
applicable mainly to Netware and NT-based systems,  neither of which I am
running nor have any plans to run here.

 PK> When you have a few spare months you can get into Forwarded 
 PK> Authentication and all manner of fiddling with Access rights, 
 PK> but for now, stick with a type 2 Logon.

Maybe.  <g>

 RJT> Clicking on the third and fourth items won't let me get past a 
 RJT> password prompt, I'm not sure what I need to configure to fix 
 RJT> this.

 PK> When you installed OS/2 PEER, 1 of 2 things happened. Either 
 PK> your FIRST startup of the network asked for a Userid and 
 PK> Password that beccame the OWNERof the mcahine, or the system 
 PK> asigned the DEFAULT values of USERID and PASSWORD. 

_That one_ worked!  For "Peer Workstation Logon",  anyhow.  And got me inot
"Lan server and OS/2 Peer Resources",  and "User Account Management",  too. 
But it still doesn't seem to want to see the Linux box for some reason.  The
w95 box shows up in that "Peer Resources" box okay,  even though it's not
turned on at the moment.

 PK> That Userid is the OWNER of the Network environment on that 
 PK> machine, and that is what it is asking for. 

Yep,  I'd been mistaken about what I was trying in those password prompts, 
and forgot where the heck it described that in the online docs.

 PK> Basically you MUST be logged in as an Administrator to be able 
 PK> to run the Administration utilities! Once you have access you 
 PK> can assign a NEW user with FULL Access rights and remove the 
 PK> default one.

Yeah,  I can see where that goes,  now.

 PK> If you have forgotten the Userid and/or the password that you 
 PK> set them to when you installed Networking, then you have no 
 PK> option but to reset the User Accounts database. Doing this will 
 PK> also wipe ALL your OS/2 PEER configuration settings and erase 
 PK> your shares and connections! If you have not yet set any of 
 PK> these up, then you are safe to reset them all.

 PK> Its actually quite easy to do this, go into the INSTALL of PEER 
 PK> Services and follow through the install process until it finds 
 PK> the existing Database and asks if you want to RESET it. Reply 
 PK> YES and it isntalls tehe defaults again.

Would that be the "Installation" under "LAN Svcs"?

 RJT> Under "LAN Svcs" there's a whole bunch of stuff.  What the difference is
 RJT> between "LAN Server Logon" and "Peer Workstation Logon" isn't 
 RJT> clear to me.

 PK> See above, the Logon explaination should resolve this
 PK> question. 


 RJT> In either case I'm trying a login that's valid on the Linux box.

 PK> The Linux box is NOT a PDC so forget trying to use a DOMAIN 
 PK> Login, it will never work without a PDC or BDC. If you CANNOT 
 PK> log in to the Local machine, then you will NEVER be able to log 
 PK> into a remote machine using a PEER LOGIN! A PEER Login REQUIRES 
 PK> a LOCAL Login to suceed first!

Ok,  I've gotten past that point,  now what to try?  :-)

 RJT> One last thing -- if I click on "Sharing and Connecting" it 
 RJT> shows me some stuff that's on the w95 box,  but that's about 
 RJT> it,  nothing on the Linux box shows up in here (though I can 
 RJT> see that stuff on the w95 box!)...

 PK> You are lucky, the problem is usually that you can't browse 
 PK> Windows resources until you build manual entries somewhere...

 PK> Make sure ALL machines have NETBIOS over TCP/IP configured in 
 PK> them. You may also have to set up some broadcast mappings in NB 
 PK> over IP, I dont know if SAMBA needs these or not (I have never 
 PK> used SAMBA).

You're not the first one to say this,  but my understanding of the protocol
issues is that you don't need that unless you want to route NETBIOS stuff
across more than one lan segment,  and that having both NetBIOS and TCP/IP (as 
separate protocols in there) should do the trick.  I can try sticking it in
there and see if it makes any difference,  though.  (Trying that in MPTS &
restarting...)

 PK> If the Linux box has an unprotected share available (IE a 
 PK> resource that does NOT require a password to access it, such as 
 PK> a printer), then that is not surprising. If the Linux box HAS 
 PK> an "open" resource, then it should be visible to you. if not, 
 PK> you have some sort of networking problem between the machines, 
 PK> probably at the SMB level, not at the physical cabling level.

It does have several such shares available,  three or four of which show up on 
the w95 box here.

 PK> I hope this helps to get some things resolved.

Gettin' there...

I've added that protocol (in addition to the two that were there,  and changed 
the "number" to 1 rather than 0 as someone else pointed out a while back), 
restarted,  logged on,  and am still stuck when I try to get any further
results with the "Sharing and Connecting" part,  particularly the "Create a
Connection" part.  I can enter the machine name of the Linux box under the
"Workstation" field,  at which point it upcases it (could that be a problem?)
and under the "Share/alias" field it says "<none>".  Trying to enter any of
the share names that I'm looking at in smb.conf on my other screen get me an
error message:  "Error 53 occurred.  SYS0053: The network path was not found." 
Trying each of the defined shares gives the same result.

So it doesn't appear to be seeing that Linux box at all,  at this point. 
There's obviously some bits I haven't got quite right,  as I just fired up the 
w95 box and it can see itself and both the OS/2 box _and_ the Linux box there. 
I just need to figure out what details I need to fiddle with here.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Elvis Hargrove                                    06-Sep-99 12:36:05
  To: Roy J. Tellason                                   06-Sep-99 18:39:21
Subj: OS/2 networking & Linux

-> Yeah,  Samba seems to have a lot of stuff in it to deal with NT
-> servers,  if you've got 'em.

Only one possible reason I can think of why you don't...... <Grin>

-> I've heard of that site,  but no web access at this point in time.
-> I'll ask around and see what I can do,  though.

I guess I should have let him go ahead and give it to me on CD since he
had it there and the CD burner was working.....


 ^..^
--- FidoPCB v1.5 beta-'j'
 * Origin: Personal Freedom is NEVER really FREE! (1:397/6.2)
278/111
724/10

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   06-Sep-99 20:13:21
  To: Elvis Hargrove                                    07-Sep-99 02:44:16
Subj: OS/2 networking & Linux

Elvis Hargrove wrote in a message to Roy J. Tellason:

-> Yeah,  Samba seems to have a lot of stuff in it to deal with NT
-> servers,  if you've got 'em.

 EH> Only one possible reason I can think of why you don't...... 
 EH> <Grin>

Only one?  Have you seen the stuff that came out today regarding cryptographic 
keys embedded into some M$ software modules?  Apparently there's two of them
in w95 and 98,  and _three_ of them in NT.  Talk about back doors...

Besides that,  it's my understanding that an NT _server_ wants at least 64MB
of ram,  and is happier with 128M or more,  while you can get the same
performance out of Linux w/ 16M or so.  <g>

I don't have an NT server because I don't have a whole pile of excess hardware 
to throw at it,  basically.  And because at this point in time I'm more
interested in functionality than in getting to know yet another package,  even 
if that other package will let me develop some marketable skills.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     07-Sep-99 22:57:28
  To: Roy J. Tellason                                   07-Sep-99 12:13:10
Subj: OS/2 networking & Linux

Hi Roy,

 RJT> Why is it that the requester starting up seems to take 
 RJT> so long? 

It looks around the LAN to see what other resources are available that it
might be able to use. The need for this is moot with the default PEER type
configuration, but if it finds a PDC it can note this now for later use. The
timings used for doing this can be user controlled, but you really need to
know a LOT about SMB Networking and using a DOMAIN CONTROLLER to be able to
tune how long it takes. As usual, IBM are rather conservative with their
default timings... If you play with this (and there are HUNDREDS of
settings!!!), be very careful, you can kill a machine or a NETWORK so easily
by getting these wrong...

 RJT> Also on shutdown it sits there on "Peer 
 RJT> service is being stopped" for a while...

It advertises to the LAN what you are doing so that anything else on the
Network can "unlink" you from their resources. This should be automatically
handled, but its possible for the user to stop and start things manually, so
it takes some time to perform a tidy shutdown of the network. In a small
network its not too important, but on a large one it ensures there are plenty
of Network resources freely available at all times. NT takes the same time to  
shut down its Networking...


 PK> I normally remove the Network Messaging icon from the STARTUP 
 PK> folder and only start it if I need it, although it can be 
 PK> useful to debug problems.

 RJT> I'll look in the starup folder next time I fire that 
 RJT> up.  How would you use that?

Actually I was thinking of the AUDIT LOG, that tool CAN be useful for
debugging problems. Network Messaging is like a chat program, it allows you to 
converse with another user on the LAN, just a simple Desktop to Desktop
Messager type of function, TOTALLY unrelated to EMAIL!


 RJT> "Network SignON Coordinator/2", and 

 PK> If you connect to Network resources spread over different 
 PK> machines and types of systems, NSC can be VERY useful to 
 PK> co-ordinate your logon to each of these platforms. Essentially 
 PK> it remembers the last login to each platform and allows you to 
 PK> re-activate each login automatically.

 RJT> That sounds like something that would come in handy,  
 RJT> particularly with using another system as a fileserver.

ONLY if you use multiple DOMAIN Logins (IE you have MULTIPLE PDC's!) If you
dont use Domain Logins, then its useless (well almost, but there are so many
problems it can cause with PEER environments if you are not experienced).
Leave it alone unless you have more than 1 PDC and really need it!


 RJT> I think that ideally I'd like to end up with a setup 
 RJT> where any user (family mostly) can go to any of these 
 RJT> boxes and log on,  and use whatever resources are 
 RJT> available on the network as a whole.

The Advantage of using a DOMAIN CONTROLLER is that EVERYTHING can be
authenticated on the one system and makes what you want easier than individual 
configurations, it can make Multi-User administration over Multiple Platforms
nice and easy. 

The Dis-Advantage of using a DOMAIN CONTROLLER is that if your PDC dies and
there is no BDC, then you are TOTALLY DEAD in the water from a Networking
perspective on ALL machines! This is not strictly true, but unless you really
plan your DOMAIN and machine configurations carefully and set up backup
options (PEER Logins as well) on ALL Clients with matching logins and
passwords, then you can really have a hassle sorting out problems unless you
really know what you are doing. Tread very carefully down this path if you
wish to persue it... 


 RJT> It also says in that "Login" box that the Network is "LS",  
 RJT> dunno where that came from or how to change it.  The domain 
 RJT> name does show up properly in another part of that,  though.

LS refers to IBM LAN Server, the standard IBM Server platform that provides
the support for a PDC/BDC. 

 RJT> In "LAN Svcs" there's a "LAN Server Logon" and "Peer 
 RJT> Workstation Logon" and "Logoff".

I can't remember the exact locations of all objects with Warp 3, I totally
dislike the Folder layout used by IBM and move everything around to suit my
own perception of the world. IBM really seems to try hard and obfuscate things 
at times.......;-( The 3 logins I mention are there, but possibly under
different names. I change the names on many objects to reflect a more
"sensible" naming (IMHO).

The different Logons are actually all the same executable, but different
parameters cause it to present a different set of boxes (with slightly
different titles) to be filled in. Look up the LOGON.EXE program help and note 
the possible commandline options. The one program does LOCAL, PEER and DOMAIN
logins...


 PK>        The Logon is validated only on the local machine. In     
 PK>      most cases, a user logged in as this cannot access 
 PK> resources on other machines that requires user validation for 
 PK> access to shared resources.

 RJT> I could be mistaken about this,  but it appears that 
 RJT> such a thing is possible with Samba running on the 
 RJT> Linux box -- that if the OS/2 machine can be persuaded 
 RJT> to hand over the user login and password it'll deal 
 RJT> with things from there...

Thats what happens with a PEER Logon. When you connect from OS/2 to a share on 
a remote system that is PROTOTECTED, depending on how things are set up, OS/2
will present your current local Logon Id and prompt for a password, or supply
your current logged on password. This can be confiugred in "Sharing and
Connecting" for each resource you wish to connect to...


 PK> This is the same style of Networking as 
 PK> provided by W4WG 3.11 operation, HOWEVER it has 
 PK> advantages...;-).  

 RJT> What advantages are those?

An OS/2 PEER environment can actually access up to 4 different DOMAINS at the
same time. To do this requires manual editing of the OS/2 PEER configuration
files, but it works fine. I used my Laptop OS/2 Peer environment co-existing
in 3 different DOMAINS for some time. WFWG 3.11 cannot exist in more than 1
DOMAIN at the same time. This really does help when doing certain types of
work. I think NT can only exist in one DOMAIN at a time too, at least i can't
find a way of getting it to exist in more than 1 at a time!


 PK> 3. LAN SERVER LOGON
 PK>         This type of Logon REQUIRES a DOMAIN CONTROLLER to be 
 PK> used. I doubt if you have one of these so this is of no use to 
 PK> you. If you do not have a Primary or Secondary Domain 
 PK> Controller on your LAN, then you CANNOT USE THIS! Basically, 
 PK> your Logon is validated on the DOMAIN controller, the LOCAL 
 PK> user profile is NOT used at all. If the Userid exists on the 
 PK> local machine, then the user may have extra access as defined
 PK> lcoally, but this is NOT required.

 RJT> This sounds to me like something that Samba would deal 
 RJT> with on the Linux box as well,  though I still have 
 RJT> some work to do on that end.

I dont know SAMBA, but I would not expect it to provide a full DOMAIN PDC
environment, there is quite a lot to providing a full PDC Server. As I said
before, unless you really need it, dont play with a PDC. 


 RJT> But it still doesn't seem to want to see the Linux box for 
 RJT> some reason.  The w95 box shows up in that "Peer Resources" 
 RJT> box okay,  even though it's not turned on at the moment.

Thats actually quite normal, previously OS/2 Peer had seen the W95 machine and 
remembered that it existed on the network. You can't browse it (obviously),
but if the machine is placed back on the LAN you can go directly to it.

Browsing an SMB Network exposes the biggest problem with SMB. SMB is a very
"chatty" protocol (there are a lot of exchanges between 2 points to complete
an information exchange and because it is a broadcast protocol, everyone on
the same LAN segment always gets all the messages.

In your case, the non-visibility of the Linux box is a little puzzelling,
however there could be several reasons for this. If ALL machines are using the 
SAME DOMAIN NAME, then the only thing I can think of is that the Linux box
MUST need NETBIOS over TCP/IP as its transport. Dont be fooled by the Windows
machine not showing NETBIOS over TCP/IP, I would bet that its probably there,
but not obvious. I haven't touched a W95 machine myself so I dont know what it 
looks like in its Networking configuration. I know that on NT its definately
in there as a unique protocol...

Add NETBIOS over TCP/IP to the OS/2 machine and see if that helps...

TIP: If when you try and browse the resources on the LINUX box from OS/2 it
reports back quickly (within about 5 seconds) and shows <none> as available,
then LINUX is saying to OS/2 that the currently logged in User on the OS/2
machine, is not allowed access to anything on the LINUX machine (access is
being rejected). If there is a delay of about 15 seconds or more before this
message comes back, then the LINUX box is not being found in the same DOMAIN
as the OS/2 box. 


 PK> Its actually quite easy to do this, go into the INSTALL of PEER 
 PK> Services and follow through the install process until it finds 
 PK> the existing Database and asks if you want to RESET it. Reply 
 PK> YES and it installs the defaults again.

 RJT> Would that be the "Installation" under "LAN Svcs"?

Yep...


 PK> Make sure ALL machines have NETBIOS over TCP/IP configured in 
 PK> them. You may also have to set up some broadcast mappings in NB 
 PK> over IP, I dont know if SAMBA needs these or not (I have never 
 PK> used SAMBA).

 RJT> You're not the first one to say this,  but my understanding 
 RJT> of the protocol issues is that you don't need that unless you 
 RJT> want to route NETBIOS stuff across more than one lan segment,  
 RJT> and that having both NetBIOS and TCP/IP (as separate protocols 
 RJT> in there) should do the trick.

Generalyl that is true, however over time the useof NB over IP has become very 
popular because it can solve a lot of problems.

I have not used SAMBA so I can't say for sure, however SMB started life as a
pure NETBIOS protocol. it could ONLY operate on a local LAN segment, unless
you had some way of connecting LAN segments together that transported NETBIOS
messages. Because NETBIOS is BROADCAST, and linking LANS over a WAN was very
slow, the entire LAN would run at the speed of the slowest WAN connection. 

At this stage the concept of encapsulating the NETBIOS traffic inside a TCP/IP 
packet was born. This had 2 immediate advantages, TCP/IP is not a Broadcast
communications mode it is Point to Point, so a large portion of the NETBIOS
traffic over the WAN was eliminated, speeding up LAN operations dramatically. 
TCP/IP can be very efficiently routed to wherever it is needed, so traffic was 
removed from everywhere it was NOT needed, freeing up the local LAN segments.
Also included in NB over IP was the ability to locate and store addressing
info to help resolve the addressing issues without refering back to the source 
all the time.

The one down side to NB over IP is that all this requires extra configuration
and can slow down the messaging between the machines that actually do connect
over the NB over IP component, but it does work. I connected from my OS/2
Thinkpad in Sydney Australia, to my OS/2 Desktop in Auckland NZ (about 1200
miles away), over a very busy routed Network and used my Desktops Modem to
place a local call in Auckland. It worked very well...

So much networking involves WAN components these days that it is not unusual
to find NETBIOS over TCP/IP in configurations, in fact over 95% of our NETBIOS 
based machines at work (about 1500) have it installed. I think the default
networking configuration for NT installs NB and NB over IP anyway...


 RJT> am still stuck when I try to get any further results with 
 RJT> the "Sharing and Connecting" part,  particularly the "Create 
 RJT> a Connection" part.  I can enter the machine name of the 
 RJT> Linux box under the "Workstation" field,  at which point 
 RJT> it upcases it (could that be a problem?) 

No, all SMB resource names are in upper case. 

 RJT> and under the "Share/alias" field it says "<none>".  

There are 3 things you need to check -

  1. The NETBIOS MACHINE name you supplied could not be found on 
     the network, 

  2. The NETBIOS MACHINE name could be found on the Network, but
     the DOMAIN NAME configured on the Server does NOT match the
     DOMAIN NAME on the OS/2 machine.

  3. The NETBIOS MACHINE name could be found on the Network, but 
     the user logged on to the OS/2 machine was not permitted to 
     access ANY resources on that Server.


 RJT> Trying to enter any of the share names that I'm looking at 
 RJT> in smb.conf on my other screen get me an error message:  
 RJT> "Error 53 occurred.  SYS0053: The network path was not found." 

Yep, the resource is not visible to OS/2 PEER, for whatever reason. From the
commandline enter -
  NET VIEW
and report the output. Also try -
  NET STATUS >zzz
and report the contents of the zzz file. The output is usually more than 30
lines so I send it to a file.


 RJT> There's obviously some bits I haven't got quite right,  
 RJT> as I just fired up the w95 box and it can see itself and 
 RJT> both the OS/2 box _and_ the Linux box there. 

Can the W95 box see AND CONNECT to a SHARE on the OS/2 box? 
Can the OS/2 box see AND CONNECT to a SHARE on the W95 box?

Regards........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   07-Sep-99 13:41:11
  To: Peter Knapper                                     07-Sep-99 19:48:19
Subj: OS/2 networking & Linux

Peter Knapper wrote in a message to Roy J. Tellason:

 RJT> Why is it that the requester starting up seems to take so long? 

 PK> It looks around the LAN to see what other resources are 
 PK> available that it might be able to use. The need for this is 
 PK> moot with the default PEER type configuration, but if it finds 
 PK> a PDC it can note this now for later use. The timings used for 
 PK> doing this can be user controlled, but you really need to know 
 PK> a LOT about SMB Networking and using a DOMAIN CONTROLLER to be 
 PK> able to tune how long it takes. As usual, IBM are rather 
 PK> conservative with their default timings... If you play with 
 PK> this (and there are HUNDREDS of settings!!!), be very careful, 
 PK> you can kill a machine or a NETWORK so easily by getting these 
 PK> wrong...

Well,  in that case I think I'll hold off on messing with any of that for the
time being.  At least until I know a whole *lot* more about what I'm getting
into here!

 RJT> Also on shutdown it sits there on "Peer service is being 
 RJT> stopped" for a while...

 PK> It advertises to the LAN what you are doing so that anything 
 PK> else on the Network can "unlink" you from their resources. This 
 PK> should be automatically handled, but its possible for the user 
 PK> to stop and start things manually, so it takes some time to 
 PK> perform a tidy shutdown of the network. In a small network its 
 PK> not too important, but on a large one it ensures there are 
 PK> plenty of Network resources freely available at all times. NT 
 PK> takes the same time to shut down its Networking...

Ok.

 PK> I normally remove the Network Messaging icon from the STARTUP 
 PK> folder and only start it if I need it, although it can be 
 PK> useful to debug problems.

 RJT> I'll look in the starup folder next time I fire that up. 

Did that,  and moved it so that it doesn't try and run on startup now.

 RJT> How would you use that?

 PK> Actually I was thinking of the AUDIT LOG, that tool CAN be 
 PK> useful for debugging problems. Network Messaging is like a chat 
 PK> program, it allows you to converse with another user on the 
 PK> LAN, just a simple Desktop to Desktop Messager type of 
 PK> function, TOTALLY unrelated to EMAIL!

Yeah,  so it appears.

 RJT> "Network SignON Coordinator/2", and 

<...>

 RJT> That sounds like something that would come in handy,  
 RJT> particularly with using another system as a fileserver.

 PK> ONLY if you use multiple DOMAIN Logins (IE you have MULTIPLE 
 PK> PDC's!) If you dont use Domain Logins, then its useless (well 
 PK> almost, but there are so many problems it can cause with PEER 
 PK> environments if you are not experienced). Leave it alone unless 
 PK> you have more than 1 PDC and really need it!

Ok...

 RJT> I think that ideally I'd like to end up with a setup where any 
 RJT> user (family mostly) can go to any of these boxes and log on,  
 RJT> and use whatever resources are available on the network as a 
 RJT> whole.

 PK> The Advantage of using a DOMAIN CONTROLLER is that EVERYTHING 
 PK> can be authenticated on the one system and makes what you want 
 PK> easier than individual configurations, it can make Multi-User 
 PK> administration over Multiple Platforms nice and easy. 

 PK> The Dis-Advantage of using a DOMAIN CONTROLLER is that if your 
 PK> PDC dies and there is no BDC, then you are TOTALLY DEAD in the 
 PK> water from a Networking perspective on ALL machines! This is 
 PK> not strictly true, but unless you really plan your DOMAIN and 
 PK> machine configurations carefully and set up backup options 
 PK> (PEER Logins as well) on ALL Clients with matching logins and 
 PK> passwords, then you can really have a hassle sorting out 
 PK> problems unless you really know what you are doing. Tread very 
 PK> carefully down this path if you wish to persue it...

Well,  I'm having a hassle sorting things out now,  so it sounds like I'm
already halfway there...!

 RJT> It also says in that "Login" box that the Network is "LS",  
 RJT> dunno where that came from or how to change it.  The domain 
 RJT> name does show up properly in another part of that,  though.

 PK> LS refers to IBM LAN Server, the standard IBM Server platform 
 PK> that provides the support for a PDC/BDC.

Ok.

 RJT> In "LAN Svcs" there's a "LAN Server Logon" and "Peer 
 RJT> Workstation Logon" and "Logoff".

 PK> I can't remember the exact locations of all objects with Warp 
 PK> 3, I totally dislike the Folder layout used by IBM and move 
 PK> everything around to suit my own perception of the world. 

I did some of that too,  so my mention of _where_ an icon happens to be
sitting probably isn't that important.

 PK> IBM really seems to try hard and obfuscate things at 
 PK> times.......;-( The 3 logins I mention are there, but possibly 
 PK> under different names. I change the names on many objects to 
 PK> reflect a more "sensible" naming (IMHO).

Same here.  I also shorten them a bit sometimes to make things easier to
arrange properly.

 PK> The different Logons are actually all the same executable, but 
 PK> different parameters cause it to present a different set of 
 PK> boxes (with slightly different titles) to be filled in. Look up 
 PK> the LOGON.EXE program help and note the possible commandline 
 PK> options. The one program does LOCAL, PEER and DOMAIN logins...

Ok.

 PK> The Logon is validated only on the local machine. In most 
 PK> cases, a user logged in as this cannot access resources on 
 PK> other machines that requires user validation for access to 
 PK> shared resources.

 RJT> I could be mistaken about this,  but it appears that such a 
 RJT> thing is possible with Samba running on the Linux box -- that 
 RJT> if the OS/2 machine can be persuaded to hand over the user 
 RJT> login and password it'll deal with things from there...

 PK> Thats what happens with a PEER Logon. When you connect from 
 PK> OS/2 to a share on a remote system that is PROTOTECTED, 
 PK> depending on how things are set up, OS/2 will present your 
 PK> current local Logon Id and prompt for a password, or supply 
 PK> your current logged on password. 

That's what I was thinking of.

 PK> This can be confiugred in "Sharing and Connecting" for each 
 PK> resource you wish to connect to...

I have not had a whole lot of luck in there.

 PK> This is the same style of Networking as provided by W4WG 3.11 
 PK> operation, HOWEVER it has advantages...;-).  

 RJT> What advantages are those?

 PK> An OS/2 PEER environment can actually access up to 4 different 
 PK> DOMAINS at the same time. To do this requires manual editing of 
 PK> the OS/2 PEER configuration files, but it works fine. I used my 
 PK> Laptop OS/2 Peer environment co-existing in 3 different DOMAINS 
 PK> for some time. WFWG 3.11 cannot exist in more than 1 DOMAIN at 
 PK> the same time. This really does help when doing certain types 
 PK> of work. I think NT can only exist in one DOMAIN at a time too, 
 PK> at least i can't find a way of getting it to exist in more than 
 PK> 1 at a time!

I guess I'm not particularly concerned at this time with multiple domains,
it's more a matter of getting these four machines talking to each other the
way I want them to...

 PK> 3. LAN SERVER LOGON
 PK>         This type of Logon REQUIRES a DOMAIN CONTROLLER to be 
 PK> used. I doubt if you have one of these so this is of no use to 
 PK> you. If you do not have a Primary or Secondary Domain 
 PK> Controller on your LAN, then you CANNOT USE THIS! Basically, 
 PK> your Logon is validated on the DOMAIN controller, the LOCAL 
 PK> user profile is NOT used at all. If the Userid exists on the 
 PK> local machine, then the user may have extra access as defined
 PK> lcoally, but this is NOT required.

 RJT> This sounds to me like something that Samba would deal with on 
 RJT> the Linux box as well,  though I still have some work to do on 
 RJT> that end.

 PK> I dont know SAMBA, but I would not expect it to provide a full 
 PK> DOMAIN PDC environment, there is quite a lot to providing a 
 PK> full PDC Server. As I said before, unless you really need it, 
 PK> dont play with a PDC.

I'm also running 'named' on that box,  a name server of some sort.  And I'm
pursuing a bit of DNS stuff there...

 RJT> But it still doesn't seem to want to see the Linux box for some 
 RJT> reason.  The w95 box shows up in that "Peer Resources" box 
 RJT> okay,  even though it's not turned on at the moment.

 PK> Thats actually quite normal, previously OS/2 Peer had seen the 
 PK> W95 machine and remembered that it existed on the network. You 
 PK> can't browse it (obviously), but if the machine is placed back 
 PK> on the LAN you can go directly to it.

 PK> Browsing an SMB Network exposes the biggest problem with SMB. 
 PK> SMB is a very "chatty" protocol (there are a lot of exchanges 
 PK> between 2 points to complete an information exchange and 
 PK> because it is a broadcast protocol, everyone on the same LAN 
 PK> segment always gets all the messages.

 PK> In your case, the non-visibility of the Linux box is a little 
 PK> puzzelling, however there could be several reasons for this. If 
 PK> ALL machines are using the SAME DOMAIN NAME, then the only 
 PK> thing I can think of is that the Linux box MUST need NETBIOS 
 PK> over TCP/IP as its transport. Dont be fooled by the Windows 
 PK> machine not showing NETBIOS over TCP/IP, I would bet that its 
 PK> probably there, but not obvious. I haven't touched a W95 
 PK> machine myself so I dont know what it looks like in its 
 PK> Networking configuration. I know that on NT its definately in 
 PK> there as a unique protocol...

On the w95 box when you go to "properties" in the network stuff there's a list 
of things,  and both "Netbios" and "TCP/IP" show up in there as separate
protocols.

 PK> Add NETBIOS over TCP/IP to the OS/2 machine and see if that 
 PK> helps...

Did that,  it didn't seem to make any difference.  The one thing I could try
is to give it the number '0' instead of the '1' it's got now,  and remove the
"NetBIOS" (by itself) entry.

 PK> TIP: If when you try and browse the resources on the LINUX box 
 PK> from OS/2 it reports back quickly (within about 5 seconds) and 
 PK> shows <none> as available, then LINUX is saying to OS/2 that 
 PK> the currently logged in User on the OS/2 machine, is not 
 PK> allowed access to anything on the LINUX machine (access is 
 PK> being rejected). If there is a delay of about 15 seconds or 
 PK> more before this message comes back, then the LINUX box is not 
 PK> being found in the same DOMAIN as the OS/2 box. 

It's not seeing that machine at all.  Which is quite puzzling as the domain
settings are the same in all machines,  and the w95 box has no trouble seeing
it.  The OS/2 and w95 boxes can also see each other quite well,  no problems
there.  This is puzzling,  and is probably going to turn out to be something
relatively simple,  once I find it.

 PK> Its actually quite easy to do this, go into the INSTALL of PEER 
 PK> Services and follow through the install process until it finds 
 PK> the existing Database and asks if you want to RESET it. Reply 
 PK> YES and it installs the defaults again.

 RJT> Would that be the "Installation" under "LAN Svcs"?

 PK> Yep...

I may give that a shot -- rip it all out and re-install,  and see if that
doesn't fix the problem.

 PK> Make sure ALL machines have NETBIOS over TCP/IP configured in 
 PK> them. You may also have to set up some broadcast mappings in NB 
 PK> over IP, I dont know if SAMBA needs these or not (I have never 
 PK> used SAMBA).

I'm pretty sure I've got this right.  I can define a share on the Linux box in 
the smb.conf file and have it show up properly on the w95 box,  no problem.
It's only the OS/2 box that has a problem with seeing that system for some
reason.

 RJT> You're not the first one to say this,  but my understanding of 
 RJT> the protocol issues is that you don't need that unless you want 
 RJT> to route NETBIOS stuff across more than one lan segment,  and 
 RJT> that having both NetBIOS and TCP/IP (as separate protocols in 
 RJT> there) should do the trick.

 PK> Generalyl that is true, however over time the useof NB over IP 
 PK> has become very popular because it can solve a lot of problems.

Oh?  What sort of problems?

 PK> I have not used SAMBA so I can't say for sure, however SMB 
 PK> started life as a pure NETBIOS protocol. it could ONLY operate 
 PK> on a local LAN segment, unless you had some way of connecting 
 PK> LAN segments together that transported NETBIOS messages. 
 PK> Because NETBIOS is BROADCAST, and linking LANS over a WAN was 
 PK> very slow, the entire LAN would run at the speed of the slowest 
 PK> WAN connection.

 PK> At this stage the concept of encapsulating the NETBIOS traffic 
 PK> inside a TCP/IP packet was born. This had 2 immediate 
 PK> advantages, TCP/IP is not a Broadcast communications mode it is 
 PK> Point to Point, so a large portion of the NETBIOS traffic over 
 PK> the WAN was eliminated, speeding up LAN operations 
 PK> dramatically.  TCP/IP can be very efficiently routed to 
 PK> wherever it is needed, so traffic was removed from everywhere 
 PK> it was NOT needed, freeing up the local LAN segments. Also 
 PK> included in NB over IP was the ability to locate and store 
 PK> addressing info to help resolve the addressing issues without 
 PK> refering back to the source all the time.

Hmm.

 PK> The one down side to NB over IP is that all this requires extra 
 PK> configuration and can slow down the messaging between the 
 PK> machines that actually do connect over the NB over IP 
 PK> component, but it does work. I connected from my OS/2 Thinkpad 
 PK> in Sydney Australia, to my OS/2 Desktop in Auckland NZ (about 
 PK> 1200 miles away), over a very busy routed Network and used my 
 PK> Desktops Modem to place a local call in Auckland. It worked 
 PK> very well...

That's pretty impressive.

 PK> So much networking involves WAN components these days that it 
 PK> is not unusual to find NETBIOS over TCP/IP in configurations, 
 PK> in fact over 95% of our NETBIOS based machines at work (about 
 PK> 1500) have it installed. I think the default networking 
 PK> configuration for NT installs NB and NB over IP anyway... 

I don't know anything about NT.  And probably won't,  unless I get a chance to 
find out in the course of some employment,  it just strikes me as wanting way
more in the way of resources than I'd feel good about giving it (if I even
_had_ them here!) for what you get.  That's why I'm doing the bit with the
Linux box...

 RJT> am still stuck when I try to get any further results with the 
 RJT> "Sharing and Connecting" part,  particularly the "Create a 
 RJT> Connection" part.  I can enter the machine name of the Linux 
 RJT> box under the "Workstation" field,  at which point it upcases 
 RJT> it (could that be a problem?) 

 PK> No, all SMB resource names are in upper case. 

 RJT> and under the "Share/alias" field it says "<none>".  

 PK> There are 3 things you need to check -

 PK>   1. The NETBIOS MACHINE name you supplied could not be found 
 PK> on the network,

That's a possibility.  Someone in another echo mentioned that I might need an
"lmhosts" file,  so I made one last night.  Haven't tried it yet...

 PK>   2. The NETBIOS MACHINE name could be found on the Network, 
 PK> but the DOMAIN NAME configured on the Server does NOT match the 
 PK> DOMAIN NAME on the OS/2 machine.

I *really* don't think that's it.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   07-Sep-99 13:41:11
  To: Peter Knapper                                     07-Sep-99 19:48:19
Subj: 2 OS/2 networking & Linux

 PK>   3. The NETBIOS MACHINE name could be found on the Network, 
 PK> but the user logged on to the OS/2 machine was not permitted to 
 PK> access ANY resources on that Server.

I don't think that's it either.  But I'll look into it...

 RJT> Trying to enter any of the share names that I'm looking at 
 RJT> in smb.conf on my other screen get me an error message:  
 RJT> "Error 53 occurred.  SYS0053: The network path was not found." 

 PK> Yep, the resource is not visible to OS/2 PEER, for whatever 
 PK> reason. From the commandline enter -
 PK>   NET VIEW
 PK> and report the output. Also try -
 PK>   NET STATUS >zzz
 PK> and report the contents of the zzz file. The output is usually 
 PK> more than 30 lines so I send it to a file.

I'm firing up that box now and will see what that gives me.

 RJT> There's obviously some bits I haven't got quite right,  
 RJT> as I just fired up the w95 box and it can see itself and 
 RJT> both the OS/2 box _and_ the Linux box there. 

 PK> Can the W95 box see AND CONNECT to a SHARE on the OS/2 box?

Yes.  Yesterday I was able to sit there at that w95 machine and click on a
.pdf file on the OS/2 box and view it.

 PK> Can the OS/2 box see AND CONNECT to a SHARE on the W95 box?

Yes again.  In both cases I can see,  and get at files on a different machine.

Trying 'net view',  it asked me to log in first,  and came back with _only_
the OS/2 box showing in the "list" there.  (The w95 box isn't currently on.)

Trying that 'net status' command,  I do have a whole bunch of stuff in there,
but it's still not seeing the Linux box,  just the local machine apparently.

Trying them again after firing up the w95 box gives me exactly the same
results, which is a little odd.  And the w95 box isn't seeing this machine,
which it did yesterday.  I wonder if the order of powering things up makes a
difference here? Trying a restart shows this to apparently be the case,  as I
can now see the OS/2 box from the w95 box,  net view shows both machines where 
it didn't before. Net status stil doesn't show me anything other than what it
did,  though -- shares on the OS/2 machine which are available to the w95 box, 
but not the other way around.  Yet doing a "dir f:" at a command prompt shows
me a directory of the HD on the w95 box.

I'm still confused...!

(Added later)

I just for the heck of it ran through the install process,  not really
changing anything but saying "Yes" when it asked me if I wanted to delete and
re-create the NET.ACC file,  and now the 'net view' command shows me all three 
machines!  The linux box is showing up in there with "Samba server" in the
Remark column.

I can also see stuff in there in the "Sharing and Connecting" function that
wasn't visible before,  including creating shares that access resources on the 
LInux box.

I don't understand this...

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: LEE ARONER                                        07-Sep-99 03:36:00
  To: PETER KNAPPER                                     08-Sep-99 13:19:02
Subj: OS/2 networking & Linux

PK> Hi Roy,

 RJT> I'm trying to get Samba configured properly on the 
 RJT> Linux box here,  and am a bit confused about the OS/2 
 RJT> side of things.  Which of the products in the Warp 
 RJT> Connect stuff is what's needed to be able to map 
 RJT> resources on other machines and similar stuff?

PK> SAMBA (for *nix) is the equivalent of PEER SERVICES (for OS/2). PEER
Services
  > consists of both the SERVER and CLIENT code. You need PEER SERVICES
running to
  > be able to connect an OS/2 CLIENT to resources served from a SAMBA Server.

PK> One point to watch out for is that the PEER SERVICES machines is
configured in
  > the SAME DOMAIN (or WORKGROUP) as the SAMBA machine. If they are in
different
  > DOMAINS, then they will not be able to see each other... Then you need to
  > consider the User profiles you are going to login in with...


   Peter, a genuine question, since I've not tried it, but wouldn't 
   the Warp box be able to see a Samba server on a different domain 
   using the OTHDOMAINS parameter in IBMLAN.INI?


                                       LRA


 -- SPEED 2.01 #2720: DD> (A)bort (R)etry (P)retend this never happened
--- Platinum Xpress/Win/Wildcat5! v2.0
 * Origin: Memory Alpha - (253) 859-6200 (1:343/311)
3613/666

+----------------------------------------------------------------------------+

From: LEE ARONER                                        07-Sep-99 03:45:00
  To: ROY J. TELLASON                                   08-Sep-99 13:19:02
Subj: OS/2 networking & Linux

RJT> David Calafrancesco wrote in a message to Roy J. Tellason:

 DC> Roy J. Tellason wrote in a message to all:

 RJT> I'm trying to get Samba configured properly on the Linux box
 RJT> here,  and am a bit confused about the OS/2 side of things. 
 RJT> Which of the products in the Warp Connect stuff is what's
 RJT> needed to be able to map resources on other machines and
 RJT> similar stuff?

 DC> File and print sharing using NetBios over TCPIP. 

RJT> I've got both TCP/IP and NetBIOS configured as protocols,  and had
thought that
   > you didn't need NetBIOS _over_ TCP/IP if stuff didn't need to be routed
to
   > other lan segments.  No?

   You do for Samba. It *only* talks NB/IP or straight IP, it does 
   not do plain NetBios.

RJT> In the network stuff is "Peer logon",  "Lan server logon",  and some
other
   > stuff.  That's where the confusion is.  I think I need to look at the
   > username/password issue,  too.


   Don't forget that both boxes need to be in the same domain. 
   Possibly, you could use the OTHDOMAINS param in IBMLAN.INI, but I 
   don't know if that will actually work or not...


                                               LRA


 -- SPEED 2.01 #2720: Alzheimers advantage: New friends every day
--- Platinum Xpress/Win/Wildcat5! v2.0
 * Origin: Memory Alpha - (253) 859-6200 (1:343/311)
3613/666

+----------------------------------------------------------------------------+

From: Peter Knapper                                     08-Sep-99 19:54:24
  To: Roy J. Tellason                                   08-Sep-99 13:19:02
Subj: OS/2 networking & Linux

Hi Roy,

 RJT> I'm also running 'named' on that box,  a name server 
 RJT> of some sort.  And I'm pursuing a bit of DNS stuff 
 RJT> there...

"named" is an OS/2 port of the unix Domain Name Server and a DNS normally has
no relationship to a NETBIOS environment (but it is actually posible to use a
DNS to help NETBIOS clients to find resources). I havent' had to do that
myself though...

Cheers.........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     08-Sep-99 19:56:18
  To: Roy J. Tellason                                   08-Sep-99 13:19:02
Subj: 2 OS/2 networking & Linux

Hi Roy,

 RJT> (Added later)

 RJT> I just for the heck of it ran through the install 
 RJT> process,  not really changing anything but saying 
 RJT> "Yes" when it asked me if I wanted to delete and re-
 RJT> create the NET.ACC file,  and now the 'net view' 
 RJT> command shows me all three machines!  The linux box is 
 RJT> showing up in there with "Samba server" in the Remark 
 RJT> column.

 RJT> I can also see stuff in there in the "Sharing and 
 RJT> Connecting" function that wasn't visible before,  
 RJT> including creating shares that access resources on the 
 RJT> LInux box.

Great news! I remember that you said there were problems with the original
install of MPTS/PEER and at boot up the MPTS configuration failed to start up
correctly, so I suspect that something in the MPTS/PEER area got clobbered
with the playing around. Re-doing the install sorted out the parts that had
been "bent" enough to make it all work (as it should do)...

Cheers.........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   08-Sep-99 12:41:09
  To: Peter Knapper                                     08-Sep-99 18:44:20
Subj: 2 OS/2 networking & Linux

Peter Knapper wrote in a message to Roy J. Tellason:

 RJT> (Added later)

 RJT> I just for the heck of it ran through the install process,  not 
 RJT> really changing anything but saying "Yes" when it asked me if I 
 RJT> wanted to delete and re-create the NET.ACC file,  and now the 
 RJT> 'net view' command shows me all three machines!  The linux box 
 RJT> is showing up in there with "Samba server" in the Remark column.

 RJT> I can also see stuff in there in the "Sharing and Connecting" 
 RJT> function that wasn't visible before,  including creating shares 
 RJT> that access resources on the LInux box.

 PK> Great news! I remember that you said there were problems with 
 PK> the original install of MPTS/PEER and at boot up the MPTS 
 PK> configuration failed to start up correctly, so I suspect that 
 PK> something in the MPTS/PEER area got clobbered with the playing 
 PK> around. Re-doing the install sorted out the parts that had been 
 PK> "bent" enough to make it all work (as it should do)...

I don't know,  there were some odd bits in the install process back then,  but 
that was a while ago and I'm a little fuzzy now as to just what it was, 
unless I dig into my notes...

And I didn't touch anything this time around relating to the MPTS stuff, 
except for adding that protocol.  Put it on "adapter number 1",  too,  rather
than "0" which is where the software initially stuck it.  I don't remember why 
this was important,  only that it had come up somewhere in these discussions
in the past.

Now I need to get the necessary shares set up on the Linux box and get going
with this,  but I think I probably won't have too much trouble with that, 
since I've got some working ones in there now.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   08-Sep-99 12:38:14
  To: LEE ARONER                                        08-Sep-99 18:44:20
Subj: OS/2 networking & Linux

LEE ARONER wrote in a message to ROY J. TELLASON:

RJT> I've got both TCP/IP and NetBIOS configured as protocols,  and had
RJT> thought that you didn't need NetBIOS _over_ TCP/IP if stuff 
RJT> didn't need to be routed to other lan segments.  No?

 LA>    You do for Samba. It *only* talks NB/IP or straight IP, it 
 LA> does not do plain NetBios.

Funny,  I don't see any mention of that in any of the stuff I've been reading
lately...

In any case,  it's working now.  I'm not sure what it was that did it,  but
the final step was re-running "install" and that seemed to get me going here.

RJT> In the network stuff is "Peer logon",  "Lan server logon",  and some
RJT> other stuff.  That's where the confusion is.  I think I need to 
RJT> look at the username/password issue,  too.

 LA>    Don't forget that both boxes need to be in the same domain.

Yeah,  I've been on top of that one all along.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   08-Sep-99 12:40:05
  To: Peter Knapper                                     08-Sep-99 18:44:20
Subj: OS/2 networking & Linux

Peter Knapper wrote in a message to Roy J. Tellason:

 PK> Hi Roy,

 RJT> I'm also running 'named' on that box,  a name server of some 
 RJT> sort.  And I'm pursuing a bit of DNS stuff there...

 PK> "named" is an OS/2 port of the unix Domain Name Server and a 
 PK> DNS normally has no relationship to a NETBIOS environment (but 
 PK> it is actually posible to use a DNS to help NETBIOS clients to 
 PK> find resources). I havent' had to do that myself though...

Point of confusion,  there (possibly poor phrasing on my part?) -- "that box"
and "there" in the quoted stuff refers to the Linux box,  not the OS/2 box...

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Steve Proctor                                     08-Sep-99 18:46:28
  To: All                                               08-Sep-99 18:46:28
Subj: OS/2 & Unix

My FTP server is on my Linux Machine.  I would like ftp users to be able to
access the file directories (on my BBS) thats on my OS/2 Machine.  Is this
possible or am I gonna need IBM's expensive NFS to do this.  I assume SAMBA is 
the other way around, OS/2 to Linux and not Linux to OS/2.

Thanks,
Steve Proctor
sproctor@microline.org


--- Maximus/2 2.02
 * Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)


+----------------------------------------------------------------------------+

From: Johan Zwiekhorst                                  06-Sep-99 23:24:18
  To: Kenneth Duke                                      09-Sep-99 00:20:11
Subj: A OS/2 machine to linux box

Hi Kenneth!

In your message to All, dated <Sunday September 05 1999 08:43>, you wrote:

 >KD: everything runs fine. However, on the OS/2 box, it won't run any
 >KD: Internet app... I can however PING the outside world with the OS/2
 >KD: box.

This sounds like you're trying the modem versions of those Internet apps (with 
LINKUP) instead of the LAN versions like you should...

 ._|~/_

e-mail: johanzw@iname.com           (home)
        johan@datatestlab.com       (office)
web:    http://surf.to/tripod       (personal)
        http://www.datatestlab.com  (Data TestLab)
--- Maximus-CBCS v3.01
 * Origin: Tripod BBS Belgium - bortaS bIr jablu'DI'reH QaQqu' nay'
(2:292/100)
278/111
724/10

+----------------------------------------------------------------------------+

From: Kenneth Duke                                      09-Sep-99 07:22:03
  To: Johan Zwiekhorst                                  09-Sep-99 11:25:15
Subj: Re: A OS/2 machine to linux box

*** Quoting Johan Zwiekhorst from a message to Kenneth Duke ***

JZ> This sounds like you're trying the modem versions of those Internet 
JZ> apps (with LINKUP) instead of the LAN versions like you should...

Nope... Netscape, and the command line "ftp" will not resolve a host..

I did find that if I typed in the IP address, I could get threw... So, its a
nameserver issue...


--- Telegard/2 v3.09.g2-sp3/mL
 * Origin: telnet://pcnashville.dhs.org (1:116/158)

+----------------------------------------------------------------------------+

From: Kari Suomela                                      09-Sep-99 10:13:09
  To: Steve Proctor                                     09-Sep-99 13:18:03
Subj: OS/2 & Unix

Wednesday September 08 1999 18:46, Steve Proctor wrote to All:

 SP> My FTP server is on my Linux Machine.  I would like ftp users to be
 SP> able to access the file directories (on my BBS) thats on my OS/2
 SP> Machine.  Is this possible or am I gonna need IBM's expensive NFS to

I have my file directories on the Linux machine, shared with SAMBA, and
controlled by the OS/2 software.

 KS



 * Origin:  *  telnet://bbs.karicobs.com * (1:2424/101)
278/111
724/10

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   09-Sep-99 16:26:18
  To: Kari Suomela                                      09-Sep-99 21:36:10
Subj: OS/2 & Unix

Kari Suomela wrote in a message to Steve Proctor:

 KS> Wednesday September 08 1999 18:46, Steve Proctor wrote to All: 

 SP> My FTP server is on my Linux Machine.  I would like ftp users to be
 SP> able to access the file directories (on my BBS) thats on my OS/2
 SP> Machine.  Is this possible or am I gonna need IBM's expensive NFS to

 KS> I have my file directories on the Linux machine, shared with 
 KS> SAMBA, and controlled by the OS/2 software.

This is exactly the sort of thing I'm trying to get happening here,  only I
keep bumping into various gotchas...

Care to share the details of your setup?  In particular,  I'd be interersted
in what sort of shares you have in smb.conf,  and in how you have permissions
set up,  since that's what appears to be where I'm having a bit of a problem
now...

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     09-Sep-99 19:42:00
  To: Lee Aroner                                        10-Sep-99 00:21:24
Subj: OS/2 networking & Linux

Hi Lee,

PK> One point to watch out for is that the PEER 
  > SERVICES machines is configured in
  > the SAME DOMAIN (or WORKGROUP) as the SAMBA 
  > machine. If they are in different
  > DOMAINS, then they will not be able to see each 
  > other... Then you need to
  > consider the User profiles you are going to login in with...

 LA>    Peter, a genuine question, since I've not tried it, but wouldn't 
 LA>    the Warp box be able to see a Samba server on a different domain 
 LA>    using the OTHDOMAINS parameter in IBMLAN.INI?

Yes, thats how you can set up for multi-DOMAIN operation of an OS/2 PEER
Client. I left that bit out of the discussion with Roy because it requires
manual editing of the OS/2 PEER configuration files to set that up and he
didn't need that functionality. 

Setting up for Multiple Domain presence is not possible using the supplied
configuraion utilities, it requires manual editing of the appropriate
configuration files, however it can be as simple as adding the paramaters as
you suggest, or it can get rather complicated, especially if you need to
useForwarded authentication for one of those Domains... This level of setup
really requires a very full understanding of what is invovled and considerably 
more documentation than is provided with OS/2.

Cheers........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Peter Knapper                                     09-Sep-99 19:15:11
  To: Roy J. Tellason                                   10-Sep-99 00:21:24
Subj: 2 OS/2 networking & Linux

Hi Roy,

 RJT> And I didn't touch anything this time around relating 
 RJT> to the MPTS stuff,  except for adding that protocol.  
 RJT> Put it on "adapter number 1",  too,  rather than "0" 
 RJT> which is where the software initially stuck it.  I 
 RJT> don't remember why this was important,  only that it 
 RJT> had come up somewhere in these discussions in the past.

If you load a protocol more than once against a Network Card, the second
config MUST use a different "Logical Adapter Number" (I will use the term
LEVEL for this value from here on), the SAME protocol cannot exist more than
ONCE at the same LEVEL. In this case, the 2 NETBIOS protocols

  0 IBM OS/2 NETBIOS
  1 IBM OS/2 NETBIOS OVER TCP/IP

means that one of them MUST run at a different LEVEL to the other. The actual
protocol titles are NETBEUI and TCPBEUI, but they are both NETBIOS protocols.
If you have both the above configured against a card, then look at your
\IBMLAN\IBMLAN.INI file and you will see the 2 protocols configured in the
[Networks] section as net1 and net2.

As an aside to this, what this really means is that it is POSSIBLE to load IBM 
OS/2 TCP/IP against a network card twice, but using different LEVEL numbers.
You could then configure different TCP/IP address ranges on the same card, 1
for each TCP/IP PROTOCOL driver loaded. The bottom line is that you could then 
have 1 OS/2 PC appearing in 2 distinct TCP/IP Networks on the same LAN
segment. You could then use this to install a Firewall on the OS/2 box between 
those segments without having a seperate physical LAN in place, however the
benefits of doing this are moot considerng the low cost of Ethernet cards
these days...

Cheers.......pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   09-Sep-99 22:49:10
  To: Peter Knapper                                     10-Sep-99 08:22:05
Subj: 2 OS/2 networking & Linux

Peter Knapper wrote in a message to Roy J. Tellason:

 PK> As an aside to this, what this really means is that it is 
 PK> POSSIBLE to load IBM OS/2 TCP/IP against a network card twice, 
 PK> but using different LEVEL numbers. You could then configure 
 PK> different TCP/IP address ranges on the same card, 1 for each 
 PK> TCP/IP PROTOCOL driver loaded. The bottom line is that you 
 PK> could then have 1 OS/2 PC appearing in 2 distinct TCP/IP 
 PK> Networks on the same LAN segment. 

Nifty...

 PK> You could then use this to install a Firewall on the OS/2 box 
 PK> between those segments without having a seperate physical LAN 
 PK> in place, however the benefits of doing this are moot 
 PK> considerng the low cost of Ethernet cards these days... 

Yeah.  I didn't know that there was firewall software available for OS/2.  It
seems to be something do-able easily enough (he says,  not having tried to do
it yet :-) under Linux...

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   09-Sep-99 22:51:08
  To: Peter Knapper                                     10-Sep-99 08:22:05
Subj: OS/2 networking & Linux

Peter Knapper wrote in a message to Lee Aroner:

 PK> Setting up for Multiple Domain presence is not possible using 
 PK> the supplied configuraion utilities, it requires manual editing 
 PK> of the appropriate configuration files, however it can be as 
 PK> simple as adding the paramaters as you suggest, or it can get 
 PK> rather complicated, especially if you need to useForwarded 
 PK> authentication for one of those Domains... This level of setup 
 PK> really requires a very full understanding of what is invovled 
 PK> and considerably more documentation than is provided with OS/2.

While you're right about me not needing to mess with more than one domain (I'm 
having enough trouble with just one :-),  perhaps this would be a workable
approach to dealing with some of the stuff I'm running into at this point. 
It's the configuration utilities,  as you say,  that are giving me a hard
time.

Basically I got a fair amount of functionality at this point.  But I can't
seem to be able to get some things working.  I couldn't write to one of the
shares,  turned out I had to fiddle with permissions on the Linux box.

I ended up moving a whole mess of the bbs files over there,  and can't get the 
share that I stuck in smb.conf to let me hook into those files from the OS/2
end of things.  The "sharing and connecting" utility will,  when I tell it I
want to "create a new share",  show me that machine and the shares that I have 
defined,  as well as a bunch of otherwise unused drive letters.  But it
complains when I select the new one and an unused letter,  complaining that it 
can't find the resource,  or something to that effect.  I did do help on that
particular error,  but can't recall what it was offhand.  SYS???? something or 
other...

Would perhaps manually editing the configs be a way past this?  What files are 
we talking about here,  and where are they generally located?

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

From: Steve Proctor                                     09-Sep-99 22:40:01
  To: Kari Suomela                                      10-Sep-99 08:22:05
Subj: OS/2 & Unix

Kari Suomela wrote in a message to Steve Proctor:

Yes, but I want to do it the other way around :)  Want the Unix Machine (that
folks FTP into) to be able to access the drives on the OS/2 machine!

 KS> Wednesday September 08 1999 18:46, Steve Proctor wrote to All: 

 SP> My FTP server is on my Linux Machine.  I would like ftp users to be
 SP> able to access the file directories (on my BBS) thats on my OS/2
 SP> Machine.  Is this possible or am I gonna need IBM's expensive NFS to

 KS> I have my file directories on the Linux machine, shared with SAMBA,
 KS> and controlled by the OS/2 software.

 KS>  KS

Steve Proctor
sproctor@microline.org 

---
 * Origin: Microline Online Services - Sacramento, Ca USA (1:203/529)
3613/666

+----------------------------------------------------------------------------+

From: Peter Knapper                                     10-Sep-99 23:37:04
  To: Roy J. Tellason                                   10-Sep-99 13:22:24
Subj: OS/2 networking & Linux

Hi Roy,

 RJT> I ended up moving a whole mess of the bbs files over there,  and can't 
 RJT> get the share that I stuck in smb.conf to let me hook 
 RJT> into those files from the OS/2 end of things.  The 
 RJT> "sharing and connecting" utility will,  when I tell it 
 RJT> I want to "create a new share",  show me that machine 
 RJT> and the shares that I have defined,  as well as a 
 RJT> bunch of otherwise unused drive letters.  But it 
 RJT> complains when I select the new one and an unused 
 RJT> letter,  complaining that it can't find the resource,  
 RJT> or something to that effect.

From what you have described it sounds like your problems relate almost
totally to permissions on the Linux box. I dont know much about SAMBA but I
would start looking at how SMB Client permissions (OS/2 Peer, W95, etc) are
mapped into the Linux permissions. 

 RJT> Would perhaps manually editing the configs be a way past this?  

As far as OS/2 Peer is concerned, absolutely not! The Files in question allow
you to resolve operational Networking issues that relate to communications
parameters, not User access parameters. All your problems sound almost 100%
like permissions on the Server platform.

I have NEVER needed to manually edit any OS/2 Peer configuration file other
than to configure an OS/2 Client to exist in multiple DOMAINS at the same
time, and thats about the easiest change I can think of. All permission
problems I ran into have been resolved by altering the OS/2 Peer User profile
on the SMB Server that presented the error. With PEER, the SERVER is just
about the only component that determines what resources a Client can access.

If you want to manually edit the MPTS/SMB control files then you FIRST need to 
pick up the EXTENSIVE documentation from an IBM Web site, otherwise you will
never know what each of the bit values does. NONE of this is documented with
OPS/2 Peer, you need access to the developers areas to find out what allthe
values are for.

My advise is DONT play with these, from the sounds of it none of your current
problems will be solved by fiddling in this area. You will end up having to
re-install OS/2 Peer just to get things working again.

Cheers........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)

+----------------------------------------------------------------------------+

From: Roy J. Tellason                                   10-Sep-99 16:05:03
  To: Peter Knapper                                     10-Sep-99 21:25:26
Subj: OS/2 networking & Linux

Peter Knapper wrote in a message to Roy J. Tellason:

 RJT> I ended up moving a whole mess of the bbs files over there,  and can't 
 RJT> get the share that I stuck in smb.conf to let me hook into 
 RJT> those files from the OS/2 end of things.  The "sharing and 
 RJT> connecting" utility will,  when I tell it I want to "create a 
 RJT> new share",  show me that machine and the shares that I have 
 RJT> defined,  as well as a bunch of otherwise unused drive letters. 
 RJT> But it complains when I select the new one and an unused 
 RJT> letter,  complaining that it can't find the resource,  or 
 RJT> something to that effect.

 PK> From what you have described it sounds like your problems 
 PK> relate almost totally to permissions on the Linux box. I dont 
 PK> know much about SAMBA but I would start looking at how SMB 
 PK> Client permissions (OS/2 Peer, W95, etc) are mapped into the 
 PK> Linux permissions.

I suspect that you're right about this.  I had occasion to fire up the w95 box 
today for a bit of work,  and when I went to look at what shares were in
_there_,  it was the same deal -- it could see that new one I'd added ("bbs")
but when I tried to access it I got essentially the same error.

 RJT> Would perhaps manually editing the configs be a way past this?  

 PK> As far as OS/2 Peer is concerned, absolutely not! The Files in 
 PK> question allow you to resolve operational Networking issues 
 PK> that relate to communications parameters, not User access 
 PK> parameters. All your problems sound almost 100% like 
 PK> permissions on the Server platform.

Ok.

 PK> I have NEVER needed to manually edit any OS/2 Peer 
 PK> configuration file other than to configure an OS/2 Client to 
 PK> exist in multiple DOMAINS at the same time, and thats about the 
 PK> easiest change I can think of. All permission problems I ran 
 PK> into have been resolved by altering the OS/2 Peer User profile 
 PK> on the SMB Server that presented the error. With PEER, the 
 PK> SERVER is just about the only component that determines what 
 PK> resources a Client can access.

Noted.

 PK> If you want to manually edit the MPTS/SMB control files then 
 PK> you FIRST need to pick up the EXTENSIVE documentation from an 
 PK> IBM Web site, otherwise you will never know what each of the 
 PK> bit values does. NONE of this is documented with OPS/2 Peer, 
 PK> you need access to the developers areas to find out what allthe 
 PK> values are for.

 PK> My advise is DONT play with these, from the sounds of it none 
 PK> of your current problems will be solved by fiddling in this 
 PK> area. You will end up having to re-install OS/2 Peer just to 
 PK> get things working again.

Ok...

Speaking of (re?) installing Peer,  I had fiddled with my resume on the w95
box a bit today,  and wanted to fax it out.  No fax on the w95 machine,  so I
thought about the fact that I had faxworks installed on _this_ box,  in the
OS/2 partition.  Rebooted into that,  and found that I didn't have Peer
installed there,  just the TCP/IP stuff!  And I don't have Faxworks installed
on the OS/2 box which _does_ have Peer installed.  AND,  I can't figure out
which box of many the package is in so I can fix that,  either installing peer 
on this box or faxworks on the other one.  Oh well...!  (Did the floppy
shuffle routine again... :-)

I guess I better study that Samba stuff and see what I can figure out on that
end.

--- 
 * Origin: TANSTAAFL BBS 717-838-8539 (1:270/615)

+----------------------------------------------------------------------------+

+============================================================================+
