Novell problem (AREV Specific)
At 14 SEP 2001 12:15:44AM Barry Stevens wrote:
I am at a client site that has been running novell for quite a while.
A new pc was installed with Windows 98
All other PCs are running Win98 too. All running AREV OK.
Short cut setup exactly the same as the others with F:\AREV\LHIPXTSR.EXE /P in the batch file section of the pif.
The following message comes up when run
LINEAR HASH IPX DRIVER - REVMEDIA OPEN ERROR FS472
UNABLE TO OPEN BOOT MEDIA MAP.
Novel Client 3.2 is installed on the pc.
Arev is Arev 2.1 (not 2.12)
Arev network driver is IPX/ADVANCED NETWARE 2.1+ Drv.
Can anyone help . I have never had a novell site before.
Remember ALL other PCs are OK.
So there must be something with the PC configuration, but I dont know what to look for.
TIA
Barry
At 14 SEP 2001 12:22AM Warren wrote:
1) You should be using the Novell Client 32, not the Microsoft client
2) Check the frame type on the ethernet settings - indeed, check if all the networking settings are the same as one of the working workstations.
At 14 SEP 2001 12:36AM Barry Stevens wrote:
]]You should be using the Novell Client 32, not the Microsoft client] Check the frame type on the ethernet settings - indeed, check if all the networking settings are the same as one of the working workstations. «
Where do I check that - I looked at Network / IPX 32 bit… / Properties - it has no values set on any PC - all just Autos and defaults
NOTE: The client install has now been changed from ver 3.3e to 3.2.
The FS error is now FS466
Barry
At 14 SEP 2001 12:41AM Barry Stevens wrote:
I just looked at the Novell Client properties on a PC that is working and its version is 3.1.0.0 (The new PC is 3.2.0.0)
Would that make a difference
At 14 SEP 2001 01:50AM Scott, LMS wrote:
Hi Barry
You can follow the network trouble shooting guide (I think it is in the knowledge base)…
From that I had to fix my PC client settings after a server shutdown and restart when previously the auto settings were fine
So (Control Panel ) Network Settings
IPX 32 bit protocol (highlight this)
click on properties
click on advanced IPX
for primary logical board, and frame type select
ETHERNET_802.2
It helps if the server uses this too but isn't absolutely necessary, I think our server is set to automatic, but I've been suffering file corruptions this last week.
While you are in control panel, you can disable write behind caching:
System | Performance | File system | trouble shooting
check the box next to "disable write behind caching".
There are some specific suggestions for error FS466 in here: NLM Troubeshooting (under Network | Performance in the KB)
And the frame type stuff is in here: Revelation NLM Installation & Follow-up Tips (under Network | Installation in the KB)
Scott
At 14 SEP 2001 01:58AM Barry Stevens wrote:
Contrary to the advice of the site's novell engineer, I found a Client 3.1 install and ran that.
It all now works
Thank you all for your help - Scott I will also check your recommended settings.
Barry