Error logging onto Netware 5 (AREV Specific)
At 02 AUG 2004 08:52:47AM Peter Bowyer wrote:
One of our clients is having problems running Arev on Netware 5.00. Three of their workstations consistently fail at startup. We are told that they all worked last week and no changes have been made to the configuration since then.
They are running Netware 5.00 with NLM ver 5, the Novell client ver 4.83 SP2 and worstation operating system Windows 2000 ver 5.00.21.95 SP4.
Any ideas gratefully recieved.
At 02 AUG 2004 10:35AM Steve Smith wrote:
Microsoft have released a whole bunch of Win2k upgrades (auto-loaded) this past week. Check that these haven't somehow re-ordered the protocols in network settings / TCP/IP and IPX etc.
Failing that, check that virus software upgrades are set to skip OV files.
Are they getting any error messages on startup?
At 02 AUG 2004 12:47PM Peter Bowyer wrote:
I'll have them check the updates.
Don't think its virus software as all but 3 workstations work OK.
The error is thrown up a some software that checks for the 'FFFFF' byte on the VOC file and decides that if its not present we are not under NLM control.
At 03 AUG 2004 04:10PM Warren wrote:
Has anything been changed on the three workstations in question?
Sounds like the LHIPXTSR is not loading. Check the config.sys/.nt files as well as the shortcuts that are used to start ARev on those stations.
From a command window on the workstations try loading LHIPXTSR manually and then starting ARev manually.
At 03 AUG 2004 04:15PM Warren wrote:
Check also that the protocol frame type on the Novell client is set to the frame type that is bound on the server card.
I've had workstations which were running fine for months with the frame type set to "auto" suddendly stop talking to the NLM until the frame type was manually set.
At 04 AUG 2004 06:01AM Peter Bowyer wrote:
Thanks for your help. Problem now solved.