Letters to the Editor
Paying Attention to WAN Traffic
I felt compelled to write you a letter after reading Laura Chappell's
excellent article, "Preserving WAN Bandwidth."
[See NetWare Connection, Aug. 1997, pp. 3237.] As someone who
installs and manages Bay Networks BCN and 3Com NETBuilder routers, I am
relieved that the networking industry is finally recognizing that a router
is more than plug-and-play. The information in Laura's article is invaluable,
particularly to many of my customers who are paying by the frame for frame-relay
services.
Steve Bellan
Installing Novell Administrator for Windows NT
After reading Sandy Stevens's article "Novell
Administrator for Windows NT: One-Stop Management for Your Network,"
I decided to try the product. [See NetWare Connection, June 1997,
pp. 614.] However, I have attempted to install Novell Administrator
for Windows NT several times, and the installation process continues to
fail. Do you have any troubleshooting tips that I can use?
Joseph Pechulis
I suggest that you uninstall Novell Administrator for Windows NT before
you start the installation process again. To uninstall the product, select
the Add/Remove Programs option in the Windows NT Control Panel. Then select
Novell Administrator for Windows NT, and click the Remove button.
Whether you are installing or uninstalling Novell Administrator for
Windows NT, you must be authenticated as the ADMIN user or an ADMIN-equivalent
user to the Novell Directory Services (NDS) tree for which you want to extend
the NDS schema and create the NT Domain or NT Workgroup object. You must
also be logged in to the appropriate Windows NT domain or Windows NT workgroup
as a user with administrative rights. In addition, you must ensure that
your IntranetWare or NetWare 4 servers and your Windows NT servers meet
the minimum hardware and software requirements for Novell Administrator
for Windows NT.
The following tips might also help you:
- The NDS Event Monitor (NDSDM.NLM) uses Service Advertising Protocol
(SAP) to advertise its availability to the Object Replication Service that
runs on Windows NT. In order for Novell Administrator for Windows NT to
work properly, SAP must be enabled on all of the servers that are running
the NDS Event Monitor.
- If you have enabled SAP filtering on your company's network, this
filtering could cause problems with Novell Administrator for Windows NT.
Because the NDS Event Monitor uses SAP type 28E, you must ensure that SAP
type 28E is not being filtered out.
- The default shares must be turned on for all of your Windows NT
servers. These default shares, which are created by the Windows NT operating
system, should not be modified in most cases. Specifically, if a Windows
NT server is running the Object Replication Service, Novell Administrator
for Windows NT requires that the server's ADMIN$ share be turned on. If
this share is not turned on, Novell Administrator for Windows NT will not
be installed properly.
- All of the primary domain controllers (PDCs) and backup domain controllers
(BDCs) in Windows NT domains that are synchronized with NDS must be up
and running while you are installing Novell Administrator for Windows NT.
If any PDCs or BDCs are down, Novell Administrator for Windows NT will
not be installed properly.
- The internal IPX network number defined on your Windows NT servers
must be set to 0. You can change this number by selecting the Network option
in the Windows NT Control Panel. Then select the Services tab and the Protocols
tab. Finally, select IPX, and click the Properties button.
- You must ensure that you are using the most current version of Novell
Administrator for Windows NT, which you can download from Novell's World-Wide
Web site (http://www.novell.com/novellsw/brands.html).
The installation program included with earlier versions of Novell Administrator
for Windows NT did not bring up the installation error log file at the
end of the installation process. This log file is critical when you are
troubleshooting installation errors.
Sandy Stevens
NetWare Connection, October 1997, p.4