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