FS 472 Error (AREV Specific)
At 24 JAN 2001 11:27:44AM Greg Motter wrote:
We have been having off and on for about the last month with FS 472 errors. It seems very bizarre to me and I cannot come up with a solution. A little background. We are running arev 2.12 and nlm 1.06 and Novell 3.12. We are running into FS 472 errors on our Dos Machines. All of our Windows machines are not getting this error. In the past, it always seemed that it was the Window's Machines that would get this error. The only thing that has changed since we have started getting this error is that we have added a Nortel Passport 8600 Chassis to the network about the time the problems started occurring.
Anyone have any ides. I have checked the net.cfg file and the frame is set correctly.
Any insight into this would be greatly appreciated.
Greg
At 24 JAN 2001 11:33AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
Did you check out this knowledgebase posting?
World Leaders in all things RevSoft
At 24 JAN 2001 06:24PM Greg Motter wrote:
Remember this is only on Dos Machines. I did however go back and make sure that both the server and the workstations were set to 802.3 and they were. I also made sure that SAP filtering was off (it was not on).
Let me know if anyone else has any ideas. We are going to try to switch to 802.2 and see if that changes anything. We are also going to attempt to disconnect the chassis from the network and see if that helps.
One other thing that is odd is that it does not happen all the time. If we continually try to start arev for awhile, it will eventually load up and the NLM seems to be working correctly with the client (F's in the VOC file).
Let me know if anyone has any other ideas,
Greg
At 25 JAN 2001 11:57AM Greg Motter wrote:
We tried a few more things with this last night. The odd thing is that it was working for awhile this morning and now we are back to getting FS 472 errors again.
Anyone have any ideas?
Greg
At 26 JAN 2001 12:07PM Donald Bakke wrote:
Greg,
You mentioned you were using NLM v1.06. Have you considered upgrading? We experienced many problems (don't recall if they were FS472 though) until v1.50 & v1.50a came out.
dbakke@srpcs.com
At 26 JAN 2001 03:25PM Don Miller - C3 Inc. wrote:
Don ..
I think you're on target. We've had similar problems with early versions of the NLM. They seem to work OK with AREV 2.12 / Novell 4.x and Client32 3.0.0 on Win95 desktops. However, some of the patches for Windows and Win98 (all versions) have had some instability until the recent versions of the NLM have been installed. Also, protocol stacking with IPX/SPX and TCP/IP has been a headache unless IPX is on top.
Don Miller
C3 Inc.
At 26 JAN 2001 06:42PM Greg Motter wrote:
I would love to upgrade these systems, but thats not going to happen right now and as I said before, our problems are not in Windows, that seems to be working fine (at least as far as the fs472 error is concerned) just in dos.
One other thing that may possibly be related is this. On this same network we have one Arev Database that is on a Novell 5 server with the appropriate NLM 5 running. For some reason, when we are seeing the the problem on the dos machines, we will not be able to attach the volumes from our Development environment which is on another Novell 5 server with the same version of the NLM running unless we remove the REVPARAM files. The error is FS109 'OPEN OR CREATE MEDIA ERROR. The name dos.path is an invalid volume directory label'. As soon as I remove the RevParam files we can attach with no problems. It seems that these are related despite the fact we are using NLM 1.5 on the Novell 5 server and 1.06 on the Novell 3.12 servers. Also as soon as we can log in on the Dos machines again this problem also goes away.
Any more ideas, a Nortel Engineer is onsite right now, hopefully we can come up with something on their end.
Thanks again,
Greg
At 27 JAN 2001 02:40PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
Potentially silly query but earlier you mention being unable to attach on the development machine with "the same version of the NLM". You don't mean this literally do you - i.e. duplicate serial numbers?
World Leaders in all things RevSoft
At 29 JAN 2001 09:27AM Greg Motter wrote:
Nope, they are different serial numbers, but the same version of the NLM. NLM 1.5a for Novell 5.
Greg
At 30 JAN 2001 01:12AM Donald Bakke wrote:
Greg,
You've been giving us conflicting information. First you say the NLM is version 1.06. Then you say that you have NLM 1.06 for your 3.12 servers and 1.5a for your 5.0 server. Now you claim that both NLM's are 1.5a. It's hard to tell what is going on without clear information.
Either way, whether your clients are DOS or Windows, you should be using NLM 1.5a for 3.x and 4.x servers. Novell 5 requires the NLM 5.0. It sounds like you are using the wrong version of the NLM for all servers.
dbakke@srpcs.com