--------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00000 Date: 09/25/96 From: GARY BLYDENBURGH Time: 09:38am \/To: CEDRIC SILVESTER (Read 2 times) Subj: Quake, IPX, Warp Connect Hello Cedric! Replying to a message of Cedric Silvester to All: CS> I am attempting to run Quake over my small home LAN. I read that it CS> is possible to do so by loading Novell drivers in the Quake DOS CS> session. Here's what I'm loading (on my Warp Connect computer) CS> C:\NWCLIENT\LSL.COM CS> C:\NWCLIENT\ETHER16.COM CS> C:\MWCLIENT\IPXODI.COM I have it working, you need to load the Novell Requester for OS/2, not these 3 files. it comes with Warp connect. Make sure you reinstall MPTS, as it rems out some of the lines Novell puts in your config.sys Gary --- FleetStreet 1.14 NR * Origin: (1:324/126) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00001 Date: 09/28/96 From: YANN LEGUELLEC Time: 10:49am \/To: LEWIN EDWARDS (Read 2 times) Subj: Warp Server to LANtastic 7.0 Replying to a message of Lewin Edwards to Yann LeGuellec: YL> No WIN95, or even Windows 3.x, on most of the machines here: strictly DOS YL> 6.x. I have to deal with mostly 386 workstations, running word processing LE> Okay.. dumb idea time.. why don't you install the MS LAN Manager DOS LE> requester on the 386 beasties ? That talks to OS/2 Peer just fine. I see LE> no reason why it wouldn't talk to Warp Server. It's also free, which is LE> damn attractive price. You can FREQ CLNT_DOS.ARJ from me if you really LE> want to call so far 8-) The downside to it is that the machines will LE> *only* be able to see resources on the server, the LANMAN requester is NOT LE> a peer system, just client software. I've successfully used the DOS LAN Services, BUT, unless there is a trick for memory management, I'm left with only about 430K once all the drivers are loaded (compared to about 530K with LANtastic). As far as Peer vs Client, that would be ok (it would require only minumum restructuring of the current architecture), but I'd much rather get LANtastic 7.x to work. LE> How exactly do you plan to make Internet resources accessible to OS-only LE> machines ? I'm not aware of any suitable DOS access software, and the only LE> DOS TCP/IP stack I know of is the one that OS/2 uses in VDMs ! -- Lewin LE> A.R.W. Edwards [Team OS/2] Tel 0419320415 * 0412809805 * 0414927056 LANtastic 7.x comes with NTS TCP PRO. I've gotten that to work (I've FTPed between the Warp and DOS machines), although I get sporadic lock ups... Thanks, Yann --- FleetStreet 1.16 NR * Origin: The Attic - (301) 428-1970 - USR v.all - Net 109 Library (1:109/423) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00002 Date: 09/25/96 From: STEVE GABRILOWITZ Time: 10:36pm \/To: ALL (Read 2 times) Subj: Windows/95 with Warp My network has two OS/2 Warp Connect 3 systems and one LOSE/95 ;-) It *mostly* works but.... If you look at a HPFS partition from WIN95 it sees the file names properly, with case sensitivity and transcending the old 8.3 limitation. If you look at a WIN95 partition from an OS/2 box the file names get mutated to conform to the 8.3 crap. Any way to tell WIN95 that OS/2 does long file names (and much better than it does ;-)? Also, I can not seem to properly share the printer on the WIN95 machine. If I issue the command NET USE LPT2: //GALILEO/CANON then it works fine for DOS and Windows sessions. However, if I try to create a shared printer object on the desktop I get this error message: LS\GALILEO\CANON does not exist on the network. Well, if it found it to put it on the menu then how can it not exist? ;-( Anybody have any ideas? (other than to change the LOSE/95 box to OS/2 ;-) ... I don't have the time for a hobby. I have a computer. --- QuickBBS 2.80 (Zeta-1) * Origin: NCC-1701 - QuickBBS Lives! (407) 380-1701 (1:363/1701) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00003 Date: 09/25/96 From: SANDRO GASPARETTO Time: 06:48pm \/To: PETER KNAPPER (Read 2 times) Subj: NETBIOS over TCP/IP Hello, Peter! PK> The end result was the discovery that Warp Connect Blue box fails to PK> update ALL the files correctly if you ADD NETBIOS over TCP/IP to an PK> existing configuration. PK> 1. You MUST configure your adapater to support BOTH NETBIOS and PK> NETBIOS over TCP/IP using a second LEVEL of protocol on the SAME card PK> as TCP/IP. PK> 0 - IBM TCP/IP, PK> 0 - IBM NETBIOS PK> 1 - IBM NETBIOS over TCP/IP Not for me. I have TCPIP and Netbios over TCPIP on the same level, and the same card, and I can connect to a NT server. The problem you had, happens sometime when you have Netbios, and you try to add Netbios over TcpIp on the same card. I only had to use NET1 and NET2 in the IbmLan.ini once, when I had to handle 2 lan cards using Warp Connect. bye/2, Sandro --- E-mail: gaspare@delenda.gvo.it * Origin: eat shit ! Billions of flies can't be wrong !! (2:334/201) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00004 Date: 09/26/96 From: MICHAEL HALL Time: 09:04pm \/To: MIKE BILOW (Read 2 times) Subj: Bind for OS/2 In a message to Michael Hall <09/08/96> Mike Bilow wrote: PP> Please allow me to pass along some excellent advice I received when I PP> was in the same spot. Go find "DNS and BIND" by O'Reilly & Associates. PP> (ISBN 1-56592-010-4) $29.95. MB> * * * MH> I'll look into getting the book, but since I'm really MH> trying to get it running as an experiment, I presently only MH> have 3 machines on my private net I find it hard to justify MH> the cost of the book. MB> If it is not worth $29.95 to you to buy the book, how much is it worth for me MB> to sit here and type an answer to your question? Sorry if I offended you, I know it was good advice from Phil to get the book. As I'm just running a small hobby type system here I have to watch my costs, I already spend way to much on programs, registrations and books that are required much less something I may only use once, if I was running a commercial business, etc. things would be different. As far as your question, I've always been glad to offer my help when I can for nothing, if you feel differently don't feel obligated to reply. Catch you later, Mike (mhall@riverside.org) PS: Sorry about the delay but I've been on vacation for the last 3 weeks house-sitting for my parents while they were on vacation. Also I'm glad to say I have it working now, after screwing around with it for a couple of weeks before I left, I got back and looked at it again and noticed I'd transposed a number in one of the config files (198.62.x.x vs 192.68.x.x). It's amazing how little things like that can show up after you step away from something for awhile and then come back to it later . * WCE 2.1G1/2049 * People who don't laugh aren't very serious. --- ViaMAIL!/WC4 v1.00 * Origin: Fidonet: Riverside BBS/2, 612-780-5030, (1:282/1008) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00005 Date: 09/26/96 From: MICHAEL HALL Time: 09:48pm \/To: MIKE BILOW (Read 2 times) Subj: proxy In a message to Barry Ryder <09/24/96> Mike Bilow wrote: MB> Well, you're kind of stuck. There's no reason in principle that OS/2 could MB> not act as an IP masquerader, but I don't know of any software which has be en MB> written to do it. Since there is IP masquerade software for Linux, I MB> recommended that. I'm sure that someone will eventually supply IP MB> masquerading for OS/2, possibly by porting the Linux software since OS/2 is MB> very close to the Unix Socket API. It's also possible that someone already MB> has written IP masquerading services for OS/2 and I just don't know about i t. The registered version of In-Joy supports IP masquerading. Catch you later, Mike (mhall@riverside.org) * WCE 2.1G1/2049 * ... Radioactive cats have 18 half-lives. --- ViaMAIL!/WC4 v1.00 * Origin: Fidonet: Riverside BBS/2, 612-780-5030, (1:282/1008) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00006 Date: 09/27/96 From: YANN LEGUELLEC Time: 05:08pm \/To: MIKE BILOW (Read 2 times) Subj: Warp Server to LANtastic 7.0 Replying to a message of Mike Bilow to Yann LeGuellec: MB> The free Microsoft Client for DOS will interoperate with OS/2 Warp Connect MB> and OS/2 Warp Server, running either NetBIOS over NetBEUI or NetBIOS ver MB> TCP/IP (TCPBEUI). If you need the DOS machines to act as file or print MB> servers rather than just clients, you can upgrade them to the (not free) MB> Microsoft Workgroup Add-On for DOS. Thanks, I'll look for that. Any idea if the Microsoft Client is better on memory useage than IBM's DOS LAN Services? I can only get about 430K left when I load IBM's drivers, vs 530+K with Lantastic... Thanks, Yann --- FleetStreet 1.16 NR * Origin: The Attic - (301) 428-1970 - USR v.all - Net 109 Library (1:109/423) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00007 Date: 09/19/96 From: ROB JUDD Time: 07:28am \/To: JON HARRISON (Read 2 times) Subj: VLMBoot problems > > In order to run programs that require VLM's, I must boot with > > VLMBoot to a private DOS session. When I do that, and type WIN, > > I get the following error message: > > Cannot run Windows in 386 enhanced mode with the currently installed > > protected-mode software. > > Quit the protected-mode software and try again. > > Trying Win/s gets me the same message. So what am I doing > > wrong that I cannot run Windows 3.1 in a private VDM? > RJ> Why not run Win/OS2 ? Most of it seems to work. > Because WinOS/2 does not support ipx (only netx). You need ipx to use > nwadmin. Netx won't make it here. Thus, I need a vlm boot. Oh, you're trying to run a network program from Windows (or Windows across a network, it's a bit ambiguous) under OS/2. Good luck, you'll need it. This is one of my major problems with OS/2's structure. Trouble is that a VLM boot from a private DOS session isn't actually DOS, but a poor emulation of one. The session has trouble seeing hardware, and memory management a la real DOS isn't there. The protected mode software Windows complains about is OS/2 itself, locking Windows out of the 386 protected mode calls. This architectural feature is probably necessary to protect OS/2 from being crashed by a rampant DOS session. I guess emulating all the memory management possibilities is just too complex for something that is essentially a dead duck (ie real DOS). If you find a solution to this one let me know. I thought I'd found a way to run Personal Netware in a Novell DOS 7 boot session on HPFS and felt quite proud of myself, even posting a description of how to set it up a couple of weeks back, but it turned out to be extremely intermittent and even when it worked I had the same problems with running a local or remote "real" copy of Windows as you're experiencing. If you're trying to talk to a Netware server, which I can safely assume since you want to run nwadmin, there's an OS/2 netware client available at Novell's site which may help solve some other areas, and part of the package is a VLM booter which may work for you. I seem to recall something in the docs about using nwadmin from it, but the details escape me for the moment. Rob --- FMail 0.94 * Origin: (3:632/103.69) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00008 Date: 09/22/96 From: PETER KNAPPER Time: 12:44pm \/To: DAVID STANTON (Read 2 times) Subj: OS/2 Connect and NT Server Hi David, DS> I have to get an OS/2 connect box to talk to the NT servers. The DS> IS people will tell me that the NT servers are running IP only, but DS> since we chose OS/2 for our development machine they won't support us DS> at all. Anyone who knows how to do this lemme know..... Question - Are you SURE the NT box is running TCP/IP ONLY, or do your IS people mean you can only reach the NT environment using TCP/IP procotols because of a WAN/Router network that only passes TCP/IP? If you have any WFWG (or Win95) people accessing the same NT box, and they use the standard WFWG resource allocation and sharing methods, then you emulate that environment using Warp Connect! If the connectivity is restricted because YOUR local LAN segment and the NT Server LAN segment are connected only via TCP/IP protocols, then you can solve the problem by using the "NETBIOS over TCP/IP" protocol (using either LAPS or MPTN) on the Warp machines AND the NT box, and route the TCP/IP protocol between the sites. I will assume this is really what you wish to do. If not, then please ignore the rest of this message. I run several Warp Connect machines in one building and use NETBIOS over TCP/IP to connect to an NT box at a site 15 miles away, on a daily basis. and it works very well. Fortunately the router/WAN connection betweent the LAN segments is via a 2MB link so performance is not too bad.......;-) OS/2 Peer is happy, the NT box is happy, the routers are happy, but it DID take some work to get it running. The end result was the discovery that if you configure Warp Connect FROM SCRATCH to use "NETBIOS over TCP/IP" (using the default configuration for this protocol), it gets it right. If you UPGRADE an existing local LAN/NETBIOS environment to include "NETBIOS over TCP/IP", then the OS/2 configuration program will probably get it wrong and NOT update the \IBMLAN\IBMLAN.INI file! I discovered this about 2 weeks after manually updating the files and getting things working.....;-( If you have NETBIOS support already configured on your Warp machines, and are not too familiar with manually configuring the LAN protocols, then you are probably better off COMPLETELY removing ALL LAN connectivity/configuration from your OS/2 machines, and then adding it from scratch to include the "NETBIOS over TCP/IP" protocol. If built from an empty LAN configuration, it usually works fine. The only other trick to watch out for is to make sure your OS/2 Peer DOMAIN is matched to the NT DOMAIN, or that you configure MULTIPLE DOMAIN support (from what I have found, it only appears possible to do this by manually updating the IBMLAN.INI file). In my case the NT people changed the NT DOMAIN on me without warning and everything vanished until I discovered this minor detail.....;-) If you need further details, then I can probably post my long-winded config instructions but they are fairly specific to our needs and some parts may not apply in your case. I hope this starts you on the way to solving your problem...........pk. --- Maximus/2 3.01 * Origin: Another Good Point About OS/2 (3:772/1.10) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: DDW00009 Date: 09/22/96 From: ROB JUDD Time: 12:44am \/To: BART VAN RILLAER (Read 2 times) Subj: OS/2 and linux > Is there a simple method to have a connection between OS/2 > Connect and Linux? Set 'em both up for tcp/ip. Snack. Rob --- FMail 0.94 * Origin: (3:632/103.69)