--------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1200007 Date: 12/28/96 From: MIKE BILOW Time: 04:54am \/To: JEFF BOOMERSHINE (Read 8 times) Subj: PUT .PRN FILE IN QUEUE? Jeff Boomershine wrote in a message to Mike Bilow: JB> COPYING THE FILE DIRECTLY TO THE PORT (LPT2) DIDN'T. MB> Your problem is unrelated to networking. Just use the "/B" switch MB> on COPY: MB> COPY /B FILE.PRN LPT2: MB> Note also that the "/B" switch must precede the file names to work; MB> it has a different meaning when following the file names. JB> You know, I hadn't thought of trying that. Alas, I'm getting JB> the same result. A small .PRN file spits out half of the JB> first page, then the complete doc. A large .PRN file gets 3 JB> or 4 pages into it, stops, then loops. JB> I haven't tried it at home, yet (no network). As I had JB> mentioned, I had no problem doing this through PCONSOLE.EXE JB> in our former NETWARE environment. At that point, I would suspect the printer cables. -- 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: E1200008 Date: 12/28/96 From: MIKE BILOW Time: 04:56am \/To: STEPHEN BUCKLEY (Read 8 times) Subj: NEt.exe Stephen Buckley wrote in a message to Mike Bilow: SB>> Any body any suggestions or inof about dos networking software, SB>> i.e. free pd network dos linkup software obtainable of the SB>> net if possible... Thanks.........:) MB> There are a lot of options here. What is it that you are trying to do? SB> Basically just transfer files from one PC to the other and SB> at a push be able to access each others CD-Rom drives SB> (Though this isn't essential) A small company in the U.S., Information Modes, makes "Little Big LAN: The $75 Network." It works across serial links, parallel links, and Ethernet links. You get an unlimited number of nodes for the US$75. The software provides raw, unadorned but functional networking of the sort you are looking for. Information Modes P.O. Drawer F Denton, TX 76202 800-628-7992 US Orders ONLY 817-898-1294 Outside US 817-387-3339 Techline 817-382-7407 Fax Hours 1pm - 5pm CST Mon & Wed 9am - 5pm CST Tue, Thu, Fri I don't know how you can obtain the software overseas, but Dave Petrucci or another regular reader of the echo might be able to help. -- 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: E1200009 Date: 12/28/96 From: MIKE BILOW Time: 05:01am \/To: RANDY MILLIS (Read 8 times) Subj: Fake TCP/IP net Randy Millis wrote in a message to All: RM> How can I fake TCP/IP over a crossover UTP cable between two RM> PCs, one running Linux and the other Win95 - or when both RM> run Linux? RM> Being ignorant about TCP/IP, what do I use for hostname, RM> domain name, IP address, network address, gateway address, RM> netmask, broadcast address, and name server for these two RM> machines to make this work? Make stuff up. If you are creating a private LAN which will not connect to anything else, use addresses from the following (RFC1597) blocks: 10.0.0.0 - 10.255.255.255 172.16.0.0 - 172.31.255.255 192.168.0.0 - 192.168.255.255 If you have only two machines, then the obvious choices would be 198.162.1.1 and 192.162.1.2. In this system (which would work for up to 254 machines), the network address would be 198.162.1.0, the netmask would be 255.255.255.0, and the broadcast address would be 198.162.1.255. Where each machine can hear every other machine directly, such as on an Ethernet wire, there is no need for gateways. If you have only two machines, gateway routing is meaningless. If you are not connected to the outside world, you will not need name service. You can define host names in the /etc/hosts file in Linux, or in some other appropriate place under other operating systems. Each machine should have a complete list of all hosts, and the file should be identical on all machines. -- 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: E1200010 Date: 12/28/96 From: MIKE BILOW Time: 05:12am \/To: SCOTT MOUNTENAY (Read 8 times) Subj: IBM CLASSROOM LAN Scott Mountenay wrote in a message to Mike Bilow: SM> Okay, since i first wrote that my network intelligence is SM> like 1000% percent greater. I kinda lurked around in the SM> novell newsgroups and stuff, read losts of texts, faqs and SM> stuff, and actually im going to the university here tonight SM> or tommorrow and get some books out and study them.. Great! You've come a long way in two weeks. -- 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: E1200011 Date: 12/28/96 From: MIKE BILOW Time: 05:16am \/To: JIM PALMER (Read 8 times) Subj: Fake TCP/IP net Jim Palmer wrote in a message to Randy Millis: JP> The only two broadcast addresses for your little net are JP> 192.168.100.0 or 192.168.100.255, but you should not have JP> to worry which, just don't number any additional machines JP> with these numbers. JP> Network address I am somewhat unsure of, there is a unique JP> 32 bit hex number burned into ethernet card, but I never JP> have had to supply it to any on my networks, yet I cannot JP> think of what else they could want. In IP, the network address is what you get when you bitwise-and the address of any machine with the netmask, and the broadcast address is what you get when you bitwise-or the address of any machine with the complement of the netmask. To make this a little simpler in practical terms, the netmask in the above case would be 255.255.255.0, so the network address would be 198.162.100.0 and the broadcast address would be 198.162.100.255. The use of the network address for broadcasts is an historical anachronism peculiar to some operating systems, notably the early Berkeley Unix. The address burned into an Ethernet card is 48 bits, known as a hardware or MAC address. This has nothing to do with IP specifically. Some less sophisticated networking protocols, such as IPX, use this hardware address as a network address, blowing away one rather resirable layer of indirection. -- 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: E1200012 Date: 12/28/96 From: MIKE BILOW Time: 05:23am \/To: BENJAMIN HANNON (Read 8 times) Subj: TCP/IP lan Benjamin Hannon wrote in a message to All: BH> I am currently working on setting up a small lan so that BH> my brothers can log in to my bbs through the lan (TCP/IP & BH> Telnet). Was just curious wether I need a server to setup BH> TCP/IP through a 10base2 (BNC) lan. The systems that are BH> runnin on the lan are: BH> Warp 4.0 System (BBS) BH> Pentium 75 OS/2 Warp 4 has all of the necessary networking built-in, so it will work. However, most BBS software expects to talk to a serial port, not a LAN port. You can finesse this using the VMODEM driver from the SIO package. -- 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: E1200013 Date: 12/28/96 From: MIKE BILOW Time: 05:24am \/To: SAM MCDANIEL (Read 8 times) Subj: MEMORY PROBLEMS Sam McDaniel wrote in a message to TORE HANSEN: SM> found the problem... Took out highmem.sys and all is fine:) SM> It now finds all 128 meg and runns faster than ever.... You should boot with an almost empty CONFIG.SYS and AUTOEXEC.BAT file to start a NetWare server. Loading HIMEM.SYS or any other DOS stuff ahead of NetWare will cause trouble and may even prevent SERVER.EXE from loading at all. -- 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: E1200014 Date: 12/28/96 From: MIKE BILOW Time: 05:27am \/To: GER VLOOTHUIS (Read 8 times) Subj: mail system Ger Vloothuis wrote in a message to Darrell Bowman: GV> And how do you get a TCP/IP stack to run together with IPX GV> and NETX? Assign them different frame types: Ethernet_802.2 to IPX, Ethernet_II to IP. -- 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: E1200015 Date: 12/28/96 From: MIKE BILOW Time: 05:28am \/To: DARYL STOUT (Read 8 times) Subj: Seed Message Daryl Stout wrote in a message to All Users: DS> With this message, The Thunderbolt BBS, GT Power 035/005, DS> FIDONet 1:3821/33, Little Rock, Arkansas...rejoins this echo DS> after a three week downtime for a system upgrade to OS/2 Warp. Welcome back. I won't ask why it took you three weeks to install OS/2. -- Mike Moderator, LAN --- * 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: E1200016 Date: 12/28/96 From: MIKE BILOW Time: 05:29am \/To: SAM MCDANIEL (Read 8 times) Subj: rent a cable sniffer? Sam McDaniel wrote in a message to Tom Moeller: > Anyone know of a company that'll rent out a LAN wiring > analyzer for a few days, just to check out an existing > installation? Or would I be better off checking with > local computer/networking companies to see if they've > got one? I'm an electrical engineer (not CNE) so > running the tool would be no problem. SM> Bought a two piece unit for $80 works real nice. SM> Checks all 4 cable pairs in the cat5 cable & rj45 connectors SM> for thoughput. pulses an led on each unit. 9v battery SM> operated. SM> very handy... if your using coax then i cant help ya... A LAN analyzer tests for considerably more than continuity and correct inout. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107)