DM> HUB-------------------+--------+-----------+ DM> | WFWG WFWG DM> WFWG + Novell Server DM> | DM> + NT Server DM> | DM> + UNIX DM> | DM> + UNIX DM> Again, we would like to put the WFWG on their own segment by adding DM> a second network card to the NT Server on the production side. Can DM> anyone explain to me how this can offload the other segments? The DM> WFWG clients only have access to the NT Server on the production DM> server. It would only increase the available bandwidth into the NT server, which, if it is compute bound rather than I/O bound, won't do much for a sluggish NetBEUI system. The data flows elsewhere, such as through the Cisco router, will be the same as before. My suggestion would be to rethink the Win NT server strategy. Either upgrade to full multi processor SMT, run NT on an Alpha, or use the existing NetWare server for the enterprise files to get some adequate file service speed back into the system. Tore tore.hansen@bbs.logicnet.com -- CMPQwk 1.42-R2 391 ... And now for something completely different... --- PCBoard 15.2 * Origin: 32 lines 40 Gig BBS, Realtime InterNet SLIP (403)247-7900 (1:134/10) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00006 Date: 07/27/96 From: TORE HANSEN Time: 10:52pm \/To: DAVID MOHORN (Read 6 times) Subj: NETWARE CLIENT 32 Hello DAVID, on 07-26-96 you wrote to ALL about NETWARE CLIENT 32: DM> Can anyone tell me how to install the Netware Client 32? I DM> downloaded it from Novell's web site. I don't see any executables DM> or any document/readme files that explain installation. Any Novell distribution archive that you download has been created as a self extracting .EXE that is really an ARJ compressed archive. Simply copy it to an empty directory, run it, and answer Y when asked "Continue extraction?" at the bottom of the copyright screen. This will create a subdirectory called IMAGE, containing the disk images, and a batch file called MAKEDISK.BAT. Simply run the batch file with eight freshly formatted 1.44 MB disks on hand. Label each disk as told by the program. DM> I am currently using Windows95 and wanted to upgrade from DM> Microsoft's Netware Client to Novell's. Any help would be DM> appreciated. OK, the instructions I gave above were for "Client32 for DOS/Windows 3.1x". With "Client32 for Windows 95" you only need seven 1.44 MB floppies. Everything else remains the same. DM> If I got the wrong file, can someone please direct me to the right DM> one? C3295D_1.EXE 5,648,481 <-- Client32 for Win 95 - takes 7 floppies DW32D1.EXE 5,952,745 <-- Client32 for DOS/Win 3.1x - 8 floppies That's the ones I have, until Novell releases another upgrade. Hope this helps. Tore tore.hansen@bbs.logicnet.com -- CMPQwk 1.42-R2 391 ... None of you exists, my Sysop types all this in. --- PCBoard 15.2 * Origin: 32 lines 40 Gig BBS, Realtime InterNet SLIP (403)247-7900 (1:134/10) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00007 Date: 07/27/96 From: TORE HANSEN Time: 10:52pm \/To: DAVID ROPER (Read 6 times) Subj: DOS PARTITION SIZE RECCOM Hello DAVID, on 07-25-96 you wrote to FRANK RAMSEY about DOS PARTITION SIZE RECCOMMENDED: DR> What would you recommend as the DOS partition Size on a new DR> 4.1 Server? 15MEG? 25 MEG? 50MEG? More? ...and while I DR> gotcha, what (big stuff) would go into there besides the DR> Novell Patches? I generally use 30 MB nowadays. I used to use 10 MB, but found that to be insufficient. You need to keep a DOS kernel (DR DOS is freely available for this use, so you need not buy a MS-DOS licence), the NetWare server directory, and whatever utilities you need when you have the server down in DOS mode. I keep a NWCLIENT directory, Adaptec EZSCSI, and various DOS hardware testing shareware utilities on the DOS partition. Keeping the DOS partition within 32 MB keeps the FAT tables and the file granularity smaller, so that is basically the size I use as the cutoff. Tore tore.hansen@bbs.logicnet.com -- CMPQwk 1.42-R2 391 ... I am Leghorn of Borg. Prepare, ah say, prepare to be assimilated. --- PCBoard 15.2 * Origin: 32 lines 40 Gig BBS, Realtime InterNet SLIP (403)247-7900 (1:134/10) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00008 Date: 07/29/96 From: DAVID CLIFTON Time: 03:24pm \/To: FRANK RAMSEY (Read 6 times) Subj: Re: 4.1 and files DC> Space is not a problem - over 1.2 gigs available. Compression is DC> enabled at the volume level but disabled at the directory level for DC> these "problem" users. I've noticed that the MicroFocus Cobol DC> editor often changes the file to ro during an edit and doesn't change DC> it back to rw after it finishes. FR> Sounds like a feature of MicroFocus to insure only one person has FR> read/write access to a file. Now I've got to ask, if MF is fooling FR> with a file's attributes, how? Sounds to me like MF might be the FR> problem. Talk to MF's technical support and see if there is a way to FR> turn this feature off. I'm waiting on a return call from MF now. I'll upgrade the workstation lan drivers while I'm waiting (I'm told it could be a long wait....). dc * SPITFIRE v3.5 --- Alexi/Mail 2.02b (#10000) * Origin: Rust Never Sleeps (1:150/280) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00009 Date: 07/30/96 From: FAWWAZ AL-SHOMIMARY Time: 02:14am \/To: ALL (Read 6 times) Subj: Looking for Modem Server Software Hello Everyone, Talking to ya from Saudi Arabia... :-) I need to know what is the best modem server (Software) for Novell 4.1? lease if anyone have any information, please leave me a message here or send me a fax to +966-2-699-2420 (Direct) or +966-2-698-2728 <- (Fax line manager). My best wishes to all, Fawwaz Al-Shomimary /Fido: SYSOP@2:542/300 /Internet: Sysop@fcibbs.woodybbs.com Written on Tuesday 30, July 1996 ... I  Saudi Arabia --- RoseReader 2.80 P007411 Entered at [FAT_CAT] * Origin: FCI-BBS Jeddah, KSA 698-2728 24 hrs (2:542/300) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00010 Date: 07/29/96 From: AL CLELAND Time: 04:19pm \/To: BEN BERGERON (Read 6 times) Subj: AUTO LOGIN TO 312 > *** Quoting Al Cleland to Tore Hansen dated 07-24-96 *** >> >> > However, what you are trying to do can be done by using a >> > simple, single >> > line DOS BAT script like this: >> >> > echo fred > login test >> >> > This will login to account TEST with the password FRED. >> >> Thanks that makes sense looking at it, and I'll try it later >> today, and because the program needs supervisor or equivlent > Put the .bat file in a VERY SECURE PLACE..... being that you are > showing the pW and logon name it goes with! ..... or better yet > get a little util (there are many floating around) which with > turn the bat into a com file. ie. Bat2com by ziff davis. I tried "echo fred > login test" and it didn't work, got a file creation error. I tried variations and found that: "login < text.txt", worked fine where text.txt contained: test fred Ok for now this is what I'm doing, at least til I find something I'm more comfortable with. My program creates the Text.txt file spawns login passing the file as parameters and then overwrites the file and deletes it. If I look at the file all I see is 0000000000000 0000000000000 and I haven't been able to find any remnants of the real USER/PASSWORD on the local HD where its created. I was able to press the reset button as the net login was occuring and there was the file bigger than life, so while I do see a possible security problem given the enviroment where this runs I'm not overly concerned about it at the moment, but I would like to figure out how to do it without writing to disk. I am now using a RAMDRIVE to solve the push the reset button but I know there has to be a better way. //AL --- GEcho 1.00 * Origin: AlTer.Ego 804-463-0095 (1:275/85) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00011 Date: 07/29/96 From: AL CLELAND Time: 04:50pm \/To: TORE HANSEN (Read 6 times) Subj: AUTO LOGIN TO 312 > Personally, I don't use either of these methods. I abhor the > idea of > canned logins with stored passwords. Machines that are set up as > mail > gateways and fax servers, and therefore need to attach to the > Novell > server on an unattended auto reboot basis, I simply set up to > attach > rather than log in, and to do so into appropriately privileged > accounts > that have no password on them. I limit such accounts to a single > login, > and impose the address restrictions available in NetWare to > limit logins > to just those Ethernet card numbers used in the back room > equipment. It > is in my mind a safe and secure approach that eliminates the > need for > scripted password stuffing. A little more on the way of explanation, IBM came out and looked at a small companies computer requirements. This company was running a very stable peer to peer network and a hodpodge of applications that weren't really designed to talk to each other in a user friendly manner yes you could export from one and import into another with various file formats but that wasn't user friendly. Someone who will remained unnamed suggested MicroSoft Office. IBM's solution was to sell the company NOVELL 3.12, WFW 3.11, and Microsoft Office. The company bought it, They also had two proprietary programs that they couldn't part with, one of which was particularly written to work with the stable peer to peer software (a point of sale package tailored to the Pizza Delivery Business) for backup purposes IBM included a Colorado T-1000 tape drive located in one of the workstations. Which IBM never was able to set up to perform automated back-ups of the Server. The company told IBM to go fly a kite, I believe it was a mutual aggreement. Then they called me up, I was able to get most of their problems taken care of rather quickly. The HP4 throwing out garbage from windows applications using Truetype fonts was a little more involved but eventually solved. The weekly server backup is quite functional but requires user intervention to get it started and has to wait for another process to go into an Idle state befor actually doing the backup. this process of course is running on a different work station than the one with the Tape unit. It doesn't require a password and has very limited rights. but it does write a semaphore file to the public directory enabling the backup, logs out, and monitors the login directory for the semaphore to dissappear so it can log back in. The company is not interested in buying a tape unit compatible with Novell. My intention is to move the tape unit to the same work station that is already running the the other process and do everything from there, however if I'm going to do a full backup of the server I can't very well restrict the programs rights. The DOS partition of the server is backed up on floppy disks and I did a BindFix and stored those files on floppy as well. The backup is supposed to be done saturday morning when nobody's home. With the kludgey login and some semaphore files files I have now been able to make it immune from power failures however I'll be much happier when I get the time to go move the tape unit and put it all in one work station and fully automate it. Well except that someone still has to remember to switch the tapes... So thats why I'd like a rather secure method of logging in with significant rights in an automated fashion... //AL --- GEcho 1.00 * Origin: AlTer.Ego 804-463-0095 (1:275/85) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00012 Date: 07/29/96 From: TORE HANSEN Time: 02:31pm \/To: KEN MURRAY (Read 6 times) Subj: DOS PARTITION SIZE RECCOM Hello KEN, on 07-27-96 you wrote to DAVID ROPER about DOS PARTITION SIZE RECCOM: KM> 4.1 needs a MINIMUM of a 30MB DOS Partition - As stated in KM> "Novell's Guide to Netware 4.1 Networks" By: Jeffery F. Hughes and KM> Blair W. Thomas That is what is recommended. You *can* get by with less. The server directory on the DOS partition actually only occupies slightly more than 3 MB after completing a system install from the NetWare 4.1 CD. My $0.02 worth. Tore tore.hansen@bbs.logicnet.com -- CMPQwk 1.42-R2 391 ... Hollowpoints - the ultimate in feminine protection. --- PCBoard 15.2 * Origin: 32 lines 40 Gig BBS, Realtime InterNet SLIP (403)247-7900 (1:134/10) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00013 Date: 07/29/96 From: TORE HANSEN Time: 02:31pm \/To: MUFUTAU TOWOBOLA (Read 6 times) Subj: NETWARE V3.12 AND CPU USA Hello MUFUTAU, on 07-24-96 you wrote to ALL about NETWARE V3.12 AND CPU USA: MT> I have a Novell Netware v3.12, the server is a 486DX/33 and I want MT> to upgrade the CPU on it... What will provide me the best MT> performance between a 486dx2/66 or 486dx4/100 on Netware server, as MT> I have been told that Netware uses Bus rather than the CPU MT> megahertz. I am not very sure how to put... it but from my statement MT> above you can understand what I was trying to ask... MT> So for a Novell Netware v3.12 server which will be better a MT> 486DX2/66 CPU (INTEL) or a 486DX4/100 CPU by AMD or Intel also.... I run both NetWare 3.12 and 4.1 home servers using AMD 486dx2/80 CPUs. The advantage is that the local bus (ie. RAM and VESA or PCI) now runs at 40 MHz instead of Intel's 33 MHz. This provides a real performance boost. I also set the clock division for the ISA bus in the BIOS to 3, giving me an ISA bus speed of 13.33 MHz rather than the standard 8 MHz. This too gives a performance boost, especially as I have an ISA bus NIC in one server, and an ISA bus SCSI card in the other. I don't believe you'll see that much difference between using a 486dx2/66 and a 486dx4/100. As NetWare tends to be I/O bound rather than compute bound, taking up the motherboard speed and adding RAM gets you more in the way of performance than simply going with a faster CPU. Tore tore.hansen@bbs.logicnet.com -- CMPQwk 1.42-R2 391 ... My other network is a positronic net. --- PCBoard 15.2 * Origin: 32 lines 40 Gig BBS, Realtime InterNet SLIP (403)247-7900 (1:134/10) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: DBZ00014 Date: 07/29/96 From: CHARLES MILLER Time: 11:10am \/To: DAVID ROPER (Read 6 times) Subj: DOS Partition Size Reccom RE: DOS Partition Size Reccom BY: David Roper to Frank Ramsey on Thu Jul 25 1996 11:20 pm > What would you recommend as the DOS partition Size on a new > 4.1 Server? 15MEG? 25 MEG? 50MEG? More? ...and while I > gotcha, what (big stuff) would go into there besides the > Novell Patches? I realize HD real estate is cheap nowadays. > Thanks for your opinion here. Peace. > Novell recommends a 15 meg DOS partition for 4.1 Charles ...Exercise your right to arm and keep bears! --- Synchronet+SBBSecho v1.21 * Origin: System Shock: 805-659-5733 & 805-647-7582 (1:206/2406)