Subj : Dead EchoArea? To : Frank Reid From : Gerald Miller Date : Sat Apr 12 2003 08:40 am Hello Frank, On Saturday March 29 2003 at 15:48, Frank Reid [1:109/500] wrote to Gerald Miller, about: Dead EchoArea? [ ... snip ... ] Sorry for taking so long to reply to your message. My employer sent me out of town for an extended period.... FR> You can network the DOS machine, but it's a bit more work (and won't FR> yield the same breadth of available applications) then the Windows FR> machine. I didn't anticipate that it was going to be a "cakewalk"... :-)) FR> First, Microsoft does produce (but probably no longer supports) a FR> DOS-based Windows network client on the Windows NT CD. I'm not sure FR> if this is still distributed on the W2K CD, but it's probably FR> available on ftp.microsoft.com under the BUSSYS folder. I searched my W2K OEM disk and did not find a BUSSYS folder... If you would be so kind to supply me with some filenames, I suspect it would be much easier to narrow the search criteria. FR> I'm guessing that the SMC router does network address translation and FR> assigns non-routable address space already to your W2K machine. In FR> other words, the router has two Ethernet interfaces -- one connected FR> to your cablemodem and using the 66.* address to the world, and the FR> second connected to your D-Link switch. Hosts that live on that FR> switch, including your Windows machine, receive an address dynamically FR> when booting... probably in the 192.168.0.* network. This 192.168.*.* FR> network is non-routable address space, meaning that Internet providers FR> treat this as private and don't route the path to get there across the FR> Internet. As far as I've been able to ascertain, the D-Link switch is "invisible" to being addressed (the router doesn't see it or assign a MAC address to it). The 192.168.0.* address that you state is in reality 192.168.2.100 and there is an IP address pool that ranges to 192.168.2.199. If I understand you correctly, the SMC router is using a 24.* address to the outside... ??? FR> You'll want to connect your Ethernet cable from the DOS box to the FR> D-Link switch. After installing the Microsoft DOS client you got from I think you are misunderstanding the purpose of the D-Link switch. It is a KVM switch - run multiple CPUs using only one Keyboard, one Video monitor and one Mouse. It eliminates the desktop clutter of requiring multiple keyboards, monitors and mice. The Ethernet cables (are) all plug into the SMC router with the WAN side going to the cable modem... FR> either the NT CD or Microsoft's FTP site, you'll see two files you'll FR> need to modify in the directories it creates. In PROTOCOL.INI, you'll FR> need to set a static (fixed) IP address for the DOS machine. (DOS FR> machines running this client are notorious for not negotiating FR> BOOTP/DHCP addresses well, and this will ensure that isn't an issue.) I haven't reached this step as I haven't located a MS-DOS client. If I provide you an email address, could you fileattach the required client files? Or do I have to pay MS for the service? FR> Assign an address in the middle of the 192.168.*.* subnet, based on FR> the current address of your Windows machine. For instance, if the FR> address of your Windows machine (viewed by doing IPCONFIG from a CMD FR> prompt) is 192.168.1.50, then change PROTOCOL.INI to be 192.168.1.200. FR> (The first three octects vary, depending on the router manufacturer.) FR> Change the subnet, gateway and default DNS values also to match FR> IPCONFIG on the Windows machine. Typically, this is 255.255.255.0, FR> 192.168.1.1 and 192.168.1.1, but these also vary by manufacturers. The subnet mask (255.255.255.0) looks to be correct, but the two identical 192.168.1.1 addresses are ambiguous to me. Are you meaning that the address on the Win2K box and the DOS box must be identical? I imagine, at this point, I should inform you that I am a complete novice when it comes to LAN and I may be required to be "spoon-fed"... ;-[ Also, when I did a search for the PROTOCOL.INI file on the W2K box, I located 72 occurrences (most of which appear to be some kind of template files created by Symantec Ghost) and 3 occurrences on the diskette that came with my NIC. Would you please give me an indication of which folder I could expect to locate the "True" PROTOCOL.INI file? I have this feeling that when the initial installation of the Windows 2K Pro software was performed, the procedure automatically detected my NIC and used a default setting because I don't recall being requested to insert a disk with the network drivers. FR> Next, edit the [DOMAIN] and [WORKGROUP] sections in both files to FR> match the workgroup that's defined on your Windows machine. By FR> default, this is WORKGROUP, but Microsoft has recently started varying FR> this. This is under the Network properties, where you'll see Machine FR> Name and Workgroup defined. Ummmmm.... I opened some of the "template" files on the W2K box and did not find any of these headers. Are these to be 'User Added' headers? FR> Now, cross your fingers and reboot. With some luck, you should be FR> able to use the "NET.EXE" command on the DOS client. One common task FR> is to "map" a network drive to be available to the DOS machine, for FR> copying files, etc. Issue the FR> command: FR> NET USE X: \\W2K-Machine-Name\C$ FR> It will prompt you to authenticate to the Windows machine... use the FR> Administrator account and associated password. This should allow you FR> to access the files on the C: drive of the Windows machine. FR> You are not yet ready to share the DOS file system to the Windows FR> machine, however... you are also not ready to run DOS Internet FR> applications on the DOS machine. This requires a bit more FR> configuration and, possibly, the installation of a DOS "packet FR> driver". Let us know if you succeed on the first part, and we can FR> progress. Whoa. I located a NET.EXE file from a KA9Q site - says compiled for 386/486 computers... Will this be acceptable to use on my (Pentium MMX) DOS box or should I require some other NET.EXE file? Cheers ... Gerald --- GoldED+/386 v1.1.5-30228 * Origin: A journey begins with a single step! (1:342/512) .