--------------------------------------------------------------------- NOV-FTP.DOC -- 19980329 -- Email thread on ftp'able files for NetWare --------------------------------------------------------------------- Feel free to add or edit this document and then email it back to faq@jelyon.com Date: Thu, 16 Nov 1995 19:35:54 -0600 From: Joe Doupnik Subject: Looking for NetWare-related utilities We see a number of exchanges such as the short one below. >>Does anyone know of a utility which would allow >>me to print out the contents of the bindery? >Try "Security >secure.doc" and then nprint the doc May I once again recommend visiting your neighborhood mirror site for interesting and helpful programs. Here is a partial list from one site, directory apps on netlab2.usu.edu, file index in that directory. There are even two utilities which apply to the query above. Joe D. Index to files in APPS ALLNETS ZIP List all NW network numbers ALOGIN20 ZIP Graphical (.BMP) screen during NetWare login. AUD10B3 ZIP Analyize Paudit output for user login durations BINDEDIT ZIP Read/write/edit NW 2/3 bindery, with source code. BLOGIN2 ZIP NW Login, menu driven. 35 day demo from Blaze Tech. CDMAP EXE Map NW volumes to drive letters CDROM ZIP Collection of CD-ROM pgms and tech info, + MSCDEX faker CDVOL UUE View NW volumes as CD volumes on server CHKADDR ZIP Standalone util to perform %P_STATION test from bat file CHKGRP10 ZIP Standalone util to perform "IF MEMBER" test like NW scripts CONMSG ZIP (and .TXT) send msgs from client to server console CONMSG EXE Send a message to the console from a batch file. CREATQ UUE Create print queues on volume other than SYS: DISKALOC ZIP Report disk space usage for entire server, sources DBOOT11 ZIP Reboot client workstation at a time or after delay time DISKUSE UUE Disk usage report DMENU168 ZIP Dougmenu, menuing for NW clients DSKHOG ZIP Report disk space used by each user on a given volume DSKTESTS TXT Informal throughput tests of VLMs vs NETX EDBIN ZIP NetWare server Bindery editor, menu driven ENET10 ZIP Ethernet address show and check EVENT ZIP Simple but effective means of counting events such as logins EXPIRED ZIP Search for users on server without logins since N days FAKESTUB ZIP Fake startup drive, aids formatting from Windows (bootless) FAKESTUB TXT Covernote on above FPS32D ZIP Print server replacement (20 min demo) from Richard Hartman FPS34C EXE Print server (newer version of FPS32D above) FILESFOR ZIP Produce list of all files on a volume owned by a given user FINGER ZIP Finger DOS client for NW 2/3, with source code. FINGERD ZIP Finger NLM for NW 3.x FINGERD1 ZIP Finger daemon NLM for NW 3.11 FNGRD201 ZIP Finger daemon NLM for NW servers, shareware FORCEMAP UUE Map drive letter, no questions asked GETBMODE EXE Return current broadcast mode in ERRORLEVEL GKACHECK ZIP Check client memory and some files against master at login GOLDKEY UUE Map NumLock key to be reported as DEC Gold key GO51D EXE Get Organized, from David Smith, St. Lawrence College GO51D DOC doc for above INIPACK EXT (and .txt) Windows program installation tracker, shareware IOZONE TXT Shell archive of disk throughput test program IOZONE EXE DOS executable version of above IPXWAT10 ZIP IPXWATCH: monitor IPX packets with Packet Driver, sources IQ ZIP Rprinter replacement, 30 day demo ISVLM ZIP Test whether VLM or NETX shell is loaded ISVLM TXT Cover note for isvlm.zip IUPOP3 ZIP POP3 Mail daemon for VMS VAXen, from Indiana Univ JCMD EXE A NW 4.x NDS backup/restore utility (NLM) JRB230A ZIP John Baird's utility suite, version 2.30A KBFIX ZIP Attempts to solve stuck key problem KMAP ZIP Saves/restores drive mappings to/from file LAST ZIP NW 2.15 only! Shows time/date of last logins LASTHOPE ZIP NW 3, preserve then remove bindery. From Richard Letts. LANLK113 ZIP Software metering, shareware LICENCE ZIP Simple DOS application metering software LICMGT11 ZIP Software license mgmt, .bat file method LOCKOUT ZIP Disable logins for all but named people (Beta) LOGINS ZIP Enable/Disable logins from any workstation LPDNLM2 ZIP LP daemon for NW servers MAILHOG ZIP Shows disk usage in NW server Mail directories on vol SYS: MAPNEXT ZIP Maps first free drive letter to network MAPNEXT TXT Cover note for mapnext.zip MASTG340 EXE UUCP mail delivery agent for Pegasus Mail MASSUSR2 ZIP Create/delete/etc users en masse MUM13B ZIP Mass User Management, shareware NETALERT ZIP Deliver msgs to users from server on a schedule NEWS ZIP Nice'n'easy news system MLOG ZIP Mercury (Pegasus Mail) log file utility: log file to ASCII MIRROR ZIP Mirror NW file servers (DOS program) NETADR11 ZIP Follow-on pgm to John Baird's USERS program NETLOG ZIP Report machine usage by hour, monthly summary NETNUM ZIP IP (dotted decimal) to IPX (hex) network number converter NETTT ZIP Net tic-tac-toe, NW programming example NETUTILS ZIP NW client utilities SU2, MAILDIR, NETDRIVE NLOGIN11 TXT Automated login program, man page NLOGIN11 ZIP Automated login program NO ZIP Removes all files of a given type from a disk/volume NODEID ZIP Put NW node ident and video kind into DOS Environment NTT ZIP Shareware, client to server file writing/throughput test NUTIL6 ZIP Collection of NW client programs, shareware NUTL6B ZIP updates to NUTIL6.ZIP NWFILE ZIP NW file utilities NWSEND ZIP SEND for 4DOS clients. Batch files use John Baird's utils. ONCE13 ZIP Schedule client DOS program to run 1-12 day intervals. PAUDIT11 ZIP Basica pgm to do analysis of PAUDIT text output PCNT312B ZIP Commercial printing page counter (including Postscript) PEGMON ZIP Pegasus mail sent if server experiences trouble, shareware PERF2 EXE Perform2, Novell disk/net performance measurement, archive PRFRM3 ZIP Perform3, Novell disk/net performance measurement, archive PORCO ZIP Collection of NW utilities from David Porco PQ TXT Print queue display QLST15 ZIP Shows items in print queues, etc QUEMON18 ZIP View many print queues in rotation QUOTA ZIP Show disk space used (and quota) on NW volume QVIEW224 ZIP View many Print Queues at once, shareware RDATED ZIP NLM + rdate (Murkworks) NLM to offer and acquire time/date RECOVERY ZIP Recover files from corrupted NBACKUP archives RENUSER ZIP Rename users RFINGD10 ZIP Finger daemon NLM for NW 3/4 servers, by Mike Ripley SDLP111 ZIP LPR/LPD NLM for NW 3/4, commercial SELECT16 ZIP Select print queue program SETSDATE ZIP Set the server date from any workstation SETSTIME ZIP Set the server time from any workstation SETUNAME ZIP Set a users Real name from the command line/Batch files SHORT_LN ZIP Deal with long usernames in NW login script SHOWPBAL ZIP Report account balance (suitable for Pcounter too) SHUTDOWN ZIP Shut down system at a specific time, or after 'n' seconds. SOFTCOP TXT A software metering suite, cover note SPLIMIT UUE Disk space limit program (talks to server) STUDENT ZIP Setup NW account via simple Q&A, user run admin SU-31 ZIP Superuser-like program (assume rights of another user) SYNCTIME ZIP Synchronize client time/date from server TALK ZIP Talk pgm using IPX, shareware TOQDIR10 ZIP Find directory for given print queue TNET ZIP Display Bindery contents TSPARSE ZIP NW sparse file handler (remover etc) TSPARSE TXT Cover note for tsparse.zip UNDOC ZIP Several "undocumented" (were) DOS functions USAGE11B ZIP Compile disk space usage report USERDUMP ZIP List all users with realnames, last login time, acct balance USERSCRP ZIP User utilities, for dealing with batches of users on NW WALL ZIP Like the Un*x wall command. Simply broadcasts to all. WHO ZIP Show who is logged on, with real name WHO UUE ditto but not same program (UUE file seems to be incomplete) WHOIS ZIP Show user real name from NW login name WHO19 ZIP Show user real name and station from login info WHO386 ZIP NLM and client pgm, show who has which files open on server WINFCON ZIP Windows FCONSOLE-like program WINONSRV TXT How to install many applications on a NW server, esp Windows WINPRT ZIP Assist printing from within Windows 3.0 WINSEND ZIP Windows 3.1 shell for NW SEND command WNETMENU ZIP Windows 3.1 menuing application-launcher WSUTIL11 ZIP Wolfgang Schreiber Utilities, original site is ftp.novell.de WSDOCS11 ZIP Cover note on wsutil11.zip WWHO EXE Windows pgm, shows WHOAMI and CAPTURE /SHOW information ------------------------------ Date: Sat, 13 Jan 1996 11:54:12 -0600 From: Joe Doupnik Subject: Re: Scheduler NLM >>There is a CRON.NLM; try looking at netlab2.usu.edu for the file. > >I have seen this reply before, but I've never been able to actually >find the file... ------------------ How to find files on netlab2.usu.edu for which you have only a fragment of the name, such as *CRON*.* CD netwire, get binary file WHATIS.ZIP. Unpack it at home, use an editor to look for the desired phrase. Whatis.zip contains the pkunzip and arj listings of what is within archive files in directory netwire. Individual WHATIS.* text files are in the same place, in case you don't want the zip'd collection. There are a number of CRON NLMs. They are written by non-Novell folks. That means they will NOT be in novlib (pure Novell) but may well be in novuser (third party, from Compuserve courtesy of Novell). We don't have a librarian so you will just have to look around. How do folks survive a trip to the library or supermarket? Joe D. ------------------------------ Date: Tue, 16 Jan 1996 17:36:35 -0600 From: Joe Doupnik Subject: Archive area "netwire", important I think the readership should be aware that as of this afternoon, Tuesday, Novell has discontinued offering file archive areas "netwire/novlib" and "netwire/novfiles." Novlib holds/held the update and patch files as seen by Compuserve users, in numbered directories and with proper time/datestamps on files. Novfiles is/was a hot-spot place for the most popular files such as VLM updates etc. Novuser holds third party files from Compuserve via transfer agreement with Novell. Netwire/novlib is gone. Netwire/novfiles is gone. Netwire/novuser is still present. Updates is still present, with all files stamped "today." If you want novlib and/or novfiles material then may I recommend you visit a nearby mirror site *right away* because we can't keep open this area for long. Bring along plenty of disk space to capture what you want. No, there has been not a word to the official mirror sites, nor to anywhere else that I've seen. Joe D. ------------------------------ Date: Wed, 17 Jan 1996 07:27:55 +0000 From: "Mark S. Edwards" Subject: Netwire - the cynical view As of this morning the novfiles area of the netwire directory on ftp.novell.com is discontinued. First they try and force everybody to use the updates directory structure, but just to make it difficult they touch all files every night so that every file has the same timestamp. Now they kill off the only remaining area where you could quickly scan for new patches. This looks like the trick British Railways use to close down lines they don't want maintain, they deliberately change the service so that its of no use to anyone, then get rid of it completely by pointing out that nobody uses it any more. ------------------------------ Date: Sat, 20 Jan 1996 19:16:03 -0600 From: Joe Doupnik Subject: Re: Netwire - the cynical view >If it is so that Novell stopped with the novfiles area Alas, it is so. >(and not just because of some error) and we don't like that, >then maybe it would help if we did what has happened with >TV-stations that stopped popular series. >Send a lot of mail! > >Good idea? --------- Not a good idea. Look, you want to influence the person making the management decisions, not the troops in the trenchs. How much attention do you think mailbombs will get on that person's desk on a busy Monday morning, and if any then what would the person think of the bomber? That is not the way to gain attention, win friends, influence decisions. The way you do it is to write a very reasonable, calm, business-like message or letter to the best contact in the outfit: bfrank@novell.com, starting as Dear Mr. Frankenberg. Take matters from your position as to what you gain and lose, and be very careful to avoid evangelizing on behalf of the rest of the world (will discredit your arguments instantly). I can assure you that beating up on the service people will get nowhere, and going to middle management will be equally unproductive (since they have a full time job of surviving and avoiding being caught in battles). Your, or my, *opinion* on matters counts for nothing. What counts is what happens to our customers, and hence to Novell's revenues and public image. It's not our job to run the company, despite many who think otherwise, so we don't use that tact. Instead we represent our customers/clients and are speaking for them. Don't forget to add a job title and other embellishments under your signature. You can also talk with the trade press, but there is considerable risk that the end result won't be similar to what you envisage. The trade press is looking for news, contraversy, juicy items, and the victim is often the person making statements (not the publication nor the target). Joe D. ------------------------------ Date: Sun, 21 Jan 1996 05:24:26 -0400 From: Eric Harold Subject: Re: Netwire - the cynical (and hidden from) view Around 5:00am EST, I logged into Novell's FTP site. At that time, ALL files and directories on Novell's FTP were hidden (They are, however, accessible if you know the full pathname). Are we now on a need-to-know basis? I suspect that, next, Utah will be removed from the map. At least, we still know JRD's full pathname. Eric Harold (eric@unoverica.COM) President, Unoverica Corporation 6731 Banner Lake Circle, Suite 12206 Orlando, Florida 32821-9392 Tel: 407-238-2310 Fax: 407-238-2565 URL: http://www.unoverica.com/ ------------------------------ Date: Sun, 21 Jan 1996 18:41:49 +0000 From: Marc Bornebusch Subject: Re: Ah, Novell...I remember that company... >Hello Bob, > >I am writing to convey a few thoughts on Novell's decision, the most >recent and worst in a long line of insults to those dependent on >Novell Internet list. > >It's a matter of revenue, isn't it? > >When people suck back files on CompuServe, your company gets a few >bucks. But when the same people get files from your ftp site (or >listserver, as they used to do before you shut down that service) then >it actually costs Novell, Inc money. > >My reply to this approach is to suggest you retire now, and sell >as many shares as you can as soon as possible. > >[In case you haven't noticed]Every company is providing web/ftp >service these days...and there is no thought of losing revenue >or crippling the service or changing file dates and times to >today's date so that the service is next to useless and thousands, >yes thousands, of people have to grovel like dogs. > >What you/Novell are doing is so beneath me I won't hurl negative >adjectives at you. Instead I will let your own conscience, shame >and remaining fragments of business sense snap you out of your most >recent stupor. > >Don't forget what business you are in, Bob... > >Floyd Maxwell >Novell Internet list FAQ Maintainer & >Project Manager at a 400 employee engineering firm that is >depending on NetWare systems and updates to get their job done. On the assumption that you are talking about the Netwire ftp site I was told recently by a Novell person that they had been restricted by their Compuserve agreement from replicating Netwire on the web until the files were SIX MONTHS old - restrictive practices I'd call that. If that is the case I would not blame them from removing the facility. However I see no reason why the files (Novells property) could not be placed on a web site similar to but not named Netwire. Once the legal eagles get involved common sense typically goes out of the window - maybe that's what has happened. Hope I'm talking about the same thing as you. Good luck. Ian Gordon ------------------------------ Date: Sun, 21 Jan 1996 20:09:17 -0600 From: Joe Doupnik Subject: Re: Ah, Novell...I remember that company... >On the assumption that you are talking about the Netwire ftp site I was >told recently by a Novell person that they had been restricted by their >Compuserve agreement from replicating Netwire on the web until the files >were SIX MONTHS old - restrictive practices I'd call that. > >If that is the case I would not blame them from removing the facility. > >However I see no reason why the files (Novells property) could not be >placed on a web site similar to but not named Netwire. > >Once the legal eagles get involved common sense typically goes out of >the window - maybe that's what has happened. > >Hope I'm talking about the same thing as you. ------------ Let's see if I can hockeystop rumors and say something nice in the same message (it will be a struggle...). The above certainly looks rumor-ish to me, and none of us know what the CIS story really is, if CIS is involved at all. So maybe we should let the item rest. For those who are puzzled by all this, be aware that CIS has subscription terms which read close to "you put files on CIS and CIS owns distribution rights." Legal interpretations are best left to real lawyers. The nice thing is this. Archive area netwire\novuser is filled with programs from third party (non-Novell) authors who placed their material in Novell's section of Compuserve. Some time ago some of us worked in the background with Novell to get a legal statement acceptable to all that gave Novell the right to offer those files on its Internet machines (and hence also on the official mirrors). Novell didn't have to do that since they made no money on the arrangement and it would be their neck in the noose during a contraversy. But they did go ahead, and the files are available with agreement of the authors and CIS. The files are still offered on ftp.novell.com (plus or minus snafus in the machinery area) and on the official mirrors. I think Novell should be patted on the back for this public service. And, in case it's not apparent, sites offering someone else's files needs to have permission of the owner/author to carry them in some cases. It's a curious point, but an important one where authors wish to control distribution. See the fine print at the bottom of top level file "index" when you log into netlab2.usu.edu. Sorry to belabor the points, but newer members of the net are probably unaware of how all these wonderful things came about and survive to this day. Joe D. ------------------------------ Date: Mon, 22 Jan 1996 07:18:52 GMT From: Kevin Pidd Subject: Re: Ah, Novell...I remember that company... I don't know for sure, but I think the ftp server just has a technical problem. When I access it via a windows ftp utility, I can't see any files. When I access it using a DOS utility, I can do an ls and see the files as normal. I think it has been reported as lets hope it is fixed soon. Regarding Compuserve and Netwire, Novell owns the files but the discussion groups are owned by Compuserve. So you can't publish the contents of the discussion forums without Compuserve's permission and that is probably what the six monthe rule is referring to. The file updates can be redistributed by anyone as per the disclaimer inclued in each file. Best rgds Kev (speaking for myself) ------------------------------ Date: Mon, 22 Jan 1996 14:26:35 UT From: Dave Kearns Subject: Re: Ah, Novell...I remember that company... >On the assumption that you are talking about the Netwire ftp site I was >told recently by a Novell person that they had been restricted by their >Compuserve agreement from replicating Netwire on the web until the files >were SIX MONTHS old - restrictive practices I'd call that. > >If that is the case I would not blame them from removing the facility. There is NO restriction on Novell putting Novell files on any site in addtion to NetWire on Compuserve. There is a restriction on files uploaded by 3rd parties to Compuserve's NOVUSER forum. These are the files subject to the "6 month rule". Dave Kearns Sysop, Compuserve's NetWire 76704.62@compuserve.com ------------------------------ Date: Mon, 22 Jan 1996 11:05:29 -0600 From: Joe Doupnik Subject: Re: Netwire - the cynical view >Just a couple of comments on the internet services... Snipping the above message to give a tiny progress report on the empty-filename problem at ftp.novell.com. It's a strange problem, and probably an interesting one after it's been identified and fixed. "ls" and "dir" return nothing, "nlist" returns directory names. Sure seems like a wierd software gotcha. In any case, Novell is working on the matter at this moment, they see what you and I see and from the same vantage point. Files & listings are available from the mirrors. The dust will probably settle after local lunch time today when thought can be applied quietly. To other sysmgrs: what do you do when the sky falls, the user community yells and screams, and the intrinsic problem just doesn't reveal itself? Oh, "reboot" is it? Joe D. ------------------------------ Date: Tue, 23 Jan 1996 03:47:18 GMT From: Barry Davis Subject: Re: Ah, Novell...I remember that company... >Hello Bob, > >I am writing to convey a few thoughts on Novell's decision, the most >recent and worst in a long line of insults to those dependent on >Novell Internet list. > >It's a matter of revenue, isn't it? > >When people suck back files on CompuServe, your company gets a few >bucks. But when the same people get files from your ftp site (or >listserver, as they used to do before you shut down that service) then >it actually costs Novell, Inc money. > >My reply to this approach is to suggest you retire now, and sell >as many shares as you can as soon as possible. > >[In case you haven't noticed]Every company is providing web/ftp >service these days...and there is no thought of losing revenue >or crippling the service or changing file dates and times to >today's date so that the service is next to useless and thousands, >yes thousands, of people have to grovel like dogs. > >What you/Novell are doing is so beneath me I won't hurl negative >adjectives at you. Instead I will let your own conscience, shame >and remaining fragments of business sense snap you out of your most >recent stupor. > >Don't forget what business you are in, Bob... I agree completely with you. If Novell has to scratch for a few pennies from C$S for the file downloads it doesn't say very good things about their state of business. Novell, do you really need the money that bad? Is this how you treat the people who support your product by forcing them to go to a pay site (C$S) to get updates? One more nail in the Novell coffin. ------------------------------ Date: Wed, 24 Jan 1996 00:33:00 MET From: "Arthur B." Subject: Re: Netwire - the cynical view >>Novell must have had some reason for stopping novfiles and only if they >>believe that lots of people wouldn't like that they could consider >>bringing the service back on line. What counts here is numbers. >> >I'd thought I'd already posted this, but (perhaps to reiterate). The >directories NOVFILES and NOVLIB mirrored forums on Compuserve. Those forums >have now gone away (in favor of NWOSFILES, NWGENFILES, etc.). Since its easier >to promote all of their on-line services together, they need to have as >similar file paths as possible. Thus, NOVLIB and NOVFILES were removed from >the FTP site. They aren't going to come back, no matter how many people write. > Sorry, lack of sleep and time has caused my reading of my e-mail to speed up. Must have missed your e-mail while sending my own. Back to the problem. Let me understand it first.. 1. Compuserve/Novell (one or both) find it a good thing to promote all of their on-line services together. * I have no problem with that. 2. NOVFILES and NOVLIB mirrored forums on CompuServe. But because of 1. they had to go. * This I find a problem. Has there been a warning that this was going to happen? (so people could prepare) No? Why not? Yes? Some of us have missed it. Any ideas why? A lot of people use bookmarks and so on (there real handy). Now many people have to modify there saved settings because it seems impossible to keep the 'old' ones around for a bit. NOVFILES and NOVLIB are stuck in peoples mind around the globe, you don't change that within a year. Have you ever heard of 'Symbolic links'? Isn't there a single solution to this problem? Somehow restore NOVFILES and NOVLIB without causing big problems for Novell and/or CompuServe? Something to make everyone happy again or at least give them time to get used to the new idea? Imagine that I would suddenly decide to remove F:\DATA\USERS and change it to F:\HOME\USERS because I linked up with some other network that has that directory-structure. If a would to that today can I work for you guys then (because I imagine I would be looking for a new job then)? Perhaps you find this a bad example, I do not. No, maybe you have very good reasons for what has happen, but I feel a little bit left out in whatever reasons there where for doing what has happened. Hope you see my view on this subject. ------------------------------ Date: Sun, 28 Jan 1996 20:01:18 -0600 From: Joe Doupnik Subject: Re: Question to Novell >It was never easy to find out what are the latest patches for >Netware, but now that files are marked hidden in the appropriate >directories, what sense does this make? Well, there is a reason why some files are invisible. You can guess by the common name construction: blahIT.exe and blahFT.exe and similar. Those are not yet fully tested and are made available only upon customer need, as determined by Novell Tech Support troops. They tell you the filename, you can ftp it by name but we can't see a list of filenames (ls, dir). Clearly, putting them on production servers is a risk the system manager must consider. Yes, I know that left and right hands often are unsynchronized and there is no message "synthetic hand time is being used" beeping round the company. This means one group says "you really must employ 410IT6.EXE" and another group says "it's still IT flavored, not ready for prime time, and thus it should remain invisible." Generally, everyone means well. The files released to the general public are visible (when ftp.novell.com is visible). Mirror sites do not carry the NSD invisible series. Please do recall that recently all files became invisible in Provo due to technical difficulties, but that event lasted only about 18 hours. They have been back to normal for many days (including today). I put msgs on this list concerning the event. Joe D. ------------------------------ Date: Sun, 18 Aug 96 17:33:45 CDT From: John_Cochran@odp.tamu.edu To: netw4-l@bgu.edu Subject: Re[2]: FTP for Netware 4.1 revisited I must say that both of the FTP NLM's (MurkWorks and HellSoft) have installed and work pretty flawlessly. Of course, the one hour functionality on the MW demo version isnt very practical, but sufficed for testing. I like the Hellsoft's capability of being able to run the FTP nlm on one of your Netware servers, but allowing you access to any FTP server within your network. This I found very useful because I will only have to run the FTP nlm on one system! One problem that I am having with the HellSoft one is that it cannot read anything from volumes that have the underscore character in their names. This is a major problem for us since most of our user volumes have this underscore character (ex. server_volume). Novell's FTP and MurkWorks FTP do not have this problem. Are other users of HellSoft's FTP seeing the same thing? (Under both Netware 4.1 and 3.12) ------------------------------ Date: Mon, 17 Mar 1997 12:07:08 -0600 From: Joe Doupnik Subject: Re: NWAdmn95.exe -Reply >>I've seen references to this file in a thread over the past few days. >>The name obvioulsy suggests it's a Win95 app, but I've never seen it. >>I'm running NW 4.11 and the NWAdmn3x.exe that came with it. The >>Help-About information is "Netware Administrator for Windows, ver >>4.11.11". I notice the lack of the "windows 95" tag. > >>Novell's Web site doesn't contain a NWadmn95.exe file >>Where do I find the nwadmin95.exe and supporting files? >Here is the URL that should get you what you need: >http://support.novell.com/Ftp/Updates/nwos/nw411/Date0.html ------------- Big Red Flag: Look in updates\nwos\your-os-version and see file 00Index. Use FTP, not a dumb web browser, nor a http labyrinth. Direct, unambigous, shows all. Please make a note of this facility. Once you do this then all kinds of goodies will become visible. To ftp (remember that? The File Transfer Protocol not the decorate my screen thingy), go to either ftp.novell.com or to one of the official mirror sites (two of which are netlab2.usu.edu and netlab1.usu.edu). Happy hunting, Joe D. ------------------------------ Date: Tue, 17 Jun 1997 10:34:56 -0600 From: Joe Doupnik Subject: Re: patches for IntraNetware >Good morning Joe, I know you think folks that use the Web and Web >browsers are techno wimps....but, when I use my FTP client and/or my >browser to reach the Netlab2 sites, I receive an error......at one time >you mentioned something about using REAL FTP with a port number...how is >this done? ---------- I didn't say wimps nor did I rate the people involved. On the other hand using feeble tools is not always a good idea. Netlab2 is a NetWare 3.12 file server, using NFS 1.2C from Novell to provide TCP/IP services including ftp support. The full filename listings of ANY ftp server are completely up to author of the code; there are NO rules on what it looks like because it is intended for real human beings. Alas, web browsers try, and often fail, to read such displays; screen scraping is the name we use. Netscape, in particular, has parsing trouble when it sees whitespace where it really wants to see a filename. Feeble tools. Ftp to netlab2 works just fine. Nothing special is required. But don't web browser screen scrape with broken tools unless you are prepared to correct the errors by hand (remove the whitespace). Please do look at the screen to see what your program is attempting to perform. Ftp to netlab1 works just fine too. It is a real Unix machine, using UnixWare 2.1.1. Netscape does better here, and netlab1 also provides a real web server (Apache) to help. Netlab1 holds all the files from netlab2 under directory heading pub/mirror; it's done by NFS mounting netlab2 to netlab1. FTP is a protocol, File Transfer Protocol, an Internet standard. If it is strange to newcomers then I recommend becoming familiar with your ftp program; read the manual and experiment. It is a sharp tool. One cannot be uninformed about ftp and still claim to be a networking professional. Gentle reminder: the machine names are netlab1.usu.edu and netlab2.usu.edu. There is no prefix of www nor suffix of com. At the top of the anonymous ftp heirarchy is file "index" which describes the immediate subdirectories. It's worth reading. There are many third party utilities in apps and misc and drivers. UnixWare is supported under UnixWare and third party UW material is in freebird. Kermit material, ODI material from Novell, NetWare manuals, and so on are present, as well as all the NW updates/patches (under updates). These two machines are official mirrors of ftp.novell.com and related places. They are remirrored nightly. They are as safe and secure as the originals, and must be by legal arrangement. Time and resources are devoted to keeping them that way. Don't be disappointed by displays that make no attempt to dazzle or entertain. I have zero tolerance and zero time for that unproductive aspect. Files are present for those wishing to take advantage of them. The list's FAQ is on netlab1.usu.edu for web browser access. That has become an obligatory reminder to newcomers. Joe D. ------------------------------ Date: Wed, 25 Jun 1997 18:30:48 -0600 From: Joe Doupnik Subject: Re: Can someone share exactly what is wrong with FTPSERV.NLM? >>If it helps, our use will be relatively low-volume FTP >>access for authenticated users to get/put files from >>one of our INW 4.11 servers to their home computers. >>We won't be getting into any type of high-volume >>anonymous service. Thus, my main question is really >>"if we turn this on, what bad things can happen?" > >Not totally relevant, but we've been using the FTP service under 4.1 ever >since it shipped and have had no problems at all. We don't have any high >volume stuff - just usage as you suggest and it's been fine. Sometimes we >do a transfer > 250Mb with no problems. No complaints at all. > >If you're having a problem with the 4.11 FTP server (when/if you get it >running), maybe you can try getting hold of an older version - I have no >idea if it works or not, but it _might_ be worthwhile trying... --------- It has a multitude of problems. Outside folks can probe your system and find every server connected by IPX and the Tree and more that I'd really not like to mention on an open list. If you use ftpserv please put it behind a good firewall. Please contact me directly for a hand patched edition which only slightly reduces exposure. I can't make this available for anonymous ftp. If possible I recommend not using it at all. I can say that Novell is well aware of the details and is working on a new version (but we have no timeline for release). Joe D. ------------------------------ Date: Sat, 12 Jul 1997 05:48:25 -0700 From: Floyd Maxwell Subject: Re: MurkWorks FTPD.NLM >With all the problems surrouding the Novell FTPSERV.NLM, I've been >looking around trying to find alternatives. For my application, >I really need long filename support and graphical FTP browser support, >which kills the possibility of using the Hellsoft FTPD.NLM. This >appears to leave only the MurkWorks FTPD.NLM. Their current beta >adds long filename support and seems to work well. > >Does anyone have any opinions good or bad regarding their previous >product, or are there any other NLMs that I should be looking at for >this? I recommended we use MurkWorks FTPD.NLM at my last place of employment, and we did -- Brad's support via email was very good (he's a very patient man ). The printed docs could be enhanced by more complicated examples for the commands...ditto the example CFG file. Also it would be helpful to show or explain what does not work (you know, the old command parsing problem -- Murkworks is pretty specific about what it is looking for). It is very stable, provides good performance, and is "alive" (i.e. ongoing improvements, bug fixes, support). ------------------------------ Date: Mon, 11 Aug 1997 17:12:45 -0600 From: Joe Doupnik Subject: Re: Webserver slow response >I have an Intranetware 4.11 web server and when I first try to connect to >the home page, It takes like 30 seconds for the server to respond. >I have DNS running on the same machine, the entries are present for the >server and all seems to work ok, except for the lag time. There is NO >traffic between the time the client requests the page and the server >responds with the page. I don't have lanalyzer to look at the packets, but >it seems to do it at the FIRST attempt of the client request after having >launched the browser. Subsequent requests seem to have immediate response. ----------- I see shorter lags. But I believe they are involved with reverse IP lookups to find who you are by IP name rather than just IP number. Thus if your client's IP info were also on the server in the DNS material it ought to find the scoop rather quickly indeed. There can be, with some web servers, an identd probe sent to discover who lies behind an IP number, and obviously regular DOS/Windows machines don't know about that and don't respond (meaning, time goes by). LZFW should show that, as well as any remote DNS lookup by the server (assuming LZFW and server are on the same wire). Once identified information is cached so that subsequent requests go along quickly. What I see beyond what you have reported is lots of fragmented pages. The pictures are often missing. I interpret this as the NW web server pushing out information faster than the web client is prepared to accept and packets are dropped. In my case client and server are on the same wire. Joe D. --------- Date: Tue, 12 Aug 1997 09:21:41 -0600 From: Jason Green Subject: Webserver slow response -Reply FWIW, I had the exact same symptom running the Novell Webserver 3.0 and 3.1. It would take approximately 30 seconds to make the initial connection from a browser (in my case I was even on the same sub net). Once the connection was made, everything worked just fine. I was running it on a low power server so I just figured it was because of that, but then I moved it to a real server (HP Netserver LC with 140 MB RAM) and had the same problem. I was to the point of shelving NWS for a different web server. After doing some testing and not loading everything, I was able to fix the problem by not loading Novell's ftp server. I went back to the other server and unloading the ftp server fixed the speed problem on it also. I don't know why it slowed down, but it is running just fine now. I moved ftp services to a unix machine which is where they should have been anyway. ------------------------------ Date: Sat, 13 Sep 1997 19:55:00 -0700 From: Hansang Bae Subject: Re: TFTPD Server >>Is there any way to make an IntraNetware server a TFTP Server? > >FTP Services for IW, the 4th CD in the set has a TFTP server component. >After install, look at sys:etc/inetd.cfg, and see that the corresponding >line is commented out by default. Remove the semicolon, and go! You >don't have any other management options to play with. Keep in mind that tftp (trivial ftp) can be a BIG security hole. As no passwords or usernames are required. It's typically used to download bootstrap code or new firmwares. So make sure you know what you are doing before implementing tftpd. ------------------------------ Date: Sun, 8 Feb 1998 11:50:15 -0700 From: Joe Doupnik Subject: Re: FTP daemon recommendations >>>The very last product in the known universe that I would >>>recommend is Novell's FTP "NLM"..."dousing a candle with a >>>fire hose" comes to mind..."garbage" also does. >> >>What's SO BAD about Novell's ftp daemon? I've installed it a few >>places and it seems to work. I'm not doing anything terribly serious >>with it so it hasn't been pushed very hard. If there are serious >>problems with it, I'd like to know what they are. > >Well, aside from the bugs and security problems, it requires >a ton of stuff to be installed. NWIP is a monster, RAM-wise >and module-wise. With the worst DNS product I have ever seen. > >Murkworks FTPD.NLM takes some tiny fraction of an MB of RAM. >One NLM (maybe two, it's been a while) -- load it and go. >Next to no "interface" complexity, reinitializes in a few >milliseconds. > >The point is that we installed on a separate 200 MB hard drive >NW server, and then had to bump the RAM to 32MB just to be able >to run NWIP...some of the "core" modules wouldn't even load! >Ridiculous. Like installing all of MS Office to use the clip art. > >Floyd Maxwell ------- Golly, I wish you hadn't mentioned MS Office 97 ClipArt. It's my current systems worry... For what it's worth and in the interest of tracking the discussion I brought up DNS service on a INW 4.11 server, via a beta of NFS 2.3 for INW 4.11. It was easy to do and the memory consumption was very modest, under 100KB by quick count for managing itself and no other zones. This is not NW/IP. I am not counting memory consumed by other items such as NIS (ugh) and NFS etc on my system. In regard to existence of PTR records, the Unixcon utility (via rconsole) created them on the fly, and said as much (creating in-addr.arpa entries). Displaying the results showed the A records and NS records, etc, and one can (and should) edit the details while still in Unixcon. The problem here seems to be confusion in the program about "domain", "host" and "zone". These terms are special for DNS work. To set the record straight, "domain" is a branch of the DNS tree, such as all of novell.com. A zone, on the other hand, is a subset of a domain and means the region managed by a DNS server; it is the part of the domain for which the server is an authority. If a slice of novell.com is delegated to another on-site DNS server then the zones are smaller than the domain, but taken together equal the domain. A host is the name of a particular machine and it is one word (the first, leftmost) in a dotted string Fully Qualified Domain Name; the domain is all the rest of that string. If one compares the process of using Unicon to setup a DNS server with that of building and installing Bind v4 or v8 plus wading through the "DNS and BIND" insect book (O'Reilly & Assoc) for a Unix machine then the Novell version is vastly easier. I have been doing all three over the past ten days. The Novell version shields one from many gory details, yet I would be happier dealing with the details (just my opinion, yours may differ). On ftpd.nlm's. I've run three flavors here: Novell's for NW 3, for NW 4, and Brad's (Murkworks Inc). Brad's is slick and recommended. Novell's have had a long history of difficulties, and as I have remarked the NW 4 rendition is being redesigned and rewritten for Moab. I would not expose the present NW 4 ftpd.nlm to the world, but I have run the NW 3 flavor to the world for many many years (netlab2.usu.edu uses it). On running a DNS server at all. If one runs a web server on NW then running a caching-only DNS server on it is recommended. The reason is web serving is a large sequence of individual connections, one per piece of a web page, and each connection can result in a DNS lookup of the IP name to number, and also the reverse (two lookups). Those may have to travel across the Internet. A caching-only DNS server on the web server has memory and thus a lookup pair occurs only once and not for every tiny thing. There is a big improvement in performance, and reduction in Internet traffic, by creating a local cache of DNS information. A caching-only DNS server is one which is responsible for next to nothing. Make it authorative for only localhost (127.0.0.1), which is in fact a strictly local item anyway. It will then remember info gathered from other name servers in the course of resolving IP numbers of callers. Joe D. ------------------------------ Date: Mon, 2 Mar 1998 13:24:47 -0000 From: John Lyon Subject: Novell FTP (revisited, with comments) Just went thru the Building an Intranet w/ IntranetWare course, and boy, are my arms tired. Why? All the typing to set up Novell FTP. I'll be looking for another solution for our needs (one point of admin, and lfn support) elsewhere (wonloo, murkworks and/or hellsoft) thank you very much. --------- Date: Mon, 2 Mar 1998 12:37:03 -0700 From: Joe Doupnik Subject: Re: Novell FTP (revisited, with comments) >Just went thru the Building an Intranet w/ IntranetWare course, and boy, are >my arms tired. Why? All the typing to set up Novell FTP. I'll be looking >for another solution for our needs (one point of admin, and lfn support) >elsewhere (wonloo, murkworks and/or hellsoft) thank you very much. ------- Don't give up quite yet. Improvements are in the works. After all, they can't make it any more complicated than it is presently. The timeline for the improvments is the unpredicatable part, and I can't offer much here except summer is a natural interval (NW 5 time). Novell does have the word on these things, I assure you. Joe D. ------------------------------ Date: Wed, 18 Mar 1998 13:54:13 -0700 From: Joe Doupnik Subject: Re: FTP Server in UNIX Print Services >I have Novell's UNIX Print Services 2.1 running on a 4.1 server. The reason >this package was added was for FTP server functionality. (We have been >using this regularly from within the domain.) The problem is that FTP users >from outside the domain cannot access the server. They can however >successfully ping the server. > >What I know so far: > >This package includes a utility called UNICON to config/manage the >installation. In UNICON there is an option to Restrict FTP Access. This >option is actually updating the Restrict.ftp file (SYS:ETC). I have added >the commands needed to allow access, to no avail. Furthermore when I go >back to the menu option to edit these settings the script is blank. > >I am not aware of any patches for this version of UXP. ----------- The current release for NW 4 is NFS version 2.3. It is an interim release at that. In just about all the NFS for NW 4 releases the restrict control is pretty badly broken, as is what ftpserv itself provides. I hate to say these things about a Novell product, but this one has been a sore spot for a long time (though the troops are working on improving it). In the meanwhile edit sys:etc\restrict.ftp by hand and test it thoroughly before exposing your site to the Internet. Joe D. ------------------------------ Date: Sun, 29 Mar 1998 17:39:43 -0700 From: Joe Doupnik Subject: Re: Novell FTP and Long file names. >This does not seem to work, I am running the latest ftp nlm (IWSP5) >Is this true? ------ Try QUOTE SITE UNIX at your ftp client's prompt. You should be able to set the default presentation to Unix or NW/DOS in the server's ftp configuration. Be aware that MS style long filenames are unlikely to be worth anything via FTP because the latter does not want names with embedded spaces. MS style long filenames are, at least today, a poor hack on top of things. That's not to say they may be a good idea, but the way they have been implemented by MS is terrible. Smart sites use 8.3 format for DOS/Windows material, and regular Unix names for Unix systems. Joe D. ------------------------------