Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 05 AUG 2003 11:28:30PM Chris Callaghan wrote:

We've got a client who have just upgraded to Windows XP (from Windows95/98) but now can no longer access the NLM.

They're using the latest Novell Client (4.83) it's latest service pack (including the vipx fix) with IPX set as the preferred protocol.

The server is NetWare 5.0 SP6 and they're using OI 4.1.2 with the 1.5c NetWare driver.

They don't get a specific FS error number, rather a (REPOS_BFS) – OpenEngine cannot continue.

Has anyone had any success using WinXP with NLM 5.0? Is there anything we could have missed?


At 06 AUG 2003 12:44AM Donald Bakke wrote:

Chris,

One of our clients resolved this issue by making sure that the Novell server was set up as the "Preferred Server" from the Advanced tab when the user is logging in. There is a list of other "try this" options that can be gleaned from this site but this was the magic bullet that resolved the issue. If you still have trouble then let me know and I'll post the rest of the check list for you.

[email protected]

SRP Computer Solutions, Inc.


At 06 AUG 2003 05:52PM Chris Callaghan wrote:

Thanks Don

But they've decided to bite the bullet and upgrade to the Universal Driver.

Of course my next question is does the Universal Driver support NetWare 5.0 SP6? RevSoft's Knowledgebase article only mentions NetWare 5.1 SP6 and NetWare 6 SP3.

Revelation, whats up with the Universal Driver on NetWare 5.0?


At 11 AUG 2003 02:16PM Matt Sorrell wrote:

If you still have trouble then let me know and I'll post the rest of the check list for you.

Don,

I'd be very interested in seeing this checklist. I'm pulling my hair out trying to get ARev to run correctly on one WinXP box.

[email protected]

Greyhound Lines, Inc.


At 21 AUG 2003 11:22PM Donald Bakke wrote:

Matt,

Sorry for the delay on this. I had to pull together various email exchanges to piece this together. Keep in mind these were solutions that OI clients have used with various degrees of success. Some are fairly standard and obvious and some seem unusual…but they are all listed here for convenience. These are not in any particular order:

1. Uninstall the Novell client. Install the Microsoft for Netware client. Finally, re-install the Novell client on top of the Microsoft client (i.e. don't uninstall the Microsoft client)

2. Remove unnecessary protocols.

3. If possible, make IPX the priority protocol.

4. Hard set the Frame Type (i.e. 802.2) rather than auto-detect.

5. Disable any virus software from scanning the data files or at least disable the scanning of *.OV files.

6. Copy the nwipxspx.dll file over to the Windows\System folder.

7. Install the Novell client more than once.

8. Install the Novell client from a local drive instead of a network drive.

9. Specify files=200 in the config.nt file.

10. Turn off power management features.

11. Specify the server hosting the NLM as the "Preferred Server" when the user is logging into the network (i.e., via the Advanced tab in the login screen).

[email protected]

SRP Computer Solutions, Inc.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/75009cb15ce375e585256d7a00131710.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1