Urgent Gateway Services for NetWare (nlm or NT Service) (AREV Specific)
At 10 DEC 1998 04:01:27AM Q Bower wrote:
I am implementing a NW4.11 server (as a resource server) into an NT 4.0 Domain. I have installed the Gateway Services for NetWare on the NT 4.0 Sp3 Server as well as File and Printer services for NetWare.
The arev application resides on the NW Server.
Scenario
1. nt 4.0 client authenticates with nt 4.0 server. The nt 4.0 server has a mapped drive to the arev volume and reshares the resource. The client then has a mapped drive to the resource.
I now have a problem:
I have the NLM on the NW Server and the Advanced Network Driver loaded. I find that I can not obtain record locking.
I am fortunate enough to have the NT Service, so if I unload the NLM and start the NT Service and bump to the All Network Driver, I am still unable to obtain record locking.
The only soloution that I have found to obtain record locking is to load the NLM and use the All network driver 1.5. A mixture of the two to obtain record locking. However, once you access an already open record you can not exit the application until the first record that has been locked is released.
If any one out there can provide a soloution to this mixed environment set up I would be appreciative.
All the Best
QB
At 15 DEC 1998 05:16AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura, Inc.[/url] wrote:
First off, try doing everything from a COMMAND.COM prompt, not a CMD.EXE prompt. Second, load up Novell's client and access tools, not Microsofts, on both the workstations and the server. Go to the COMMAND.COM prompt and go to the ARev directory. Load LHIPXTSR with the /p option and start ARev.
If this does not work, try loading a COMMAND.COM session and MAPping to the Novell server drive.
At 15 DEC 1998 02:19PM Serguei Poliakov wrote:
Q Bower wrote:
]I am implementing a NW4.11 server (as a resource server) into an NT 4.0 Domain. I have installed the Gateway ]Services for NetWare on the NT 4.0 Sp3 Server as well as File and Printer services for NetWare.
]The arev application resides on the NW Server.
]Scenario
]1. nt 4.0 client authenticates with nt 4.0 server. The nt 4.0 server has a mapped drive to the arev volume and ]reshares the resource. The client then has a mapped drive to the resource.
]I have the NLM on the NW Server and the Advanced Network Driver loaded. I find that I can not obtain record ]locking.
As far as I know this can?t work.
NT client knows nothing about NetWare server. It thinks that the mapped drive belongs to NT. It works fine while you don?t use NLM. The idea of NLM is that it receives messages from the client application using network protocol. As your application thinks that the disk belongs to NT server it sends the messages to the NT server.
Even if NW server could receive the message how it will know who it have to reply? One of the advantages of Gateway Service is that from the point of view of NW Server only one connection with NT Server exists that let you access NW disk from as many NT clients as you like even if this number is higher that number of NW client licenses.
Serguei