Sniffer trace showed AREV had difficulty finding correct server/file locations during login.  The trace showed excessive file retranmissions, numerous Loops on requests, and denied requests due to misplaced calls to other servers in DOS Path or mapped on client. 

  Network info: Client is Windows 95 using Client for Netware Networks driver.  Windows 95 Client login is to Novell 4 directory tree though Network Neighborhood preferred server is set to AREV server name. AREV application is on Novell 3.11 bindery server which is attached via drive map to client R: drive.  Map is to root of server Volume (Vol1).  This server is on same LAN as clients.  Client DOS path does not contain AREV server drive, but the complete drive location is identified in Windows95 AREV application icon. AREV is given correct working directory. 

  Will your 1.5 NLM update correct this?  Any other recommendations?

Thank you,

Brian

Brain,

    It sounds like you are doing everything correctly. You could try looking at the r an c parameter switches for the lhipxtsr to see if these may be able to help at all. They are found on page 15 of your NLM installation Guide. They are sleep and retry times for the tsr. Does your Sniffer trace allow you to see if the SAP address Ox5B8 (the nlm's SAP ID) is getting through? If not make sure that it is. 

1. DaveRevelation

View this thread on the forum...