--------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: EAE00000 Date: 06/05/97 From: BRIAN NIEGOCKI Time: 01:05pm \/To: MIKE BILOW (Read 6 times) Subj: Re: 4pin & 8pin? MB> BN> Anyone know where I can get a patch cable that has a phone jack MB> BN> type connector on one end with 4pins and the same connector on MB> BN> the other with 8? MB> MB> BN> I was told my school's ethernet setup has 4pin hookups but MB> BN> ethernet cards use 8 pins.. MB> MB> BN> Anyone know of a place that sells an adaptor or a patch cable? MB> MB> Unless you know how the 4-pin jack is wired, you are out of luck. There is MB> standard way to wire Ethernet on such a 4-pin jack. Are you sure that he MB> school is actually using Ethernet and not some other system such as Token R 99% sure. It's 10baseT as far as I've been told. The entire third floor of my dorm is/was running it last semester. I've since moved up there for the next semester coming up in the fall. --- GEcho 1.00 * Origin: Brian's World (516)-331-5540 Long Island, NY (1:2619/232) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: EAE00001 Date: 06/05/97 From: BRIAN NIEGOCKI Time: 01:13pm \/To: ALL (Read 6 times) Subj: workings of a T-1/3 and an ISP... I've been discussing some stuff about networking, bulletin boards, and the internet with a friend of mine, and the workings of an ISP came up. We tried to find some information out about it via the net and a few books, but couldn't find anything worthwhile for what we were interested in knowing. Basically, myself and my friend, are curious as to how exactly an ISP is hooked up and wired together. For example, lets say there is a T-1 or partial-T or something or the sort running into your office space for the ISP. What exactly gets hooked up between that, the dial-in phone lines, etc? How are things routed from one thing to another? We got some information regarding this pertaining to something called a router which everything plugs into, but it didn't make uch sense to say the least. Another guy I talked to mentioned something about having a large box which ll the modems plug into and that's how the calls get handled. From there it's "routed" to a server machine that handles the PPP connect for example. I'm not sure what sort of machines an ISP would/is running either. I've eard they run seperate servers for such things as: = A DNS SERVER = A NEWGROUP SERVER = AN EMAIL SERVER = PPP SERVER = WEB SERVER Anyone care to take some time and help explain some of this to me? --- GEcho 1.00 * Origin: Brian's World (516)-331-5540 Long Island, NY (1:2619/232) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: EAE00002 Date: 06/09/97 From: MIKE BILOW Time: 02:02pm \/To: ROY J. TELLASON (Read 6 times) Subj: testing network cards Roy J. Tellason wrote in a message to Mike Bilow: MB> All of the "WD*" cards have drivers and support from MB> "http://www.smc.com," which bought the Western Digital MB> networking line many years ago. The WD8003 and WD8013 are MB> classics that are widely respected. RJT> I have no web access at present, unfortunately. My BBS should have SMC drivers; I'll check. Can you do FTP? RJT> Any particular address or IRQ settings that would make a RJT> good set of defaults? Personally, I like to put Ethernet cards at 340h and IRQ 12. Second choices are 320h and IRQ 11. The most likely conflicts are a PS/2-style (motherboard) mouse port on IRQ 12 and a SCSI controller on IRQ 11. Older Adaptec SCSI controllers also need 330h, which conflicts with 320h. Third choices are 300h and IRQ 10. I try to avoid 360h because that conflicts with LPT1 at 378h. I also try to avoid 300h, since that is the common default dumping ground for all sorts of peripherals. IRQ 10 is also the only high IRQ which is available on most sound cards, so it is not a good place for network cards. If your network card needs a DMA channel, prefer 5. Low-numbered DMA channels (0-3) are 8-bit, while high-numbered DMA channels (4-7) are 16-bit. Adaptec SCSI controllers also default to DMA 5. Memory aperture should be selected to be immediately above and contiguous with the video ROM. This usually means starting the aperture at segment C800h. It is always desirable to preserve the largest continguous block of UMB possible, and keeping the card aperture at the one end of the arena will do this. It is also desirable to use the low end instead of the high end because of the broken way in which certain Microsoft utilities, such as EMM386, work. -- 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: EAF00000 Date: 06/09/97 From: VITALY LUKIYANCHUK Time: 06:11pm \/To: MIKE BILOW (Read 6 times) Subj: Re: IBMENIO NIC's drivers ddt.demos.su!f400.n5020!f1.n4625!f30.n4625!server.oaio.savebank!f30.n4625.z2!p 11.f30.n65535.z2!not-for-mail Hi Mike! Quoting message from Mike Bilow to Vitaly Lukiyanchuk [04 Jun 97 at 22:14] MB> Vitaly Lukiyanchuk wrote in a message to All: VL> did anybody have the problems with drivers for ISA ethernet VL> adapter such as follow: VL> ibmenio.com (28.12.92)- DOS driver VL> ibmeniop.sys (15.01.93) - OS/2 VL> ibmenio.lan (25.01.93) - Novell MB> Could you be more specific? My fileserver (NetWare 3.12) had ne2000.lan driver. But NIC's option diskette contained IBMENIO.LAN and I thought it was more "native" for the NIC and changed autoexec.ncf as it was recommended on the diskette. File server succesfully loaded but it deadly hung (while reading 5M file) a few minutes later. I've got OS2/warp WS with Novell Requester 2.12. There were problems with ibmeniop.sys too. I've changed it for ne2000.sys and problems disappeared. Have a nice day! Vitaly Lukiyanchuk. --- TM-Ed 1.14+ * Origin: Happy people have no stories (2:4625/30.11) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: EAF00001 Date: 06/05/97 From: JUHA-MATTI TAPIO Time: 03:08pm \/To: TIM PROVENCIO (Read 6 times) Subj: ms-dos, tcp/ip >> I also think that with the DOS MS client you can bind TCP/IP. JT>> I tried that but it didn't work out. At least not yet. > I do think it takes a seperate disk and you add the client. I am very > sure we have done this with the Microsoft Client. I got it almost working. There is still some driver missing. Another thing. I understand there should be ip-adresses for each machine. How do I set them so that there comes no conflict when dialing to isp? ... If only my faith was as strong as my coffee. --- FMail 0.92 * Origin: Point Frasier (2:224/930.5) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: EAF00002 Date: 06/09/97 From: RUNE JOHANSEN Time: 10:57pm \/To: ULDIS MIKELSONS (Read 6 times) Subj: NGC Sniffer > UPS for every HUB/Router/Switch will always be usefull :) we have requirments >that all network equipment ( eg bridges/modems/hubs/routers/switches/ _servers >) can handle up to 1hr off power shortage ( besides alternative power source : > .. so every rack have nice ups with snmp managment module inside .. its ot > "cost effective" but it works :) It depends on what type of UPS you have. If it is the cheap ones from APC, you are sure that you don't have one with galvanic separator, so power stings will burst right through your UPS, and could do serious damage. On the subject of using SNMP and SNMP traps in a LAN/WAN environment (just trying to stay on echo's topic here... ), you are absolutely reliant on UPS to run your infrastructure. You use the LAN to communicate with the SNMP objects, and you use the LAN to transfer the SNMP traps so that you can be alerted in case of power outages :-)) --- BBBS/2 v3.33 How-D * Origin: BarCode BBS - now with ISDN at 47-67061044 (2:210/20) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: EAF00003 Date: 06/10/97 From: WES NEWELL Time: 07:34pm \/To: JUHA-MATTI TAPIO (Read 6 times) Subj: ms-dos, tcp/ip >> I also think that with the DOS MS client you can bind TCP/IP. JT>> I tried that but it didn't work out. At least not yet. > I do think it takes a seperate disk and you add the client. I am very > sure we have done this with the Microsoft Client. JT> I got it almost working. There is still some driver missing. JT> Another thing. I understand there should be ip-adresses JT> for each machine. How do I set them so that there comes JT> no conflict when dialing to isp? We just set up TCP/IP on our Novell lan at the office. Pings a router which calls our ISP when someone wants on the net. We used addresses 255.255.255.x. Where x identifies each machine. Used 0 for the router. The main part was; 1) running tcpip.exe on net startup. 2) finding current drivers for the 3 types of old nic's we had. 3) bind tcpip in net.cfg. I had never even been on the Internet before starting this thing. It was a real learning experience.:-) --- Maximus/2 3.01 * Origin: Wylie Connection 128K ISDN / V34+ 972-429-7005 (1:124/7028) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: EAF00004 Date: 06/11/97 From: MIKE BILOW Time: 07:37am \/To: WES NEWELL (Read 6 times) Subj: ms-dos, tcp/ip Wes Newell wrote in a message to Juha-Matti Tapio: WN> We used addresses 255.255.255.x. Where x identifies each WN> machine. Used 0 for the router. This is a really bad idea, since the convention on IP is that an address where the network portion has all bits set is the broadcast network, or all networks. If you need a private network, use 192.168.x.x as recommended by RFC1597. -- 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: EAF00005 Date: 06/10/97 From: MARK WRIGHT Time: 04:46am \/To: MIKE BILOW (Read 6 times) Subj: NIC types MB=>You will probably find that 10 Mbps is adequate for nearly everything excep MB=>extremely high bandwidth applications, such as live video to the desktop. We certainly agree here, getting requests for 100mbps printer connections... seems like the buyer is of the feeling that bigger numbers is the secret to everything these days when purchasing new hardware. Time_Wounds_All_Heels______Mark Wright______Kirkland WA__USA * OLX 2.1 TD * "I am Fudd of Borg. Wesistance is usewess!" --- GEcho 1.11+ * Origin: (1:343/70) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: EAF00006 Date: 06/10/97 From: MARK WRIGHT Time: 04:46am \/To: KURT WEISKE (Read 6 times) Subj: NIC types KW=>Different strokes for different folks, I suppose. I like jumperless ards. KW=>just boot up off a boot disk, run the diags and configuration program, nd KW=>re-boot. What, you don't have a boot disk handy with the NIC software on it I'll go with the NE2000 compatibility issue.. but the cards have to have jumpers! too many disks, so much clutter. 3com and any other card that uses jumperless design forces boot param ters that has many times been far more difficult to setup due to video, scsi or ps2 complaints during boot forcing removal of card to another motherboard, setting the card via software, then reinserting the card into the original pc. Call me old fashioned but.. I think less is more. Time_Wounds_All_Heels______Mark Wright______Kirkland WA__USA * OLX 2.1 TD * Is it OK to yell 'MOVIE' in a crowded firehouse? --- GEcho 1.11+ * Origin: (1:343/70)