--------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2F00002 Date: 02/10/97 From: FRANK SEXTON Time: 08:05pm \/To: NICKY MORROW (Read 0 times) Subj: Requester Woes -=> /* Quoting Nicky Morrow to Michael McBroom */ <=- NM> I'll tell you my story...maybe it will help: NM> 2) Modem support needed to be set to 9600 baud or less NM> or about what you describe happens...of course I set NM> modem support as high as it would go initially. I left mine at the default 9600 too. But I never did understand why or what was going on. What is this 9600 stuff all about? I don't use a modem on these cards anyway (dial up connections?). Is this only for dial-up connections? Boy am I confused:-). -Frank (fsexton@xpert.net - http://www.concentric.net/~fsexton) --- Blue Wave/OS2 v2.30 * Origin: Wildcard BBS,Thornton,CO HST/V34+ +1-303-252-0491 (1:104/725) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2F00003 Date: 02/11/97 From: SANDRO GASPARETTO Time: 01:10am \/To: CHUCK SADOIAN (Read 0 times) Subj: OS/2 as a router Hello, Chuck! ->> But there can be other problems, and things to understand. ->> ->> The best documentation I found on this, is in the file : ->> Tserve11.??? CS> Is that something that comes with OS/2 Warp? If not, where CS> can I find it? In Hobbes, where else ?? Directory: /os2/network/tcpip bye/2, Sandro --- E-mail: gaspare@delenda.gvo.it * Origin: Found Dos+Win, delete? (Y)es, (O)ui, (S)i, (J)a? (1:270/101.201) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2F00004 Date: 02/10/97 From: CHUCK SADOIAN Time: 10:07pm \/To: TONY LANGDON (Read 0 times) Subj: OS/2 as a router Tony, -> As I use a Linux router, I haven't tried routing with OS/2, but it is -> possible. Can you please post some details of your setup (include things -> like assigned IP addresses, your config - routing, netmasks, etc), and -> anything else that seems even vaguely relevant. :-) -> -> It could be as simple as a netmask problem. :-) Be glad to. LAN0 is my INTERNAL net, LAN1 is my ISP. My ISP gave me the subnet 206.43.243.64-95, netmask 255.255.255.224. So for LAN0 I gave it the address 206.43.243.65, netmask 255.255.255.224. My connection to my ISP is a direct ethernet connection to their Livingston Portmaster 2eR (they rent space in my office for their POP). They told me to use the address of 205.199.145.151 for my connection to the portmaster. So for LAN1 I used 205.199.145.151, netmask 255.255.255.0. Now their portmaster has a built-in router, and it lives at the address 205.199.145.21. So in the routing section I set up a default route to 205.199.145.21. I first set this up using Warp 3, so I added the command IPGATE ON to my TCPEXIT.CMD file, although it is my understanding it is on by default. After trying to get the setup to work with Warp 3 and not having any luck someone told me I needed WARP 4 to make it work, so I upgraded to Warp 4. I actually REMOVED TCP/IP V2 (what I was using with WARP 3) so I could do a fresh install of the TCP/IP that came with WARP 4 (Merlin). With Merlin I just checked the box to enable IPGATE. Anyway, the router machine has no trouble accessing the Internet via LAN1, I can run Netscape, telnet, ftp, etc. No trouble at all. And anyone on the internet can ping either address on the router machine. In addition, the router can also access any machine on my subnet through LAN0, and any machine on my subnet can access the router. However, no machine on my nteral subnet can get any farther than the portmaster. I cannot ping the ISP's router address. Futhermore, from the internet I cannot ping an address on MY ubnet, other than the subnet address assigned to my router. All the machines on my subnet have a default route of 206.43.243.65, which is the address of the S/2 router. At this point I STRONGLY suspect my ISP has not configured their portmaster correctly, although I do not know enough about TCP/IP to offer any specific solutions for them. It's my guess that the portmaster is lacking a route for my subnet, but the question then arises: why can someone on the internet PING the subnet address used by my router? If one address can be pinged, I don't understand why nothing else is responding on my subnet.. Any help would be greatly appreciated. Chuck --- QScan/PCB v1.17b / 01-0154 * Origin: MicroLink BBS * Dinuba, CA 209-591-8753 (1:214/80) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2F00005 Date: 02/11/97 From: ALEC HERRMANN Time: 12:05am \/To: MICHAEL MCBROOM (Read 0 times) Subj: Another Newbie Needs Help Hello Michael, Replying to a message of Michael McBroom to Alec Herrmann: MM> Here's where I am now, if you still have a mind to lend your MM> expertise: MM> I've reinstalled the OS on both machines, and have selected minimal MM> installations for networking -- Peer, TCP/IP, and System Management MM> Client. During the installation process, I entered my ID and MM> password, machine descriptions, and domain name (same one for both MM> machines). I let the installation routine select the machine IDs and MM> the network card driver. For ease of troubleshooting, these would have been the same userid and password, different machine names, and same domain name. If you do not have the same userid/password on both, it is easy to create another userid/password - provided the requester starts and you can logon with the userid/password defined during installation. Are all of these simple names such as 4-8 character alphanumeric (A-Z,0-9) names with no starting numbers and no special characters or punctuation characters or spaces ? MM> The way things are right now on both machines, if I open the MM> Connections folder, I see the "File and Print Client..." folder and MM> the "Network" folder, but with no + buttons. If I click on the MM> "Network" folder, so I can access the "Logons" folder, like the book MM> says to do, the Network window pops open, but that's as far as things MM> get. It appears to be empty, but when I move the mouse cursor over MM> the window, it turns into the clock. I can close the folder, but it MM> isn't really closed -- whatever it is the systems are trying to do MM> right there, they are not able to finish, so the application hangs at MM> this point. The systems are not hung, just the application. My best guess here is that the requestor code on both is not started, or is trying to start but can't finish - and your statements in your message seem to support this. MM> I have "set autostart=programs . . ." in both config.sys files, so MM> when I reset either machine (gotta do a Ctl-Alt-Del to reset them too MM> if I've tried to start the network), the Network window will reappear MM> on bootup. But this time, there's stuff inside of it, like the MM> Logons folder, for one. Try removing PROGRAMS and CONNECTIONS from AUTOSTART to avoid this, however, leave in FOLDERS. MM> address conflict. I've run the diagnostics utilities that came with MM> the cards, and they check out fine. I don't know what else to try. MM> For whatever reason, the requester just doesn't want to start. The MM> only thing I haven't tried yet is a different pair of cards. The MM> ones I have now are LinkSys NE2000 combo cards (ISA), which came with MM> OS/2 drivers btw. MM> Any ideas you may be willing to provide would be greatly appreciated. At the command line, what happens when you run the following (some may not work until the requester is started and you are logged on): NET START NET CONFIG NET STATUS NET ERROR NET STATISTICS REQUESTER NET STATISTICS PEER NET USE NET USER NET VIEW NE2000 cards. Hmm... Some NE2000 cards have a history of not working properly with OS/2 depending on the address chosen. Try varying the address - 280, 300, etc. Also try using different NE2000 OS/2 NDIS drivers - yes, they are NOT all the same. You can download them from various internet sites of makers of NE2000 clone cards. If possible, I would try different network cards. If you do not have any, perhaps calling 3COM at 1-800-NET-3COM and ask what special evaluation deals they have. I have gotten a pair of 3C509 Combo ISA cards (both RJ45 and BNC) for $79 US from them. PS - this is a long shot - try taking out the BASEDEV=DETNE2.SYS from your CONFIG.SYS files. Alternate approach (to check out your software): If you install OS/2 networking features, but don't select a network card, the parallel port ANDIS driver will be installed. You should be able to install this afterwards as well. Save a copy of your CONFIG.SYS and \IBMCOM\PROTOCOL.INI and \IBMLAN\IBMLAN.INI files. Run MPTS.EXE from the \IBMCOM directory, remove your network card drivers, and install the 'SSW Parallel Port NIC-less adaptor'. If you have a LapLink type parallel port cable, you can actually connect two (and only two) computers this way - the parallel cable will act as a slow network cable. Regards, Alec --- FleetStreet 1.12 NR * Origin: The Nibble's Roost, Richmond BC 604-540-8048 (1:153/8086) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2F00006 Date: 02/11/97 From: ALEC HERRMANN Time: 12:35am \/To: MICHAEL MCBROOM (Read 0 times) Subj: Another Newbie Needs Help Hello Michael, Replying to a message of Alec Herrmann to Michael McBroom: MM>> folder, but it isn't really closed -- whatever it is the systems are MM>> trying to do right there, they are not able to finish, so the MM>> application hangs at this point. The systems are not hung, just the MM>> application. AH> My best guess here is that the requestor code on both is not started, AH> or is trying to start but can't finish - and your statements in your AH> message seem to support this. MM>> address conflict. I've run the diagnostics utilities that came with MM>> the cards, and they check out fine. I don't know what else to try. MM>> For whatever reason, the requester just doesn't want to start. The One of my previous experiences just came back to me. Are you using coax? Did you check the coax cable connection between the network cards when you ran the diagnostics on the network cards themselves? 3COM has an utility in its diagnostics that allows you to transmit packets from one machine, and receive them on another machine - thus testing the cable AND the cards. Also check to see if you have BNC or RJ45 selected (as a definite selection, for whatever cable type you are using) on both cards using the config program (if any available) - do not rely on 'autodetect' if available. The reason I thought of this - I used to run coax on one installation, and if anything on the coax cable was bad (ie broken connection, etc) the server simply would not start at all. This does not happen on twisted pair (RJ45 type) connections. If I had a broken coax cable, and started the server from the command line using NET START SERVER, I would get the following for up to 15 minutes - the periods would keep on appearing at a rate of about 1 every 2 seconds: Starting server ........................................ If you set up your peer services NOT to autostart at boot time, and then type NET START PEER at the command line, you may get something similiar to above. Regards, Alec --- FleetStreet 1.12 NR * Origin: The Nibble's Roost, Richmond BC 604-540-8048 (1:153/8086) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2F00007 Date: 02/10/97 From: RAYMOND ENGELBRECHT Time: 02:07am \/To: MICHAEL MCBROOM (Read 0 times) Subj: Requester Woes Hello Michael! Friday February 07 1997 20:30, Michael McBroom wrote to All: MM> I'm having a problem with the requester starting on one of my MM> machines. The system is running Warp4, with Peer-to-Peer and TCP/IP MM> installed. The hardware is an AMD 5x-133, 32MB RAM, AMI PnP BIOS. MM> Depending on which way I go about trying to start the requester, I get MM> either a NET3060 or a NET2140 error message. Usually, the process MM> gets "stuck" at this point, and I have to reboot the machine to MM> unstick it. I've called IBM. The techguy thought there might be a MM> conflict with my S3 ViRGE video card, so we set the system to VGA. No MM> luck. I'm inclined to agree with him that there is probably a MM> hardware conflict of some sort, but I've gone over the stuff in the MM> hardware manager with a fine-toothed comb, and can't find it. MM> Anybody out there had similar problems? Yes, i had the same problem over here with a 486-DX2/80 and a Cx166+. My 486 ran just fine, while my Cx166+ had some major network troubles. I tried everything on this Cx166+, never to think that the 486 was causing all the troubles. A trap 000E on the 486 in one occassion indicated that this 486 was troubling the networking capabilities of Peer-to-Peer between both machines. So I finally slowed down the 486 in the BIOS and since that time all my networking troubles dissappeared as snow in the sun..... Maybe slowing down the timimg of your AMD 5x-133 will do trick aswell... Cheerio, Raymond --- GEcho 1.11+ * Origin: ----> Switching off and on all the time !!!! < (2:282/211) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2G00000 Date: 02/11/97 From: MACK BARSS Time: 01:58pm \/To: DAVID A. BEISEL (Read 0 times) Subj: OS/2 to WIN95 David A. Beisel wrote in a message to ALL: DAB> How do I connect a WIN95 machine to an OS/2 Warp Connect Network DAB> using NETBEUI? Do I need a special Client for the Win95 machine? No you don't need a special client. When you install Win95 with netbeui, you should be able to connect to the OS/2 WarpConnect network. I have done this many times. => Mack <= --- timEd/2 1.10 * Origin: Modem Connections/2 (613) 820-2594 - Nepean, Ont. (1:163/545) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2G00001 Date: 02/08/97 From: KRISTOFFER RESELLMO Time: 05:03pm \/To: DARRELL SALTER (Read 0 times) Subj: Conecting lan to dial-up? // Darrell Salter skrev til Phil Pattengale // DS> I have done so, but the docs on IP masq. are sparse at best. Support DS> seems very good though. What I really need is a step by step setup DS> procedure from the machine that will connect to my ISP to the rest of DS> the machines on the lan. Any suggestions? What you want to do is download Philippe Gillain's SockD and install it. Just setup the auto-dial option and add some hosts to your resolv file (in your ETC directory). SockD will need to find the req. host here in order to start the dial-up session. For the WFW machines, get a copy of SocksCap (16 bit) at http://www.socks.nec.com. Set it up with the IP address of your warp machine as the socks v5 server, and put the program in the startup-folder. SockD is freeware, and AFAIK SocksCap as well. I'm using this setup myself, with one Warp and two win95 machines. Kristoffer --- Blue Wave/OS2 v2.30 * Origin: ineo - PCB v15.3 - 2 noder USR 33k6 - 72561242 (2:212/24) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2G00002 Date: 02/11/97 From: MICHAEL MCBROOM Time: 07:34am \/To: NICKY MORROW (Read 0 times) Subj: Requester Woes Hi Nicky, NM> When I first started using Warp v4 I bought 2 3Com 509B cards to NM> network 2 machines. The setup was pretty easy and the speed of the NM> network even on ISA cards has surprised me greatly. The only 2 NM> problems I had to figure out were: NM> 1) PnP needed to be turn off on these cards. You can do that with NM> the included setup utility. NM> 2) Modem support needed to be set to 9600 baud or less or about NM> what you describe happens...of course I set modem support as NM> high as it would go initially. Well, everything helps -- to increase my knowledge base, if nothing else. Yesterday, I talked with a tech support guy at Linksys. He recommended a procedure to follow, pointing out a bug in Warp4's configuration of protocol.ini for their driver. I will try this today, and see if it works. Regards, Mike --- Maximus/2 3.01 * Origin: Paradigm Shift: Home of the UnSpun Truth! (1:103/652) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: E2G00003 Date: 02/11/97 From: MICHAEL MCBROOM Time: 07:39am \/To: FRANK SEXTON (Read 0 times) Subj: Warp4 books Hi Frank, FS> I also have a favorite book to promote. It's a generic FS> "network" book designed for folks new to networking. But FS> it is very comprehensive and has plenty of technical stuff FS> in it as well as "how-to" and "why" stuff. It's the best FS> overall networking book I've ever seen. FS> I got it at our local (famous) book store here in Denver FS> called "The Tattered Cover". It's got 856 pages. Title is FS> "PC Networking Handbook". Written by Ed Tittel. Copyright FS> 1996 by Academic Press, Inc. ISBN 0-12-691398-6. Thanks for this little gem of info, Frank. What's it sell for? I've been looking for just such a book, and have been unsuccessful so far. Just to show you how green I was on networking just a couple of weeks ago -- I thought that Warp4 came with some sort of "lite" version of Lan Server. I kept seeing all these references to it during install and configuration, but couldn't find the program itself. I even bought a couple of books, hoping it would help me out. :) Anyway, I kept one of them, and returned the other. The one I kept is called _The Essential CLient/Server Survival Guide_ by Robert Orfali, Dan Harkey, and Jeri Edwards. (John Wiley & Sons, 1996. ISBN 0-471-15325-7) List price $32.95. This book gives a person a general overview of the subject of client/server networking. It seems it would be suitable as a text for a college survey course on the subject. The book that I returned was an IBM publication. I don't recall the exact title, but if it is the Redbook listed in the back of my Warp 4 Redbook, then the title is _Inside OS/2 Lan Server 4.0_ (IBM # SG24-4428). I scanned through this book before I returned it. It seems to be an ideal "how-to" book for setting up and configuring a Lan Server-based LAN. Lots of example screens and step-by-step instructions. It was about $32 as I recall. Mike --- Maximus/2 3.01 * Origin: Paradigm Shift: Home of the UnSpun Truth! (1:103/652)