Setup a local network (2 win98 PC's)

I have two freshly installed windows 98se PC's connected to different
ports of a linksys wired router and then to a DSL modem. Both PC's
are enjoying concurrent access to the internet, both have "client for
microsoft networks" installed and both have selected "microsoft family
logon" as their primary network logon. They have different computer
names, but both have the same workgroup name ("HOME").

Now I would like to take the next step in setting up a local network
so that these two windows 98se PC's can access each others hard drives
and printers.

Please advise me as to what I do first, and I hope there are step-by-
step instructions somewhere that can guide me through the whole
process. My goal is to be able to use windows explorer (NOT internet
explorer) and have new drive letters show up that are mapped to the
other PC's hard drives.

Any help would be greatly appreciated. I didn't make any non-
recommended selections during windows 98se installation, so, I suppose
I don't have any firewalls or anything you wouldn't get during the
recommended windows 98se installation..

Help.

Littleberry

On Fri, 09 Nov 2007 22:20:48 -0800, surface9 <(E-Mail Removed)> wrote:

>I have two freshly installed windows 98se PC's connected to different
>ports of a linksys wired router and then to a DSL modem. Both PC's
>are enjoying concurrent access to the internet, both have "client for
>microsoft networks" installed and both have selected "microsoft family
>logon" as their primary network logon. They have different computer
>names, but both have the same workgroup name ("HOME").
>

I forgot to mention in the other post. To get the machines to startup
automatically (without the logon prompt) you need to select "windows
logon" as well as using a blank password with your chosen user name.

It's because I haven't used it for a few years.

It's not necessary to have the client for ms networks as primary logon
unless you are connecting to a microsoft domain (which you aren't).
For peer to peer networks like this use the windows logon as primary
logon.


>Now I would like to take the next step in setting up a local network
>so that these two windows 98se PC's can access each others hard drives
>and printers.
>
>Please advise me as to what I do first, and I hope there are step-by-
>step instructions somewhere that can guide me through the whole
>process. My goal is to be able to use windows explorer (NOT internet
>explorer) and have new drive letters show up that are mapped to the
>other PC's hard drives.

The tutorials on
http://www.windowsnetworking.com/articles_tutorials
should suffice




Jim.

On Nov 10, 7:43 am, James Egan <je...@jegan.com> wrote

.. . .
:
>
> The tutorials onhttp://www.windowsnetworking.com/articles_tutorials
> should suffice
>
> Jim.

Thanks, Jim, but the tutorials at that large webpage did not address
my specific issue: that is, connecting two Win98s3 PC's peer-to-peer
via a linksys wired router.

I got lucky, and stumbled over a method that is very simple and easy
to use, so, for the benefit of anyone out there who wants to do the
same, I will lay out the steps:

a) After installing windows 98se on two PC's and getting connected on
both machines to the internet via a wired router, then you should have
a "Network" icon under the control panel (within My Computer). Double
click that icon (open it), and you will see a Network dialogue box
with two windows and 4 boxes. The top window ("the following network
components are installed") needs to have "Client for Microsoft
Networks" in it, so, if it doesn't, then click the first box ("Add",
below the window) and select "Client", and your computer will reboot
and you need to come right back here and see that you do indeed have
"Client for Microsoft Networks" as one of your installed network
components.

Then, you need to click the bottom button "File and Printer sharing",
and click the two boxes (sharing files, and sharing printers).
Finally, you need to look at the 2nd window ("Primary Network Logon"),
and select "Client for Microsoft Networks"). You will be rebooting
after each of these selections, and, after you have gotten this last
one selected, then you will notice it takes a bit longer to boot up,
and you will be forced to answer the logon dialogue when you are
booting. You needn't supply a password (unless you just want to),
and when you get rebooted, you will have a new desktop icon titled
"Network Neighborhood".

You can browse the network neighborhood (just double-clck this icon)
and you should see both computers by the name you would have selected
during windows installation (keep them different, of course). You
needed to have selected the very same "workgroup" name for both PC's
during windows installation. If you don't see both computers under
Network Neighborhood, then you've done something wrong and need to
analize it and fix it..

Now go back to the desktop and select My Computers on each of your
PC's, and right click on your hard-drives - you will have as a
selection: "sharing", which you click on then seledt "shared as", and
then pick a unigue name for that hard drive and "full" as access
type. Select OK and then both machines should now see that hard drive
when browsing under "network neighborhood".

Take special note of the exact character string used as the address of
your shared drive (such as \\P2\p2c, in my case), and then you can go
back to the desktop, right click on "network neighbohood", and select
"Map Network Drive", and then you can select which drive letter you
want, and then type in the exact character string (when you browed
under network neighborhood), making sure you are case sensitive (upper/
lower case makes a difference), and that drive will now appear under
windows explorer by that drive letter. You can repeat this with all
your h/d's on each machine and select "reconnect at logon" so you
don't have to repeat this every time.

I haven't done this with the printers yet, but, I am thinking it is
probably just as easy as this.

Mind you, I still don't know anything about IP addresses or protocols,
and I am as much of a dunce as before, but, uning "client for
microsoft networks" makes it failry easy for the unsophisticated to
set up.

Good luck to all.

Littleberry.