OI, 2000, and Netware (OpenInsight Specific)
At 04 FEB 2002 06:53:49PM Dean Lowe wrote:
Ok, here is the 64,000 dollar question.
I have a Novell server 3.12 running Arev and now OI. I have a Windows 2000 server running gateway services for Netware trying to access the Novell server for the OI. The network driver I am using is the IPX/Netware multi-user driver ver. 1.14 vxd. It works fine for my 98 workstations.
When I try to access OI through the Win 2000 server or Terminal Server. I get the Revelation splash screen and then it goes away. No error message nothing. If I switch to another driver say for example the byte-range locking multi-user driver. It will work with the 2000 and the Terminal Server, but file locking does not occur. If I try to use the All Networks driver, it tells me that tables aren't attached.
So my question is, what driver can I use to be able to have the file locking and use Terminal Server. I know it works because I have read about other people using this format here, but nobody really says how they do it.
Also just for some extra info, we are currently running a winframe server the same way to access Arev from the Novell server without a problem. But it will not run the OI. It kicks you out of the workstation when you try to do that.
At 04 FEB 2002 11:46PM Chris Callaghan wrote:
Hi Dean,
First thing to try is a Novell Client (I think 4.81 is the latest) on the 2000 server.
Are you running the NLM at all? Give 1.5 a go if you have it (or upgrade - costs money tho).
We've tried connecting to a NetWare server with WinFrame and NT 4.0 Terminal Server, but never got it going… well it worked but was so slow that it was impossible to use.
I think it may have worked when the NLM wasn't running - but we needed the NLM anyway so that defeated the point
At 05 FEB 2002 08:41PM Scott, LMS wrote:
Dean
I get this problem when ini files for my applications are not in the Operations directory eg for Win98, the default directory for the install being "Windows", I make sure that the *.ini files are in there. Ie make sure the ini files are there on your windows server.
Eg
OIPI.ini
Oinsight.ini
and
myOIapp.ini (this might be optional but my application "myOIapp" needs it)
You might need to do the special install of OIPI as well if you are using OIPI and the Windows Server as a Open Insight terminal.
(although that won't explain the peek-a-boo effect).
I don't know if you'd need the windows 2000 service on the windows server as well to make all this work. I have put a similar question in the Network specific forum to find out.
Scott, LMS
At 06 FEB 2002 01:08PM Dean Lowe wrote:
Thanks for the suggestion Scott. The ini files are on the server, I did a search for those and they appear. It has to be something with the network drivers because when I change to the different driver, I can get it to run, but the file locking does not occur.
At 06 FEB 2002 05:17PM Donald Bakke wrote:
Dean,
Is there a reason you need to run Microsoft's gateway services for Netware? I'm pretty certain that's where the problem lies. If your system has no other reason for using the gateway service then you ought to try and install Novell's client v4.82. That should allow your Win2000 and Terminal Server to run OI (and AREV) much better.
At 06 FEB 2002 06:12PM Dean Lowe wrote:
The reason I am running the gateway services for netware is so the Win 2000 server can see and talk to the Novell server where our application lies. I am trying to setup our remote users so they can start using the application. When we are finished converting the app from Arev to OI I will move it to the Win 2000 server and it won't be an issue. Maybe I am not thinking right on this but don't I need to run the gateway servies for netware just for that reason? Or are you saying that I can load the Novell client on the Win 2000 server and access the Novell server that way?
At 06 FEB 2002 07:36PM Donald Bakke wrote:
Hi Dean,
That is what I'm suggesting. The Win2000 server can connect to the Novell server just as a regular Win2000 client workstation would. Then those remote users will have a session that connects to the Novell server using Novell's client instead of the Microsoft gateway.
Another client went through almost the exact same scenario: Use NT 4.0 Terminal Server to talk to a Novell 3.12 server. Also, they had another NT 4.0 Server running the OICGI so they could have web access to their database. Novell was recently replaced with NT (or Win2000, I can't recall) but they kept the original Terminal Server and Web Server as separate machines to keep the load off of the main server.