RZBERAT1@DKNKURZ1.BITNET (Dierk Lucyga) (01/18/90)
First the facts: Novell 2.15a on Ethernet (the boards are said to be
NE-2000 compatible). There are 30 normal 286 noname PCs as workstaitions
connected to a 386 (same) noname server.
During the christmas holiday the workstations were upgraded from DOS 3.3
to 4.01. The net was small then (only 5 ws). Now as all the ws are connected,
I get "A file server could not be found" after NET4.
I tried it in the "small version" with the five ws that worked previously -
the same result.
Must I go back to DOS 3.3? I haven't tried it, yet, as the boss *wants*
DOS 4.01. Or do I have to look at other things?
Desperately
Dierk LucygaHUGHESB%AC%CSC@CSC.ISU.EDU (01/18/90)
>First the facts: Novell 2.15a on Ethernet (the boards are said to be >NE-2000 compatible). There are 30 normal 286 noname PCs as workstaitions >connected to a 386 (same) noname server. > >During the christmas holiday the workstations were upgraded from DOS 3.3 >to 4.01. The net was small then (only 5 ws). Now as all the ws are connected, >I get "A file server could not be found" after NET4. >I tried it in the "small version" with the five ws that worked previously - >the same result. > >Must I go back to DOS 3.3? I haven't tried it, yet, as the boss *wants* >DOS 4.01. Or do I have to look at other things? > > > > Desperately > Dierk Lucyga > There are a few things to look at re the infamous "A file server could not be found" in my experience I have seen all three of these causes (I try to find different and creative was to mess things up). This is a quote from the system messages manual. This error could be the result of one of the following: * A bad shell file or a shell that is not configured properly for the network interface board in your workstation. * A bad network interface board or a network interface board that is not configured properly * Cabling problems on the network. These problems can involve bad cables hubs, repeaters, or transceivers, or improper (or no) termination. I have also seen this message caused by IRQ conflicts between a board and the PC it's in. As far as going back to DOS 3.3 you may have multiple versions of DOS on the server at once, so it's free to try, but I think you'll find the answer in one of the above. Since this list narrows it right down :-) I would probably start with the cabling. Hope this helps, Brian Hughes Tech Support Mgr Idaho State University hughesb@csc.isu.edu