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...     

 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.  

 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 "".  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.

---