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.

---