Fatal Error Reading - No server response on Dell Optiplex GX240 (Networking Products)
At 12 FEB 2002 09:52:00PM W Woodbury wrote:
I have a client site that has consistent error only on the new Dell Optiplex GX240 workstations:
"Fatal Error Reading (a random record id) in the file (a random file).
——–FS466—————————————————–
Linear Hash Client/Server.
No Server Response."
System configured as follows:
Network OS: NetWare 5.0
LH NLM: 5.0
W/S: Dell Optiplex GX240
W/S OS: Win 2000
Client: Novell Client 32, Version 4.80
Processor: P4
RAM: approx 500
Does anyone have any information to help? TIA!!
Here are answers to the Technical Support Checklist:
The checklist below presents information that is required before any problem resolution can begin:
3. Revelation product and version number.
AREV 2.12
4. Operating system version.
Win2000 on Dell Optiplex GX240
Client 32, v4.80
5. Network operating system and version.
NetWare 5.0
LH NLM 5.0 (LH.NLM, LHIPXSER.NLM & TURBODIS.NLM)
6. Statement of the problem or question.
Error (Fatal Error Reading) only occurs on Dell machines above. Other machines on the network run fine. I found on the RTI KnowledgeBase online discussion some information and made changes to the LHSTART.NCF as suggested: changed ?load lhipxser /p:1506? to ?load lhipxser /p:576?. It did not correct the problem. I find it very perplexing that it only occurs on these particlar machines.
7. Complete text of error messages.
"Fatal Error Reading (a random record id) in the file (a random file).
——–FS466—————————————————–
Linear Hash Client/Server.
No Server Response."
The following information is useful to have, if it is available:
1. Reproducible test case that demonstrates the problem.
2. Examples of problem output.
3. Number of users on the system.
20
4. TSRs running.
LHIPXTSR
5. Recent changes to environment or code.
NetWare upgrade performed months ago.
6. Recent hardware problems.
At 22 FEB 2002 04:10PM W Woodbury wrote:
I think I found the problem. A collogue found this on the Dell site.
http://delltalk.us.dell.com/messages/message_view.asp?name=oplex_network&id=zzxdv
It appears to be a problem with the integrated NIC card!