--------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DG500003 Date: 12/03/96 From: ALEC HERRMANN Time: 11:21pm \/To: JOHN ANGELICO (Read 2 times) Subj: Lanserver 4.0 on Warp Co Hello John, Replying to a message of John Angelico to Alec Herrmann: AH>>>> Try taking out the BASEDEV=DETNE2.SYS line from your config.sys file. JA> Do we need it after the install is all done ie for daily use? No, you do not need it afterwards as far as I know. However, I do not personally use NE2000 type cards so I could be wrong in that case. JA> Ciao, JA> John Angelico JA> alias talldad@pobox.com.au JA> ___ JA> X KWQ/2 1.2i X To err is human. To moo is bovine. JA> -!- JA> ! Origin: Melbourne PC User Group BBS (3:632/309) 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: DG500004 Date: 12/04/96 From: GEORGE FLIGER Time: 08:14am \/To: RICHARD JAMES (Read 2 times) Subj: Re: OS/2 and Novell On 2 Dec 96 10:48pm, Richard James wrote to Eric Rusk: ER>I am the Technology Administrator at a High School and >right now we run a Windows 3.11/Novell Netware v3.15 >network. We are looking into OS/2, but we need to know if >our lab has the power to run it. We have 25 486dx2/66mhz >machines with 8 meg ram and 210meg hard drives. Our server >is a Pentium-133 with 16meg ram and a 2.5 gig hard drive. >Will we be able to go to an OS/2 based network? RJ> IMO, you would be at the bottom end with 8megs on the RJ> machines.... It will work, but will be slow. I'd suggest Warp RJ> 3 without Warp Connect and using Lantastic for OS/2 as one RJ> way to speed it up, but it will cost you about $100 more per RJ> WS... for that price you should be able to get some RAM..... Why in the world would he want to downgrade to Lantastic for OS/2 when he has Netware running in the background? It's obvious that peer-to-peer networking support is not an issue here and OS/2 v3.0 with the Netware Requester is a solid solution. Memory-wise I agree with you. 8 Megs is a bit short. 16 Megs would be better, 24 Megs - ideal. Straight Warp v3.0 would, as you suggest, be the best choice and 16 Megs would be the appropriate "sweet spot" for this setup. Lantastic for OS/2, on the other hand, would just add overhead and actually slow things down rather than speed them up. As for Win95 applications -- Stay with Netware and OS/2 with Windows 3.1. The idea is to be a stable system. Why compromise that by putting in flaky Win95 code? There's enough legacy products out there that you don't need Win95 unless you just need to massage the old ego by being able to claim that you own the latest and greatest (a matter of opinion as far as Win95 is concerned). George ... Anything is good if it's made of chocolate. --- Via Silver Xpress V4.3P BT003 * Origin: Chipper Clipper * Bradenton, Fl * 941-745-5677 * (1:137/2) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DG500005 Date: 12/04/96 From: ALEC HERRMANN Time: 07:17pm \/To: JAMES LAINE (Read 2 times) Subj: InterNet between OS/2 and WIN-OS/2 Hello James, Replying to a message of James Laine to All: JL> Is it possible to start a TCP/IP connection to the InterNet via OS/2, JL> then access the TCP/IP connection through WIN-OS/2, or even an OS/2 JL> DOS session? Copy the DLLs in x:\TCPIP\DOS\BIN (wftpapi.dll and winsock.dll), to your Windows or Windows System directory. Run WinOS2, and run the x:\TCPIP\DOS\BIN\TCPCNTL.EXE program. Nothing immediate will be apparent, however, if you try to run TCPCNTL.EXE a second time, a message will appear that it is already loaded. Alternatively, you can put TCPCNTL.EXE in your Windows startup folder. Connect to your Internet service provider with the usual OS/2 programs. Try running one of your Windows internet programs as a test, or try running x:\TCPIP\DOS\BIN\WPING.EXE - you should be able to ping your provider as well as any other address available. You should now be able to run your favourite Windows Internet programs. 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: DG500006 Date: 12/04/96 From: UDO VAN DEN HEUVEL Time: 05:23pm \/To: ALL (Read 2 times) Subj: computername from IBMLAN.INI not used!??17:23:2212/04/96 Hello All! I'm using Warp plus IBM Peer. When I start Sharing and Connecting and View the Settings of the Network the domain is OK (same name as in IBMLAN.INI) but the computername isn't used at all, the default name (PEER) is used! How do I change this? Manually changing IBMLAN.INI to a different name doesn't help. Argh! Please help!! Greetz, Udo --- * Origin: (2:285/308.2) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DGA00000 Date: 12/03/96 From: TONY LANGDON Time: 08:31am \/To: MICHAEL HATCHARD (Read 2 times) Subj: warp 3 networking to linux It's 01 Dec 96 03:11:56, We'll return to Michael Hatchard and Tony Langdon's discussion of warp 3 networking to linux MH> Linux machines MH> Network 203.1.91.205 (Main Server) MH> Network 203.1.91.206 (Client) MH> Netmask 255.255.255.252 MH> OS/2 MH> Network 203.1.91.207 MH> Netmask 255.255.255.252 MH> Default route 203.1.91.205 TL> Hmm, looks a rather unusual setup there. What are the 2 IP's on TL> the Linux box used for? I assume by "Network", you mean the IP TL> address. Also, there's no way you can use 3 IP's on a 2 bit subnet, TL> as one will clash with either the network or broadcast address. MH> I originally only had one machine .205 with one phone line for MH> incoming calls & one other line connecting me to the net. I then added MH> another machine that was going to handle the incoming lines, which I MH> numbered .206 I had trouble getting them to talk origianlly as I was MH> told to use the netmask 255.255.255.0 I was then told to change the MH> netmask to 255.255.255.252 which then worked great. For 2 machines, each with a single IP, this arrangement will work great. Once you try adding IP's beyond 2, you'll be in trouble. :-) TL> Otherwise, see if you can get a 3 bit subnet allocated, which will TL> give you 6 useable IP's. :-) MH> Every day I learn something new playing with this stuff:)) MH> Okay how do I go about a 3 bit subnet?? Ask your ISP for a block of 8 IP addresses. They will be different to the ones you have (unless you're lucky enough to get .200 - .207). Once you have your IPs, assign them as you see fit, and you'd set up your LAN much the same, except that the netmask will become 255.255.255.248, instead of 255.255.255.252, and your network and broadcast addresses will have to be changed to the appropriate values. ... Each of us can either lead, follow, or quit dancing --- FMail/386 1.02 * Origin: The Bridge - Remote Sysop. (3:635/728.18) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DGA00001 Date: 12/03/96 From: PAUL SALETAN Time: 04:42am \/To: ALL (Read 2 times) Subj: MS LanMan 2.2c & IAK Is anyone successfully running both the IAK and the Lan Manager client on the same machine? I'm trying to set up a test intranet between a Warp Connect server and an OS/2 Warp 3.0 client. The client has been successfully running NetBeui using the Microsoft OS/2 LanMan 2.2c drivers. However, in trying to add TCP/IP protocol, I'm still unable to get WebExplorer browser on the client to recognize the webserver address (http://myhost), although the same operation works fine from the server itself. I've made an entry for "myhost" in the client's \LANMAN\HOSTS file (and \TCPIP\ETC\HOSTS also) and I can "ping myhost" from the client, so I don't understand why WebEx fails to locate it, unless it is only\ looking at the nameserver entries in \TCPIP\ETC\RESOLV. (I do not have a default router defined anywhere.) Any ideas on how to make the IAK apps see the hostname on the LAN? --- Blue Wave/Max v2.12 * Origin: The HUB * Austin TX * Centex PCUG * 512-346-1852 (1:382/1201) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DGA00002 Date: 12/03/96 From: TOMI SKYTTA Time: 03:53am \/To: ALL (Read 2 times) Subj: Warp 4 LAN Hi, Just want to get confirmation on whether Warp 4 inherently supports LAN without needing to get a "Connect" version or other software. thanks Tomi Skytta ___TheEdit v2.03 --- * Origin: The Brook * (519)858-0774 * E-Mail * 28.8 * 3 Nodes (1:2401/309) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DGB00000 Date: 12/06/96 From: SCOTT BROWN Time: 12:31am \/To: TONY LANGDON (Read 2 times) Subj: Net... PP> DSK3-1.EXE 865834 PP> DSK3-2.EXE 289253 ML> I suppose this is windows stuff, not that DOS client thing? TL> These are the DOS clients. I ftp's them myself. :-) They wouldnt work for me... so I went to the LanServer 60-day eval CD I got a while back, and lo-and-behold - Version 5.0 DOS LS Clients, sitting waiting to be installed... And they worked too. --- Maximus/2 3.01 * Origin: Batman BBS, Waterloo,Ont. USR DS V.34+ (519)886-3437 (1:221/1401) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DGB00001 Date: 12/05/96 From: RICH WONNEBERGER Time: 10:21pm \/To: ALEC HERRMANN (Read 2 times) Subj: TCP/IP and Dialup networking *** Quoting Alec Herrmann to Rich Wonneberger dated 12-02-96 *** > There is nothing in the help file on the basics of TCP/IP, and how you > set up 'ports' for various devices such as your serial port and > ethernet card. You will have to go to one of the well-known TCP/IP (bit del) > Basically, you want to assign a IP address to your serial port, and > another one to your ethernet card. You then want to set up your > routing so any packets intended to go out the serial port (your dialup So the o/l doc's are worth less then I thought.. :{ I know the basic theory, as I finish'd the TCP/IP course for Novell, but I just havent the foggiest idea what programs to set things up in.. Now to try to find a book for TCP/IP for OS/2 4.0 should be more fun.. Thanks anyway.. Rich I-Net turtil@ny.frontiercomm.net --- GEcho 1.00 * Origin: Turtil's Pond BBS. Monroe NY 914-783-2106 (1:272/50) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DGB00002 Date: 12/05/96 From: DOUG VOGT Time: 07:57pm \/To: ALEC HERRMANN (Read 2 times) Subj: 3Com 3C900-Combo In a msg on , Alec Herrmann of 1:153/8086 writes: AH> If calling 3COM (1-800-NET-3COM) does not solve your problem, AH> then you will have to wait till 3COM releases drivers - I doubt AH> the latter though since I have been able to download drivers from AH> their BBS for every card I have used from 3COM. OK, thank you for the information, I'll give them a call. Now here's a tougher question: is there a reasonably decent book (or any book at all!) on Lanserver 4.0? I've been running a network under Warp 3 and LS 4 for quite a while with only minor problems. To upgrade to Warp 4, I switched the 486 motherboard to a Pentium Pro 180 motherboard and have not been able to get the LAN up again. (TCPIP was installed on Warp 3 and now with 4.) The main symptom: the requester starts but the server just produces dots for hours at a time if I let it. One specific reason for the book: perhaps it will answer why I get a startup.cmd like this (everything is remmed out so my BBS which is in the startup object comes up): rem NET START SERVER rem @if errorlevel 2 C:\IBMLAN\NETPROG\lserr.exe rem detach C:\IBMINST\crtuidp rem logon userid /p:password /d:house EXIT What's the detach doing there and what does it do? The basic question is: can LS 4.0 coexist with TCPIP and Warp 4? --- msgedsq/2 2.1a * Origin: GYPSY BARON, Bridgewater, NJ V32b/V42b/V34/VFC (1:2605/638)