--------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1Q00004 Date: 01/20/98 From: SCOTT PARKS Time: 07:08am \/To: LUIS MANTEROLA (Read 3 times) Subj: win95.nam or unix.nam Luis Manterola wrote in a message to Scott Parks: LM> No, we are talking about different things. LM> ADD NAME SPACE OS2 TO and you must do this only LM> once for each volume. It may be that easy for NW3.12+ but I believe 3.11 requires the "supportLFN=2" that Jonathan suggested. I'll find out today if that fixes it. --- GEcho 1.11+ * Origin: (1:343/70) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1R00000 Date: 01/20/98 From: BERND HEUCKENDORF Time: 10:09pm \/To: SCOTT PARKS (Read 3 times) Subj: New NW4.11 install Hi Scott, Scott Parks wrote in a message to all: SP> The first real problem was with TCP/IP. I created an autoexec.ncf SP> similar to the 3.11 machines ... but now INETCFG REM's out the Load SP> and Bind statements and refers to another NCF in ETC directory. It SP> did not accept my Bind command for IP, did not REM it out .. and SP> now when I try to add TCP/IP from the Console in INETCFG it won't. SP> 802.3 is working fine. There's no need to add/change protocols manually in INW (actually NW 4.x). After running inetcfg for the first time, the new configuration is stored in sys:etc\netinfo.cfg and at startup configuration is loaded using the initsys.ncf file from autoexec.ncf. You have to configure TCP/IP first, using the option "Protocols" then bind TCP/IP to a network card using "Bindings". You will have to use Ethernet II or SNAP to bind this protocol, 802.x won't work. SP> Is the purpose of Netsync3/Netsync4 (I think those are the names) SP> to allow the 3.11 servers to be added as objects to the current SP> tree or can they be added? Or are they only for migration? You can add NW 3 servers and its users to the NDs using NetSync. But this utilityy is for temporary use only. You should use it when migrating to NW 4 and want to do all administrative work with NDS utilities and discard all bindery tools. SP> Also, how many patches are there for NW4.11 at this point? I'm not SP> too interested in the Internet features yet. I hope patches are SP> still a matter of just replacing files rather than the MS style. IWSP4A.EXE is the main service pack for 4.11, replacing a lot of NLMs and has a size of >10 MB. Bernd --- * Origin: Please state the nature of the medical emergency (2:2433/1224) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1R00001 Date: 01/19/98 From: JRD@CC.USU.EDU Time: 06:01pm \/To: ALL (Read 3 times) Subj: MS won't support NT with NDS -=> Note: Copied (from: bit.listserv.novell) by Scott Parks using timEd. From: Joe Doupnik Subject: Re: MS won't support NT with NDS >Some interesting reading from Wired.com: >http://www.wired.com/news/news/technology/story/9739.html >http://www.microsoft.com/ntserver/comparisons/ndsfornt2.asp?A=2&B=12 >http://www.novell.com/lead_stories/98/jan16/bridge.html > >Basically, MS has stated a policy that if you are using NDS for NT, you >have broken the OS, and they can no longer support you for some problems. >Most interesting to me was their claim that NDS for NT replaced 2 or three >DLL files (depending which part you read), when in only replaced one. MS >also says that NDS for NT will break NT's C2 security. Last I knew, NT >couldn't have C2 security if a network card is installed. --------- This particular dustup flared about a week ago with a particularly unpleasant web article by Microsoft (www.microsoft.com/ntserver/comparison/ nondsfornt.asp). Novell replied on their web page, as we can see by visiting it. The original MS article seems to have vanished and what's left is some much outdated FUD. The points of interest seem to be NDS4NT is an exceptionally clean replacment for NT SAM (sec access man) which puts NT authentication and management into NDS, and which can be cleanly undone later. Thus managment of NT domains becomes one (NDS) point of management. Only one DLL is eplaced, not two or three. And it works with NT 5 beta. That's very neat work, indeed. Novell's web material explains the technology. On security ratings. INW 4.11 has C2 capability rating on the etwork. As I recall, NT 4 has C2 rating only if no floppy drive and no lan adapter are present. Given our previous discussion on ways bad guys can subvert NT both components do seem to be open invitations. Hopefully NT 5 will plug the holes, but that will need to be demonstrated. MS' reaction was to declare NT customers are out of luck: no support from MS if they use NDS4NT. Needless to say, this is not a pleasant tactic. Compare this with Novell's statements about customer support and folks moving from one vendor to another. Joe D. --- GEcho 1.11+ * Origin: helix.uucp =FidoNet/Internet= Seattle 206.783.6368 (1:343/70) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1S00000 Date: 01/06/98 From: CHARLES MILLER Time: 10:53am \/To: MICHAEL PATRICK (Read 3 times) Subj: NETX under win95 RE: NETX under win95 BY: Michael Patrick to All on Thu Dec 04 1997 08:11 pm > any know if there is a netx.exe that will work under win95 dos mode? > > I would like to use a win95 boot disk with netware drivers to attach to > servers and would like to upgrade my boot disk from Dos 6.22 > NETX.EXE should work fine under Windows 95 DOS mode. I just got through upgrading 500 machines to NW 4.11/Win95 and we had to run DOS mode until the rollout. We used NETX and it worked just fine. Charles --- Synchronet+SBBSecho v1.22 * Origin: System Shock: 805-659-5733 & 805-647-7582 (1:206/2406) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1S00001 Date: 01/06/98 From: CHARLES MILLER Time: 10:58am \/To: JAY STEWART (Read 3 times) Subj: Limiting file space RE: Limiting file space BY: Jay Stewart to All on Sat Dec 13 1997 08:53 pm > Hi, > > I'm managing a Novell 4.10 Network for a school, and we have recently had > problems with pupils installing large files (i.e. 15-20MB each) on our > server. > > I was wondering if anyone could tell me a way of limiting the amount of > storage space available to each user? > > Many thanks, > > Jay NWadmin or netadmin will allow you to place restrictions on the user's space. Just go to the user and under Account Restrictions should be a place to limit volume space. Charles --- Synchronet+SBBSecho v1.22 * Origin: System Shock: 805-659-5733 & 805-647-7582 (1:206/2406) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1S00002 Date: 01/06/98 From: CHARLES MILLER Time: 10:59am \/To: HOWIE COOMBE (Read 3 times) Subj: ? RE: ? BY: Howie Coombe to All on Sat Dec 20 1997 04:59 pm > What is this echo about,?. > Novell Netware in all flavors! Charles --- Synchronet+SBBSecho v1.22 * Origin: System Shock: 805-659-5733 & 805-647-7582 (1:206/2406) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1S00003 Date: 01/22/98 From: SCOTT PARKS Time: 07:11am \/To: ALL (Read 3 times) Subj: 3com PCI garbage info in LAN INFO When I first setup our new server (HP LD Pro) I found the setup CD did not support NW3.11 so I was unable to setup partitions or install the network card (Intel PCI) with it. Since I had a 3com PCI and the drivers and knew all the load commands I swapped the cards. It wasn't until a week or so later that I looked at the LAN INFO in Monitor and when I look at the card's protocol info it displays garbage and will crash the server. Since everything works if I don't probe the card info with Monitor I wonder if this is really a problem ... or possibly a problem with NW3.11 and PCI cards? --- GEcho 1.11+ * Origin: (1:343/70) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1S00004 Date: 01/22/98 From: SCOTT PARKS Time: 07:33am \/To: BERND HEUCKENDORF (Read 3 times) Subj: New NW4.11 install Bernd Heuckendorf wrote in a message to Scott Parks: BH> You have to configure TCP/IP first, using the option BH> "Protocols" then bind TCP/IP to a network card using BH> "Bindings". You will have to use Ethernet II or SNAP to bind BH> this protocol, 802.x won't work. So far I've been unable to add anything with INETCFG. My first Bind for TCP/IP was to Ethernet II but it didn't take. Time to take a closer look at the ETC directory. BH> You can add NW 3 servers and its users to the NDs using BH> NetSync. But this utilityy is for temporary use only. You BH> should use it when migrating to NW 4 and want to do all BH> administrative work with NDS utilities and discard all BH> bindery tools. Thanks ... I'm not ready to manage 300 users under 4.11 yet ;) --- GEcho 1.11+ * Origin: (1:343/70) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1S00005 Date: 01/22/98 From: SCOTT PARKS Time: 07:49am \/To: ALL (Read 3 times) Subj: Client errors I'm suddenly getting client time-out errors with all 95 clients. The MS client times out and the new Intranetware client has reported "this is not a WIN32 application". Win3.11 clients on the same Lan segment seem to be having no problems. Server is NW3.11 --- GEcho 1.11+ * Origin: (1:343/70) --------------- FIDO MESSAGE AREA==> TOPIC: 194 NOVELL Ref: F1S00006 Date: 01/22/98 From: JAY DICKINSON Time: 07:23pm \/To: SCOTT PARKS (Read 3 times) Subj: 3com PCI garbage info in Hello Scott! SP> It wasn't until a week or so later that I looked at SP> the LAN INFO in Monitor and when I look at the card's protocol info SP> it displays garbage and will crash the server. Since everything SP> works if I don't probe the card info with Monitor I wonder if this SP> is really a problem ... or possibly a problem with NW3.11 and PCI SP> cards? When mine did this I went to the Novell web page and d/l'd and installed a newer MONITOR.NLM file. ... Jay * LAKOTA v1.5 --- Alexi/Mail 2.02b (#51) * Origin: The Port Brew | San Antonio, Tx | 337-4338 (1:387/310)