RE: Connect Peer & DLS
BY: Rich Wonneberger to Mack Nethkin on Wed Nov 20 1996 09:33:04
 > *** Quoting Mack Nethkin to Andrew Grillet dated 11-14-96 ***
 > >    uhm, OS/2 really doesn't like the same guy logged in from mulitple
 > >    machines.  Network messaging will fail to work, and it'll let you
 > > know it
 > >    too.  Think about it.  On a LAN, Mack is logged onto machine 1, and
 > >    Mack is logged onto machine 2, how could I address a msg to send to
 > > Mack?
 > >    That's me!  What if I had Mack logged on 3 machines, which 'Mack'
 > > did
 > >    I really want my msg going to?  OS/2 get's confused, so it just
 > > shuts
 > >    down the network messaging... True, that's probably not a big deal
 > 
 > Mack,
 > Not doubting what you say, but have you actually seen this happen??
   It really happens. Happened to me.
 > I would think its a bug, as Novell & Lantastic do allow multiple login..
 > If I was log'd in at several stations (which was normal) & a message was 
sen
 > to me, I had to clear it at all the stations..
   It's not a bug... it's simply the difference between Peer to Peer, and
   Client/Server with a PDC.
 > I would be supprised if OS/2 network couldnt handle this..
   OS/2 handle's it just fine with a PDC on the LAN. As it should be.
 > Could you (or anyone) point me to something in the docks showing this or a 
w
 > around??
 > If I was at my last job, I couldnt be limited to login in to just 1 
w-statio
 >  Had to many things running at once..   :}
   Who runs Peer to Peer in their office, especially with so many
   workstations as to end up with multiple logins?
   If you think about it, logically it makes sense.  In Peer to Peer, each
   machine controls it's own user access, has it's own user databases', and
   therefore, Mack on WKS1 does not have to be the same Mack who's on WKS2.
   OS/2 realizes this, and lets you know of the situation, and shuts
   network messaging down since it realizes that it won't know who's who
   and doesn't really want to go broadcasting msgs to someone who the msg
   may not be intended for.
   When you've got a Primay Domain Controller on your Lan, it is the SOLE
   access for the user database. ALL accounts are stored on the PDC.  ALL
   workstations must access the PDC to find out if the user requesting 
   access is allowed, and if so, what is he (or she) allowed access to.
   In english... When Mack logs on WKS1, it checks the PDC (Server) for my
   account, find it, lets me log on, and grants me applicable access.  I 
   then go to WKS2 and log on, it ALSO checks the PDC for my acces, and 
   low and behold, it notes that I'm now logged on WKS1 and WKS2, but MACK
   is the SAME Mack on both machines.. hence, network messaging works fine,
   and is broadcast to both machines.
   No bug, just the way things works.
    -- Mack
--- TRWMail v3
---------------