File locking Problem with Novell NLM & Winframe 1.x (OpenInsight Specific)
At 09 DEC 1998 02:02:18PM Richard Seemangal wrote:
This now seems to be a classic problem so someone must have the solution.
The problem
Is that the Winframe users do not connect using the NetWare NLM, preventing correct record locking.
Extended: Win95 Clients login on Novell lock successfully and an MS NT Workstation 4.0 login onto Novell locks successfully with the Win95 clients.
Winframe Locks it?s own client?s records.
But both systems accessed the locked records of the other system.
The Configuration:
The details are:
OI for Workgroups, v 3.61
NetWare 4.11 server, using Revelation NLM
OI network driver: IPX v1.14 vxd.
Local clients: Win95 Novell 32 bit clients
Winframe 1.7 (SP5 installed) Server Notes:
Winframe NT 3.51, using IPX protocol Winframe Server using IPX/SPX transport protocol. Loaded with Novell 32bit client to access Novell 4.11 server. OI accessed via Mapped network drive.
If we add a REVPARAM file to the revelation data directories, with the setting:
SERVERONLY=TRUE, the Winframe clients cannot log in, proving they are not connecting to the NLM On the Winframe server:
This I believe is our main problem getting Winframe to access OI via the NLM.
We also have the MS NT Workstation 4.0 login onto the Novell server using Novell 32bit client. It files lock in line with all the Win95 clients, so I must conclude it is using the NLM.
OINSIGHT.INI in the WINDOWS directory.
In the users Director under Default home Dir. and registered WinFrame users directories the following files can be located
OI DLLs in the \\winframe\users\Default\WINDOWS\SYSTEM directory
NETWARE.DRV and VIPX.386 in the \\winframe\users\Default\WINDOWS\SYSTEM directory
NT NetWare Gateway not implemented.
Winframe Load Balancing is not implemented
The volume is formatted with NTFS
The Winframe box is configured as a server, and not as a primary or backup domain controller.
Performance is very good.
Question:
How do I make Winframe use the NLM?
What are the steps involved insetting up a NT workstation to access
OI.
Richard Seemangal
rseemangal@cwcom.net
Transputec Computer Plc.
At 16 DEC 1998 11:09AM Cameron Revelation wrote:
Hi Richard,
We have several customers that use WinFrame with the NLM. I do not know too many specifics, but here is some information:
1) Client32 from Novell does not install on WinFrame because WinFrame is based on the "NT Server" and Client32 refuses to install on "NT Server". Client32 works better on NT with the NLM than the MS Client for Netware. (So is there a way to install Client32?)
2) The VxD implementation of the LH/IPX driver should be used on Citrix. The latest LH/IPX drivers default to this, but if you have an older version (before 1.5), you need to use the LH/IPX 1.14/VxD driver.
Cameron Purdy
Revelation Software
At 19 DEC 1998 09:29AM Richard Seemangal wrote:
I have done all that I can do. Everything checks out okay.
I'm now going for one last possiblity, that is the installation files are faulty, so I'm going for a re-load of as much of the Winframe as I can.
Please continue with any ideas.