Text 71, 90 rader
Skriven 2005-05-17 20:28:02 av Peter Knapper (3:772/1.10)
     Kommentar till text 69 av Mike Luther (1:117/3001.0)
Ärende: Logged on Peer chucks access!
=====================================
Hi Mike,

 ML> None of the boxes in question are set to SHARE anything.  Their only mode 
 ML> of use is in CONNECTIONS mode, OK?  

Perhaps OK, perhaps not........;-) Lets call this the CLIENT box and the other
one the SERVER box.

What is in your Config.Sys file as far as the following 2 lines are concerned -

  SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,WARPCENTER
  SET RestartObjects=StartupFoldersonly,RebootOnly

These 2 lines are the ones that I use on ALL my boxes here. 

Also, WHERE and HOW is "OS/2 Peer Services" started on this box? 

 ML> Two took off and 
 ML> work just fine after just changing the COMPUTER NAME 
 ML> with QEDIT for OS/2 as a pure text file and no changes 
 ML> in the length of the COMPUTER NAME.  

Was "OS/2 Peer Services" running at the time you edited the IBMLAN.INI file? By
this I mean "OS/2 Peer Services" to include the following services -
        REQUESTER
        MESSENGER
        PEER
        REPLICATOR
        and any other possible services?
To find out what is currently runnning for OS/2 Peer Services use the comand -
  NET START
with _NO_ 3rd parameter! Without that it just lists the currently active
services.

 ML> Two fail now as follows.  One is a FP17 box, latest and greatest 
 ML> everything official as to FP's - MPTS, PEER, TCP 4.3 
 ML> and so on.  

TCP 4.3 has no involvement with "Peer Services" unless you are using TCPBEUI or
NETBIOS over TCP/IP, and even then thats part of MPTS, not OS/2 Peer Services.

 ML>   1.) Boot the box.
 ML>   2.) Log-on to the PEER LAN.

BEFORE you log onto the LAN, what starts "Peer Services" on EACH box?

 ML>   3.) Box immediately connects to the only SHARED box on the PEER LAN.

What do you mean by "Connects to"? I guess you mean that the moment you log
into the machine, a CONNECTION is re-established to a SHARE on another HOST? If
so, then that CONNECTION was BUILT under the access present at the time of that
particular logged in user, AND was marked as permanent, and therefore the
CONNECTION setup is "Owned" by that user.

 ML>   6.) The instant that anything tries to ACCESS any CONNECTION file
 ML>       that is shown there and a DIR will also show..

 ML>       POOF!

Are you ABSOLUTELY SURE that the currently Logged in User on the CLIENT box has
PERMISSIONS on the SERVER box to access the resource that is SHARED on the
SERVER? WHO owns the SHARED resource?

 ML>       Total PEER connection is lost.  Nothing, including File Freedom
 ML>       can even access that CONNECTION object any longer in any way.

This sounds like a classic permissions issue. IE the PERMISSIONS being
different between the Client and Server boxes as far as the Logged in User on
the Client, at the time the CONNECTION was originally built. This could easily
happen in a CLONED environment!

 ML> Nothing short of a complete reboot can get you 
 ML> connected again.  Not even a manual NET STOP REQUESTER, 
 ML> followed by a NET START PEER and try again will even 
 ML> work!  The setup parameters for the PEER LAN shared box 
 ML> indicate that there isn't a total machine connection 
 ML> complexion probem here.  Until you try to actually 
 ML> access a file on the shared connection target drive and 
 ML> partition, you can see all the directory, the whole 
 ML> thing, even into the subdirectories at will.

Again a Classic permissions issue. I know most people don't consider OS/2 as
having fantastic user authentication for Peer Services but it really does work
quite well, and is sufficient to trip many people up. 

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


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