Apols, I just posted this message in OI area.

Our client is running Novell 5.0 support pack 5

OI 3.7

Novell Client 4.8

Workstation NT 4.0 service pack 5

I have installed NLM 5 as per instructions and created REVPARAM file with contents ServerOnly=True. I get the following error message when loading OI:

Filing System Installation Failed (REPOS_DFS–FS477)

Openengine cannot continue

Removal of REVPARAM file allows access, however the SYSOBJ record in SYSTABLES does not contain FFFFFF as described, leading me to believe although the NLM is installed on the server it is not taking control of file access.

I have tried multiple frametypes on server and workstation starting with Ethernet_ii and going back to 802.2 but the error message is always the same.

Please assist.

Regards,

James.

Revelation has received several support calls describing similar problems. We are able to replicate this in the test lab.

Novell 5 seems to be the common thread.

We have tested with Nt and Win32 clients, and with several recent client releases.

The problem seems to be that the client is unable to locate the service. We are working to determine the cause and develop a resolution for this issue.

Bob Carten

WinWin Solutions, Inc.

Thanks Bob. I appreciate you looking into this. I was going to try calling support today but will leave you in peace. It is promising that you can replicate the problem. My personal email is james_birnie@hotmail.com and contact is +61 2 9281 3733 (Australia) if I can be of any assistance.

Following is a cut/paste to Don's query from general discussion outlining our situation -

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.

James, you mention that you are using the client for NT 4.0. Is that the Novell Client v4.71 or 4.8?

Also, did you install the client using 'typical' install or 'custom' install and make any adjustments (i.e. 'IPX Only' or 'IP and IPX')?

Thanks

Kevin

Hi Kevin,

The client we are using is 4.80 and we tested 4.60 initially.

I installed the client using both typical and custom installation - it made no difference.

If you are aware of any combination of Novell 5 Server/Windows NT 4 workstations Client custom install settings that you have working please let me know.

Regards

James

View this thread on the forum...