Deja NewsHome
Quick Search   Power Search   Search Filter   Interest Finder   Browse Groups   Post Message

Please visit our sponsor

 Article 4 of 27 Text Only   Help?
[Previous Article]
Previous
Article
[Next Article]
Next
Article
[Current Results]
Current
Results
[View Thread]
View
Thread
[Post Message]
Post
Message

Subject:      Re: Can DOS see Win95 in peer to peer
From:         mwilson@cts.com (Marc Wilson)
Date:         1997/09/07
Message-Id:   <3414249a.158700604@nntp.cts.com>
Newsgroups:   comp.os.ms-windows.networking.win95
[More Headers]


On Sun, 07 Sep 1997 00:44:15 GMT, xdhawkins@ix.netcom.com (Derrick Hawkins)
wrote:

>Is it possible to have an MS-DOS client particpate in a Win95 peer to
>peer networking environment?

Sure: 

(\\mako) D:\>net view
Servers available in workgroup WORKGROUP.
Server name            Remark
-------------------------------------------------------------------------------
\\AMI                  Samba 1.9.16p11
\\MAKO                 Kino Makoto
\\MINA                 Aino Minako
\\USAGI                MS-DOS Peer Server
The command was completed successfully.

(\\mako) D:\>net view \\usagi
Shared resources at \\USAGI

Sharename    Type         Comment
-------------------------------------------------------------------------------
TSUKINO      Disk         Usagi's Drive C
USAGI-A      Disk         Usagi's Floppy Drive
The command was completed successfully.

(\\mako) D:\>

See the MS-DOS Peer Server there?  That's the DOS machine under my desk that
runs IPROUTE. :)

>If so, what software does the DOS machine need loaded?

Ahhh... now you want to know how to DO it?  Thought you might. :)

Go over to ftp.microsoft.com.  In directory /bussys/Clients/Msclient, get the
two files in that directory.  They're self-extractors.  Install 'em.  If it
doesn't support your particular NIC, then check to see if your NIC provides
LAN Manager drivers.  You should be able to use those.  You can also use ANY
NDIS driver for your NIC, with a little bit of tweaking.

Make sure you configure the client to use whatever protocol your existing
Windows network is using.  If you're doing everything THERE via TCP/IP,
consider installing NetBEUI as well for the DOS machine's benefit.  The DOS
client supports TCP/IP... but you *don't* want to have to try to make it work.

There.  Now your DOS machine is a client on your Windows network.

Now, you want the DOS machine to be able to *share* its resources, in addition
to being able to use those shared by the Windows machines, right? :)

Go back to ftp.microsoft.com, and get WG1049.EXE, from /Softlib/Mslfiles.

It's another self-extractor.  Run it in your /NET directory... let it
overwrite whatever it wants to.

Next, look at the copy of SYSTEM.INI in your /NET directory.  It probably
looks something like this:

[network]
sizworkbuf=1498
filesharing=no
printsharing=no
autologon=yes
...

Change it to:

[network]
sizworkbuf=1498
filesharing=yes
printsharing=yes
autologon=yes
...

And restart the DOS machine.  That's all there is to it.

Now, you will find that NET.EXE has gained a few options it didn't have
before.  In particular, look at the embedded help for 'NET START SERVER' and
'NET SHARE'.

Any questions? :)

-----
Marc Wilson
mwilson@cts.com (preferred) -or- marc.wilson@juno.com
http://www.geocities.com/Athens/1148

Please visit our sponsor

Previous  |  Next  |  Results  |  View Thread  |  Author Profile  |  Post Message  |  Post Reply  |  Send Email

Copyright © 1995-97 Deja News, Inc. All rights reserved.