Article View: comp.os.netware.connectivity
Article #280Re: HELP: 3.11 (No known file server)
From: Dan Sobel
Date: Sun, 23 Jul 1995 00:00
Date: Sun, 23 Jul 1995 00:00
49 lines
2905 bytes
2905 bytes
In article <3uln4r$12d@news.bu.edu>, crofoot@bu.edu says... > > >I am running a LAN to LAN connection between 2 sites. Here's the stats: > >Site 1: Novell file server running Netware 3.11 > 3 PC's (all connecting to file server file) > Shiva Netmodem/E 28.8 > >Site 2: 2 PC's > Shiva Netmodem/E 28.8 (this is a router that sits on the network) > >* All of the PC's on the site 1 end connect to file server fine. >* The file server has a 5 user license. >The only bit of rumor I have heard about this is that there is some NLM >that fixes a bug in 3.11 that forces clients to drop connections. >(something about Netware 3.11 storing ethernet addresses in memory or on >disk and not allowing connections to those addresses until the first is dro >pped.) > I think that you're looking for... It is in each patch kit (3.11, 3.12, 4.01, 4.02). Interestingly enough, 4.10 uses a different scheme, and does not have this problem. You can check this out by using MONITOR to KNOCK everybody off line, then trying to log in on the SHIVA system. GNSFIX NLM 2397 02-19-92 1:43p This patch fixes a problem found when rebooting and attempting to get a connection to the file server. If all of the connections are in use (such as 20 for the 20-user version, 50 for the 50-user version, ...) and one of the users reboots, the user will not be able to log back in to the server. This problem only occurs when there is only one network. When the user is on an internet, a reconnection is possible. The problem is that when a user reboots, the connection is not terminated at the server until a time out limit is reached (usually 15 minutes). This patch corrects the problem by checking the source node address of the incoming packet to the node address of all workstations to which the server currently recognizes attachment. If a match is found, the server responds to the workstation, thus recreating a connection in the same slot the workstation had before its reboot. -- --------------------------------------------------------------------- Dan Sobel Amateur N6HLZ snake@wco.com
Technical Details
Message-ID:
<3uunjf$djq@news.wco.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<3uln4r$12d@news.bu.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,6cb9d2c1fc8836d6 X-Google-Attributes: gidfe659,public X-Google-Thread: fa939,6cb9d2c1fc8836d6 X-Google-Attributes: gidfa939,public X-Google-Thread: f8bf7,6cb9d2c1fc8836d6 X-Google-Attributes: gidf8bf7,public From: Snake@WCO.Com (Dan Sobel) Subject: Re: HELP: 3.11 (No known file server) Date: 1995/07/23 Message-ID: <3uunjf$djq@news.wco.com> X-Deja-AN: 106773300 references: <3uln4r$12d@news.bu.edu> content-type: Text/Plain; charset=ISO-8859-1 organization: WEST COAST ONLINE keywords: 3.11,netware,novell,error mime-version: 1.0 newsgroups: comp.os.netware.connectivity,comp.os.netware.misc,bit.listserv.novell