Frequently Asked Questions (FAQ) for NOVELL@LSV.SYR.EDU Version: 20000326 The FAQ attempts to cover Netware 3.x, 4.x, and 5.x and is organised into sections. A change log is available. The FAQ is currently under heavy construction and re-organization. As a result you'll see that a lot of entries are marked as "deleted". This simply means that I don't want to have to renumber all of the sections until I've finished shuffling things around. Material for the FAQ is always welcome. One good way to immortalize yourself is to submit a question (and answer) for the FAQ. Also, if you spot any errors in the FAQ, please contact the FAQ maintainer. The current FAQ maintainer is Peter Burtt (phb@nbnet.nb.ca). TABLE OF CONTENTS A. INTRODUCTION -- QUICK INDEX A.1 What is this "FAQ" file? A.2 How can I get the FAQ? A.3 How are questions added to the FAQ? A.4 Things that should be in the FAQ but currently aren't B. THE MAILING LIST -- QUICK INDEX B.1 LISTSERV -- what is it? B.2 Commands to LISTSERV B.3 Posting a message to the list B.4 List sysops B.5 Guidelines to network etiquette B.6 Other useful mailing lists/newsgroups B.7 Archived messages from the mailing list C. Pointers to other resources -- QUICK INDEX C.1 Novell user groups C.2 Official FTP sites for Novell files C.2.1 Official GOPHER site for Novell files and Information C.3 Other useful FTP sites C.4 Novell's phone numbers C.5 Recommend reading C.6 WWW links of note C.7 NetWare Free, Patching, Patches and Version FAQs locations C.8 Off-line alternatives D. NOVELL Security, passwords, etc. -- QUICK INDEX D.1 Misc. security info D.2 What to do if you've lost your SUPERVISOR password. (NW 2.x & 3.x) D.3 What to do if you've deleted your ADMIN account. (NW 4.x & 5.x) D.4 What to do if you've locked yourself out of the console (NW 3.x & 4.x) E. TCP/IP AND NETWARE -- QUICK INDEX E.1 What is TCP/IP E.2 Why you might want TCP/IP and Netware to co-exist E.3 Packet drivers/ODI drivers/NDIS drivers E.4 deleted E.5 Routing TCP/IP through a file server E.5.1 Why TCP/IP Routing Doesn't Always Work As Expected E.5.2 Security considerations of allowing IP Source Routing E.6 Setting up a Netware server as an FTP server E.7 BOOTP and RARP F. ELECTRONIC MAIL -- QUICK INDEX F.1 Pegasus Mail F.2 Setting up an Internet gateway for Pegasus Mail -- Charon F.3 Another Internet gateway for Pegasus Mail -- Mercury F.3.1 Pegasus/Mercury plus NetWare 4.1 considerations F.4 Other electronic mail packages F.5 Eudora F.6 DNS and smart mailer G. PRINTING -- QUICK INDEX G.1 Printing to/from Unix systems G.2 Sharing PC and Macintosh printers G.3 Getting garbage in printouts G.4 Alternatives to PCONSOLE & PSTAT for monitoring printer queues G.5 Relocating print queues G.6 Do postscript printer viruses exist? G.7 Printing to the right queue without running Win / Print / Setup G.8 Alternatives to PSERVER for more than 16 printers, etc. G.9 Print Server auditing programs G.10 Running NPrinter or RPrinter without being logged in G.11 Page counting software H. MISC -- QUICK INDEX H.1 Booting a server without running STARTUP.NCF/AUTOEXEC.NCF H.2 How to login without running the system/user login script H.3 Remotely controlling a PC with a telnet compatible program H.4 Getting userIDs and other information into programs H.4.1 Environment variables H.4.2 Piping in information from WHOAMI H.4.3 Novell APIs H.4.4 Third Party Utilities H.5 What do all those columns in STAT.NLM v2.0 mean? H.6 Changing the number of licenced users on a Netware server H.7 Register memory ("Cache memory alloc. out of avail. memory" msg) H.8 Full Duplex versus Half Duplex ethernet H.9 deleted H.10 Getting a list of usernames on a server to an ASCII file H.10.1 Creating users from an ASCII file H.10.1.1 Mass User Management H.10.1.2 UImport -- reads an ASCII text file and adds users H.10.1.3 ScanUser -- scans/creates unknown/missing Mail directories H.10.1.4 BULKLOAD.NLM -- imports users from an LDIF file H.11 Remote access to a LAN H.12 Short Term Memory -- how much does your server need? H.13 BTRIEVE -- what do I need? H.14 deleted H.15 Synchronising workstation time with server time H.16 Problems with disks and tape drives on Adaptec SCSI controllers H.17 deleted H.17.1 Suitable NICs for the NetWare server itself H.18 Fax products for NetWare H.19.1 Backup software products for NetWare H.19.2 Backup hardware products for NetWare H.19.3 Backup methodologies H.19.4 Disaster Recovery methodologies H.20 Resetting Intruder Detection for Supervisor ID H.21 Testing that the Login process was successful H.22 Cron-like programs H.23 Anti-Virus programs H.23.1 A bit of an Anti-Virus tutorial H.24 How can I keep my server on time? H.24.1 What is my TIMEZONE? H.25.1 NetWare Memory Requirements -- Time To Worry? H.25.2 NetWare Memory Requirements -- How Much Is Enough? H.25.3 NetWare Memory Requirements -- And The Real World H.26 How to wire 10base-T cable using RJ-45 jacks H.27 Advantages of purging files H.28 Moving user rights/passwords from server to server H.29 Spanning a volume across multiple hard drives H.30 Load Balancing NLMs H.31 Should I use SCSI or IDE hard drives on the file server H.32 Expected bandwidth from "10 Mbit" ethernet H.33 Performance considerations of Bridges versus Routers H.34 Data Transfer by Bus type H.35 Maximum wiring lengths H.36 AC Power and its effect on file servers H.37 Negative numbers from CHKVOL -- yup, time to worry H.38.1 Running Netscape across NetWare (vs dial-up) H.38.2 Running Netscape wherever (without dial-up facilities) H.39 Help Desk software for NetWare H.40 Deleting very large "sparse" files H.41 Slow mount of 50 GB drive array H.42 Clearing "Not-Logged-In" license robbers H.43 Running alternatives to MONITOR on the server console H.44 NLMs allowing access to NetWare Server C drive H.45 NLM to delay loading of AUTOEXEC.NCF NLMs H.46 Checksum errors showing up on MONITOR.NLM screen H.47 deleted H.48 Fixing NetWare partition problems when Mac support NLMs are used H.49 deleted H.50 Running a World Wide Web server on NetWare H.51 Testing the strength/security of your users' passwords H.52 Faster (but riskier) re-mirroring after server crash H.53 Sharing a modem across a NetWare network H.54.1 Using the Debugger to determine the cause of the ABEND H.54.2 Help for Debugger commands H.55 Network management utilities H.56 Only see 2 GB of disk space in DOS/Win when U know HD/volume is bigger I. SAMPLE CONFIGURATIONS -- QUICK INDEX I.1 Comparison between NETX and VLM NetWare Client Software I.2 Sample Appletalk entries in AUTOEXEC.NCF J. NETWARE 4.X MATERIAL -- QUICK INDEX J.1 Installing Netware 3.12 or 4.0x without a CD-ROM drive (sort of) J.2 Dumping your configuration to an ASCII file J.3 To Upgrade or Migrate to NetWare 4.1 J.3.1 Upgrading to NetWare 3.12 instead of NetWare 4.1 J.3.2 Upgrading from NetWare 3.11 to NetWare 3.12 J.4 Disable Login Banner J.5 Backing up/Restoring NDS -- multiple methodologies J.6 Handling NetWare 4.x Page Faults J.7 NetWare 4.x block size, compression and sub-allocation J.7.1 Alternative compression products J.8 Expanding the size of the NetWare SYS volume J.9 NetWare 4.1 NLM version list J.10 NetWare 4.1 NLM patch list J.11 The Novell Consulting Services (CD-ROM) Toolkit J.12 Gaining access to the Admin password on a NetWare 4.x Tree J.13 NetWare 4.10 SFT-III (System Fault Tolerance III) J.13.1 Considerations J.13.1.1 Backup Considerations J.13.1.2 UPS Considerations J.13.1.3 MSL Considerations J.13.1.4 Network Management Considerations J.13.2 SFT-III and Raid 5 J.13.3 Will SFT-III work on NetWare 3.12 ? J.13.4 Will NetWare Connect work on SFT-III ? J.13.5 ARCserve 5.01g and SFT-III configuration J.13.6 TCP/IP and SFT-III configuration J.13.7 SFT-III Engines swapping J.13.8 MS_Engines produced a different output J.13.9 Additional information J.13.10 Other products of interest: Vinca StandbyServer J.14 Mirroring K. SOME USEFUL TEXTS & SOFTWARE -- QUICK INDEX K.1 The Novell Companion K.2 LAN Connectivity from New Rider Publishing K.3 Using NetWare 4 K.4 Novell's guide to NetWare LAN analysis K.5 Novell's SDK CD-ROM K.6 EMS Professional Shareware NetWare CD-ROM K.7 Shareware NetWare API Library K.8 Quickpath to NetWare 4.1 Networks K.9 Novell Application Notes K.10 The NSE Pro CD K.11 Netware 4 Administration K.12 Using NetWare 4.1 - The Most Complete Reference L. ETHERNET FRAME TYPES: DON PROVAN'S DEFINITIVE ANSWER -- QUICK INDEX L.1 Introduction L.2 The Physical Structure of the Four Ethernet Frame Types L.3 The Political Origin of the Four Ethernet Frame Types L.3.1 Where did Ethernet_II come from? L.3.2 Where did Ethernet_802.2 come from? L.3.3 Where did Ethernet_802.3 come from? L.3.4 Where did Ethernet_SNAP come from? L.3.5 Why does IPX run on all four frame types? L.4 Should You Use Ethernet_802.3? L.4.1 What frame type Joe D. uses L.5 Which Ethernet frame type should I use for IPX? M. OBTAINING CNE QUALIFICATION -- QUICK INDEX N. CD-ROM MATERIAL -- QUICK INDEX N.1 How do I get to see a CD drive on my Netware v3.12 server? N.2 100% CPU utilization when mounting a CD-ROM N.3.1 CD-ROM software products for NetWare N.3.2 CD-ROM hardware products for NetWare N.4 CD-ROM resources via the WWW N.5 Mounting an IDE CD-ROM on a NetWare server N.6 Mapping CD-ROM drives N.7 Save grey hairs - don't use CDs! O. NETWARE AND VISUAL BASIC -- QUICK INDEX O.1 Obtaining files demonstrating Visual Basic with Netware O.2 Visual Basic and Netware AppNotes O.3 Visual Basic and Netware Books O.4 Apiary's Developer Suite for NetWare - VB 4.0 Edition O.5 NetBasic & Visual NetBasic P. SELECTED ERROR MESSAGES AND WHAT THEY MEAN -- QUICK INDEX P.1 "Lan receive buffer limit reached" P.2 "Primary Interrupt Controller Detected A Lost Hardware Interrupt" P.3 "Loader cannot find public symbol..." P.4 Getting rid of *all* NetWare system messages on a client PC P.5 Using the Message Timeout option of the VLM P.6 Non Maskable Interrupt (NMI) detected Q. NOVELL AND WINDOWS 95 -- QUICK INDEX Q.1 Which client should I use for Win95? Q.2 Upgrading to Windows 95 Q.3 deleted Q.4 Server install note Q.5 Long filename install workarounds Q.6 Crippled MS NetWare Requestor stack Q.7 NetWare 4.x NDS and Windows 95 Q.8 deleted Q.9 Telling Windows 95 to back-off! Q.10 Let's be clear...this is a _NOVELL_ list Q.11 The best version of the Windows 95 Help File is... Q.12 deleted Q.13 Windows 95 + SAPs .NE. NetWare file server !!! Q.14 Is there any way to check the version of Client32 for Win95? R. Historical Material -- QUICK INDEX R.1 Sample NET.CFG (NETX) R.2 Sample NET.CFG (VLMs) R.3 Tuning the NetWare DOS requestor (memory, performance, etc.) R.4 Sample STARTNET.BAT (VLMs) R.5 Booting Windows 95 from NetWare on a disk-less workstation R.6 Running Windows 95 with VLMs R.7 Joe D's sample NW 3.12 .NCF files R.8 Why can't I format a floppy under Windows when using boot ROM? R.9 Why can't multiple TCP/IP stacks run on a DOS workstation? R.10 Using EMM386 with Boot ROM (ie. diskless) workstations R.11 Windows 3.x BSOD (Black Screen of Death) fix S. FURTHER INFORMATION -- QUICK INDEX S.0 NOVTOP10.TXT - Top "10" NetWare Related Internet Sites S.1 311-312A.TXT - Info on Updating a NetWare 3.11 server to 3.12 S.2 311-312B.TXT - Info on Upgrading a NetWare 3.11 server to 3.12 S.3 31x-41x.TXT - Email thread on Upgrading NetWare 3.1x to 4.10 S.4 AUDITCON.TXT - Email thread on NetWare's Auditing Facilities S.5 BRIDGING.TXT - Info on NetWare 4.x Bridging S.6 ETHvsTRx.TXT - Email thread on Ethernet versus Token Ring S.7 FTP&HTTP.TXT - Info on NetWare Hardware/Software Vendors S.8 INTERNET.TXT - Email thread on Netware & The Road Ahead S.9 INTRO2IP.TXT - Info on the Internet Protocol S.10 IPX-2-IP.TXT - Email thread on IPX to IP Convertors S.11 NETNOTFY.TXT - NetNotify Bulletin & Notification mailing list S.12 NOT-NEWS.TXT - Info on this NOVELL-specific mailing LIST S.13 NOV-100.TXT - Email thread on NetWare 4.x 100% Utilization issue S.14 NOV-ATM.TXT - Email thread on NW & Asynchronous Transfer Mode S.15 NOV-BAKx.TXT - Email thread on NetWare Backup issues S.16 NOV-BIO.TXT - Info on contributors to the Novell Internet List S.17 NOV-BM.TXT - Email thread on Novell Border Manager S.18 NOV-BR9x.TXT - Notes & thread on BrainShare'95, '96 & Green River S.19 NOV-BSOD.TXT - Info on NetWare and the "Black Screen of Death" S.20 NOV-CD.TXT - Email thread on NetWare Server CD-ROMs S.21 NOV-CNEx.TXT - Email thread on NetWare and CNE certification S.22 NOV-COMx.TXT - Email thread on Netware and Serial Communication S.23 NOV-DHCP.TXT - Email thread on NetWare & DHCP S.24 NOV-FDDI.TXT - Email thread on Fiber Data Distributed Interface S.25 NOV-FTP.TXT - Email thread on ftp'able files for NetWare S.26 NOV-HDWx.TXT - Email thread on NetWare file server hardware S.27 NOV-ISDN.TXT - Email thread on NetWare across ISDN lines S.28 NOV-MAP.TXT - Email thread on NetWare drive mappings S.29 NOV-MEMx.TXT - Email thread on NetWare memory management S.30 NOV-MOAB.TXT - Email thread on NW's "Next Gen" IP-Only NOS S.31 NOV-MSCx.TXT - Email thread on miscellaneous NetWare topics S.32 NOV-NAL.TXT - Email thread on the Novell Application Launcher S.33 NOV-NCFG.TXT - Email thread on Net.cfg settings S.34 NOV-NDSx.TXT - Email thread on NetWare Directory Services S.35 NOV-NFSx.TXT - Email thread on the Network File System S.36 NOV-NICx.TXT - Email thread on Network Interface Cards S.37 NOV-NLI.TXT - Email thread on NetWare Not-Logged-In Clearers S.38 NOV-NLSP.TXT - Email thread on Novell Link State Routing Protocol S.39 NOV-NWIP.TXT - Email thread on NetWare IP (Internet Protocol) S.40 NOV-OS2.TXT - Email thread on NetWare and OS/2 S.41 NOV-PERx.TXT - Email thread on NetWare Performance Aspects S.42 NOV-RS.TXT - Email thread on Novell Replication Services S.43 NOV-SAP.TXT - Info on NetWare SAPs S.44 NOV-SCSx.TXT - Email thread on Netware and SCSI devices S.45 NOV-SET.TXT - Email thread on NetWare SET Commands S.46 NOV-SVY.TXT - Responses to Novell's "Your NW 4 wish list" survey S.47 NOV-TIMx.TXT - Email thread on NetWare & Time Synchronization S.48 NOV-UPS.TXT - Email thread on Uninterruptable Power Supplies S.49 NOV-VER.TXT - Email thread on NetWare Software Versions S.50 NOV-VLM.TXT - Email thread on NetWare and Virtual Loadable Modules S.51 NOV-W95x.TXT - Email thread on NetWare and Windows 95 S.52 NOV-WEB.TXT - Email thread on NetWare as a WWW Server S.53 NOV-WIN.TXT - Email thread on Windows 3.x and NetWare S.54 NOVABEND.TXT - Email thread on NetWare ABnormal ENDs S.55 NOVBOOKS.TXT - Email thread on NetWare Books S.56 NOVCONSF.TXT - The Comp.Os.Netware.Security Faq S.57 NOVEMAIL.TXT - Email thread on NetWare and Electronic Mail S.58 NOVERMSG.TXT - Email thread on NetWare Error Messages S.59 NOVFRAME.TXT - Email thread on Ethernet Frame Types S.60 NOVNCOPY.TXT - Analysis of what NCopy *Really* Does S.61 NOVPRINx.TXT - Email thread on NetWare Printing S.62 NOVSETUP.TXT - Email thread on NetWare Setup Methodologies S.63 NOVTCPIP.TXT - Email thread on NetWare and TCP/IP S.64 NOVVIRUS.TXT - Email thread on NetWare Anti-Virus Products S.65 NVCL-NT.TXT - Email thread on the NT Requestor for NetWare S.66 NVCL32Dx.TXT - Email thread on NetWare's Client 32 for DOS&Win S.67 NW-NEWSx.TXT - Selected items from the NetWare News Mail List S.68 NW-vsxNT.TXT - Email thread on NetWare versus Windows NT S.69 NW411.TXT - Email thread on (Intra)NetWare 4.11 S.70 NW4SAA.TXT - Email thread on NetWare for SAA S.71 NWSCRIPT.TXT - Email thread on NetWare Log-In Script Files S.72 NW4xFAQ.TXT - NetWare 4.x FAQ based on CIS forum Q&A's S.73 NWUFAQ.TXT - A well-aged FAQ on NetWare for Unix S.74 ODI-IPX.TXT - Info on the move by Novell to the ODI specification S.75 ROUTERS.TXT - Email thread on Routers and NetWare routing S.76 SECURTYx.TXT - Email thread on NetWare Security Issues S.77 SUBNETS.TXT - Email thread on Subnetting S.78 SWITCHES.TXT - Email thread on Network Switches S.79 TCPIPWIN.TXT - Info on Windows + TCP/IP for Internet access S.80 UNIXWARE.TXT - Info on Novell's UnixWare S.81 USERMGMx.TXT - Email thread on NetWare User Management S.82 UTAHSTD.TXT - Utah naming & numbering standard for Novell objects S.83 VLM-NETx.TXT - Email thread on VLMs versus NETx redirector S.84 W95_SAPs.TXT - Info on Windows '95's SAP "feature" S.85 WIN95BOO.TXT - Info on booting Windows '95 diskless from NW server S.86 deleted S.87 NOV-DNS.TXT - Email thread on NetWare & Domain Name Service S.88 NOV-LONG.TXT - Email thread on NetWare & Long filenames S.89 NOV-Y2K.TXT - Email thread on NetWare & and the Year 2000 S.90 NOV-ZEN.TXT - Email thread on NetWare & Zero Effort Networks S.91 Y2K.HTM - Email Comments on General Year 2000 Issues S.99 2BADDED.TXT - Misc. stuff not yet added to the FAQ QUICK INDEX And remember... "We don't run 'Novell', [Eric Schmidt] does" - Joe D. A. INTRODUCTION A.1 What is this "FAQ" file? This FAQ file is a list of Frequently Asked Questions, both administrative (how do I use this list?) and informational (where do I find this, how can I use this correctly?), that are asked often enough that it would be of general interest to post the answers to them periodically. A.2 How can I get the FAQ? The master Novell FAQ can be found here, and the index page contains a list of mirror sites. A.3 How are questions added to the FAQ? This FAQ is maintained as a service to the group. Most editorial opinions are those of the FAQ maintainer; if you disagree or spot an inaccuracy, or have a new question *with* answer that you would like included in the FAQ file, please email me directly phb@nbnet.nb.ca and I will attempt to include it in the next edition. I will edit answers to make the style consistent, but I cannot research answers. A.4 Things that should be in the FAQ but currently aren't Many items could be included in the FAQ, if people wish to contribute in any of the following areas (or create a new area): - The NetWare 5 section is still very sparse B. THE MAILING LIST B.1 LISTSERV -- what is it? LISTSERV is an automatic mailing list manager program. Each mailing list has a e-mail address which LISTSERV controls. For example the Novell mailing list has as its e-mail address NOVELL@lsv.syr.edu. LISTSERV forwards any mail sent to the list to all the people on the mailing list (in fact not all mail messages are forwarded: LISTSERV tries to catch spurious or faulty messages before they are forwarded). LISTSERV has its own e-mail address as well: the LISTSERV responsible for the Novell list can be found at LISTSERV@lsv.syr.edu. B.2 Commands to LISTSERV Any commands concerning the list (such as signing on or off the list) must be sent to LISTSERV and not to the list. Sending mail to the mailing list address, as opposed to the LISTSERV address will not only NOT get you subscribed, it will annoy over 3000 people world-wide, and use inordinate amounts of computer time around the world for no reason. To subscribe to the list, send the following mail to the above address: To: LISTSERV@lsv.syr.edu Subject: Doesn't matter Text/body of: subscribe NOVELL Your Full Name If you have problems subscribing to the list, contact novell-request@lsv.syr.edu. You may find it necessary to sign off the list (if you change e-mail address or job or find that there's too much mail to deal with). To get yourself removed from the list, send the following mail to the LISTSERV: To: LISTSERV@lsv.syr.edu Subject: Doesn't matter Text/body of: unsubscribe NOVELL If you have problems unsubscribing from the list, contact novell-request@lsv.syr.edu. By default, LISTSERV does not send you a copy of mail you post to the list. If you want to see mail you send to the list, send the following mail to the LISTSERV: To: LISTSERV@lsv.syr.edu Subject: Doesn't matter Text/body of: set novell repro To receiving mail in undigested format, send the following mail to the LISTSERV: To: LISTSERV@lsv.syr.edu Subject: Doesn't matter Text/body of: set novell NODIgest The NOVELL list now defaults to a digestified form, so that you get a day's worth of list traffic in one message. This change was done in 1994 to ease the mainframe's task of managing this list. To change to receiving list mail in a digest format, send the following mail to the LISTSERV: To: LISTSERV@lsv.syr.edu Subject: Doesn't matter Text/body of: set novell digest If you're in need to see all possible commands use: To: LISTSERV@lsv.syr.edu Subject: Doesn't matter Text/body of: INFO REFCARD [Thx A.B.] B.3 Posting a message to the list The address of this list is: NOVELL@lsv.syr.edu To post a message, all you need to do is send it as a mail note to the above address. Please see the etiquette rules (Question B.5) before you post a message. B.4 List sysops The sysops of the NOVELL@lsv.syr.edu mailing list include: Joe Doupnik jrd@cc.usu.edu David Harris david@pmail.gen.nz Dave Molta djmolta@sunrise.syr.edu David A. Cantrell david_cantrell@novell.com Glen Malling gmalling@mailbox.syr.edu [Thx Joe D.] B.5 Guidelines to network etiquette Remember, about three thousand people around the world read this list, and all of us think our time is valuable, as do you. Also, every message posted uses a great deal of computer and transmission time, because it is propagating around the world. Therefore, the polite user of this list will try to follow these guidelines: * Do not post subscribe/unsubscribe requests to the list. See how to do these tasks above, question B.2. * Do not post test messages to the list. The first time you have a substantial post, let that be your test. If you keep the file, you won't have to retype it in the event that for some reason it doesn't go through the first time. * Do not post "Is this list working?" messages to the list. E-mail links between computers may go down for some reason and it is much more likely that a link between you and the Internet has gone down than the list itself has gone down. If you ask, you should ask one of the list's sysops. See question B.4 for a list of the sysops. * Consult Novell, system, and application documentation before you post a question. Also, if your site has a computer support staff that deals with Novell issues (many universities do), consult with them before posting a question. * When you post to the list, please include an informative and accurate Subject: line. The traffic on this list is very high; this helps those people who have time only to read posts they may be able to help with, or that apply to their networks. Additionally, in your post, make sure to include all of the information people will need to respond. * If you post a question, and receive no response, please don't repost it. The people who read this list are very helpful--someone will answer the question if they can. If you don't receive an answer, you need to find professional consultants for your specific problem. Reposting will not get an answer, and will only waste the time and bandwidth mentioned above. * The purpose of this mailing list is to serve as a resource from which all participants can learn. Therefore, if you think an answer to a question will be of wider interest than the just the asker, please post it to the list (the default reply-to address) and/or the FAQ maintainer, Peter Burtt phb@nbnet.nb.ca. * Don't flame people. If some information is presented that is incorrect or incomplete, please do post a message offering the correction. But don't make personal attacks on the list members. That has no place on this list. * Include your email address at the bottom of your postings. This will allow people to correspond directly with you, since most mail systems, by default, normally default your reply to the entire list. * If you use a signature, please make it no longer than four lines, and don't include "graphics" composed of ASCII characters. Remember, everyone's time is valuable, and some people read this mailing list at a very slow baud rate and/or pay for their connection "by the pound". Long signatures, and frivolous graphics just frustrate them; they may take to deleting your messages unread. * Please do not send HTML, MIME, or attachments to the list. Bandwidth is still an issue for many readers, and many of us still use email software that only understands ASCII. * When you reply to a message, include just enough of the previous message for readers to remember what the issues were. It is not necessary to include the whole message again and is expensive for those mentioned above. * When you post a message, use proper upper *and* lower case. In the eWorld, all uppercase text is considered SHOUTING and uppercase messages are much harder to read. People may just delete or skip your messages without even giving them a chance. * Please post to the list *only* in English. If you are posting in any other language, obviously you did not intend to communicate with the entire list, as this is an English language list. Therefore, private email would be more appropriate. * Do not post lines longer than 77 characters. Some mailers do not handle long lines well. When quoted, these lines grow, compounding the problem. Failing to heed this advice could cause you to receive, from S.M.D., your own copy of the following humorous note: Please use your Return or Enter key _before_ you reach 80 chara cters. Otherwise, your article becomes very difficult to read. If it is very diffic ult to read, then people are less likely to read it. If less people read it, y ou are not as likely to get the responses you desire. * If you reply to a message on the list, consider if you should reply to the entire list or to the sender (a private reply). It's a good idea to reply privately if you ask a question of the sender, or if you are thanking someone or if the sender asks for a private reply. You should consider replying to the list if the reply is of general interest or if you are contributing to an ongoing discussion. B.6 Other useful mailing lists/newsgroups Other mailing lists you may want to try are include: * BANYAN-L@akronvm (internet BANYAN@vm1.cc.uakron.edu), send subscriptions to LISTSERV@akronvm (internet LISTSERV@vm1.cc.uakron.edu). This is for discussion of Banyan networks. * BIG-LAN@suvm (internet BIG-LAN@suvm.acs.syr.edu), send subscriptions to the LISTSERV@suvm (internet LISTSERV@suvm.acs.syr.edu). * CICA-L@ubvm.cc.buffalo.edu for announcements of Windows uploads to CICA. To subscribe, send mail to LISTSERV@ubvm.cc.buffalo.edu with the message SUBSCRIBE CICA-L Firstname Lastname. * CUTCP-L@nstn.ns.ca for a discussion of Charon and CUTCP Telnet issues. Send subscription requests to LISTSERV@nstn.ns.ca. * Garbo-Ann@Garbo.uwasa.fi for announcements of Garbo uploads. To subscribe, send mail to Majordomo@Garbo.uwasa.fi with the message SUBSCRIBE GARBO-ANN Firstname Lastname. * MSDOS-ANN@@SimTel.Coast.NET for announcements of SimTel uploads. To subscribe, send mail to LISTSERV@SimTel.Coast.NET with the message SUBSCRIBE MSDOS-ANN. * MSMAIL-L@YALEVM.CIS.YALE.EDU for Microsoft Mail. To subscribe, send mail to LISTSERV@YALEVM.CIS.YALE.EDU with a text/body message of SUBSCRIBE MSMAIL-L Firstname Lastname * IntranetWare News Info list. To sub, send email to intranetwarenews@novell.com with a text/body line of subscribe intranetwarenews [your_e-mail_address] [Thx Robert Sfeir and Steve Sathue] * NGW@lists.teltrust.com for discussion on Novell's GroupWise. To subscribe, send mail to majordomo@lists.teltrust.com with text/body line of "subscribe NGW ". For help, send email to: ngw-admin@teltrust.com. [Thx Trevor Harrison for this info] * NWP@lists.teltrust.com for programming under Netware. Send email to listproc@lists.teltrust.com with any subject line and text/body line of "subscribe NWP YourFirstName YourLastName" * PMAIL@ua1vm.ua.edu for discussion of Pegasus Mail. The author, David Harris, is active on this list. Send subscription and other administrative requests to LISTSERV@ua1vm.ua.edu. * WFW-L@umdd.umd.edu for Windows For Workgroups. Send subscription and other administrative requests to LISTSERV@umdd.umd.edu. * Windows-nt@mailbase.ac.uk. Send the command "JOIN Windows-nt firstname lastname" to mailbase@mailbase.ac.uk. I also recommend you issue the command "SEND mailbase user-guide" to mailbase@mailbase.ac.uk if you do join up. Additionally, if you have access to usenet news, you may want to subscribe to the newsgroup comp.os.netware.misc, which is a "mirror" of this mailing list but you may not be able to post messages to this list if you are only subscribed to the newsgroup (you can subscribe to the list, and then set your subscription to NOMAIL, and thus be able to post questions [or answers!] to the list. There are also the following newsgroups: comp.os.netware.announce (moderated announcements) comp.os.netware.security (security issues) comp.os.netware.connectivity (connect. issues incl. LAN Workplace) comp.os.netware.misc (topics not falling into the above categories) [Thx J.B., Bengt Bolinder and S.M.D. for this info] For more comprehensive sources of mailing lists on all subjects, on info.umd.edu (128.8.10.29) you can find a list of listserv bitnet lists under /inforM/inforM/CompRes/NetInfo/Listserv/listserv-lists and the complete List of Lists is available as /inforM/inforM/CompRes/NetInfo/Internet/interest-groups. [Thanks to Chaisiri Wongkham for updating this info] Also, sending any listserv the command "list global" will get you a large (750k to 1MB) file of all public listserv lists. For a searchable directory of mailing lists that IS the world's largest, check out: http://www.liszt.com/ [Thx to Scott Southwick for this info] For similar searches spanning mailing lists, newsgroups, vendors, and FTP sites, try: http://www.tile.net/ [Thanks to Mark Holland for this info] B.7 Archived messages from the mailing list [As of 01/31/ The ability to search the NOVELL archive logs is again available. The old VM style search functions are not supported. There is a new user-oriented LISTSERV manual available at: http://www.lsoft.com/manuals/userindex.html OR ftp://ftp.lsoft.com/ftp/documents [Thx Glenn A. Malling, Novell Listserv Postmaster, gmalling@mailbox.syr.edu for this info] You can search the FAQ at http://netlab1.usu.edu/cgi-bin/texis/webinator/search/. There is a searcheable archive of the mailing list at http://lsv.syr.edu/scripts/wa.exe?S1=novell. Also, see Section S for archives on selected topics. C. Pointers to other resources C.1 Novell User Groups There are Novell user groups all over the world. For more information, including a list of user groups, check out http://www.novell.com/corp/community/nui/index.html While you're attending your local user group meeting, it couldn't hurt to mention how wonderful our mailing list is :) [thx. John L. Stevens & Randy Richardson] C.2 Official FTP sites for Novell files Novell has designated several FTP sites around the world as "official" mirrors of the Novell FTP server. These sites are updated at least once a week from the server in Utah. The mirrored FTP sites are available through the Internet as well as through other mechanisms like JANET in the UK and BBS systems in the Netherlands. In addition to the files from ftp.novell.com these servers may contain other useful information for managers of Novell networks. This is a list of the mirrors, their URLs, IP addresses and directories. BNUG FTP server ftp://bnug.harvard.edu *128.103.85.201* University of Groningen ftp://ftp.rug.nl/networks/novell *129.125.4.15* This server is updated daily. It is also available via BITNET and BBS (indirect) University of Salford ftp://ftp.salford.ac.uk/novell *146.87.255.21* Also available via JANET IP Utah State University ftp://netlab2.usu.edu *129.123.1.44* For Netscapers: ftp://netlab2.usu.edu/sys/anonftp Dir: /sys/anonftp subdirectories follow novell FTP. Index is the top level directory in each. Also available via BITNET, SPAN, Gopher (gopher.usu.edu) Lincoln University ftp://tui.lincoln.ac.nz/novell/novlib *138.75.90.4* University of Alabama ftp://risc.ua.edu/pub/network/novlib *130.160.4.7* Also available via BITNET National Research Council (Canada) ftp://novell.nrc.ca/netwire *132.246.160.4* (Actually mirrors nightly from Joe D.'s netlab2.usu.edu, thus Joe's WHATIS files, for example, are also on this mirror) United Kingdom ftp://ftp.novell.co.uk/pub United Kingdom ftp://ftp.mechnet.liv.ac.uk [Thanks to Steven Carpenter for this info] So how to find things on Novell's master FTP server (or on Netwire, Novell's Compuserve forum)? First obtain a copy of FORUM.DOS, packaged as either forum.zip or forum.exe typically in forum 01. That's a good summary but not always up to date nor explicit about filenames within archives. The Netwire archive changes daily. A full listing of the contents of each archive file, via Pkunzip,is the set of text files WHATIS.xxx in the Netwire directory on netlab2.usu.edu. "xxx" is the name of the forum, 01 etc. That suite is regenerated every week or two. The time/date stamp is shown for each file within a .zip/.exe archive. The Netwire archive contains over 1000 files totaling 100+MB, most are .zip/.exe collections. Thus if things were unpacked there would be tens of thousands of files. The archive is divided into forums with special purposes. Forum Novfiles contains hot items which will be moved to the numbered forums in due course. One is very unlikely to find files named RCONSOLE.NLM or similar in the archive as bare files; instead those will be within .zip/.exe archives of arbitrary filenames. Most Netwire files are self-extracting archives, to be found with .EXE extensions. For Rconsole, see netwire\novlib\04\rcnsle.exe, where the latest Rconsole material resides. Here is a cutout from netwire\whatis.04: Searching ZIP: NOVLIB/04/RCNSLE.EXE Length Method Size Ratio Date Time Name ------ ------ ----- ----- ---- ---- ---- 9147 Implode 3052 67% 04-17-91 10:36 RCONSOLE.HLP 83391 Implode 45356 46% 06-19-91 13:15 RCONSOLE.EXE 3042 Implode 1451 53% 08-26-91 10:00 READ.ME ------ ------ --- ------- 95580 49859 48% 3 To be complete, "Netwire" is formally the Novell area of Compuserve. The Novell owned files are placed on ftp.novell.com for anonymous ftp access. That is mirrored by a small number of official sites. At last, many of the user-contributed files to NetWire (Compuserve) are now available via anonymous ftp from your favorite mirror of Netwire, including from ftp.novell.com. See directory netwire\novuser which has 12 subdirectories 01..12 (11 and 12 are empty right now). File netwire\novuser\Index and text files netwire\novuser\whatis.xx (xx = 01..12) on netlab2 indicate the nature of each directory and the contents of each zip'd archive, respectively. A variety of archiving methods have been used by contributors, so don't expect PKUNZIP to work on all. Here is the big picture of the novuser area (file Index): User contributed material from Compuserve, Netwire\novuser NOVUSER Library Sections 1) New Uploads 2) Disk Drivers/Patches 3) LAN Drivers/Patches 4) Comm Drvs/Patches 5) Host/Unix Dvrs/Ptch 6) Printer Utils 7) Network (Sys) Utils 8) Client WS Utils 9) Management Tools 10) Text Files/Help 11) Job Postings 12) Classifieds The following is a list of indices for novell software on ftp.novell.com and mirrors: /netwire/novfiles/novfil.idx /netwire/novlib/01/forum.* (may be in /02/) /netwire/novlib/01/novchg.txt (may be in /02/) /netwire/novuser/01/taplib.exe /netwire/novuser/01/tapusr.exe /netwire/novuser/01/titles.exe On the netlab2.usu.edu only mirror, you can also find the following: /netwire/novuser/Index /netwire/novuser/whatis.* /netwire/versions/novlib04.ver /netwire/versions/novlib05.ver /netwire/versions/novlib06.ver ftp.novell.com is being moved away from the netwire library concept. The managers of ftp.novell.com advise that users should familiarise themselves with the pub2 directory tree. Information for the pub2 tree can be found in /pub2/00DIR. Each subdirectory in /pub2 also has a 00DIR index file. C.2.1 Official GOPHER site for Novell files and Information Novell has established an excellent Gopher-based site. It is must faster than the www site and is located at: http://support.novell.com The links on this site are just about everything a Netware support person could ever want or need. Explore! C.3 Other useful FTP sites Useful ftp sites, along with their Novell related directories include: ftp://splicer2.cba.hawaii.edu/files/novell ftp://splicer2.cba.hawaii.edu/files/pegasus *128.171.17.2* ftp://cc.usu.edu/slip ftp://cc.usu.edu/tcp-ip *129.123.1.1* ftp://risc.ua.edu/pub/network/novlib ftp://risc.ua.edu/pub/network/pegasus ftp://risc.ua.edu/pub/network/misc ftp://risc.ua.edu/pub/network/tcpip *130.160.4.7* ftp://wuarchive.wustl.edu/etc/system/novell *128.252.135.4* ftp://ftp.uni-kl.de/pub/novell *131.246.9.95* ftp://netlab.usu.edu/novell ftp://netlab.usu.edu/netwatch *129.123.1.11* ftp://chaos.cc.ncsu.edu/share/pc/novell ftp://chaos.cc.ncsu.edu/share/pc/utils ftp://chaos.cc.ncsu.edu/share/pc/email ftp://chaos.cc.ncsu.edu/share/pc/net ftp://chaos.cc.ncsu.edu/share/pc/manage *152.1.19.23* ftp://ftp.novell.de/pub/NetWire ftp://ftp.novell.de/pub/unix ftp://ftp.novell.de/pub/unixware ftp://ftp.novell.de/pub/drdos ftp://ftp.novell.de/pub/sjf-lwp *193.97.1.1* [Thanks to Mark Burgess and David Silverstein for this info] C.4 Novell's phone numbers The following list of numbers was extracted from a list sent by Sarah Peterson of Novell to Larry Bradley, which he kindly posted to our mailing list. I have included in the FAQ because I believe it is of general interest. These numbers were accurate as of November 18, 1991. DEPARTMENT/GROUP TOLL-FREE REGULAR After Market Products (AMP) 800-346-7177 801-568-8856 Anthem/Eagle (Ethernet) 800-733-2453 408-453-1200 API Development/Austin 800-RED-WORD 512-794-1795 Authorized Reseller Information 800-828-3362 Contract Inquires/AMP 800-346-7177 801-568-8856 Corporate Headquarters 800-453-1267 801-429-7000 Customer Success Portfolios 800-UPDATE1 801-429-5155 Developer Assistance 800-729-4357 Reseller Authorization 800-828-3362 LANalyzer Products 800-243-8526 408-473-8324 Literature Orders 800-UPDATE1 801-429-5155 NetWare Users International 800-228-4NUI Novell Education 800-233-3382 Novell Education FaxBack 801-429-5363 OURS Program 800-237-OURS Professional Developers Program (PDP) 800-RED-WORD 512-794-1795 Piracy 800-PIRATES 801-429-7600 Product Information 800-NETWARE 801-429-5155 Promotional Products 800-526-4483 RMA 800-NETWARE Technical Marketing Support 800-733-9673 Technical Support 800-NETWARE 801-429-5588 Technical Support/PDP 800-SAY-HELP 512-794-1795 Upgrades/Updates 800-UPDATE1 801-429-5155 Warranty Registration 800-458-7773 Novell BBS 801-429-3030 [Thx L.C.H.] C.5 Recommended Reading The quality of technical books is very uneven, it's nice to have someone you trust recommend a book so that one don't waste time and money on a poorly edited piece of trash that simply regurgitates the manual. Over the years, listers have recommended the following: Books about NetWare Thomas and Hughes, "The Four Principles of NDS Design" Books about TCP/IP For a gentle intro to TCP/IP, try Douglas Comer, "Internetworking with TCP/IP", vol 1 2nd edition, ISBN For a VERY detailed book, try W. Richard Stevens, "TCP/IP Illustrated", vol 1 ISBN 0-201-63346-9 Seriously, buy both of the above books, read Comer first and then Stevens. Jeff Doyle, "CCIE Professional Development: Routing TCP/IP" Vol I, ISBN: 1-57870-041-8 Books about DNS This is THE book on DNS. It is rather Unix centric, but is an excellent roadmap for understanding DNS on any platform. Albitz & Liu, "DNS and BIND", 2nd edition ISBN 1-56592-236-0 Books about networking h/w and protocols Andrew Tanenbaum, "Computer Networks" Rich Seifert, "Gigabit Ethernet" ISBN 0-201-18553-9 For an excellent discussion of switching and the spanning tree algorithm, try Kennedy Clark et al, "Cisco LAN Switching " [Thx Joe D., Hansang Bae, and probably many more] C.6 WWW links of note I have found the following links to be useful, I hope that you do, too. You can search the FAQ at http://netlab1.usu.edu/cgi-bin/texis/webinator/search/. There is a searcheable archive of the mailing list at http://lsv.syr.edu/scripts/wa.exe?S1=novell. Novell maintains a site which periodically adds case studies, tips, etc. about some of their products. info about ZEN - http://www.novell.com/coolsolutions/zenworks/ info about GroupWise - http://www.novell.com/coolsolutions/gwmag/ info about NDS - http://www.novell.com/coolsolutions/nds/ Novell maintains an online version of most of their documentation at http://www.novell.com/documentation/ You can search the knowledge base at http://support.novell.com/search/kb_index.htm Novell's AppNotes (an excellent monthly periodical with in depth explanations on a variety of subjects) can be found at http://developer.novell.com/research/appnotes.htm Programmers may be interested in Novell's monthly DeveloperNotes at http://developer.novell.com/research/devnotes.htm The Ethernet Page is an outstanding technical reference, located at http://wwwhost.ots.utexas.edu/ethernet/ You can find a database matching MAC addresses to a particular vendor at http://www.cavebear.com/CaveBear/Ethernet/ C.7 NetWare Free, Patching, Patches and Version FAQs locations A list of freeware NLMs is located at: http://mft.ucs.ed.ac.uk/novell/techsup/archive/freenlms.htm A FAQ on patching a Netware server is located at: http://mft.ucs.ed.ac.uk/novell/techsup/patchfaq.htm A FAQ on NLM patches is located at: http://mft.ucs.ed.ac.uk/novell/techsup/nlmpatch.htm And an NLM version FAQ is located at: http://mft.ucs.ed.ac.uk/novell/techsup/nlmver.htm [Thx G.J.S.] C.8 Off-line alternatives There is a NetWare CD-ROM containing 2,141 Public Domain/Free/Shareware programs and a database of 450 commercial add-ons available from EMS Professional Shareware, 4505 Buckhurst Ct., Olney MD 20832-1830, (301) 924-3594, Fax (301) 963-2708, ems@wdn.com. Novell Security, passwords, etc. D.1 Misc Security Info * The first rule of security is to physically secure the file server. Without physical security, there is no security - no OS in the world will fix this. * Another important principle is to keep up to date on patches/service packs for your server, client OS, and NW client s/w. Often these patches contain important security fixes. * RCONSOLE sends all information, including passwords, in clear text. Don't use RCONSOLE over the network, you're at the mercy of anyone with a packet sniffer. * Many would recommend that all passwords be written down, sealed in an envelope, and put in a safety deposit box or vault, etc. for emergencies. This provides insurance against you forgetting a password, and also protects your employer in the case that you suddenly aren't available. (i.e. win the lotto, get run over by a cement truck, etc etc.) Obviously this is only useful if the passwords are kept up to date. * In a similar vein, every NDS tree should have a backup admin account. Create a new account with a strong password, and give it full rights to the [ROOT] of the tree. Don't just make this account security equivalent to admin - if admin is deleted, then your backup account would lose it's rights. * Simple Nomad maintains an excellent NetWare Hack FAQ at http://www.nmrc.org. His step by step instructions on breaking into a NW server provide the administrator with a convenient checklist of holes to plug. This same page also includes information about "Pandora", an NDS reverse engineering effort. Very educational, for the admin as well as the cracker. D.2 What to do if you've lost your SUPERVISOR password. (NW 2.x & 3.x) Panic. :-) In fact there are several options you can try. SETSPASS.NLM, available via anonymous ftp from netlab2.usu.edu in misc or: ftp://ftp.zennet.com/pub/netware/ [Thx S.R.# allows you to change the SUPERVISOR password from the server console, as long as you know the serial number of your copy of Netware. SETPWD.NLM, which doesn't require that you have the serial number, is located in the same directory. LASTHOPE.NLM renames the 3 files NET$*.OLD to NET$*.TMP, and it renames the live bindery files NET$*.SYS to NET$*.OLD. ftp://netlab2.usu.edu/sys/anonftp/apps/lasthope.zip This effectively deletes the bindery, so you can log on to the server next time as SUPERVISOR with no password. This is truly a LAST HOPE if the bindery is irredeemable, as the bindery will have to be rebuilt manually, unless something can be done with the .OLD or .TMP files, or a backup. [Thx Michael Salem] If you have some unallocated disk space on the server you could create a new SYS: volume on that. This will create a new bindery as well as LOGIN, SYSTEM, PUBLIC and MAIL directories. However it is a bit drastic. Alternatively, *FOR NETWARE 2.X SERVERS ONLY*, you can try the following: 1. Bring the server down. 2. With some disk sector editing software (Norton Disk Edit for example) find the directory tables. 3. Change the name of files NET$VAL.SYS, NET$PROP.SYS, NET$OBJ.SYS to something else (preferably NET$VAL.OLD etc.) After that all user definitions will be deleted. 4. Bring the file server back up. 5. Login as supervisor (at that time you will need no password) 6. Find changed files in SYSTEM directory (they have attributes hidden, system), change their attributes to normal and be sure that they have extension ".OLD" 7. Run BINDREST program to get your original user definitions back. Now, you will have all your users including supervisor with their old definitions and passwords, but you are already in as supervisor and so you can change your password to anything you like. Note: It appears that in NetWare 2.x there are only two bindery files. For more information on this see the Hacking Netware FAQ at: http://www.nmrc.org/faqs/netware/index.html [Thx S.M.D. and Simple Nomad] You can also try to use your sector editor to edit the names used for the bindery files in SERVER.EXE. Unlike the previous NETWARE 2.X ONLY method, this has the advantage of not damaging the directory tables if things go wrong. Try the following steps: 1. Bring the server down. 2. Make a backup copy of SERVER.EXE. 3. With some disk sector editing software (Norton Disk Edit for example) change the name of files NET$VAL.SYS, NET$PROP.SYS, NET$OBJ.SYS where they occur in SERVER.EXE to something else (preferably TMP$VAL.SYS etc.) 4. Bring the file server back up. 5. Login as supervisor (at that time you will need no password) 6. Find changed files in SYSTEM directory (they have attributes hidden, system), change their attributes to normal and be sure that they have extension ".OLD" 7. Bring the server down again. 8. Restore your backed-up SERVER.EXE and reboot. 9. Run BINDREST program to get your original user definitions back. Now, you will have all your users including supervisor with their old definitions and passwords, but you are already in as supervisor and so you can change your password to anything you like. There is a program called BURGLAR that is designed to break passwords at: ftp://ftp.rhij.nl/cyco/burglar.nlm Note: BURGLAR creates a tempory user that is incomplete. Log in under this users name (and remove the account after use). BURGLAR was written by Bart Mellink from Cyco. http://www.cyco.nl There is additional information in the Hacking Netware FAQ at: http://www.nmrc.org/faqs/netware/index.html [Thx S.M.D. and Simple Nomad] D.3 What to do if you've deleted your ADMIN account. (NW 4.x & 5.x) As far as I know you have 4 choices... 1. You can just live with it. Probably not a good choice, but it IS cheap. 2. You can recreate the server from the last backup. A bad choice since data changed since the last backup will be lost. And it will cost a lot of downtime, or overtime, or both. 3. You can call Novell, and for $200 they will help you create a new Admin account. What they help you do will work once, right then. If your admin does it again, you're out another $200. 4. You can surf over to http://www.dreamlan.com and look for their makesu utility. It will let you create a new admin account, or elevate an existing account to admin status. It costs $100, you will have to prove you have the right to do work on the LAN in question, and it will only work in the tree you tell them you are working on. Moreover, the NLM will only run from a floppy. But... it will work again and again. A cool utility. [Thx Mike Avery] D.4 What to do if you've locked yourself out of the console (NW 3.x & 4.x) For NetWare 3.x, you can use the SUPERVISOR password to unlock the screen saver. If you're running NW4.x the hidden SUPERVISOR account's password will unlock the screen saver. The SUPERVISOR password will be whatever password was originally given to NDS when the server was installed into the tree. If (like most of use) you don't know this password, get yourself a copy of SYSCON, and use it to reset the SUPERVISOR password on the server, and then use that password to disable the screen saver. E. TCP/IP AND NETWARE E.1 What is TCP/IP TCP/IP is another networking protocol (like IPX) widely used in academic and commercial networks. It is used to allow different types of computers to communicate over a network. For further information, check out: http://www.futureone.com/~opeth/internetwork.html Also, check out the TCP/IP Transport Supervisor's Guide. [Thx H.B. & S.R.# "Daryl's TCP/IP Primer" is located at: http://ipprimer.windsorcs.com It is designed for people familiar with networking, but not necessarily familiar with TCP/IP networking. Includes a section on the differences between IPX and IP. [Thx D.B.# E.2 Why you might want TCP/IP and Netware to co-exist Many organisations have different types of computers on their networks. For example most universities have PCs and Unix or VAX computers on the network. Most Unix computers (and many others besides) use TCP/IP as a networking protocol. Also the Internet uses TCP/IP as its networking protocol. If your Netware PC users want to access Unix computers, they will most likely use TCP/IP and a package like telnet to do this. E.3 Packet drivers/ODI drivers/NDIS drivers Packet Drivers, ODI drivers, and NDIS drivers share a common purpose of recognizing packets coming in and distributing them to the appropriate piece of networking software as well as sending pre-built packets. Packet Drivers were first on the block once FTP Software realized the difficulty of writing complete drivers for every Ethernet board on the market. It's a short specification that does little more than hand out packets; consequently a Packet Driver is very small (about 2.5K in memory) but highly effective. 3Com/Microsoft came out with the NDIS specification to accomplish the same goal, but with many enhancements. The specification itself is very large and difficult to understand, and the code was the same way. NDIS is most commonly seen on Lan Manager systems (3Com, Microsoft, DEC, AT&T and so on). And, since Microsoft has of late taken to adding networking stuff in Windows products, those running Windows for Workgroups, Windows 95 or Windows NT as a network client will find themselves using NDIS, at least to some degree. [Thx S.M.D.] Then, most recently, Novell decided to tackle the board variety problem, but by starting from the top and looking down toward the hardware. Their ODI specification is the largest and most elaborate, and yet in many ways is the "best" of the bunch. There is a new version of the documentation describing ODI calls, tables, and functionality which are expressed in ANSI-C available at: ftp://netlab2.usu.edu/odi/update/codidocs.zip For Netscapers: ftp://netlab2.usu.edu/sys/anonftp/odi/update/codidocs.zip OR ftp://netlab1.usu.edu/pub/mirror/odi/update/codidocs.zip Both NDIS and ODI drivers are commercial endeavors, but their specifications are public. However, neither NDIS or ODI makes any effort to accommodate alternate ("competing") protocol stacks. This is changing with the appearance of small software converter "shims" which have a Packet Driver interface as the common denominator. Novell's Lan WorkPlace for DOS is a shining example of providing an ODI driver supporting both NetWare and TCP/IP. You can see the pressures here: software vendors want a cheap way of using many boards because drivers are expensive to write, and users want everything, including the ability to run things requiring dual protocol stacks on a single board. The commercial NDIS and ODI drivers should be more solid than the volunteer effort Packet Drivers, and correspondingly harder to get changed when bugs are found. NDIS and ODI drivers need to come from board vendors; Packet Drivers come, normally, from individuals and are distributed via Columbia University (you may get them by anonymous ftp from wuarchive.wustl.edu and many other sites). ODI is at this stage the driver type with the widest acceptance. It the only driver that Novell supports (IPX.COM, the monolithic shell or "driver" used before the introduction of ODI has long since been discontinued). [Thx Joe D.] E.4 deleted E.5 Routing TCP/IP through a file server If you use TCP/IP on two or more network adapters in a file server, chances are you want to route TCP/IP through the server (for example, you have one network adapter attaching to a room of PCs and the other attaching to your campus backbone). Each interface to which you bind TCP/IP has an IP address and a network mask. The combination of network mask, IP address and the destination field in a received IP packet determines whether that packet is routed through the server. As an example, let's assume your server attaches to two IP subnets, one with the address 137.43.101.0 (IP numbers between 137.43.101.1 and 137.43.101.255) and the other subnet with the address 137.43.102.0. Here is the IP configuration of the two network interfaces: IP address Network mask Driver 1: 137.43.101.1 255.255.255.0 Driver 2: 137.43.102.10 255.255.255.0 In Novell terms the bind configurations look like this: BIND IP TO DRIVER1 ADDR=137.43.101.1 MASK=255.255.255.0 BIND IP TO DRIVER2 ADDR=137.43.102.10 MASK=255.255.255.0 Note: You must also have LOAD TCPIP Forward=Yes in AUTOEXEC.NCF to setup the routing of IP-packages. This configuration will route packets from machines in 137.43.101.0 to 137.43.102.0 and vice versa. [Editor's note: these IP subnets are for example only. They actually exist in University College Dublin's IP network. If your IP network will connect to other networks you should apply for your own set of IP network addresses] DRIVER1 and DRIVER2 may be either driver types or aliases specified by the NAME= option when loading the driver. Novell's documentation kit includes extensive manuals which cover how to configure a server to route TCP/IP, as well as the concepts behind subnets. [Thanks to Amnat (Nat) Choeypatkul for some corrected info] E.5.1 Why TCP/IP Routing Doesn't Always Work As Expected The RFCs (Request For Comments, the papers which define Internet standards) governing IP addressing state that no portion of a node's address may consist of all zeros or of all ones. You can logically break down an address into two components where subnetting is not used (the network portion, defined by the address' class; and the node portion), and three components where subnetting is used (the network address; the subnetwork address, which is the difference between the subnetwork mask and the normal mask used for that address class; and the node address). Let's look at an example. Let's say we're subnetting a class B address, 166.166.0.0, into a number of class C-sized subnetworks. We would do this with a subnetwork mask of 255.255.255.0. This yields 254 networks, 166.166.1.0 through 166.166.254.0. We cannot use 166.166.0.0, as the subnetwork portion (the third octet) is all zeroes; similarly, we cannot use 166.166.255.0, as the subnetwork portion is all ones. Some equipment will allow you to use these illegal networks. Such equipment is providing an extension to the specificationss, and technically could be considered to be broken in that it does not behave according to the original specifications. Novell has released a version of MPR which permits the use of the all-zeroes subnet. Before using any all-zeroes or all-ones subnet, make sure you understand the applicable RFCs and are fully aware that you are "Off Spec". [Thx S.M.D.] There is a shareware program, SUBNET, that suggests appropriate masks based on the quantity of subnets and hosts per subnet; creates listings of subnets, directed broadcasts and host-ranges per the number of bits you tell it to use for subnetting (it then tells you what the mask should be). Lists include both binary and decimal displays and can be saved to disk as ASCII text or can be added to a database file (MS Access). The shareware version is limited to Class C addresses, the Deluxe version supports Class A - C addressing, including Variable Length Subnet Masks and Management tools for IP addresses. It needs VBRUN300.DLL. Author is Guy Michaud, gmichaud@cisco.com, and it can be downloaded at: http://www.futureone.com/~opeth/internetwork.html [Thx S.R.# E.5.2 Security considerations of allowing IP Source Routing IP source routing comes in loose and strict flavors...[A] bad guy on a far-away machine can send IP traffic to your place with a) source AND destination addresses at your place and b) an IP source route table which includes his far-away place. Naturally they have just tapped the wire and typically do not forward traffic back to the fake local destination. [The net effect is to] penetrate firewalls which are unaware of IP [source routing]. IP source routing is rarely used and can be turned off forever with really no loss. So turn it off on your major routers. [Thx Joe D.] E.6 Setting up a Netware server as an FTP server Novell's FTP server is bundled in both their Novell NFS package and in their NetWare Flex/IP package. According to the May 11, 1992 press release when Novell announced NetWare Flex/IP, the "high performance FTP server allows UNIX users to transfer files to and from NetWare v3.11 servers on the network. It also enables FTP clients to use the NetWare v3.11 server as an FTP gateway to access any other NetWare server on the network, including those that do not support TCP/IP. The FTP server provides full support of both UNIX/NFS and DOS name spaces..." An alternate, and less expensive, solution is to run NCSA telnet in FTP server mode on a dedicated workstation--an old 8088 machine is perfectly suitable. (NCSA is available on many sites. The people ftp'ing into the workstation will have access to anything the account logged in on the workstation has access to. You can set up "accounts" and passwords, but the only thing this controls is who can ftp into the workstation. Additionally, only one ftp connection at a time is possible. In many cases, however, these restrictions will not be a problem. Yet another alternative solution is a third-party FTPD.NLM. Brad Clements (MurkWorks) has an FTP NLM available: ftp to ftp.msen.com to pick up a demo copy. This is not shareware: you must pay Brad a license fee to use the actual software (the demo is free). HELLSOFT in the Czech Republic also produce an FTPD NLM, available via anonymous ftp from Michal Meloun's ftp site novell.felk.cvut.cz. Michal Meloun can be reached at meloun@vision.felk.cvut.cz. Both products work under NetWare 4.x but in Bindery Emulation mode only. MurkWorks FTPD.NLM demo: ftp://ftp.msen.com/pub/vendor/murkworks/demos/ftpd/ftpdnlm.zip Hellsoft FTPD.NLM: ftp://novell.felk.cvut.cz:/nw311/ftpd/ftpd18.zip [Thanks to Steven Nygard for the info on Hellsoft] E.7 BOOTP and RARP Bootp is a method by which a workstation can determine what ip number it should use and to find out what its nameservers and gateways are. If a workstation [using NCSA or CUTCP] runs telnet or ftp and has the myip variable in its config.tel file set to bootp, it will send out a broadcast on the network. A bootp server somewhere will see this broadcast, and respond to it with the ip number the workstation should use and what its nameserver and gateways are. The advantage is that all ip numbers, nameserver, and gateway information are kept in one file on the bootp server. You can get LPD.EXE at: ftp://tacky.cs.olemiss.edu/pub/lpd/ncsa/lpd.exe This will do bootp as well as lpd. You do not need a state of the art workstation to run this program. BOOTP is also available on lancaster.andrew.cmu.edu. [Thanks to Dan Abts for this info] Jocelyn Nadeau has informed me that the documentation for lpd doesn't indicate that it performs BOOTP; however, you can find BOOTP.ZIP and BOOTPNOS.ZIP as follows: ftp://ftp.ci.cuslm.ca/public/network/bootp.zip ftp://ftp.ci.cuslm.ca/public/network/bootpnos.zip *142.17.2.244* Another BOOTP server is BOOTPD.NLM from Hellsoft, available as follows: ftp://novell.felk.cvut.cz/nw311/ftpd/bootpd18.zip *192.108.160.5* or ftp://ftp.salford.ac.uk/network/nlms/bootpd18.zip (needs resolv.nlm) ftp://ftp.salford.ac.uk/network/nlms/bootpfwd.nlm (bootp forwarder) You'll need the Hellsoft name resolver NLM as well, available as follows: ftp://novell.felk.cvut.cz:/nw311/resolv/resolv13.zip [Thanks to David Gersic and J.P. for this info] Rarp is similar in function to bootp, but is less sophisticated. As with bootp, the workstation sends out a broadcast request for an IP number. If a rarp server picks up this request it will respond with an IP number for the requesting workstation. No other information is returned (this is one major difference between bootp and rarp). If your workstations use NCSA or Clarkson TCP/IP software, you can get them to use rarp by specifying the MYIP variable to be RARP. Many Unix machines come equipped with a rarp server and PC versions are available from ftp servers. One drawback with rarp is that it doesn't use IP packets: rarp is an ethernet protocol all to itself. This means that rarp requests *won't* make it through a Netware file server routing IP (or indeed through many other IP routers). Rarp servers are available for Novell servers and for PCs running LAN Workplace for DOS (and quite possibly for other platforms as well). An NLM-based rarp server is available as follows: ftp://netlab2.usu.edu/misc/rarpserv.nlm For Netscapers: ftp://netlab2.usu.edu/sys/anonftp/misc/rarpserv.nlm F. ELECTRONIC MAIL F.1 Pegasus Mail Pegasus Mail is a free mail program written by David Harris. It has almost every feature you could wish for in a mail program, and is well supported. Pegasus supports MHS and runs on NetWare 3.x and 4.x. DOS, Windows and Mac versions are available at: http://www.pegasus.usa.com If you also need an Internet e-mail gateway get Charon or Mercury (same directory--see questions F.2 and F.3 for details) you will be able to setup a Novell/Internet gateway. F.2 Setting up an Internet gateway for Pegasus Mail -- Charon Charon is a bi-directional Novell print queue to Unix LPD gateway and Internet/Novell mail gateway program. The mail gateway section works in conjunction with Pegasus Mail. Charon is free. It requires a dedicated workstation to run on; if you use the mail gateway you require an SMTP mail server as a mailing agent. Charon is available on many ftp sites, including: ftp://info.umd.edu/Software/Novell/Email/charon40a.zip *128.8.10.29* Note: Charon is no longer under development. F.3 Another Internet gateway for Pegasus Mail -- Mercury Mercury is an Internet/Novell mail gateway program that is designed to work in conjunction with Pegasus Mail (in fact its also written by David Harris). A major difference from Charon is that Mercury is a set of 3 NLMs and so runs on a file server. Mercury requires that your file server handle TCP/IP and can only serve one file server (whereas Charon can route mail to up to 8 file servers). Like Charon, Mercury needs an SMTP mail server (such as a Unix system) to handle outgoing mail. Mercury runs on NetWare 4.x in bindery emulation mode and is available at: http://www.pegasus.usa.com F.3.1 Pegasus/Mercury plus NetWare 4.1 considerations With v4.1, Mercury/Pegasus no longer supports the print queue method of passing email back and forth. Instead, they use only the SPOOL directory method. However, many installations migrated from CHARON, which supports only print queues, to Mercury. Since most of us have a bias in favor of doing what worked in the past, a Mercury/Pegasus reconfiguration is a common NetWare v3.1x to v4.1 prerequisite. [Thx D.E.H.] After upgrading from 3.x to 4.1, and assuming you're running Bindery Emulation (for the benefit of Mercury), you'll have to run Pegasus' PCONFIG to set all the info again. Only the new PCONFIG that comes with the WinPmail 2.4x has stuff for working directly with NDS. If you're using the "older" PCONFIG (like many of us), then run "PCONFIG /B" to correctly set the Bindery Emulation stuff under 4.1. [Thanks to Theodore Hope for this info] F.4 Other electronic mail packages There are a variety of commercial e-mail packages on the market, including Microsoft Mail and CC:Mail. These can be connected to an Internet gateway (like Pegasus Mail). However, these packages use their own gateway systems, available from the suppliers of the e-mail packages. F.5 Eudora Eudora started as freeware, but now there are freeware and commercial versions. There are DOS, Windows and Mac versions, with the latest free "lite" version is available at: http://www.eudora.com/ F.6 DNS and smart mailer Charon and Mercury are SMTP gateways and provide no DNS or Sendmail capabilties. To obtain a smart mailer (ie. sendmail/smail/mmdf) with DNS for the NetWare platform, try: http://www.unoverica.com/ [Thanks to Eric Harold for this info] G. PRINTING G.1 Printing to/from Unix systems The Novell solution is to purchase the NetWare Flex/IP package which includes a bi-directional print gateway. According to Novell's press release, it "allows Unix users to access printers attached to NetWare systems and NetWare users to access printers that are attached to UNIX systems. The UNIX printer will appear to the user as a normal NetWare print queue, while the NetWare queues will appear as UNIX print queues to the UNIX user. In addition, the UNIX print filter mechanism is supported enabling print jobs to be preprocessed before submission to the printer device..." The Netware NFS package which provides Unix file services on a Netware v3.11 server also includes the Flex/IP printer functions. NetWare NFS was updated on August 10, 1995, with the update file available at: ftp://netlab2.usu.edu/netwire/novlib/01/nfs197.exe For Netscapers: ftp://netlab2.usu.edu/sys/anonftp/netwire/novlib/01/nfs197.exe A third-party solution is also available. iQueue is a pair of LPD and LPR NLMs for Netware 3.1x and 4.x. Filters supported are: Text (CR/LF), Text to Postscript and Fortran. A demo that runs for 1 hour then unloads is available by: ftp://ftp.novell.com/pub/netwire/novuser/05/lpdnlm.zip [Thanks to Quentin Smart for the info on iQueue] For a free solution, see section F.2 for information on Charon 4.x. G.2 Sharing PC and Macintosh printers You can share printers between PCs and Macintoshes using Netware. The exact mechanism depends on whether you use Netware v2.x or Netware v3.11. Macintoshes can only print over the network to Appletalk printers (which are network devices, similar in concept to a Netware print server). Sharing PC and Mac printers involves setting up a print queue to appear on the network as an Appletalk printer. If you use Netware v2.x you can set up an Appletalk printer to be used by Macintoshes. This printer must be on the Appletalk network and serves a queue on the file server. This queue appears on the network to be an Appletalk printer (such as a LaserWriter) and like an ordinary print queue PC clients can print to it. The important thing to note here is that the Appletalk printer must be attached to the network and is visible to Mac clients. Since Appletalk offers limited access controls the printer is available to any Mac client on your network. Netware v3.11 offers more options than Netware v.2x. With Netware for Macintosh v3 you can advertise any printer queue to appear as an Appletalk printer and service a queue with a real Appletalk printer Effectively a printer queue can be advertised as an Appletalk printer, regardless of how the printer attaches to the queue. This means printer queues serviced by a normal Netware print server can also appear to a Macintosh client as an Appletalk printer. Also, a printer queue can be serviced by an Appletalk printer without the queue being visible to a Mac client. Other options with Netware for Macintosh v3 allow you to hide an Appletalk printer which is serving a queue. This means that Mac clients must use the queue instead of the real printer. You can also restrict Mac-based users of the queue to those connected to the file server. The combination of these two features allows you to carefully control access to printers. These options are controlled by switches in the printer specification in ATPS.CFG. A complete description of these switches can be found in the "Netware for Macintosh Installation and Maintenance Guide", pps 213-241. Some are summarised here: Option Does this -------- -------------------------- -o Renames a localtalk Q to a netware print Q -h Hides a localtalk printer which services the queue -a Makes a netware Q accessable only when logged in -y Disables the 'job completed' notification for Mac Users And some examples: e.g. 1 Print Q in same zone as server "localtalk name" -o "netware Q name" -h -a -y e.g. 2 Print Q in zone other than server "localtalk name:zone name2" -o "netware Q name:zone name2" G.3 Getting garbage in printouts If you occasionally get garbage in the middle of your print jobs, you're probably running PSERVER V1.21, which ships with NetWare 3.11. There is a known bug in this version which causes it to sometimes emit spurious characters when its buffer empties. A temporary solution would be to increase the size of the buffer in PCONSOLE; this should mask the problem for typical text jobs (but not for long ones, or for graphics) and is often not a bad idea as it will slightly improve the efficiency of PSERVER's operation. The permanent solution is to get a current copy of PSERVER. Look for the latest copy of PSERVER on Compuserve or your favourite ftp site. Another possibility is that you are running a serial printer and having problems with handshaking. In general, a print server can send data faster than a printer can print it (and in fact, this is the way you want it so that you are not artificially slowing down your printer). At some point, the printer has to be able to tell the print server to stop sending until it can deal with the data that's in its buffer. This can be done using hardware handshaking (there are several RS-232 pins for this purpose) or software handshaking (usually using the ASCII XON and XOFF characters). Both the printer and the print server must be configured to use the same method of handshaking. You will probably need to look in your printer's manual to find out what method(s) it supports, and how to enable them. For the print server, use the Printer Configuration screen in PCONSOLE. Another factor to bear in mind is whether or not your printer uses binary codes to position print on the page (such as a HP Laser Jet). You may need to set the queue to use BYTESTREAM rather than TEXT to allow control codes with value 13 to be transmitted. G.4 Alternatives to PCONSOLE & PSTAT for monitoring printer queues QView v1.5 is a program that will allow you to view several print queues at once. QView Pro v2.3 is a Pconsole replacement. With QView Pro, an operator may place jobs on hold, delete jobs, or move jobs between queues with a click-drag-drop of the mouse. You are welcome to try both if you would like. Note that these are demo versions of licensed software. Full details are available form the author (Stephen Herzog/Secure Design) at http://www.peak.org/~sdesign or support@sdesign.com. Jeff Pilant (pilant@nadc.nadc.navy.mil) wrote QLST [on netlab2.usu.edu] to show all pending and active jobs on all queues. Source is included. He also wrote SELECT [also on netlab2.usu.edu] to select a print queue when you have many to choose from. It also provides for defaulting the queue based on workstation location and source is included. [Thx J.P.] If you use Windows and Netware 3.11, 3.12 but not 4.10, you can use QManager (freeware) at: ftp://ftp.arch.pwr.wroc.pl/home/ftp/novell/adminutl/qm.zip [Thanks to Bengt Bolinder for this info] QUEMON will monitor several queues at once and show the status in an easy to read fashion. It's free and it's at: ftp://ftp.mechnet.liv.ac.uk/novell/freeware/quemon18.zip or http://www.mechnet.liv.ac.uk/~roy/freeware.html [Thx R.C.] G.5 Relocating print queues Try the freeware utility CreateQ: ftp://ftp.novell.com/pub/netwire/novuser/06/creatq.zip [Thanks to Paul Tichy for this info] The following steps will allow you to move print queues to another NetWare volume: Use JRBUtil's CreatObj with the following statement : creatobj /o=3 /d=data:queue temp Note: JRBUtils are available at netlab2 and mirrors and at: ftp://netlab2.usu.edu/apps/jrb400a.zip For Netscapers: ftp://netlab2.usu.edu/sys/anonftp/apps/jrb400a.zip - Goto pconsole and select print server, print server configuration, queues serviced by printer, press insert, choose temp. - Goto pconsole and select print queues. - Rename an existing queue (press F3) to something else - Rename temp to the existing queue name - This way, users will transparently be printing to the same print queue but it will be using a different location. [Thanks to Rajnish Mishra for this info] NetWare 4.x now allows the administrator to create print queues on volumes other than SYS: [Thx S.M.D.] G.6 Do postscript printer viruses exist? >Anyone heard of printer viruses? We've been told that some viruses can >be spread to a printer by downloading a Postscript font. Various >printer manufacturer's say no way. Only problem I know of for PS printers is if some PS code resets the password to "lock you out", requiring you to take the printer apart and remove the battery backed CMOS chip or battery (if memory serves). I think that qualifies as a virus...except that it doesn't propagate...until the person printing tries another printer when the first chokes. The following code is supposed to protect against this -- it also provides an alert if someone tries to change the password as well. Just replace "NAME" and "xxx-xxxx" as appropriate, then using DOS just copy this code to the printer. serverdict begin 0 exitserver statusdict /setpassword {userdict begin /evilpassword exch def pop (PASSWORD ALERT - CONTACT NAME at xxx-xxxx)=flush /Helvetica findfont 24 scalefont setfont 20 50 720 {70 exch moveto (PASSWORD ALERT - CONTACT NAME at xxx-xxxx) show} for showpage stop } put [Thx F.P.M.] G.7 Printing to the right queue without running Win / Print / Setup CAP2 is a Windows shareware that lets you print from lpt1-lpt9 on up to 100 netware queues using only the right printer driver for that printer. Only allow HP -> HP, Canon -> Canon, etc. Capture in user hold mode. If a queue is not found, try default server or other servers. ftp://ftp.coast.net/SimTel/win3/network/cap202.zip [Thanks to Bengt Bolinder for this info] G.8 Alternatives to PSERVER for more than 16 printers, etc. FPserver (Fast Printer Server) by Richard L. Hartman, rlh@ior.com, is $95 for a file server license. You can run up to 7 printers off each computer, 4 serial and 3 lpt, and as many computers as you want to setup as print servers. Printing is fast, and it uses the same queues as NetWare so no special configuration is required. We are using 8088 cpus, and it can service 3 printers as fast as they can go. It also doesn't use interrupts which is one less worry, and allows monitoring what is printing so you can delete or rush print jobs. ftp://netlab2.usu.edu/apps/fps34c.exe For Netscapers: ftp://netlab2.usu.edu/sys/anonftp/apps/fps34c.exe [Thanks to Michael D. Setzer II & Richard L. Hartman for this info] NetWare 4 relieves this situation by allowing PSERVER to handle 255 printers. [Thx S.M.D.] G.9 Print Server auditing programs AuditTrack v2.0 will audit everything on 3.x and 4.x servers. It is available for a free 30 day trial at http://www.egsoftware.com [Thx E.S.] G.10 Running NPrinter or RPrinter without being logged in It is possible to execute NPrinter without first logging into the network. Possible with RPrinter too. I use a local directory for the xPrinter files. You will need the following files: NPRINTER EXE 350,606 11-15-93 3:39p TEXTUTIL HEP 11,735 10-26-92 4:06p NPRINTER HEP 8,205 01-22-93 5:23p NPRINTER HLP 7,618 06-17-93 11:49a NPRINTER MSG 9,259 05-18-93 9:49a TEXTUTIL MSG 29,466 01-27-93 6:56p 437_UNI 001 659 01-26-93 4:57p 850_UNI 001 659 01-26-93 4:57p UNI_1252 001 2,196 01-26-93 5:10p UNI_437 001 2,836 01-26-93 4:57p UNI_850 001 2,708 01-26-93 4:58p UNI_COL 001 4,500 01-23-93 2:24p UNI_MON 001 4,244 01-23-93 2:23p 1252_UNI 001 659 01-26-93 5:10p IBM_RUN OVL 2,815 01-19-93 10:33a TEXTUTIL IDX 9,170 12-10-90 1:37p Note: The above files are from a NW 4.01 system upgraded to NW 4.1, your file dates and sizes may differ. [Thanks to John Withers for this info] Further to the above, the way to find exactly which files are required is to execute NPrinter /v which should show the current versions of all files required by NPrinter. You can either put these files into the LOGIN directory, which all users (by default, anyway) have R F Access to or you can copy them to a local drive. Then all that's needed is to execute: LSL DRIVER.COM IPXODI [Loading IPXODI /A will save some KB of RAM] VLM N{PRINTER ??? etc. [Thx M.M.# G.11 Page counting software PCOUNTER v3.31 is a page counting print server for Novell NetWare. It counts pages on PCL and PostScript printers, logs all printer activity & maintains user accounting, supports custom banners & remote control, as well as parallel, serial and networked printers. It also has a NetWare print queue to UNIX LPR gateway, will automatically convert text to PostScript if necessary and can reject incorrect print job types or incorrect paper sizes if desired. It is available as an EXE (for dedicated print servers) or NLM (running on the NetWare server) at: http://www.andtechnologies.com/ [Thanks to Andy Charmatz & Vlasti Broucek for this info] H. MISC. H.1 Booting a server without running STARTUP.NCF/AUTOEXEC.NCF There may be times when you want to boot a file server without running the startup scripts C:\STARTUP.NCF and SYS:SYSTEM/AUTOEXEC.NCF. With NetWare 3.x, when you issue the SERVER command, include the parameter -ns To not execute the STARTUP.NCF -na To not execute the AUTOEXEC.NCF Note1: These parameters are case sensitive and MUST BE lowercase. Note2: NEVER load memory management software before running SERVER.EXE! Under NetWare 2.x all of the configuration information is incorporated into the NET$OS.EXE file so the question doesn't really apply; you would have to regenerate the operating system with NETGEN to change it. [Thanks to Jay Sissom for clarifying the 2.x issues] To start server with another STARTUP.NCF type: SERVER -S START2.NCF To start server with another AUTOEXEC.NCF type: SERVER -A AUTO2.NCF To start server without Directory Services open use -NDB and to start server in internal debugger use SERVER -D (this is the only documented option: type HELP RESTART SERVER on System Console). Options seems to work with RESTART SERVER command. [Thanks to Petr Jaklin for this info] H.2 How to login without running the system/user login script The DEFAULT login script built into LOGIN.EXE executes after the SYSTEM login script (NET$LOG.DAT) when there are no USER login scripts. The solution is to either use an EXIT command at the end of the SYSTEM login script or create individual USER login scripts. The latter approach is more work but there is security benefit to creating USER login scripts. Among other things the DEFAULT login script maps S1 and S2 search drives to SYS:PUBLIC and to the DOS subdirectories under PUBLIC. It also attempts to map a user home directory immediately under SYS: For more information see the Installaton and Upgrade red book. By the way you cannot modify the DEFAULT login script because it is built into LOGIN.EXE so the best you can do is prevent it from executing. [Thanks to Andrew Lampert for this info] In NetWare 3.12 and above, or earlier versions upgraded to the latest LOGIN.EXE, you can use the NO_DEFAULT login script command to prevent the execution of the default user login script for users who have no personal login script. [Thx S.M.D.] Alternatively, you could ensure that every user has a NetWare login script, however small, and that there is a system level NetWare login script as well. By the way, use "PATH string" as opposed to "SET PATH=string". The former goes through command.com for regularization, the latter is taken verbatim. [Thx Joe D.] This last point is a good idea from a security standpoint, too. Basically, on a server where users are allowed to have their own personal login scripts, an account without one may be a security hole. For the details, see the Hacking NetWare FAQ at: http://www.nmrc.org/ A number of Netware hacking files and additional info are at this site. [Thx S.M.D., Gabor Borsodi and Simple Nomad] Or, you could ATTACH instead of LOGIN to the NetWare file server(s). You will either need to first login to another file server which has the ATTACH command available or copy ATTACH.EXE to the workstation's disk. Then enter the login command as "LOGIN /S nul *username*" which will attempt to read the script from the DOS nul device, which always returns end of file, effectively avoiding reading a login script. If you are running NetWare 4.x you can LOGIN /NS (/NS meaning No Script). In a 3.x environment use LOGIN /S... Use /S to point to a text file on a local drive containing login script statements (A simple WRITE "It worked" should do) The easiest way of all is to LOGIN to another server and ATTACH to the problem server. If security is not an issue, copy ATTACH.EXE to your sys:login directory to avoid future problems. [Thanks to A. Murray for this info] At least in 3.1x, the Login scripts are in the mail directory. So the supervisor Login script is at sys:mail\1\login. If all login scripts are going to be the same, set the system Login scripts to what you like it to be and have only exit in the user login script. You don't want to leave no login because people have write access to the mail directory and can store a login script that causes problems. If there is something there, they can't change it. [Thanks to Tom Tuckerman for this info] H.3 Remotely controlling a PC with a telnet compatible program To use Telnet to remotely control a PC, get telnetd.zip at: http://www.futureone.com/~opeth/internetwork.html [Thx S.R.# It works really well with CUTCP TELNET, and also works fine with MacTCP TELNET and most other TELNETs as well. H.4 Getting userIDs and other information into programs There are essentially four ways to import Novell information into programs you have written, each of which is appropriate for some solutions: H.4.1 Environment variables Use the login script command: dos set VARIABLE="Value" to put the user-id (%LOGIN_NAME), station number, etc. (consult the Novell documentation for the list of available values), into an environment variable. Now you will be able to retrieve the environment variable in both batch files and programs. In Turbo Pascal as well as most varieties of C and C++ use the expression GetEnv("VARIABLE") to retrieve an environment variable. This technique is good for simple programs which only need a few Novell values, and for batch files. H.4.2 Piping in information from WHOAMI Write your program to read its input in the form that WHOAMI types, and then pipe in the output from WHOAMI: WHOAMI [/a] | YOURPROGRAM You will have to program to ignore lines that contain only / - \ because these still appear at the head of the file while the program is scanning the bindery information. This is inefficient, but it is the only way to get arbitrary group memberships if you cannot use the H.4.3 or H.4.4 below. H.4.3 Novell APIs Purchase the Novell APIs, available in both C (which work with several versions of C and C++, including all Borland products) and assembly language (which you could also use in any high level language with an interrupt command). With these you can retrieve directly almost any information that the account running the program has access to. The APIs provide not only basic services like user-names and connection number, but advanced ones like print queues and IPX/SPX communications, among others. This is the best and most efficient solution, but requires investment in the APIs as well as programming knowledge. You can order the Novell SDK by calling 800-RED-WORD or 801-429-5281. The Novell SDK is made available by subscription. The base price is $345 per year. This includes four releases of the SDK CD, a choice of a Novell product for your development/test environment, and a support incident. For further details please see http://developer.novell.com Documentation may be viewed at http://doc1.provo.novell.com/ [Thx J.P.] An alternative to the SDKs is "Programmer's Guide to Netware" by Charles Rose. This book has extensive details on Netware v2.x system calls and covers many Netware v3.x calls. There is also a shareware API library available via anonymous FTP at: ftp://ftp.coast.net/SimTel/msdos/c/netclb35.zip or any SimTel mirror site. [Thx A.C.] A Pascal NetWare API supporting programming language is NWTP06. It stands out because it is very complete (it does not however support Netware 4 as yet) and is available at: ftp://novftp.rc.rug.nl:/proglibs/nwtp06.zip It contains over 400KB of sources in more than 250 interface functions, over 500KB documentation and more than 200KB samples. The author is Rene Spronk. [Thanks to Olger Diekstra for this info] H.4.4 Third Party Utilities UPDATE.EXE is by Robert Evans is a freeware utility that allows you to detect the existence of specific sub-strings in text files, add, replace, delete specific lines, files, directories etc. ftp://ftp.soe.purdue.edu/pub/update/ [Thx D.L.] USERDUMP by Roy Coates will tap the bindery and list user info such as mail address, user id, etc. and is available at: ftp://ftp.mechnet.liv.ac.uk/novell/freeware/userdump.zip or http://www.mechnet.liv.ac.uk/~roy/freeware.html [Thx R.C.] DISKHOG by Roy Coates will list the disk space used by user, including subdirectories and is available at: ftp://ftp.mechnet.liv.ac.uk/novell/freeware/diskhog.zip or http://www.mechnet.liv.ac.uk/~roy/freeware.html [Thx R.C.] H.5 What do all those columns in STAT.NLM v2.0 mean? STAT.NLM is a process which records performance information for a Netware v3.11 file server. STAT records a data point once per second and writes to the disk once per minute to minimize the effect on the server. Use DUMPSTAT to output the STAT data in a readable format. This is a DOS command and its syntax is: DUMPSTAT inputpath [outputpath] [-L | -X | -S | -Nnum | -Mnum] where -L Lotus format (comma delimited) -X Excel format (tab delimited) -S Screen format (column justified) -N Output file size (default is 7200 points or 2 hours). You can increase this if you want to put a day's worth in one file, etc. A file with 8 hours of data would therefore have -N28800. -M Data reduction factor ... or do you really not want that much data. This is the number of records that will be averaged and output to a single record. So putting 60 in here would give you a point per minute instead of a point per second. 300 would give you a point per 5 minutes. Here is the official word from Novell on what the columns of output mean: 1. CPU utilization 2. Bytes received (bytes read from LAN comm channel) 3. Bytes transmitted (bytes written to the LAN comm channel) 4. Bytes read (bytes read from the disk) 5. Bytes written (bytes written through cache to the disk channel) 6. Packets routed (# packets using the router services of the server) 7. Number of connections An important warning for anyone using STAT.NLM: the next filename to be used by STAT.NLM is stored in a file called STAT.CFG. You must use the STAT configuration utility to change this -- using a text editor will most likely crash your file server. [Thx G.F.] H.6 Changing the number of licenced users on a Netware server Netware 2.x - requires a full "netgen" Netware v3.1x - The serial number and maximum connection count are both found in SERVER.EXE. When you get your upgrade package from Novell, copy this file from the SYSTEM-1 diskette over your old SERVER.EXE on your server's boot diskette or boot partition and your server is upgraded. Note that it might be wise to keep the old SERVER.EXE around in case you later discover that the new SYSTEM-1 diskette has a media error or something. Also, if you have applied any static patches to your old SERVER.EXE, they will have to be re-applied to the new one (semi-static and dynamic patches, loaded in your AUTOEXEC.NCF, do not modify SERVER.EXE and will continue to work as usual). Netware 4.x - the license is separate to the server.exe file. To increase or decrease the number of licenses is a matter of adding or deleting the license.mls file via install.nlm from the server console. With Netware 4.0x you may replace the current license via install.nlm, and with Netware 4.1 you may delete the previous license and/or add additional licenses. If you have two 50 user 4.1 licenses, for example, you can now create a 100 user server. If you have one 100 user license, however, you cannot split it into smaller units (at the moment) unless you can find someone to swap the license with for an equivalent number of smaller blocks of licenses. [Thx S.M.D. & Richard Phillips] H.7 Register memory ("Cache memory alloc. out of avail. memory" msg) This section is based on NOVELL FYI 1.1.39, extended to include information provided by George Whitehead, R.J.L., Joe D. and S.M.D. ISSUE/PROBLEM Server error message: Cache memory allocator out of available memory. This can occur when mounting disk volumes even when there are plenty of cache buffers available in machines with more than 16M of memory. It can also occur I guess when you have run out of memory completely but the solution in this case is obvious. SOLUTION EISA machines should be configured to use AUTO REGISTER MEMORY, but in the case of ISA machines or EISA machines that are not configured correctly, the following kludge will solve the problem. Every machine that requires the REGISTER MEMORY command, uses more than 16MB of RAM, and has large disk storage, will exhibit problems such as this. This is not an issue in machines that do not require the REGISTER MEMORY command (such as the COMPAQ SystemPro, PS/2 MODELs 90, 95, HP Vectra etc.) because at boot up you see all of the RAM. By the time you register memory in the AUTOEXEC.NCF, volume SYS: has already been mounted. At the time the first volume is mounted, NetWare draws a line in the sand, and only memory which it had available at that time can be used for FAT caching for all subsequent volumes, regardless of how much physical memory is available at that time. Therefore, subsequent volumes will be mounted downward in memory until you eventually run out of memory below 16 meg (see figure 1 below). Figure 1: |======{==}={==}={==}| ==========================| {== VL2 VL1 SYS 16 64 MEG of MEMORY MEG The key is to REGISTER MEMORY before loading the disk drivers or mounting volume SYS:, as illustrated in figure 2 below. Figure 2: |===============|=================={==}{==}{==}| 16 { = VL2 VL1 SYS 64 MEG of MEMORY MEG Here is the procedure: Step 1. Remove ALL DISK DRIVERS out of the startup.ncf file. If this is all that startup.ncf has then delete it. For example my startup.ncf is: set minimum packet receive buffers = 200 Step 2. Create an Autoexec.ncf file in the same DOS directory as SERVER.EXE, making sure that the register memory command is executed before volume SYS is mounted. Use the format listed below. file server name HOPE ipx internal net 9088 register memory 1000000 1000000 load isadisk port=1F0 int=E mount SYS autoboot Step 3. Create an Autoboot.ncf file in the SYSTEM directory. Put into it all other Autoexec.ncf commands. load NE2000 port=300 int=3 frame=ETHERNET_802.3 bind IPX to NE2000 net=01abfeed etc. The decision to use the name autoboot is purely personal. The mechanism will work with a single Autoexec.ncf on the DOS drive containing all of the autoexec.ncf commands. The advantage of the 2 file method is that the complex part of the autoexec.ncf file is on the Netware partition and can be edited from a workstation using your favourite editor while the server is up. Others may find it preferable to have a single autoexec.ncf on the DOS partition of the server as this allows access to it when the server is down. [Thanks to George Whitehead, R.J.L., Joe D. & S.M.D.] Related bits and pieces. Joe D. posted a message to the NOVELL LISTSERVER at the start of July (1994 Joe?) which described how to configure EISA memory cards. Earlier versions of the driver for the ISA/MCA Adaptec host adapters (154x and 164x series) had a command-line parameter which informed them that they were operating in a machine with more than 16 MB of memory. Current versions of the drivers for these cards do not require this parameter and the EISA cards have never required this parameter. Some drivers may require: set reserved buffers below 16 MB = 64 [See H.16 for more info on Adaptec] It is possible to 'RUN' a sequence of netware console commands from a batch file by typing the name of the file from the console. Put the commands in a file in the SYSTEM directory and give it an NCF extension. For example if the file was called TEST.NCF it could be run by typing TEST, then pressing ENTER, at the console prompt. [Thanks to Douglas Scott and S.M.D. for the info] Some EISA don't register memory above 16MB. If this is the case, the NSEPRO describes the solution for servers running NW4 is to put the following lines in STARTUP.NCF: SET AUTO REGISTER ABOVE 16 MEGABYTES = OFF SET RESERVED BUFFERS BELOW 16 MEG = 200 ...load the disk drivers LOAD MEMFRGFX [Thanks to ksommers for the info] Also, make sure there is no interrupt conflict. Drew Morris reported problems when a PCI SCSI card was set to Interrupt 15 and another problem when a PCI adapter was on Interrupt 9. [Thanks to Drew Phillips for the info] Additional note: Netware 4.x auto-registers memory in a PCI-bus server but Netware 3.x doesn't...unless you have more than 64 MB of RAM. Above 64 MB you will have to register manually, which can be done in the NetWare 4.x STARTUP.NCF file. [Thx A.S.] TID500055 Mounting Volumes and Memory Allocation Some Early Information About Mounting Volumes May Be Misleading Documented issues about registering memory on ISA and some EISA machines have been interpreted to say that NetWare mounts volumes from the top of the memory block down. That model seemed to explain the memory limits for mounting volumes and the necessity to avoid mounting the SYS volume before registering all memory. While it is true that all memory should be registered with NetWare before any volumes mount, it is not true that volumes mount from the top of the block down. How NetWare Uses Memory to Mount Volumes and Grow the Directory Hash Table Mounting a volume consists largely of reading the FAT from disk into server memory. After the FAT is loaded then the DET, directory entry table, is scanned and a hash table is built in server memory. Two simple rules govern the allocation of memory for mounting volumes. The first rule: when the first volume mounts, NetWare defines a block and all subsequent volumes will mount in that block. The second rule: the memory allocated for the volumes grows from the bottom of the block upward. The DHT, directory hash table, will be in the same block and, like volumes, will grow from low to high. Assuming the block in question to be the only block then any NLMs loaded or other cache buffers required will be allocated from the top of the block down. In summary, volumes and DHTs grow from the bottom of the block up and NLMs and other cache buffer requests use memory from the top down. [Thanks to Mark Cramer for this info] H.8 Full Duplex versus Half Duplex ethernet Q: Should I configure my ethernet equipment to operate in full-duplex or half duplex mode? A: The list has discussed this topic several times; and there is a great deal of anectdotal evidence to suggest that full duplex ethernet connections often _decrease_ network performance. This seems counter intuitive, what is the explanation? A "normal" half-duplex ethernet has a very simple flow control mechanism - the collision. If a collision happens, retransmissions are handled at the physical layer, i.e. by the electronics of the ethernet equipment. This happens very quickly, i.e within microseconds. The ethernet full duplex flow control standard is IEEE 802.3x. In order for this to work, _each_ device on the network must support 802.3x including NICs, switches, etc. The vendors seem to disagree on the interpretation of the spec, however. See http://www.nwfusion.com/netresources/0913flow.html for details and vendor finger-pointing. If the physical level 802.3x flow control is not working properly, a busy ethernet may drop packets. In this case any retransmissions must be handled at the protocol level, i.e. in software (the OS of the network device). This happens _much more slowly_ then collision handling. TCP/IP is very robust in this case, retrasmissions occur within 1/2 second or more (an eternity at wire speed!). Some protocols are very poor in this regard, i.e. NFS over UDP. Some protocols have no provision at all for retransmissions, for example RIP broadcasts, SAP broadcasts, or any multicast protocols - any dropped packets are lost forever. [Thx Joe D., Hansang Bae, Arthur B., Mike A. and probably lots of other people.] Please note that full duplex ethernet _can work_ as advertised - it just requires interoperability testing to make sure that _all_ of the equipment on the wire is playing by the same rules. >You need anywhere from 4 to over a dozen stations to reproduce >problems that can be caused by full duplex (if there are any with >your hardware). Most of our links are half duplex because they fail >stress test at full, but I have stress tested full duplex between >Foundry's BigIron switch, and Intel cards and so I leave those set at >full duplex. (BTW: I highly recommend FoundryNetworks for anyone who >needs a 10/100 or especially gigabit layer 3 switch that does IP, IPX, >and Appletalk). > >Also, even though I do have some of our servers on full duplex now, >about the best we get is a few % in performance as most of the >traffic is one way... But when the link is unreliable (Intel card >to a Bay/Nortel 350/450 for example), performance sometimes suffers by >several hundred % when under a stress test. [thx John Lauro] And some final thoughts... [SNIP] >FDX fails just when needed most, under heavy stress. Under lighter >loadings one can not tell the difference between FDX and HDX. Very >often the large transfers are unidirectional, they are file >transfers, and in those cases FDX buys almost no advantage. Backbones >are the major beneficiaries of FDX, not workstations, because the >traffic tends to be bidirectional. [SNIP] >the complete FDX path must be properly dealing with FDX traffic or the >flow control messages (PAUSE packets) will not get through to the >offending transmitter, if they get through at all with congestion. There >is no good reason to think PAUSE packets are economical of network time >since they say wait multiples of 512 bit times (contrast to a typical >collision interval of 100 bit times) and the amount of waiting is a >vendor's choice rather than dynamic sensing of the network moment by >moment. [thx Joe D.] H.9 deleted H.10 Getting a list of usernames on a server to an ASCII file John Baird of New Zealand has developed a range of tools for Netware which are widely regarded as essential for supervisors. One of these is GRPLIST, which will list all users in a group. To get all usernames into an ASCII file, issue the following command: GRPLIST * /f which will create a file called USERS.LIS containing all user names on the server. John's utilities are available from most of the ftp servers listed in the FAQ (section C.2), as well as at: ftp://netlab2.usu.edu/apps/jrb400a.zip For Netscapers: ftp://netlab2.usu.edu/sys/anonftp/apps/jrb400a.zip H.10.1 Creating users from an ASCII file There are several programs that will create users based on input from an ASCII file. H.10.1.1 Mass User Management Mass User Management reads in a tab, comma or space delimited file and creates the users. It uses templates to match different user account restrictions to different users in the ASCII file. A demo is available at: ftp://ftp.coast.net/SimTel/msdos/novell/MUM13B.ZIP This version of Mass User only works in bindery emulation on NetWare 4.1 servers so all users must be in the same context. An NDS version is in the works, though. Co-authored by Shawn_Holmstead@novell.com and others. Now works with VLMs. H.10.1.2 UIMPORT -- reads an ASCII text file and adds users UIMPORT (bundled with NetWare 4.x or higher) uses 2 ASCII text files: a control file and a data file. UIMPORT /? provides information about the format of these files, for more information consult the online documentation (http://www.novell.com/documentation/) for your version of NetWare. H.10.1.3 ScanUser -- scans/creates unknown/missing Mail directories ScanUser is a small utility that scans for unknown or missing Mail directories, with the option to create missing ones. It is for sites with many users, and avoid the bother of logging in each user with /b to create the Mail directories. It also searches for Unknown Mail and Home Directories. ScanUser is free but you are asked to register if you are using it at: http://www.petena.se/support/register.htm You can get ScanUser at: http://www.petena.se/software/ [Thanks to Peter Stromblad and Johan Wahlen for this info] H.10.1.4 BULKLOAD.NLM -- imports users from an LDIF file NDS 8 includes BULKLOAD.NLM, which can create users from LDIF (LDAP Interchange Format) files. The NDS 8 online documentation (http://www.novell.com/documentation/) describes how to use BULKLOAD, but is sketchy about LDIF. For more information about LDIF, see the relevant IETF draft (http://search.ietf.org/internet-drafts/draft-good-ldap-ldif-05.tx t). This is still a draft, so the URL will likely change... H.11 Remote access to a LAN There are a variety of ways to get access to your network remotely. These include running a telnet server (e.g. telnetd described elsewhere) on a workstation and accessing it via tcp/ip, running remote control clients and accessing them via modem, running remote network node clients and accessing them via modem and of course iptunneling across a tcpip network. Conceptually and practically, the simplest solution for many people is to run a remote control client on their own workstation which they dial into and control from remote sites. This requires 2 modems (preferably fast ones using V.34, or V.32bis in a pinch) and also requires that you leave your workstation permanently turned on - in itself arguably a Good Thing provided that the monitor is off. It also requires some software and there are a large number of choices. Commercial packages include PC-Anywhere, CloseUp, Blast, Carbon Copy and Reachout (Stac Electronics, 1201 19th Place, Vero Beach, Fla 32960 (407)770-4777, FAX: (407)770-4779, TECH: (407)563-2255, www.stac.com). These cost around $100 to $200 per node and often work quite reasonably. Shareware packages such as Telereplica (check your SimTel mirror) ftp://ftp.radio-msu.net/.1/.m/Coast/msdos/modem/tr4-26.zip offer a very cost effective solution. Telereplica has long passwords which are very hard to crack and can even do dialback for added security. The only drawback is that it does not do graphics but at 9600 baud, life's too short anyway! If you really need to run a graphics package (e.g. Harvard Graphics or whatever), do it at home and upload the results to your workstation. It's much faster that way ! There's also PCRemote from PC Magazine. ftp://ftp.cdrom.com/.5/asme/COMM/PCREMOTE.ZIP PCRemote has assembler source for a simple remote control package via modem which could be the basis for a more sophisticated effort. [Thanks to Dr Ross Lazarus & S.R.#2 for this info] One of the Very Frequent Questions on this list is how can folks dial into their NetWare file server. At present, they can't, at least not like they think they might. Some device has to act as a client node on the network and then put things into a form suitable for async transmission. Whether SLIP or PPP or another framing method is used normally is a small part of the picture. In any case, the server is not an interactive login machine such as a Unix box and DOS does not work to a classical terminal interface. This means the node on the net can execute the DOS programs and relay screen and keyboard updates across the phone lines (Carbon Copy, PC Anywhere, et al), or it can try to wrap IPX packets into async frames and unpack them on the other end. Things such as Netblazer/Worldblazer modems (though by now "modem" is the small part) act as such relay nodes. Novell's Access Server, and similar boxes, run a bunch of DOS machines having keyboard/screen relayed across the net. NAS simulates many machines on one via a special version of DESQview. Since you have LWP/DOS 4.1, have a look at the XPC part of things. The idea is to relay the keyboard/screen of a DOS machine executing the program of choice across a wire using IP packets and the X window system protocol on top. Thus you could execute WordPerfect/DOS sessions from your Sun workstation, with your DOS PC doing the real work. Taking one more step, put a modem on your office DOS PC, run XPC there, and at home fire up a PC running X to a matching modem. You might want to look at: ftp://netlab2.usu.edu/..???../brainshr.zip which is basically the floppy disk passed out at Brainshare/SLC (aka Novell Developer's Conference) this spring by Brian Meek addressing LWP/DOS, dialing, SLIP_PPP, and even Kermit's role in this. The development Kermit was just for developers, is out of date and should not be redistributed. [Thx Joe D.] H.12 Short Term Memory -- how much does your server need? The default Short Term Memory allocation will ALWAYS crash your server if any type of load is put on it. I would suggest that you immediately set this value up to 5000000. We happen to run our servers at 8000000. The exact syntax, which can be placed in your AUTOEXEC.NCF would be, SET MAXIMUM ALLOC SHORT TERM MEMORY=8000000 [Thx G.F.] Long term readers will recall my personal recommendation is to use the maximum amount of memory in the machine, or NW's limits, whichever is smallest, in this line. I don't have much factual information to go on, but my crystal ball says it makes a pool available contiguously and helps NLMs when their memory needs arise. It does not hinder other memory allocations nor consume cache buffers etc. [Thx Joe D.] H.13 BTRIEVE -- what do I need? Btrieve is a record manager running as an NLM on a Novell server. Certain applications can use a Btrieve client to make requests to the engine on the server. BTRIEVE.NLM is the server component, while BREQUEST.EXE is the DOS client. More complete documentation is included with the Novell manual set. When performing installs of some programs, make sure the btrieve related programs in sys:system are NOT flagged as read-only. Btrieve is no longer part of Novell. Btrieve Technologies can be reached at: #300 - 8834 N Capital of Texas Hwy, Austin, TX 78759-9774, Tel: 800-BTRIEVE (US & Can), 512-794-1719, eMail: Info@BtrvTech.COM, http://www.btrieve.com [Thanks to Mark Fogel, H.K. & R.J.L. for this info] H.14 deleted. H.15 Synchronising workstation time with server time Time synchronization occurs at two times. The first is at the time when the shell or redirector makes a connection to a server (the NOT-LOGGED-IN connection which gives you access to SYS:LOGIN). To disable this connection from setting your workstation's time, use SET STATION TIME = OFF in your NET.CFG. The second time is during the login process. In the absence of a SET_TIME OFF command in any login script executed by the user, the workstation's time will be set to that of the fileserver. This command is supported in the LOGIN.EXE which ships with NetWare 3.12 and 4.x; it can be downloaded from the usual places for earlier versions. [Thx S.M.D.] The synchronization of workstation and server clock is explained in the Novell Application Note "Time in the NetWare Environment", Jan 94. [Thx M.W.] [ H(1) | H(2) | H(3) | H(4) | Novell FAQ Home Page ] [ H(1) | H(3) | H(4) | Novell FAQ Home Page ] H.16 Problems with disks and tape drives on Adaptec SCSI controllers Many users have experienced problems with older Adaptec SCSI controllers with both disks and tape drives. If you're running older Adaptec software you should upgrade it immediately to the current release (minimum 2 June 1994). You should also seriously consider upgrading your hardware, as the 1542C has problems in servers with more than 16MB memory. The 1542CF doesn't. [Thanks to Julian Byrne for this info] Contact Adaptec's Literature Hotline at 800-934-2766, BBS: 408-945-7727 Tech. Support Hotline: 800-959-SCSI (7274) or 408-945-2550, Interactive FAX: 408-957-7150 (PCI compatibility list is doc #21105), ftp://ftp.adaptec.com, http://www.adaptec.com [Thx V.K.R.] H.17 deleted H.17.1 Suitable NICs for the NetWare server itself >Are the 3Com "3C509" cards I have in my server suitable? 3C509 have a very small packet buffer, too small to stand much traffic at all. They interrupt the cpu with "packet has arrived" before the full packet is in, and that means the software does not know the size of the buffer to allocate to absorb the packet and thus it must allocate a max length one every time (memory hog, oink). The cpu must hang around waiting for the packet to arrive (1.5msec for a full length Ethernet packet, forever in cpu terms) and then clear the board. The cpu has to do all the work because the board is not a bus master kind. Given the tiny board buffering the cpu must attend to the board swiftly or packets get lost from overruns. All of these things are bad characteristics in a busy server, and modern NICs avoid these problems. An NE-2000 is a better board in a server, and there are many boards much better than the (ISA bus) 3C509 NIC. Good boards in servers are bus masters, meaning EISA or PCI bus currently. Not just PCI or EISA boards, but bus master boards. With these the main server can keep working on requests while the lan adapters deal with packet busywork, cpu utilization goes way way down, fewer packets are lost from overload, the server continues to perform well as the load grows high and higher. The disk system is happier too because there are fewer lapses of attention to it, so think of the server as being less stressed by better lan adapters (and by better disk adapters). Servers (CPUs, disks, NICs & RAM) are about to be strained by (1) Win95 and its applications which require larger file transfers, (2) User demand for 100Mb/s service to the desktop. [Thx. Joe D.] H.18 Fax products for NetWare Optus Facsys provides OCR for incoming fax routing. Cheyenne FaxServe [runs as an NLM on the server] from Cheyenne Software, 516-484-5110 or 800-CHEY-TEC, Fax: 516-484-3493, faxserve@cheyenne.com. The latest version, 3.x, supports NetWare 4.x, NDS, and includes an enhanced FAX client for Windows workstations. QNT QPServer [requires a dedicated PC] Castelle FaxPress [allows the use of multiple fax/modems, doesn't need a dedicated PC, but incoming faxes must be routed] GammaLink, by Dialogic, makes fax boards supporting from 1 to 12 lines on a single board, each with it's own fax coprocessor. RightFAX, also by Dialogic, has servers for OS/2 and NT (but no NLMs). The OS/2 server works well with NetWare & there are RightFAX clients for DOS, Win & OS/2. http://www.dialogic.com/ Another possibility for fax boards is Brooktrout. [Thanks to H.K., Bill Willcutt & Ivo Spigel for this info] WinPort allows Network Faxing, Remote Access and Modem Pooling. You can also map the network modem to a standard unused comm port in windows. LanSource's Tech number is (416) 535-3555, sales@lansource.com [Thanks to Greg Horne and L.C.H. for this info] Faxware from Tobit, Germany. Is NLM based, supports almost any fax-modem, ISDN adapters with G3 add-on board for inbound routing, has an optional PCL NLM, an optional fax-on-demand module, an API and is fully integrated with Netware, ie. it knows users and groups, uses NW queues and can poll directories. [Thx A.S.] For more information, check out: http://www.traffic.is/ http://www.faximum.com/w3vlib/fax/ [Thanks to Lennart Regebro for this info] H.19.1 Backup software products for NetWare Novaback works with NW 3.x and 4.0x servers, but it doesn't back up NDS. It also backs up FAT based disk drives on the local machine. Novaback is made by Novastor Corporation, #109-30961 Agoura Road, Westlake Village, CA 91361, Voice: (818) 707-9900, Fax: (818) 707-9902 and is available in DOS, Windows or NLM versions. Cheyenne Software makes ArcServe for DOS and Windows clients. ArcServe can also back up workstations. Cheyenne can be reached at 516-484-5110, Fax: 516-484-3493, or 800-CHEY-TEC for Technical Support. Mailing address: 3 Expressway Plaza, Roslyn Heights, New York 11577, eMail arcserve@cheyenne.com or arcserve-win@cheyenne.com (for ver. 5), arcserve-dos@cheyenne.com (for ver. 4) or support@cheyenne.com. They also have an ftp site, ftp.cheyenne.com and a Web site, www.cheyenne.com. Make sure that the hardware that you plan to use is *fully* supported and certified by Cheyenne's compatibility listing and that you have all the *latest* patches and updates for your NetWare and supplementary products. Current version is 5.01G and there is a patch file for this, aw0200.exe. As of May 4, 1995 there is now a Arcserve eMail list run by Kevin Cheek (kcheek@umich.edu) -- send a message to majordomo@mmg2.im.med.umich.edu with a Text/Body line of Subscribe Arcserve or Subscribe Arcserve-Digest to get the digest. NOTE: A lot of people are very unhappy with Arcserve... [Thanks to Robert Maubouche, David Jancan & Kevin Cheek for this] BackupExec is a server based product by Arcada. It is fully SMS compliant and can back up 3.x and 4.1 based server including NDS. It also has the ability to backup other servers as well as DOS, Windows, Mac and Unix client stations. Arcada can be reached at http://www.arcada.com, or at #1101-37 Skyline Drive, Lake Mary, FL 32746, (800) 3ARCADA/(407) 333-7500, Fax: (407) 333-7730, BBS (407) 444-9979. Arcada provides an upgrade for Cheyenne users. A full featured 30 day evaluation is available at ftp.arcada.com. Tech support is available via the 800 number. BackupExec is not as full featured as competing products but it handles backups and restores well. [Thx J.M.] A newcomer is SnapBack from Columbia Data Products. Simply backup your existing drive, prepare a boot diskette, plug in your new drive, boot from diskette, run the restore directly to the new drive (no drive pre-prep). Once your server is back up and running with the new drive(s), run the ReSize option supplied with Snapback to resize your partitions. Columbia can be reached at (407) 869-6700, Fax: (407) 862-4725, BBS: (407) 862-4724, cdpi@cdpi.com or http://www.magicnet.net/cdpi [Thx B.F. & John Sharpe] LANShadow from Horizons Technology, Inc, 3990 Ruffin Road, San Diego, CA 92123, (800)828-3808, 619-292-9439, uses a backup server that can backup multiple servers if necessary and can be located anywhere on the network. [Thx E.T.W.] 45-day evaluation copies of Palindrome's Backup Director 4.0 and Storage Manager 4.0 for Netware 4.1 are available from Palindrome, (800)288-4912, 600 E. Diel Rd., Naperville, IL 60563, (708)505-3300. Also, their software can be found at: ftp://ftp.palindrome.com or ftp://ftp.seagate.com/palindrome [Thanks to P.R. & L.C.H. for this info] H.19.2 Backup hardware products for NetWare Digital Linear tape is 50-100% faster than DAT and more reliable, since the tape floats above the tape heads and are never in contact with it. DLT's work just fine with just about any backup application that you might have. They are ASPI compatible with ASPI drivers readily available. The standard DLT holds 10 GB uncompressed, 20 GB compressed. A new DLT offering was recently released that holds 20 GB uncompressed and 40 GB compressed. The 10/20 GB tapes are about $25-$30 each, the 20/40 GB about $100. Both single drive and jukeboxes are available, with the jukeboxes harder to come by due to the present demand. Quantem owns the rights to DLT, but the technology is licensed to a number of vendors. [Thx G.F.] Note: 8mm tape allows for 1500 passes, DAT - 5000 and DLT - 1,000,000. [Thanks to Shaun@CCNET.UP.AC.ZA for this info] The Intel Storage Express can be equipped with an auto changer DAT drive with up to 24 GB capacity (48 with compression). It can achieve up to 100 MB/sec across the [fiber] network. [Thx B.F.] HP Jetstore 6000: Stores up to 8 GB, 5 drive auto-changer available. [Thx D.T.] Colorado Memory Systems, 800 S. Taft Ave., Loveland, Colorado 80537, (800) 451-4523 Product info/purchase, (970) 635-1501 DOS Tech Support (970) 635-1502 Windows Tech Support, (970) 635-1503 Netware Tech Support (800) 368-9673 QicFAX, (970) 635-0650 BBS H.19.3 Backup methodologies Weekly Full: Five tapes, labeled Monday through Friday. Incrementals are performed Monday to Thursday and a full backup on Friday. The backup horizon is one week. Using ten tapes would extend this to two weeks. Sequential Reuse: This uses five full tapes which are recycled. Four incremental tapes are used from Monday to Thursday, with the Friday full being rotated. This gives a backup horizon of five weeks. Tower of Hanoi: The five full tapes of the Sequential Reuse, relabelled A to E here for brevity, are used as: A B A C A B A D A B A C A B A E. In this method, tape A is reused every two weeks, tape B every four weeks, tape C every 8 weeks, tape D every 16 weeks and tape E every 32 weeks. Using more tapes extends the backup horizon further. Paul Merenbloom method: Tapes are divided into groups of daily, weekly, monthly, and annual. Use eight sets of daily tapes (two-month rolling rotation) and two sets of weekly tapes (104-week rolling rotation). Monthly and annual tapes are set into permanent storage. Cheyenne ARCserve method: Based on a seven-day week, which has at least one full backup that produces a weekly tape. During each week, there can be zero to six daily backups. You have the choice of running full, differential, or incremental backups for your daily backups. Every month a monthly tape is produced. At the end of the year the last monthly tape becomes the yearly tape. This cycle can go on indefinitely. [Th