TIP: Click on subject to list as thread! ANSI
echo: lan
to: BONG BENITEZ
from: JOHN DONOHUE
date: 1997-02-28 12:44:00
subject: Dos/95 Lan

 BB> This is regarding my earlier question on items needed to
 BB> connect a DOS and a Win 95 computer.
 BB> The hardware components have already been installed.
 BB> Win 95 Computer detected the card. I have Network Neighborhood Icon.
 BB> The DOS Computer detected the card using its diagnostics software.
 BB> Got a copy Microsoft Client for DOS (MSCLIENT.ZIP).
 BB> Unzipped MSCLIENT.ZIP and ran SETUP.EXE.
 BB> Any ideas why the Win 95 can't see the DOS computer and vise-versa ?
Ya know, I had exactly that problem when I set up the DOS clients using MS 
Client for Dos 3.0 to get some 286's to use drive resources on our NT 
ervers.
Funny story, if it hadn't take me so long to figure it out (Duh!)
======  
When we setup our NT3.51 and 4.0 servers, and our Windows for Workgroup pc's 
I blitzed the NWLINK protocol in ControlPanel/Network/Protocols (setup 
defaults to NWLINK and NETBEUI) because there wasn't a single Netware machine 
in the organization. I saw no reason to have it using memory. On the machines 
that were Internet servers or clients, I added TCP/IP. Everything's chugging 
along fine. Some months later, I decide to take a shot at hooking up a couple 
of 286's. Run the MSClient 3.0 install (WITHOUT following every menu option 
all the way to the bottom), reboot the 286's to get the client to take 
effect. Get the network login. OK. Tell it to NET USE D: 
\\servername\resource. Get 'Server not responding' or somesuch. Sound 
familiar? ;-)
=====
For some truly brain-dead reason, MSClient 3.0 seems to default to only 
installing the NWLINK protocol. That's why my 286 couldn't attach a drive; 
the 286 was speaking NWLINK, the NT servers were speaking NETBEUI, and 
couldn't understand each other. After I added the NETBEUI protocol to the 
286, it all worked fine. Well, except that, while I could find an 'add 
protocol' in MSClient setup, I couldn't find a 'remove protocol' in MSClient 
setup. Had to go edit the system files with a text editor to remove NWLINK. 
(hey, it's a 286, I want EVERY byte or RAM I can salvage)  ;-)
--- Maximus 2.02
---------------
* Origin: McAllen Memorial Library FidoNet (1:397/5258)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.