From: Pamela Forsyth (pforsyth@xxxxxxxxx)
Date: Thu Aug 17 2000 - 09:23:53 GMT-3
>Date: Thu, 17 Aug 2000 08:21:13 -0400
>To: "Stephens, Paul [Prof.Serv]" <Paul.Andrew.Stephens@compaq.com>
>From: Pamela Forsyth <pforsyth@clark.net>
>Subject: Re: IPX SAP
>
>Paul,
>
>If the only IPX devices on the LAN are Novell (or even IPX-speaking
>Microsoft) clients and printers you have nothing to worry about because
>they don't process the periodic SAP broadcasts at all. A Novell client
>discovers services by querying its server specifically for them as needed,
>and does not build its own full table of services.
>
>The only time you might have a problem changing SAP intervals on a LAN
>would be when you have Novell servers or other IPX routers on the
>LAN. They depend on the periodic SAPs to build their service tables, and
>expect to hear a broadcast every 60 seconds.
>
>Pamela
>
>At 12:10 PM 8/17/00 +0100, you wrote:
>>If am working on a scenario where I want to optimize sap traffic on an
>>ethernet. I thought the way to do this was to apply the ipx update internal
>>sap changes-only to the etherent interface, when I applied this command I
>>got the following warning;
>>
>>% Warning: Changing the SAP interval on LANs is dangerous!
>>
>>So my question is why do i get this warning and what efect does this command
>>have on client end stations receiving saps
>>
>>Cheers
>>
>>Paul Stephens
>>
>>UK INI Network Consultant
>>Networks and Systems Integration Services
>>Compaq Computer Ltd
>>paul.andrew.stephens@compaq.com
>>
>>Tel: (Mobile) +44 (0)7818 457948
>>
>>www.compaq.co.uk
>>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:27 GMT-3