Hello again,

Is there anyone in the world (using OI3.7 on Novell5.0 with Support pack 5 and the clients are windows NT4 service pack 5)can connect to the NLM 5?

I,ve been testing every single thing you can think of in terms of Frame type, Protocol, ……… with no luck.

From what I found in the knowledge base and all the messages posted in this site I am convinced now that it never worked on Windows NT4.

Any help please. It is urgent as all my clients in this site are running Windows NT4.

regards

James,

While we are presently dealing with a problem with an NT Server working like a workstation against a Novell 4.11 server (FS477 errors), there are NT 4.0 Workstations w/SP5 running just fine. We also support clients with OI based vertical applications in many environments just like this one.

I don't know if I can resolve your problem but I thought you would like to know that it isn't impossible to make it work.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

Thanks Don, that is encouraging.

Can I ask you or anyone else if you to had the previous errors and how/what you are doing or looking at to resolve them?

It is quite an urgent matter ;)

Regards,

James.

James,

Can I ask you or anyone else if you to had the previous errors and how/what you are doing or looking at to resolve them?

I'm certain we've done everything that you implied in this quote: "I,ve been testing every single thing you can think of in terms of Frame type, Protocol, ……… with no luck." Perhaps if you detailed your steps we could point out something you missed.

dbakke@srpcs.com

SRP Computer Solutions, Inc.

James

Are you using the revparam file? Do you have it in every directory that could have OI table in it (including temp dirs for temp files)?

What happens if you turn off the revparam (we wrote a .bat file to go through all our OI app directories and rename revparam to revparam.txt) - does it work then - if so either you missed a directory with a rev table in it or OI/NLM doesn't like your server set up.

We have one client with MS NT cluster and it refuses to speak with the NLM - possibly because there are more than one server computer mapped/logically viewed as one and I'll take a punt that the actual NLM is only installed on one of them. Unfortunately all the server admin is outsourced and I cannot investigate or experiment with it or test it because you can only install the NLM once. That client uses Novell to log in(client)/run the LAN network and they have NT workstation on the client PCs. Ugly. We had to turn off the revparam stuff, so their response is not good and it corrupts easily but it is better than no system at all.

Scott.

Hi Don,

Thanks for responding once again. The following are details of our steps to date:

Background:

Server: Novell 5.0 with support pack 5, IPX and TCP/IP protocols, Frame type Ethernet_II.

Workstations: WINNT 4.0 with service pack 5, Nwlink IPX/SPX Compatible protocols, Frame type Ethernet_II.

Situation:

We have been trying to connect using OpenInsight NLM for almost a week now with WINNT workstations.

I changed the frame types on the server and on workstation to match using all the available frame types but the error FS477 remains. I changed the preferred protocol on the workstation to be IPX as suggested on the discussion group.

In trying to isolate the problem this morning I logged in using Win98 workstation with Novell client 3.0, IPX/SPX and TCP/IP protocols, Frame type=Ethernet_II. The message FS472 appeared again. I removed the TCP/IP protocol completely from Win98 and connected to Novell server by using just IPX protocol and now the OpenInsight software is working fine and I can see the 5 FFFFF on the SYSOBJ record. This was a big break as it indicates the NLM and server are not the problem. However, doing the same on WINNT (removing TCP/IP protocol and connecting to the server solely by Nwlink IPX/SPX protocol ) still results in same error.

The last thing I am wondering is that perhaps the Nwlink IPX/SPX compatible protocol (Microsoft?) for NT is not the right one and it should be a Novell version. I don?t know how to install the original Novell IPX/SPX protocol for WINNT if this is the case.

Finally, something to consider is that our client is a fairly major government branch and their whole network infrastructure is based on IP network connections, and there will be NO WAY we will be able to totally remove TCP/IP from their network setups.

Any help will be appreciated. Also if Revelation are listening we are a recent member of Works program, and are not adverse to paying for this problem to be solved!

Regards,

James.

Hi Scott

Renaming the REVPARAM file does allow access, however the NLM does not appear to work in this case (checking the SYSTABLES SYSOBJ record for FFFFFF). It is in all directories/subdirectories. I assumed this REVPARAM file was for "ENSURING" access by client machines uses the NLM?

Also, I feel the server is probably ok, as I just mentioned to Don when outlining our situation that we CAN connect using NLM on a Win98 workstation without TCP/IP installed.

Keep thinking though and thanks for your response.

Regards,

James.

Hi James

Yes the revparam turns the access using the server NLM on and off, ie when you have serveronly=1 it forces things like table updates to be handled by the server which is a very good thing, ie it prevents problems that occur when the clients crash or get switched off without closing the application.

It sounds like (and I am out of my depth here) that there is a problem with the network protocols that upsets the NLM which is a form of network protocol too. We usually install the novell lan client directly onto our systems and that is definitely better than using Microsoft's version of IPX. The novell client comes on CD and your network techs should have a copy somewhere.

There are nlms for NT too, but I don't know if this will help - you probably do need to talk to Revelation and they are good about sending your email on to the right person even when you email to info@revelation.com. Just put "attn NLM Guru" in the subject. I don't know why TCP/IP should upset things, because we have that as well as novell and novel NLM. It may have to do with primary network controller/protcol.

At least you have established that it is not the server config.

Scott.

I am having the same problem!

All the postings on this subject are rather old.

Does anyone know, was a solution ever found or did everyone just give up?

I have tried everything I can think of and still get FS477.

View this thread on the forum...