--------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500003 Date: 09/04/96 From: MIKE BILOW Time: 01:28pm \/To: HANS WAASDORP (Read 6 times) Subj: LBL <> Linux Hans Waasdorp wrote in a message to All: HW> I placed an order for Little Big Lan, but forgot to ask HW> myself if it would be possible to hook up a Linux machine to HW> a 2 PC network running Dos\LBL. (now Dos\Pers. Netw) HW> Does anyone know if this is possible ? Not as far as I know. HW> I plan to build the Linux machine in the next couple of HW> months (i am new to Linux). 1 Dos machine is my "work" PC, HW> the other Dos machine runs a BBS, the Linux machine should HW> become a Usenet "gateway" for the BBS. If you are going to play with this kind of thing, you want TCP/IP, not LBL. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500004 Date: 09/04/96 From: MIKE BILOW Time: 01:43pm \/To: RAJ THOMAS (Read 6 times) Subj: Mac SE to ethernet Raj Thomas wrote in a message to All: RT> I am about to setup a home network running TCP/IP over RT> ethernet. RT> I plan to use one of the SMC cards and use T-Base 2 ( thin RT> coaxial ) It will link a P 100, a P 166 and a 486 SX 33. RT> They will run various combinations of Linux and Win 95 RT> ( They will all be able to dual boot to Linux and Win 95 RT> and I hope to keep the network running under all 8 RT> combinations of operating systems :-) I did say that I was RT> doing it for the challenge, didnt I ? ) You should be able to make it work, as long as you do not set up the Windows 95 machines to use DHCP. Just assign IP addresses and routes statically. RT> My 5 year old son currently has a Mac SE ( he will probably RT> be getting the 486 soon ). Is there any simple way of RT> adding the SE ( 40 meg hd 4 meg ram no expansion slots but RT> has one of those wierd Apple talk ports ) to my proposed RT> network. The SE is only worth a around a 100 $ and so I RT> dont want to spend a lot on Mac connectivity. RT> Any advice ( including "junk the SE !" ) gratefully RT> accepted. Junk the SE. It is possible that you could put a LocalTalk card into a PC and find a Linux driver for it, but it just is not worth it. Especailly since you are dealing with TCP/IP and the Mac SE has no native TCP/IP stack, you would find there would be a lot of headaches. RT> BTW, I was planning to use 10 Mbits ethernet. RT> Any comments on whether I should be considering 100 MBps by RT> using a SMC 10 / 100 card with Cat 5 wiring ? While 100 Mbps cards are not so much more expensive, the hubs are. You could buy your son a couple of replacements for his Mac SE with the money you would have to spend on a 100Base-T hub. A 100Base-T network card might cost twice what a 10Base-T card would, but a 100Base-T hub might cost ten times as much as a 10Base-T hub/concentrator. Also, 100Base-T wiring is far more critical. Just using Category 5 cable does not mean your wiring will meet Cat 5 standards. You must also use Cat 5 plugs, jacks, blocks, and installation techniques. RT> Any comments on SMC as a choice ? They make good stuff, but it is a little expensive. Do you really need this for a home network? -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500005 Date: 09/04/96 From: MIKE BILOW Time: 01:53pm \/To: JIM PALMER (Read 6 times) Subj: Mac SE to ethernet Jim Palmer wrote in a message to Raj Thomas: RT> My 5 year old son currently has a Mac SE ( he will probably be getting RT> the 486 soon ). Is there any simple way of adding the SE ( 40 meg hd RT> 4 meg ram no expansion slots but has one of those wierd Apple talk RT> ports ) to my proposed network. The SE is only worth a around a 100 $ RT> and so I dont want to spend a lot on Mac connectivity. JP> If we assume connecting the SE protects a 5 year old from a JP> 486 and vice versa, then perhaps it makes sense. A new JP> ethernet card to go in the SE's expansion slot is $130US, JP> and supports 10base5, 10base2 and 10baseT cabling. System JP> 7.5.3 contains MacTCP. I don't see System 7 going into a Mac SE with 4 MB RAM and a 40 MB HD! JP> Another alternative would be FreePPP which should allow a JP> 57,600 serial connection to a PC acting as a PPP server. JP> You wanted a challenge, right? I didn't think of that, but it would be a good idea -- if the machine was capable of running System 7. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500006 Date: 09/04/96 From: MIKE BILOW Time: 01:57pm \/To: JONATHAN OSTRUS (Read 6 times) Subj: Help Jonathan Ostrus wrote in a message to All: JO> I have 2 network cards and I don't know who they're made by JO> or how to configure them. Can someone tell me how to JO> configure them or where to get the info? Can anybody also JO> tell me who they're made by? * * * JO> | | | PCN-002 This is not an Ethernet card. It is from the old IBM PC Network, often called "baseband." They were fairly popular for educational installations where IBM gave them away like water, but never caught on elsewhere since IBM pushed SNA (Token Ring) for commercial customers and the rest of the world used Ethernet. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500007 Date: 09/04/96 From: MIKE BILOW Time: 02:01pm \/To: BRUCE LANE (Read 6 times) Subj: 100 base-t Bruce Lane wrote in a message to Ben Bergeron: BB> ISDN (57.6 , 11.52 (2 B Channles)) BL> Not quite. BRI (Basic Rate Interface) ISDN has two 64K BL> B-channels and a single 64K D-channel for control and BL> signaling. Officially, BRI ISDN is 64+64+16. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500008 Date: 09/04/96 From: MIKE BILOW Time: 02:03pm \/To: ERIC MCCORMICK (Read 6 times) Subj: Numbering Eric McCormick wrote in a message to Luis Manterola: LM> The cable to link two PCs with UTP is the cross-over LM> cable.. so you have the next pin configuration: LM> Pin 1 = Pin 3 LM> Pin 2 = Pin 6 LM> Pin 3 = Pin 1 LM> Pin 6 = Pin 2 EM> I'm having trouble with a one computer to another setup. EM> It keeps telling me the thin coax cable is not there, and EM> the cable checks out fine. I have nevet tried a Hubless UTP EM> like this. All I know the cabling by is the colour code EM> tip/ring standard, Wh-Bl, Wh-Or, Wh-Gr, and Wh-Br are the EM> ones used in an 8 pair. However, how does your chart above EM> translate to these? See, if I have the crimped connector EM> with the tab on top, it comes out one way. And with the tab EM> on bottom another. EM> .. +--------+ EM> ---- |12345678| EM> +--------+ +--------+ EM> |12345678| ---- EM> +--------+ '' EM> OR EM> Are you using the pair numbering, which is a telcom EM> standard. .. EM> ---- EM> +--------+ EM> |75312468| EM> +--------+ I don't know where you are getting your "telecomm standard." The relevant standard is EIA T568, which defines the connector in straight row order: 1 2 3 4 5 6 7 8 The pairs in standard order are 4-5, 3-6, 1-2, 7-8: ---2--- | | -3- | -1- | -4- | | | | | | | | 1 2 3 4 5 6 7 8 Pair 1 (pins 4-5) is usually reserved for voice, but is rarely used. For Ethernet 10Base-T, the only wires used are pair 2 (pins 3-6) and pair 3 (pins 1-2). For a cross-cable that connects two machines without a hub, you have to connect pair 2 on each end to pair 3 on the other end. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500009 Date: 09/04/96 From: MIKE BILOW Time: 02:17pm \/To: ERIC SMITH (Read 6 times) Subj: SMC card Eric Smith wrote in a message to Raj Thomas: ES> Keep in Mind, that 10 Megabits is faster than most hard ES> drives as it is, and 100Base-T would have a hard drive ES> bottle neck. Hard drives measure speed in megaBYTES per second (MBps), while networks measure speed in megaBITS per second (Mbps). A 10 Mbps network is only 1.25 MBps, assuming no overhead. Most modern hard drives under modern operating systems will have no trouble sustaining rates like this. Even IDE hard drives can break 2 MBps easily, and SCSI drives can break 5 MBps. Under OS/2, I've kept multiple drives simultaneously pegged to the limits of a SCSI bus. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500010 Date: 09/04/96 From: MIKE BILOW Time: 02:25pm \/To: HUBERT LELONG (Read 6 times) Subj: server and W95 Hubert Lelong wrote in a message to all: HL> a friend of mine had an idea that seems not stupid, but we HL> cannot realize it : as we are teaching computers, [and you HL> know, learners are dangerous on workstation, with there HL> funny "and what if I clic here ?"] HL> we'd like to save our standard HL> configurations on a server (Novell 3.12) with the HL> possibility of booting any station with a disket and copy HL> the configuration back. HL> With a W 3.11 station, it's OK HL> with W95, it is NOT. I think it's a problem caused by non HL> 8.3 names of file. HL> Am I right ? HL> and (more important point) what can I do ? I am not sure if your problem is long file name support or not, but loading the OS/2 namespace driver (OS2.NAM) on the server will give you support for long file names under Windows 95. Under Windows 95, a lot of information is stored in the Registry, which is a binary file intended to be inaccessible to users. If you want to prevent users from blowing up a Windows 95 installation, the officially supported method is to enforce "Policies" on the user, restricting the user from access to parts of the system which could be damaging. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500011 Date: 09/04/96 From: MIKE BILOW Time: 02:29pm \/To: LUIS MANTEROLA (Read 6 times) Subj: Migrating 3.12 Luis Manterola wrote in a message to George Fliger: LM>> My question is: What are the advantages and disadvantages of LM>> paying the upgrade for a 4.1 Netware? GF> Just to name a few... GF> Advantages: GF> Disadvantages: GF> Other than that, not much of a difference between the two. LM> Ok.. what would you advice? Should I migrate? LM> I can afford it and the server is a Pentium 120 with 32 MB.. LM> I can increase that too.. LM> Is it worth? The major enhancement of NW 4 over NW 3 is NetWare Directory Services, which would be essentially useless in a single-server environment. There are other enhancements which may be attreactive, such as built-in storage management with integrated compression. However, the upgrade would be a lot of money and a lot of aggravation without a compelling reason to do it. Further, even if you decided to do the upgrade, it would be a bad time to do it now with a major new release of NW 4 ("Green River") expected imminently. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: DD500012 Date: 09/04/96 From: MIKE BILOW Time: 02:33pm \/To: CHRIS MADDOCK (Read 6 times) Subj: Cheap LAN Chris Maddock wrote in a message to Tom Moeller: CM> I tried this one. It didn't do anything. Bear in mind also CM> that these were real honest-to-goodness NE1000 and 2000 CM> cards and not clones. The job of reporting the hardware address is primarily laid upon the driver software. If this is failing, the driver is almost certainly at fault. CM> That is not an unusual situation. I've found the same thing CM> with NETBUI networks sometimes too. Most NetBEUI networks depend upon NDIS drivers, while LBL depends upon a Packet Driver. It is possible that both were wrong, but unlikely. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107)