🚀 go-pugleaf

LAN: NetWare 3.12 installed a compiled dBase4 client/server program 
     (server part)
     
     NT 3.51 running Citrix WinFrame Access version 
     (A program like pcAnywhere, but much better and is one-to-many)
     w/ dBase4 client part 
 
Remote: DOS client running WinFrame client (only screen update like 
        pcAnywhere)

Sympton: When a dial-up connection between NT and DOS client loses and then
	 reconnect, NetWare gives a different connection no.
         However, when the connection loses, WinFrame still keeps the 
         original session (we cannot kill it or it may result in file crash)
         but Novell frees all file locking. 
	 When user reconnects, he is connected to original session with
	 a new connection no. This results in "No file locking and no
	 transaction locking" which means User A can edit a record
	 currently edited by User B when User A reconnects a lost session.

Problem: The only way to solve it as far as I know is to tell the user 
         reconnects again and logout the lost session gracefully and 
         reconnects the system again. But if the user doesn't follow, 
         transaction will be non-atomic and is extremely hazard.

Solution: So, is it a bug of NetWare 3.12 + NT 3.51?
          Any solution?
	  How about NetWare Connect? Can it resume the original 
          connection no?

--
Rgds,
IMAGM