>>>ok gang....yet another question about GPLib, Novell, NT and the general insanity surrounding.
>>>
>>>Here's the situation:
>>>
>>>VFP 3.0 - data sits on a Novell server
>>>
>>>Needs to be reached by users on NT workstations. The workstations are connected to the domain server and through THAT are connected to the Novell tree.
>>>
>>>I told the Network guy that he had to have the Novell Client loaded on the server - and he replied that the Novell Client is loaded on each workstation, why doesn't that work? I don't know enough about NT and the interaction with Novell to answer that....but I'm guessing that having something on the workstation is VASTLY different from running it on the server....could anyone give me a clear, concise explanation that I can pass on?
>>
>>The client can not run on the server. It is used by the workstations to login to a Novell network. For a Novell workstation to have access to an NT server, you have to have bothe the MS and Novell client loaded on the workstation. Your NT guru should be able to connect your workstation to the NT server without disabling the Novell login as well.
>>
>>The way it works is the Novell login is primary. Once logged in the MS client pops up for you to login on the NT side as well. You then have access to both worlds.
>
>Just to make sure I understand what you're telling me, the NT workstations, hooked to the NT server, need to have the Novell client loaded on the individual workstations?

If you are at an NT workstation logged in to the NT server, can you actually see the Novell server where your data reside without the Novell login part? The way we do it here is we login to the Novell server first then to the NT server. This is the only way we get access to both resources.

You mentioned GPLib, so you may be able to omit the Novell login if GPLib will let you do this step using one of their functions. I use NetLib but I do not use it for initial user login. I use NetLib to get the user ID of the person who is logged on as verification and for authenticating to other Novell servers. I am still leary of this actually working without Client32 loaded on the WS.