Device does not exist, using All Networks Driver, wireless Wan (AREV Specific)
At 20 OCT 2000 09:22:11AM Dave Bennett wrote:
Using arev 3.111 on Nt with the All Networks Driver on a wireless WAN I receive Device does not exist Abort Retry Fail, and nothing gets my out except to close the session. Revparam is set to serveronly=true in all directories. This message happens printing, idle moving through the system, or I receive the message file not opened. If I look through windows explorer I can still see the drive, but I think windows is reconnecting the workstation.
At 20 OCT 2000 01:27PM Don Miller - C3 Inc. wrote:
This may be a case of response-time latency such that the speed of the connection is above the threshhold of the driver time-out. I'm not sure if its the All Networks Driver of the interface between the driver and the client desktop. I've seen similar behavior on networks when there are high-error rates on the cable or through a router. The driver doesn't get responses back quickly enough and thinks the network isn't there. Have you tried tweaking the GroupLockTimeOut value in your REVPARAM file. The default is 60 seconds. Normally, this value is sufficiently high to prevent a workstation from hanging. Try increasing the value in small increments (maybe at a time) to see if it helps.
Don Miller
C3 Inc.