Cell Relay Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: NDS queries VERY slow over ATM
This is a multi-part message in MIME format.
--------------58A9331E4B33
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
John Dunning wrote:
>
> We just implemented an ATM backbone for our token-ring lan yesterday
> and while everything seems to work ok, clients querying NDS info from
> servers over the ATM link is exceptionally slow. Our network is
Maybe this will help...
--------------58A9331E4B33
Content-Type: text/html; charset=us-ascii; name="optimize the wan.htm"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="optimize the wan.htm"
Content-Base: "file:///C|/netware/nds/optimize%20the%20
wan.htm"
<BASE HREF="file:///C|/netware/nds/optimize the wan.htm">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe PageMill 2.0 Mac">
<TITLE>Preserving WAN Bandwidth</TITLE>
<SCRIPT LANGUAGE="JavaScript">
<!-- Begin to hide script contents from old browsers.
browserName = navigator.appName;
browserVer = parseInt(navigator.appVersion);
if (browserName == "Netscape" && browserVer >= 3) version = "n3";
else version = "n2";
if (version == "n3") {
// MAIN LINKS ROLLOVER
what = new Image();
what.src = "/miscart/templates/1997/nav_what.gif";
what_over = new Image();
what_over.src = "/miscart/templates/1997/nav_what_over.gif";
what_info = new Image();
what_info.src = "/miscart/templates/1997/navinfo_what.gif";
how = new Image();
how.src = "/miscart/templates/1997/nav_how.gif";
how_over = new Image();
how_over.src = "/miscart/templates/1997/nav_how_over.gif";
how_info = new Image();
how_info.src = "/miscart/templates/1997/navinfo_how.gif";
search = new Image();
search.src = "/miscart/templates/1997/nav_search.gif";
search_over = new Image();
search_over.src = "/miscart/templates/1997/nav_search_over.gif";
search_info = new Image();
search_info.src = "/miscart/templates/1997/navinfo_search.gif";
site = new Image();
site.src = "/miscart/templates/1997/nav_site.gif";
site_over = new Image();
site_over.src = "/miscart/templates/1997/nav_site_over.gif";
site_info = new Image();
site_info.src = "/miscart/templates/1997/navinfo_site.gif";
novell = new Image();
novell.src = "/miscart/templates/1997/nav_novell.gif";
novell_over = new Image();
novell_over.src = "/miscart/templates/1997/nav_novell.gif";
novell_info = new Image();
novell_info.src = "/miscart/templates/1997/navinfo_novell.gif";
// HERE BEGINS SUBNAVIGATION ROLLOVERS
nav3_subscriptions = new Image();
nav3_subscriptions.src = "/nwc/images/nav3_subscriptions.gif";
nav3_subscriptions_over = new Image();
nav3_subscriptions_over.src = "/nwc/images/nav3_subscriptions_over.gif";
nav3_subscriptions_info = new Image();
nav3_subscriptions_info.src = "/nwc/images/navinfo_subscriptions.gif";
nav3_network_resources = new Image();
nav3_network_resources.src = "/nwc/images/nav3_network_resources.gif";
nav3_network_resources_over = new Image();
nav3_network_resources_over.src = "/nwc/images/nav3_network_resources_over.gif";
nav3_network_resources_info = new Image();
nav3_network_resources_info.src = "/nwc/images/navinfo_network_resources.gif";
nav3_bookstore = new Image();
nav3_bookstore.src = "/nwc/images/nav3_bookstore.gif";
nav3_bookstore_over = new Image();
nav3_bookstore_over.src = "/nwc/images/nav3_bookstore_over.gif";
nav3_bookstore_info = new Image();
nav3_bookstore_info.src = "/nwc/images/navinfo_bookstore.gif";
nav3_advertisers = new Image();
nav3_advertisers.src = "/nwc/images/nav3_advertisers.gif";
nav3_advertisers_over = new Image();
nav3_advertisers_over.src = "/nwc/images/nav3_advertisers_over.gif";
nav3_advertisers_info = new Image();
nav3_advertisers_info.src = "/nwc/images/navinfo_advertisers.gif";
nav3_past_issues = new Image();
nav3_past_issues.src = "/nwc/images/nav3_past_issues.gif";
nav3_past_issues_over = new Image();
nav3_past_issues_over.src = "/nwc/images/nav3_past_issues_over.gif";
nav3_past_issues_info = new Image();
nav3_past_issues_info.src = "/nwc/images/navinfo_past_issues.gif";
}
function img_over(imgName) {
if (version == "n3") {
imgOver = eval(imgName + "_over.src");
document [imgName].src = imgOver;
navInfo = eval(imgName + "_info.src");
document ["navinfo"].src = navInfo;
window.status = "imgName"; return true
}
}
function img_out(imgName) {
if (version == "n3") {
imgOut = eval(imgName + ".src");
document [imgName].src = imgOut;
navInfo = "/nwc/images/navinfo_nwc.gif";
document ["navinfo"].src = navInfo;
window.status = ''; return true
}
}
// End the hiding here. -->
</SCRIPT>
</HEAD>
<BODY TEXT="#000000" LINK="#164ead" VLINK="#cb0016" ALINK="#00028A" BGCOLOR="#FFFFFF">
<!-- START NAVIGATION BAR -->
<TABLE CELLPADDING=0 CELLSPACING=0 BORDER=0 WIDTH=557 NOWRAP COLUMNS=2>
<TR>
<TD VALIGN=top><!--
Unix line break --><A HREF="/index.html" ONMOUSEOVER="img_over('novell'); window.status = 'Novell Home'; return true" ONMOUSEOUT="img_out('novell'); window.status = ''; return true"><IMG SRC="/miscart/templates/1997/nav_novell.gif" NAME="novell" WIDTH="80" HEIGHT="27" BORDER=0></A><!--
Unix line break --><A HREF="/whatsnew/" ONMOUSEOVER="img_over('what'); window.status = 'What\'s New'; return true" ONMOUSEOUT="img_out('what'); window.status = ''; return true"><IMG SRC="/miscart/templates/1997/nav_what.gif" ALT="whats_new" NAME="what" WIDTH="83" HEIGHT="27" BORDER="0"></A><!--
Unix line break --><A HREF="/sales/" ONMOUSEOVER="img_over('how'); window.status = 'How to Buy'; return true" ONMOUSEOUT="img_out('how'); window.status = ''; return true"><IMG SRC="/miscart/templates/1997/nav_how.gif" ALT="how_to_buy" NAME="how" WIDTH="89" HEIGHT="27" BORDER="0"></A><!--
Unix line break --><A HREF="/nwc/search/" ONMOUSEOVER="img_over('search'); window.status = 'Search'; return true" ONMOUSEOUT="img_out('search'); window.status = ''; return true"><IMG SRC="/miscart/templates/1997/nav_search.gif" ALT="search" NAME="search" WIDTH="62" HEIGHT="27" BORDER="0"></A><!--
Unix line break --><A HREF="/sitemaps/" ONMOUSEOVER="img_over('site'); window.status = 'Site Map'; return true" ONMOUSEOUT="img_out('site'); window.status = ''; return true"><IMG SRC="/miscart/templates/1997/nav_site.gif" ALT="site_map" NAME="site" WIDTH="76" HEIGHT="27" BORDER="0"></A><!--
Unix line break --></TD><TD VALIGN=bottom><IMG SRC="/miscart/templates/1997/pixel.gif" WIDTH="40" HEIGHT="1"><BR CLEAR=all><IMG SRC="/miscart/templates/1997/nav_end.gif" WIDTH="167" HEIGHT="16"></TD>
</TR>
<TR>
<TD VALIGN=top COLSPAN=2><IMG SRC="/miscart/templates/1997/pixel.gif" WIDTH="40" HEIGHT="15"><A HREF="/nwc/index.html"><IMG SRC="/nwc/images/navinfo_nwc.gif" NAME="navinfo" WIDTH="511" HEIGHT="15" BORDER="0"></A><IMG SRC="/miscart/templates/1997/nav_sideshadow.gif" WIDTH="6" HEIGHT="15"><BR CLEAR=all><IMG SRC="/miscart/templates/1997/pixel.gif" WIDTH="39" HEIGHT="1"><IMG SRC="/miscart/templates/1997/nav_shadow.gif" WIDTH="517" HEIGHT="9"></TD>
</TR>
</TABLE>
<!-- END NAVIGATION BAR -->
<!-- START SUB NAV TABLE -->
<TABLE CELLPADDING=0 CELLSPACING=0 BORDER=0 WIDTH=553 NOWRAP COLUMNS=2>
<TR>
<TD VALIGN=top><IMG SRC="/nwc/images/pixel.gif" WIDTH="39" HEIGHT="15" BORDER="0"></TD>
<TD VALIGN=top>
<A HREF="/nwc/sub.html" ONMOUSEOVER="img_over('nav3_subscriptions')" ONMOUSEOUT="img_out('nav3_subscriptions')">
<IMG SRC="/nwc/images/nav3_subscriptions.gif" NAME="nav3_subscriptions" ALT="Subscriptions" WIDTH="109" HEIGHT="10" BORDER="0"></A>
<img src="/nwc/images/pixel.gif" width=1 height=1 border=0>
<A HREF="/nwc/resources/" ONMOUSEOVER="img_over('nav3_network_resources')" ONMOUSEOUT="img_out('nav3_network_resources')">
<IMG SRC="/nwc/images/nav3_network_resources.gif" NAME="nav3_network_resources" ALT="Network Resources" WIDTH="86" HEIGHT="10" BORDER="0"></A>
<img src="/nwc/images/pixel.gif" width=1 height=1 border=0>
<A HREF="/nwc/bookstor/" ONMOUSEOVER="img_over('nav3_bookstore')" ONMOUSEOUT="img_out('nav3_bookstore')">
<IMG SRC="/nwc/images/nav3_bookstore.gif" NAME="nav3_bookstore" ALT="Bookstore" WIDTH="89" HEIGHT="10" BORDER="0"></A>
<img src="/nwc/images/pixel.gif" width=1 height=1 border=0>
<A HREF="/nwc/advertis.html" ONMOUSEOVER="img_over('nav3_advertisers')" ONMOUSEOUT="img_out('nav3_advertisers')">
<IMG SRC="/nwc/images/nav3_advertisers.gif" NAME="nav3_advertisers" ALT="Advertisers" WIDTH="99" HEIGHT="10" BORDER="0"></A>
<img src="/nwc/images/pixel.gif" width=1 height=1 border=0>
<A HREF="/nwc/past/" ONMOUSEOVER="img_over('nav3_past_issues')" ONMOUSEOUT="img_out('nav3_past_issues')">
<IMG SRC="/nwc/images/nav3_past_issues.gif" NAME="nav3_past_issues" ALT="Past Issues" WIDTH="93" HEIGHT="10" BORDER="0"></A>
<BR CLEAR=all></TD>
</TR>
</TABLE>
<!-- END SUB NAV TABLE -->
<TABLE CELLPADDING=0 CELLSPACING=0 BORDER=0 WIDTH=550 NOWRAP COLUMNS=2>
<TR>
<TD WIDTH=40 NOWRAP></TD>
<TD WIDTH=510 NOWRAP></TD>
</TR>
<TR>
<TD></TD>
<TD VALIGN=top><BR>
<FONT FACE="times" size=-1>
<!-- end header_tier3.html -->
<H3>Preserving <FONT COLOR="#000000">WAN Bandwidth</FONT></H3>
<H3><HR ALIGN=LEFT></H3>
<P><I>Laura Chappell</I></P>
<P>As you expand your company's network to include more servers, workstations,
and WAN links, network performance can become a problem. To ensure that
you are not wasting bandwidth, you should examine the type of communications
that are being sent across the network. For example, if your company's network
includes a dial-on-demand WAN link, such as an Integrated Services Digital
Network (ISDN) line between two offices, you need to eliminate unnecessary
communications that initiate this WAN link.</P>
<P>Because IntranetWare and NetWare devices perform several processes to
maintain connectivity, these devices may be sending unnecessary communications
over your company's WAN link. This article examines how processes such as
NetWare serialization, NetWare Core Protocol (NCP) watchdog, SPX keep-alive,
and queue sampling affect a WAN link. This article then explains how to
prevent these processes from creating network traffic across a WAN link.</P>
<H4>NETWARE SERIALIZATION</H4>
<P>Like many products, IntranetWare, NetWare 4, and NetWare 3 use a serialization
process to detect copyright violations. Approximately every 66 seconds,
each IntranetWare or NetWare server sends five serialization packets to
other IntranetWare or NetWare servers on the network. These serialization
packets are IPX packets that are addressed to serialization socket 0x0457
and contain the serial number of the transmitting server. (See <A HREF=
"wanf187.html">Figure 1</A>.) Although serialization packets provide only
copy-protection information, they can consume bandwidth on your WAN link.
If your company has a dial-on-demand WAN link, serialization packets can
even establish this link between two servers.</P>
<P>Despite what you may have heard, you can use routers on each side of
the WAN link to filter out serialization packets without affecting the way
IntranetWare and NetWare servers communicate. In fact, many routers, such
as Novell's NetWare MultiProtocol Router (MPR) 3.1, filter out serialization
packets across a dial-on-demand WAN link by default.</P>
<H4>NCP WATCHDOG</H4>
<P>When you log in to an IntranetWare or NetWare server, the server begins
to monitor your workstation's connection for activity. If you log out of
a server, the Novell client on your workstation sends a Destroy Connection
NCP request to the server, which clears your workstation's connection ID
number. If you simply turn off your workstation without logging out of the
network, however, the Novell client on your workstation cannot send a Destroy
Connection NCP request to the server. As a result, the server does not clear
your workstation's connection ID number.</P>
<P>IntranetWare and NetWare use the NCP watchdog process to identify and
terminate invalid connections. If you log in to a server and do not communicate
with this server within a specified amount of time, the server sends your
workstation an NCP watchdog request to determine if your workstation's connection
is still valid. (See <A HREF="wanf287.html">Figure 2.</A>)</P>
<P>If the Novell client is loaded on your workstation, this client sends
an NCP watchdog reply to ensure that the server does not clear your workstation's
connection. If the Novell client on your workstation does not send an NCP
watchdog reply (because you shut off your workstation, for example), the
server sends another NCP watchdog request. The server repeats this process
the number of times specified by the Number of Watchdog Packets SET parameter.
After reaching this number, the server assumes that the workstation's connection
is invalid and clears the connection.</P>
<P>By default, an IntranetWare or NetWare server sends an NCP watchdog request
after your workstation's connection has been inactive for five minutes.
If your company has a dial-on-demand WAN link and no user is accessing this
link, you certainly don't want the NCP watchdog process to establish this
link because the connection has been idle five minutes.</P>
<P>To avoid establishing a WAN link for the sole purpose of sending and
receiving NCP watchdog packets, some routers perform NCP watchdog spoofing:
If the server and your workstation are separated by a dial-on-demand WAN
link, the local router replies to the NCP watchdog request on behalf of
your workstation. As a result, a WAN link is not established. NetWare MPR
3.1 provides an NCP watchdog spoofing option, and Cisco's IOS software includes
an IPX watchdog spoofing command that performs the same function.</P>
<P>Because these routers perform NCP watchdog spoofing, your workstation's
connection remains intact unless you log out of the network. If you want
to periodically clear connections on your server, you can have this server
force every workstation to log out at a predetermined time, such as 9 p.m.
In this way, all connections are available the next day.</P>
<P>If you do not have a router that performs NCP watchdog spoofing, you
can reduce the traffic sent across the WAN link by increasing the values
for three SET parameters:</P>
<UL>
<LI>Delay Before First Watchdog Packet (default: five minutes)<BR>
<BR>
<LI>Delay Between Watchdog Packets (default: one minute)<BR>
<BR>
<LI>Number of Watchdog Packets (default: 10 watchdog packets)
</UL>
<P>The default values apply to IntranetWare, NetWare 4, and NetWare 3. You
can use the SET utility to change these parameters on your server. For IntranetWare
and NetWare 4, you can also use the SERVMAN utility.</P>
<H4>SPX KEEP-ALIVE</H4>
<P>Because SPX applications are connection oriented, each SPX application
performs an SPX "handshake" with its partner before transferring
data. Each side of an SPX connection is called a partner. For example, if
you were to use Novell's RCONSOLE utility, this utility would instruct the
Novell client on your workstation to initiate a connection with the server
that supports the RSPX and REMOTE NetWare Loadable Modules (NLMs). The SPX
partners in this case are the Novell client (acting on behalf of the SPX
application) and the server.</P>
<P>Because an SPX application sends an acknowledgment request with the data
being transmitted, the SPX partner sends an acknowledgment packet after
receiving this data. The following are common SPX applications:</P>
<UL>
<LI>NetWare for SAA Gateway<BR>
<BR>
<LI>Btrieve<BR>
<BR>
<LI>Print server applications such as Novell's PSERVER utility and Hewlett-Packard's
JetDirect<BR>
<BR>
<LI>Backup applications such as Cheyenne's ARCserve and Seagate's Backup
Exec for NetWare
</UL>
<P>SPX applications such as the ones listed above use a keep-alive, or watchdog,
process that is similar to the NCP watchdog process: By default, the SPX
partners send watchdog packets to each other after their connection has
been idle six seconds. For example, <A HREF="wanf387.html">Figure 3</A>
shows SPX watchdog traffic from an idle RCONSOLE session.</P>
<P>You can decrease SPX watchdog traffic in the following ways:</P>
<UL>
<LI>Increase the time before the SPX watchdog process begins, and increase
the interval between the SPX watchdog packets.<BR>
<BR>
<LI>Disable the SPX watchdog process at the workstation to stop the Novell
client from sending SPX watchdog requests to the server. (However, the
client will still answer SPX watchdog requests from the server.)<BR>
<BR>
<LI>Purchase a router that can perform SPX watchdog spoofing.
</UL>
<H4>Increase Time Before the SPX Process Begins</H4>
<P>To decrease the number of SPX watchdog packets sent over a WAN link,
you can change the following SPX parameters.</P>
<UL>
<LI><B>SPX Watchdog Verify Timeout.</B> This parameter specifies the time
in ticks that an SPX partner waits before requesting a watchdog packet
from its SPX partner. (A tick is approximately 1/18 of a second. Default:
108 ticks.)<BR>
<BR>
<LI><B>SPX Ack Wait Timeout.</B> This parameter specifies the time in ticks
that an SPX partner waits for an acknowledgment packet before resending
an SPX watchdog packet. (Default: 54 ticks.)<BR>
<BR>
<LI><B>SPX Watchdog Abort Timeout.</B> This parameter specifies the time
in ticks that the SPX partner waits without receiving an acknowledgment
packet from its partner before concluding that the connection is no longer
valid. (Default: 540 ticks.)
</UL>
<P>For example, to make the server wait a longer time before sending an
SPX watchdog query, you would increase the SPX Watchdog Verify Timeout parameter
and the SPX Ack Wait Timeout parameter. You could increase the SPX Watchdog
Verify Timeout parameter to 14 seconds, and you could increase the SPX Ack
Wait Timeout parameter to three minutes.</P>
<P>On an IntranetWare or NetWare 4 server, you can use the INETCFG utility
to change the SPX parameters. (You must load the INETCFG utility at the
IntranetWare or NetWare 4 server console.)</P>
<P>You can also change the SPX parameters at the workstation level. If you
are using Novell's NETX shell or Virtual Loadable Module (VLM) client, you
can change SPX watchdog parameters in the NET.CFG file. If you are using
Novell's IntranetWare client or NetWare Client 32, you can change the SPX
parameters by accessing your Windows 95 Control Panel. Then you select Network,
IPX 32-bit Protocol for Novell NetWare Client 32, and SPX.</P>
<P>Changing these parameters can significantly reduce the overhead on a
WAN link. If you have a dial-on-demand WAN link, however, you should disable
the SPX watchdog process or purchase a router that performs SPX spoofing.</P>
<H4>Disable the SPX Watchdog Process</H4>
<P>You can also prevent an SPX application on your workstation from using
the SPX watchdog process to periodically validate SPX connections. If you
are using Novell's NETX shell or VLM client, you can disable the SPX watchdog
process by entering SPX WATCHDOGS = OFF under the PROTOCOL IPX heading in
the NET.CFG file.</P>
<P>Of course, the Off setting specifies that the workstation cannot use
the watchdog process. However, using the Off setting does not disable the
SPX watchdog process at the server. If the server sends an SPX watchdog
request to your workstation, the Novell client still answers this request.</P>
<P>If you are using the IntranetWare client or the NetWare Client 32, you
can disable the SPX watchdog process by accessing your Windows 95 Control
Panel. Then select Network, IPX 32-bit Protocol for Novell NetWare Client
32, and SPX. You must then deselect the Allow Connection Watchdogging option.</P>
<P>If you want to disable the SPX watchdog process at the server, you can
use the SPXWDOG NLM. You can download this NLM from the Novell Support Connection
World-Wide Web (WWW) site at <A HREF="http://support.novell.com/">http://support.novell.com</A>.
(Use the search engine to find the STRTL5.EXE file.)</P>
<H4>Purchase a Router That Performs SPX Watchdog Spoofing</H4>
<P>To eliminate SPX watchdog traffic across a WAN link, you can use a router
that performs SPX watchdog spoofing. For example, Cisco's IOS Software 11.1
includes an IPX/SPX spoofing parameter that enables the router to respond
to SPX watchdog packets on behalf of your workstation. (For more information
about Cisco's IOS Software 11.1, see <A HREF="http://www.cisco.com/warp/public/732/Releases">http://www.cisco.com/warp/public/732/Releases</A>.)</P>
<H4>QUEUE SAMPLING</H4>
<P>Your printer configuration can also generate unnecessary traffic if you
assign a print server to a remote printer that is located on the other side
of a WAN link. When a printer is idle, the print server assigned to that
printer queries its print queue at regular intervals. This process is called
<I>queue sampling</I>, or <I>queue polling</I>.</P>
<P>IntranetWare and NetWare 4 have a default queue sampling interval of
five seconds; NetWare 3 and NetWare 2 have a default queue sampling interval
of 15 seconds. (The <I>queue sampling interval</I> is the number of seconds
between each query.) Unless you have changed the default setting, the print
server looks for jobs in the print queue every five to 15 seconds, depending
on which version of the operating system you are running. This queue sampling
is a nightmare for WAN links.</P>
<P>You can solve this problem in one of two ways:</P>
<UL>
<LI>Do not configure a print server to service print queues that are located
on the other side of a WAN link.<BR>
<BR>
<LI>Use Novell's NetWare Administrator (NWADMIN) utility or Novell's PCONSOLE
utility to increase the queue sampling interval to the maximum setting,
which is 255 seconds. (See <A HREF="wanf487.html">Figure 4</A>.)
</UL>
<H4>CONCLUSION</H4>
<P>Analyzing the communications sent across your company's network is essential--what
you don't know can hurt you. If network devices are sending serialization
packets, NCP watchdog packets, SPX watchdog packets, and queue sampling
packets across a WAN link, you should prevent these packets from crossing
the WAN link or reduce the number of packets being sent. Taking these steps
will improve performance and even reduce costs if your company has a dial-on-demand
WAN link and pays for this link on a per-packet basis.</P>
<P><I>Laura Chappell researches, writes, and lectures on NetWare protocol
performance, troubleshooting, and optimization. She speaks at NetWare Conferences
and presents customized training courses on network analysis. You can reach
Laura at <A HREF="mailto:lchappell@imagitech.com">lchappell@imagitech.com</A>,
and you can view her trace files and presentation notes at <A HREF="http://www.imagitech.com/">www.imagitech.com</A>.
</I></P>
<P><I>NetWare Connection</I>, August 1997, pp.32-37</P>
<P><!-- This document was created using BeyondPress(TM) 2.0 -438062. -->
<!-- Begin footer.html -->
</FONT>
</TD>
</TR>
</TABLE>
<!-- -->
<FORM METHOD="get" ACTION="/cgi-bin/custom/corp/selector.sh">
<TABLE CELLPADDING=0 CELLSPACING=0 BORDER=0 WIDTH=555 NOWRAP COLUMNS=4>
<TR>
<TD WIDTH=40 NOWRAP></TD>
<TD WIDTH=14 VALIGN=top rowspan=2 NOWRAP><IMG SRC="/miscart/templates/1997/footer_left.gif" ALIGN=BOTTOM WIDTH="14" HEIGHT="29"></TD>
<TD WIDTH=501 HEIGHT=12 VALIGN=top COLSPAN=2 NOWRAP><IMG SRC="/miscart/templates/1997/pixel_b.gif" WIDTH="501" HEIGHT="1"></TD>
</TR>
<TR>
<TD></TD>
<TD VALIGN=top> <SELECT NAME="Instant Navigator">
<!-- INSTANT NAVIGATOR GOES HERE -->
<OPTION SELECTED>Instant Navigator
<OPTION>ManageWise
<OPTION>Developernet
<!-- END INSTANT NAVIGATOR -->
</SELECT> <INPUT TYPE=image SRC="/miscart/templates/1997/footer_go.gif" ALT="go" WIDTH="17" HEIGHT="9" BORDER="0">
</TD>
<TD ALIGN=right VALIGN=center>
<FONT FACE="times" SIZE=-2>
<!-- <A HREF="wrong.html">Text Only Version</a> -->
<!-- EMAIL ADDRESS FOR YOUR SECTION GOES HERE -->
<A HREF="/nwc/feedback.html">Feedback</A>
<!-- END EMAIL ADDRESS -->
| <a href="/nwc/copyright.html">© 1997 NUI, Inc.</a>
</FONT>
</TR>
<TR>
<TD WIDTH=40 NOWRAP></TD>
<TD WIDTH=14 NOWRAP></TD>
<TD VALIGN=CENTER COLSPAN=2>
<br>
<font face="helvetica, arial" size=-2>
<a href="/">NOVELL HOME</a> >
<a href="/nwc/">NETWARE CONNECTION</a>
<br><br>
<a href="/nwc/sub.html">Subscriptions</a>
<a href="/nwc/resources/">Resources</a>
<a href="/nwc/bookstor/">Bookstore</a>
<a href="/nwc/advertis.html">Advertisers</a>
<a href="/nwc/past/">Past Issues</a>
</font>
</TD>
</TR>
</TABLE>
</FORM>
<!-- END FOOTER -->
</BODY>
</HTML>
--------------58A9331E4B33--
|
|