From: Mike Gutknecht (mike@xxxxxxxxxxxxx)
Date: Thu May 24 2001 - 00:59:41 GMT-3
I'm a bit confused here. The lab statement says "Configure R3 so that it
can respond locally and not send explorer frames for the host AS400." By
explorer frames, do they mean, frames destined for other DLSW peers or frame
destined for local interfaces.
My initial thought was to use a dlsw netbios-name command to keep R3 from
asking it's peers for reachability info on AS400. However, the answers use
icanreach.
Are we assuming that AS400 is hanging directly off a connected interface
(ethernet or TR)?
-----Original Message-----
From: Bob Chahal [mailto:bob.chahal@ntlworld.com]
Sent: Sunday, May 20, 2001 2:36 PM
To: Steven Weber; GROUPSTUDY..
Subject: Re: dlsw in ccbootcamp lab 16 V2
icanreach for netbios name AS400 I seem to remember, put that on R3.
----- Original Message -----
From: "Steven Weber" <itweber@earthlink.net>
To: "GROUPSTUDY" <ccielab@groupstudy.com>
Sent: Sunday, May 20, 2001 7:14 PM
Subject: dlsw in ccbootcamp lab 16 V2
> I can't seem to configure Section 3 task 3 step 3.
> Configure r3 so that it can respond locally and not send explorer frames
for
> the host AS400.
> Can someone please shed some light.
>
> Thanks
> Steve
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:51 GMT-3