--------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1V00004 Date: 01/25/97 From: NICHOLAS COAD Time: 06:00pm \/To: MIKE BILOW (Read 8 times) Subj: Lan client Hello Mike. 25 Jan 97 12:22, Mike Bilow wrote to Nicholas Coad: MB> Client expects the workgroup to be named "WORKGROUP," while OS/2 Peer MB> expects it to be named "IBMNET." You can name it anything as long as MB> it is the same across all machines. Thank a lot Mike. I was having great difficulty setting things up. We'll see how this goes. :) ttyl Nicholas --- GoldED 2.50 UNREG * Origin: The Imperial Palace BBS, Ottawa, Canada, 613-226-2858 (1:163/428) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1V00005 Date: 01/25/97 From: SCOTT PARKS Time: 05:21pm \/To: JOSHUA SMALL (Read 9 times) Subj: Various net stuff.. Joshua Small wrote in a message to All: JS> My ISP gave me a DNS address. JS> I'm having no trouble without it. JS> What does it do, and is it worth implementing, and if so, JS> can someone give directions on how to do it under windows JS> 95. JS> He also gave me a gateway address. I set it up under tcp/ip JS> properties, but as yet i can't see any difference it may JS> have made. Any help much appreciated. You set them both up about the same way. Domain Name Server (DNS) is a server with a considerable sized translation table that changes your domain names to IP addresses. Scott Parks sparks@helix.eskimo.com --- GEcho 1.11+ * Origin: Helix BBS - Support National Public Radio (1:343/70) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1W00000 Date: 01/27/97 From: MIKE BILOW Time: 01:14am \/To: BRYAN FULLERTON (Read 8 times) Subj: lantastic 6.0 and windows 95 Bryan Fullerton wrote in a message to All: BF> I have been running lant 6.0 for a while now and just BF> upgraded one of my machines to win95. now no matter how I BF> try an d configure win95 it says network card not found.. BF> yet I can configure it to work in dos and can use the card BF> in windows for playing games etc. but even if ipx and BF> everything is turned off it still doesnt work.. Any hints BF> clues or ideas? or perhaps artisoft just pulled a bill gates BF> on us? Artisoft expects you to buy Lantastic for Windows 95 now. There have been some people in the LANTASTI echo who have reported unofficial workarounds to avoid having to do this, but I don't have that information at hand. I think you should consider replacing Lantastic if you are looking at using non-DOS operating systems, since this situation is only going to get worse. -- 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: E1W00001 Date: 01/27/97 From: MIKE BILOW Time: 01:16am \/To: SCOTT PARKS (Read 8 times) Subj: Various net stuff.. Scott Parks wrote in a message to Joshua Small: SP> Domain Name Server (DNS) is a server with a considerable sized SP> translation table that changes your domain names to IP SP> addresses. A DNS does not use a translation table except for the rare case of domians for which it happens to be authoritative. In most cases, your local DNS will query other DNS machines in order to find out which DNS is authoritative for a particular query and then to send the query to the appropriate DNS. The idea is that domain information constitutes a distributed database maintained in many different places by many different people. -- 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: E1X00000 Date: 01/25/97 From: BRUCE LANE Time: 10:45pm \/To: NICHOLAS COAD (Read 8 times) Subj: Re: Lan client Nicholas Coad woke half the neighborhood at 03:12 by yelling at All about Lan client... NC> Does anyone know where exactly the Microsoft Lan Client for DOS can be NC> found? Should be available from Microsoft's FTP site, though I don't recall the exact directory. NC> Also, would it work correctly with 3c503 cards and OS/2 Warp 4 NC> as the other peer computer? I believe the client package has native support for the 3C503. If not, most of the later cards should work with it or you could (if you have Internet access) download the disk for the '503 from ftp.3com.com. As for OS/2, no idea. I -think- OS/2's net client will talk to Microsoft's, but I'm not sure. ==Bruce ... Don't use blood for invocations--you'll get hemogoblins. --- Blue Wave/RA v2.30 * Origin: No drones allowed... (1:343/272) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1X00001 Date: 01/27/97 From: CHRIS MADDOCK Time: 12:57pm \/To: BRYAN FULLERTON (Read 8 times) Subj: lantastic 6.0 and windows 95 On 16 Jan at 13:52, Bryan Fullerton of 1:105/184 wrote to All: BF> I have been running lant 6.0 for a while now and just upgraded one of my BF> machines to win95. now no matter how I try an d configure win95 it says BF> network card not found.. yet I can configure it to work in dos and can use BF> the card in windows for playing games etc. but even if ipx and everything is BF> turned off it still doesnt work.. Any hints clues or ideas? or perhaps BF> artisoft just pulled a bill gates on us? BF> thanks --Bryan Before voicing wild theories, maybe a little more info would be in order ?? Are you running Microsoft Network, Lantastic, or both ?? What sort of card ? What port and IRQ and if applicable, shared memory address?? If it's a noderunner, try port 300 IRQ=15. If you have a secondary HDC, use the config disk to change the IRQ to something more reasonable like 10 (A good idea anyway). Did you follow the installation instructions =to the letter= ?? I have installed many Microsoft Network and Lantastic (and mixed) systems with little or (more commonly) no problems at all. If you want to use Lantastic to communicate with the Microsoft Network you will need to install the NDIS drivers with packet driver support - on the Lantastic machines. If you need, call Artisoft Tech Support. I've found them to be =very= helpfull. Regards, Chris Maddock chrism@softtech.brisnet.org.au --- Msged/386 4.00 * Origin: Diagnostic CBBS - DownUnder - (3:640/302) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1X00002 Date: 01/27/97 From: NICHOLAS COAD Time: 06:38pm \/To: MIKE BILOW (Read 8 times) Subj: MS Client Hello Mike. I found the files and setup the Microsoft Dos client and all works well. I can now use the drives on my Os/2 machine perfectly. What remains is that I don't know how to let the os/2 machine access the drives on the dos machine. Is this possible with MS client? Nicholas --- GoldED 2.50 UNREG * Origin: The Imperial Palace BBS, Ottawa, Canada, 613-226-2858 (1:163/428) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1X00003 Date: 01/27/97 From: TOM MOELLER Time: 10:22pm \/To: MIKE BILOW (Read 8 times) Subj: Novell login troubles Mike Bilow wrote in a message to Tom Moeller: MB> Tom Moeller wrote in a message to all: TM> The box is a gateway 2000 running dos 6.22, with setver TM> reporting 6.00 to netx.exe. Are there any known conflicts with TM> 6.22 and this older netware 2.2? MB> You should not use the old monolithic client under any MB> circumstances. Use the newer ODI stack, even with a NetWare MB> 2.2 server, if you are running DOS 5.0 or later clients. I'm planning on upgrading soon (by your suggestion) but thought I'd pass along the unexpected solution to the immediate problem... After finding a similar computer elsewhere on the network that boots from a floppy (no local hard drive) we copied the floppy and booted the mystery machine from that, no problem. Logs in perfectly. I combined the 'working' autoexec and config.sys with the 'sick' one, and tweaked until I found what killed it. When he installed a new modem, DOSFAX stuck its directory at the head of the path... there's something in there that Novell just didn't like. After removing the C:\DOSFAX; entry from the path, it booted fine with the original config.sys and autoexec that had been causing troubles. No other changes to device drivers, TSRs, or anything. I didn't hunt further for the specific culprit, though I expect anything with the word CAPTURE in it might be suspect. Thanks for the reply! Tom --- * Origin: The Engineer's Studio BBS || Saratoga, NY (1:267/14) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1X00004 Date: 01/26/97 From: ALAN FRAYER Time: 10:08am \/To: NICHOLAS COAD (Read 8 times) Subj: Lan client NC> Does anyone know where exactly the Microsoft Lan Client for DOS can be foun >Also, would it work correctly with 3c503 cards and OS/2 Warp 4 as the ther >peer computer? The Microsoft LAN Client for DOS is to be used in a Microsoft-supported network. I wouldn't expect it to work with OS/2 Warp as a peer. Alan * 1st 2.00 #8111 * Boy, this Soylent Green tastes great! What's in it? --- InterEcho 1.19 * Origin: FidoNet: The Casino Royale (941)739-8789 (1:137/212) --------------- FIDO MESSAGE AREA==> TOPIC: 193 LAN Ref: E1X00005 Date: 01/26/97 From: ALAN FRAYER Time: 10:08am \/To: MIKE BILOW (Read 8 times) Subj: Novell login troubles MB>First, NETX queries the operating system for its version number and does >different things accordingly, and DOS must use the SETVER TSR to lie to NETX >This practice was continued in DOS 6.x, but the old client should be replace This is no longer the case. The last runs of NETX had problems with detecting the version, but the final one does correctly recognize DOS 6.x. I still find it in use widely, and use it myself when I need a quick install to NW 3.x, as VLMs take a little time to put in place. MB> Your real problem is memory management. The old IPX/NETX system makes >certain assumption about DOS memory configuration that became invalid when D >5.0 introduced the "LOADHIGH" and "DEVICEHIGH" facilities. DOS 6.x makes an >even bigger mess with its introduction of MEMMAKER. You are using grossly >obsolete software that has so far been working entirely by coincidence. Using VLMs only makes it better to the respect that VLMs handle memory better than NETX, but since BOTH can and do use IPX ODI, and IPX ODI is what worries about NIC addressing, your point is invalid. Yes, old IPX should be replaced with IPX ODI, but NETX does not need to be replaced simply because IPX is replaced. VLMs must be used with NW 4.x. If you are not using NW 4.x, you don't NEED to ditch NETX. The network can work very well without going to VLMs. If, however, memory still needs some serious management, VLMs may help. Just because Novell isn't upgrading NETX or supporting it any further is not cause to totally abandon it. Alan * 1st 2.00 #8111 * Junk: Stuff we throw away. Stuff: Junk we keep. --- InterEcho 1.19 * Origin: FidoNet: The Casino Royale (941)739-8789 (1:137/212)