--------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCD00007 Date: 08/03/96 From: DIETER MIRBACH Time: 11:43pm \/To: TERRY COLLINS (Read 1 times) Subj: Ethernet cards On the 01/8/96 22:30, Terry waffled to Dieter.. Hello Terry, TC> We meet again. I read your reply of the os2-l this morning I haven't posted there for a week or so - you catching up on some outstanding mail ?? I still have to get back to you re that Token ring card co-existence that you replied to me. Alas, time time has prevented me from pursuing this issue any further, for the moment anyway. DM> I've a yum-cha NIC card in the PC where I work, and it works DM> perfectly under Win95, but with Warp, not a whistle. 3 error DM> messages, and nothing connects. DM> As another message said, disable autodetect, This is the problem DM> with my NIC, but I can't disable auto-detect at all. One of the DM> error messages I get is something about unable to detect media DM> type or similar. TC> I used a software configurable NE2000 Plus yum cha and it is working TC> under a BBS in os/2 linking to a novell file server. TC> It was the only card I could lay my hands on that got around TC> the IRQ squeeze. Some cards do, some don't. No matter what I did, what driver I selected, it just refused to talk. I swapped it with another, from a different vendor, and the replacement works fine. It seems the autodetect on the NIC card somehow doesn't translate into the MPTS, or whatever. Can't explain why not - it was cheaper to swap it out, and saved a few headaches too :-) Dieter ... If I dream about Heaven, would she dream about me ?? ___ Blue Wave/QWK v2.12 --- * Origin: Mirbachs MadPoint (3:711/934.8) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCD00008 Date: 08/01/96 From: TERRY COLLINS Time: 10:30pm \/To: DIETER MIRBACH (Read 1 times) Subj: Re: Ethernet cards -=> Quoting Dieter Mirbach to George Falcon <=- We meet again. I read your reply of the os2-l this morning DM> On the 07/06/96, George waffled to All.. DM> Hello George, GF> wondering if any of you have had positive experiences using GF> inexpensive ethernet cards with Warp Connect peer services. DM> Nah, mainly negative .... GF> I have a couple of Accton cards, but they're not on the supported GF> list, nor is there an entry for a generic NE2000-type 16-bit ethernet GF> card. DM> I've a yum-cha NIC card in the PC where I work, and it works DM> perfectly under Win95, but with Warp, not a whistle. 3 error DM> messages, and nothing connects. DM> As another message said, disable autodetect, This is the problem DM> with my NIC, but I can't disable auto-detect at all. One of the DM> error messages I get is something about unable to detect media DM> type or similar. I used a software configurable NE2000 Plus yum cha and it is working under a BBS in os/2 linking to a novell file server. It was the only card I could lay my hands on that got around the IRQ squeeze. DM> IOW, buyer beware. DM> Dieter (dieter@intelligent.com.au) DM> ... A dead dog doesn't bark. DM> ___ Blue Wave/QWK v2.12 DM> -!- DM> ! Origin: Mirbachs MadPoint (3:711/934.8) --- Blue Wave v2.12 [NR] * Origin: Sydney PC Users Group Mail Exchange (3:712/505) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCD00009 Date: 08/08/96 From: JIM WHITELAW Time: 11:29pm \/To: MIKE BILOW (Read 3 times) Subj: OS/2 Peer Thus spake the keyboard of Mike Bilow: MB> When you install OS/2 Peer, it sets those values for a MB> reason. Dropping links unilaterally can orphan resources in MB> a NetBIOS network. What is written into the code is the MB> shutdown notification. By messing with MPTS at this level, MB> you simply cause the shutdown notification to fail I'm unsure what you mean by "dropping links unilaterally" and "causing the shutdown notification to fail ungracefully". Can you please elaborate? Here is the explanation of the NETBIOSTIMEOUT and NETBIOSRETRIES parameters that I'm going by: > Most of the delay is waiting for the netbios name registration. > The documentation tells you to lower the timeout values if you > are running a small, reliable network. [...] > These are the parameters which affect the LOGON time, netbios > name registration and timeouts. The timout should be set to 25% > greater than the echoplex time between the discrete ends of > your network when it is loaded. Basically, all netbios data > transmissions will expect that a response (or acknowledgement) > will be received within the timeout specified. > A failure to acknowledge a data packet in transit is counted as > a window error, so you can have this set a little too low, and > compensate by increasing the WINDOWERROR parameter to allow for > the occasional late acknowledgement. > Netbios name registration transmits a broadcast name > registration request. No reply is ever expected UNLESS there is > a conflict. Therefore, a successful name registration will > always require timeout * retries milliseconds to complete. All I can tell you further to that is that I've adjusted these settings on several machines with no ill effects whatsoever, and markedly improved logon/logoff (and therefore startup/shutdown) speeds. "Works for me", though I can see how on larger LANs it could cause problems if the settings were too low. --- * Origin: Starship Heart of Gold - Edmonton, AB [403]489-1735 (1:342/42) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCE00000 Date: 08/07/96 From: TERRY COLLINS Time: 02:24am \/To: GEORGE FALCON (Read 1 times) Subj: Re: Ethernet cards -=> Quoting Jay Hickman to George Falcon <=- JH> @MSGID: 1:106/2000.0 3200db8a JH> On 07-28-1996 Terry Collins enlightened George and us with his JH> thoughts concerning Re: Ethernet cards TC> GF> Now I'm going to try to set up my home office with ethernet, and I was TC> GF> wondering if any of you have had positive experiences using TC> GF> inexpensive ethernet cards with Warp Connect peer services. TC> TC> You really need to get the NE2000 OS/2 drivers. TC> I've finally got a NE2000plus clone card going, but it was such a TC> bad experience, I've forgotten it. It was my first set up of OS/2 TC> warp, a bbs upgrade under pressure and it was just done. TC> JH> George, JH> My experience was a bit different from Terry's. I got the El JH> cheapo GVC NIC cards which are generic NE2000 compliant. I used the JH> Eagle NE 2000 configure straight from the MPTS set up screen and it JH> has been working fine for over a year. Best of luck The NE2000 driver in Warp Connect wants IRQ, PORT & Memory settings. The cards I have only had IRQ & PORT settings. I had trouble finding a any driver to match. So there is NE2000 & NE2000 cards. JH> ****************************************************************** JH> Jay R. Hickman jrhick@ibm.net JH> ****************************************************************** JH> -!- Maximus/2 3.01 JH> ! Origin: COMM Port OS/2 (713) 980-9671 (1:106/2000) --- Blue Wave v2.12 [NR] * Origin: Sydney PC Users Group Mail Exchange (3:712/505) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCE00001 Date: 08/07/96 From: TERRY COLLINS Time: 02:29am \/To: CHRIS WOLCOTT (Read 1 times) Subj: Re: Multi-Protocols -=> Quoting Chris Wolcott to George Fliger <=- CW> @MSGID: 1:3612/250.0 32025812 CW> I tried to load TCP/IP, NetBEUI and NetBEUI over TCP/IP, but the setup You can either run NetBeui (NetBios) or NetBeui over TCPIP, you can not have the both on the same card as the system will not know where to send NET BEUI. CW> wants a seperate card for the 'second' NetBeui. I am experimenting CW> with TCP/IP, with am aim to convert to it. Until then, I need the CW> IPX, NetBIOS and 802.2 (SNA) also. Can I have all on one physical Um, what version is your IPX, 802.3 (Netware V3.11 & #.12) or 802.2 (Ver 3.12+)? You might have some SNA conflict. CW> card, or do I need to bite the bullet and add a second card (and line CW> to the phone room....) to get this to work? Will loading NetBEUI over CW> TCP/IP also allow normal NetBEUI traffic? CW> Also, at a computer show here a vendor of a NETBIOS DNS said even CW> NetBIOS over TCP/IP can not be routed because the router can't see CW> into the TCP/IP packet to get the destination address from the NetBIOS CW> frame. I thought that was the whole idea of running NetBIOS thru CW> TCP/IP? Did I understand him correctly? Isn't the TCP/IP header CW> built with the appropriate address already in it? Yes it is. If the NetBeui doesn't package itself properly, of course the router won't be able to route. Wasn't a MS salesperson by any chance? CW> -!- Maximus/2 3.01 CW> ! Origin: The OUTER LIMITS: Another BBS proudly running OS/2 WARP! CW> (1:3612/250) --- Blue Wave v2.12 [NR] * Origin: Sydney PC Users Group Mail Exchange (3:712/505) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCE00002 Date: 08/07/96 From: TERRY COLLINS Time: 02:33am \/To: MIKKO HYVARINEN (Read 1 times) Subj: Re: Warp Server as TCP/IP router? -=> Quoting Lawrence Garvin to Mikko Hyvarinen <=- LG> @MSGID: 1:106/2223.0 1ffdf8b0 LG> Mikko Hyvarinen said in a message to Jeff Dunlop: MH> Jeff Dunlop wrote in a message to All: JD> Is it possible for a Warp Server to act as a TCP/IP router using a JD> dialup connection on the server? I don't see how to get past the JD> allocated IP address that's assigned by the ISP. MH> That requires firewall software, which is not included in MH> Warp Server. LG> With all due respect, it does not. Firewall software is used to LG> -prevent- the passage of specified packets from passing through a LG> network interface. LG> The services that Jeff require are fully contained within Warp Connect LG> or Warp Server. LG> lawrence@garvin.hd.co.harris.tx.us I feel that Mikko hasn't fully said what he wants to do. If you have a registered IP address, then you can do it, but if you have fudged numbers set up as home and PPP or whatever to an ISP, then there is no way you Warp can route back into your home network. The problem is that outside looks for the real address that you have chosen for home. LG> -!- LG> ! Origin: The Health Center * Houston, Texas (1:106/2223) --- Blue Wave v2.12 [NR] * Origin: Sydney PC Users Group Mail Exchange (3:712/505) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCE00003 Date: 08/08/96 From: JIM WHITELAW Time: 11:48pm \/To: PHIL PATTENGALE (Read 1 times) Subj: Odd www question... Thus spake the keyboard of PHIL PATTENGALE: PP> From my understanding of IP addresses and the DNS, this in PP> and of itself shouldn't be a problem. Simply have the same PP> IP address for both domains in my DNS server and have my DNS PP> server listed w/ Internic for both domain names. PP> (Corrections to this presumption happily accepted). An alternative is to have each domain name assigned to a different IP address, and one machine that responds to both IP addresses. I think in Unix the term used is IP aliasing, and it is a function that is present in the TCP/IP 4.0 beta and in the TCP/IP included in the Merlin beta. Essentially, what it does is allow you to assign more than one IP address to a single network interface. PP> However, if I want to have two http servers running on the PP> same machine, I'm unsure if it's even possible. For PP> example, I'd like to have both www.abc.com and www.xyz.com PP> on one pc, with only one (?) ip address for that machine. As above, what you want is www.abc.com and www.xyz.com on one PC with two IP addresses and a server that is capable of functioning as a multi-homed server. PP> I'd prefer to NOT have to resort to such "home pages" as PP> www.ghi.com/~abc.html or www.ghi.com/~xyz.html. You shouldn't need to. You don't specify what www server you are using, but I think most can be configured to have a different "home directory" for different IP addresses. PP> Anyone have any actual experience doing something similiar? PP> I currently have Warp Connect. This is capable of at least PP> being one web server, correct? Yes, and more. Though the TCP/IP in Warp Connect doesn't explicitly support P aliasing, it can be 'hacked' to work. What you do is set up multiple dummy SLIP or PPP interfaces with the IP addresses you want, then configure real Internet-connected interface to do proxy arp for those addresses. Here is a sample of how that was done to set up the system for the above example. Here is something that was recently posted to the GoServer mailing list, explaining how to do it: ========================================================================== We've done it here! In the end it's quite simple, but it took me a while to vaguely understand what was happening, and I'm still not entirely on top of it. Routing seems to be a bit like designing radio transmitters. They work but nobody quite knows how. I've used an idea from the mailing list where 'dummy' TCPIP entities are created via SLIP. Once created they can be reconfigured. Here's the .cmd file. For the time being I manually press ^C to stop the slip driver (which leaves behind the devices used) slip ifconfig lo 203.9.252.32 ifconfig sl0 203.9.252.48 203.9.252.16 ifconfig sl1 203.9.252.64 203.9.252.16 ifconfig sl2 203.9.252.72 203.9.252.16 arp -s 203.9.252.16 00:40:33:30:d3:88 pub arp -s 203.9.252.32 00:40:33:30:d3:88 pub arp -s 203.9.252.48 00:40:33:30:d3:88 pub arp -s 203.9.252.64 00:40:33:30:d3:88 pub arp -s 203.9.252.72 00:40:33:30:d3:88 pub route add 203.9.252.32 203.9.252.16 0 route add 203.9.252.48 203.9.252.16 0 route add 203.9.252.64 203.9.252.16 0 route add 203.9.252.72 203.9.252.16 0 As it stands now the computer responds to: 203.9.252.2 203.9.252.16 203.9.252.32 203.9.252.48 203.9.252.64 203.9.252.72 I'll leave the reader to see what they are. Here's the slip.cfg file: # Set up a simple default sl0 (default parameter values commented above) interface sl0 {device="com2"} interface sl1 {device="com2"} interface sl2 {device="com2"} The slip driver does seem to want a com port, but it doesn't seem to care if you use the same one n times over. (The mouse has the other port). In the GoHTTP.V20 script I've hacked in: IF myaddr = '203.9.252.16' THEN dir = 'c:\goserve\gohttp\sydney\' ELSE IF myaddr = '203.9.252.32' THEN dir = 'c:\pds\' ELSE IF myaddr = '203.9.252.48' THEN dir = 'c:\goserve\gohttp\melbourne\' ELSE IF myaddr = '203.9.252.64' THEN dir = 'c:\goserve\gohttp\adelaide\' ELSE IF myaddr = '203.9.252.72' THEN dir = 'c:\goserve\gohttp\brisbane\' ELSE dir = datadir() /* Data directory (root of all data directories) */ /* [must include drive and end in '/'] */ Having done that, I fire up the Web server and it responds to all the addresses popping up different pages depending on which domain the request is for. ==================================================================== See also http://www.slink.com/ApacheOS2/virtualhosts.shtml for another explanation of how to do this and a .CMD file to do it automatically for you. The limit for using the dummy SLIP method is 10 aliases (sl0 - sl9), but I think you might be able to do the same thing again with dummy PPP interfaces (ppp0 - ppp9) and get another 10. The TCP/IP 4.0 and Merlin docs don't state what the maximum number of aliases is. All in all, it looks like Merlin (or TCP/IP 4.0 in some form) will make this much easier. PP> And finally, all of the above and how it would apply to ftpd PP> and such. Hmmm... I think you'd have to find an ftpd that supports a multi-homed setup or maybe run multiple ftpd's. Check out PowerWEB++ at http://www.compusource.co.za - their server does HTTP, FTP, SMTP and POP3 and is designed to be used as a multi-homed server. Also check out http://w3.ag.uiuc.edu/DLM/HTTPDforOS2.html for more info on OS/2 based WWW servers. --- * Origin: Starship Heart of Gold - Edmonton, AB [403]489-1735 (1:342/42) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCE00004 Date: 08/09/96 From: CHRIS WOLCOTT Time: 01:34pm \/To: TERRY COLLINS (Read 1 times) Subj: Re: Multi-Protocols TC> Um, what version is your IPX, 802.3 (Netware V3.11 & #.12) or 802.2 TC> (Ver 3.12+)? You might have some SNA conflict. Netware 4.1 (802.2) and SNA (Also 802.2). We do not seem to have any difficultites. In what way would these manifest themselves? --- Maximus/2 3.01 * Origin: The OUTER LIMITS: Another BBS proudly running OS/2 WARP! (1:3612/250) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCE00005 Date: 08/10/96 From: MIKE BILOW Time: 04:38am \/To: STEVEN HENDRIKS (Read 3 times) Subj: OS/2 Peer Steven Hendriks wrote in a message to Mike Bilow: MB> OS/2 simply is not designed to be rebooted often. SH> But it shouldn't make a Pentium look like an XT when SH> starting up...:( Part of the problem is a design mistake in OS/2: there is no way for a device driver to query for the speed of the system. As a result, device drivers often run delay loops to measure how much real time has passed in order to estimate machine speed. As each device driver does this, the time spent in delay loops tends to add up, and eventually delay loops consume a very large portion of the time spent booting, perhaps more than half. -- Mike --- * Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DCF00000 Date: 08/10/96 From: GUSTAVO MUSLERA Time: 12:42am \/To: PHIL PATTENGALE (Read 1 times) Subj: DNS for OS/2 - cheap? Hi PHIL, In a message of to GUSTAVO MUSLERA (), you wrote: -> Exist the port of Bind 4.9.3 for OS/2, that could be found in -> Hobbes. This works very well in OS/2 (as far I'm running it ;-), and -> is freeware. -> In the other hand, from IBM you have the DNS Kit for TCPIP 2.0 (I -> think that costs 200-300 US$), that works with 3.0, and the DDNS -> included with Warp Server (in this case, the cost is 0, if you buy -> Warp Server that costs 600-1000 US$ :-) PP> Thanks for the reply.... I've found this and wow, what a mess! PP> I'd like to get some information from you, if I may. PP> 1. What files go where? PP> I made sure that the \tcpip\etc\namedb\named.boot path and file PP> exists, as stated in the pathnames.? file. Also made sure that the PP> \tcpip\bin\named-xfer file exists there. I didn't see any other paths PP> to worry about (I do have a \temp dir already). I have the binaries in \tcpip\bin, and the configuration files in \tcpip\etc\namedb. In named.boot, you can specify a directory where goes the other files (i.e directory /tcpip/etc/namedb :-), and configure they to work with you configuration. I also have the temporary files in \temp :-) PP> 2. What files need editing? All :-) You must create the named.boot file, then one for the name resolution, and another for the reversed resolution. You must also download the initial cache file. PP> I attempted to read thru the \doc\misc\dns-setup file, and the two PP> faq files, but am totally confused. Is a good doc, I made my first configuration with it... but I have some errors in the configuration (lack of base concepts). A must-have book for all of this is "DNS and BIND" by Paul Albitz & Cricket Lui, from the editorial O'Reilly&Associates. Is THE reference to install and mantain a domain name server... PP> ps. Do you think that the DDNS file included with OS2 Warp Server Beta2 PP> would function or die since it's older than the 60 day expiration date? I'm not tried it... but perhaps will die. You can also obtain the Warp Server demo... but will also die after 60 days of installation. Gustavo Muslera gmuslera@tips.org.uy --- The-Box Point 0.15- PC * Origin: uuFido (4:850/3.7)