Article View: comp.os.netware.connectivity
Article #199Netware client address/connectivity
From: Ronen Friedman
Date: Mon, 11 Mar 1996 00:00
Date: Mon, 11 Mar 1996 00:00
29 lines
1727 bytes
1727 bytes
Greetings,
I have to describe some netware operations details, in a paper I'm
writing. After reading some manuals, and tracing a few connections, I
was left with following questions:
1> I know of two ways for the client to determine its network address:
<> by passively listening to the broadcasted RIP response packets;
<> by sending, in its initialization phase, a SAP Get Nearest Server
request, with an all-0 sender net.
My questions here:
--> how is the address determined from the response? does the
responding server modifies the original all-0, or is it taken
directly from the server's address?
--> can it happen that the address will only be determined later
in the initialization sequence, when the response to the
RIP-Get Local Target is received?
2> I've noticed that when the path from a Windows-for-Workgroup
client to its server is broken, the client will not re-establish
the connection using a different route. DOS clients, on the other
hand, do so.
How can this behaviour be fixed in WfW?
Thanks
Yosefa Margalit-Friedman
ronen@actcom.co.il
Technical Details
Message-ID:
<Do4KrD.6Ku@actcom.co.il>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,17da5617ffdd6005,start X-Google-Attributes: gidfe659,public X-Google-Thread: fa939,17da5617ffdd6005,start X-Google-Attributes: gidfa939,public From: ronen@actcom.co.il (Ronen Friedman) Subject: Netware client address/connectivity Date: 1996/03/11 Message-ID: <Do4KrD.6Ku@actcom.co.il> X-Deja-AN: 142313361 sender: news@actcom.co.il (News) x-nntp-posting-host: p4.haifa3.actcom.co.il organization: ACTCOM - Internet Services in Israel newsgroups: comp.os.netware.connectivity,bit.listserv.novell