Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

LAN between Win2K and WinMe

1 view
Skip to first unread message

RG

unread,
Dec 9, 2000, 6:11:54 AM12/9/00
to
LAN between Win2K and WinMe


I have w PCs, one a dell 1000MHz Dimension running WinMe (argh!) the other a
Compaq Presario 450MHz running Win2K. Lets call the Compaq one PC1 and the
Dell PC2.

On PC1 I have two NICs, one running to the Hub (fast ethernet) the other to
my Cable Modem (normal ethernet). On PC2 I have 1 NIC to the hub.

I have posted this to numerous newsgroups allready, but their advice did not
work. The TCP/IP address on my W2K machine is 192.168.0.1 with a submask of
255.255.255.0

The WinMe machine gets its IP automaticaly and its gateway is 192.168.0.1

When I go to "My Network Places" and then "computers near me" in PC1, I see
that PC, not the WinMe machine. On the WinMe machine, when I go to "My
network places" and click on "entire Network" It tells me that I can't
access the network and that this is due to a number of reasons.

I am well and truly stumped on this one, and would sincerely appreciate ANY
help, whatsoever.

Thanks,
Roham


Ro...@hotpop.com


Carey Holzman

unread,
Dec 9, 2000, 6:39:17 AM12/9/00
to

Fix peer-to-peer network problems in Windows Millennium

1) Download and install the networking patch (whether you think you need it
or not, it won't hurt anything) from Microsoft at
http://download.microsoft.com/download/winme/update/13387/winme/en-us/272991
usam.exe

2) Go into your Control Panel and double-click on the Network icon. Make
sure you have the following items installed:

A) Client for Microsoft Networks
B) Your Network adapter
C) TCP/IP
D) IPX/SPX
E) File and Printer Sharing for Microsoft Networks

3) Double-click on Client for Microsoft Networks. Make sure "Log on to
Windows NT domain" does NOT have a check in the box next to it. Select
"Logon and restore network connections". Click OK.
4) Double-click on your network adapter, and click the BINDINGS tab. Make
sure both TCP/IP and IPX/SPX are listed and both are CHECKED. Click OK.
5) Double click on TCP/IP, and click on the tab that says BINDINGS and
un-check File and Printer Sharing. Click on the tab that says ADVANCED, and
where it says Allow Binding to ATM, make sure the value is NO. Ensure there
is a check in the box at the bottom of the window that says "Set this
protocol to be the default protocol". Click OK.
6) Double-click on IPX/SPX and, on the NetBIOS tab, make sure it is
UN-checked where it says "I want to enable NetBIOS over IPX/SPX". Click on
the Bindings tab and make sure that Client for Microsoft Networks and File
and printer sharing BOTH ARE checked. Then click OK.
7) Double-click on File and Printer Sharing for Microsoft Networks. Click
once on Browse Master and make sure it's value is set to Automatic. Click
once on LM Announce and make sure it's value is set to NO. Click OK.
8) Below the ADD button, you'll see a line that says "Primary Network Logon"
, click the down arrow in the window below that and select "Windows Logon".
9) Below that is a button that says "File and Print Sharing.", click it
once. Make sure that "I want to be able to give others access to my files"
is checked and "I want to be able to allow others to print to my printer(s)"
is also checked. Click OK.
10) Click on the IDENTIFICATION tab and change your workgroup name to
WORKGROUP (please use all capitol letters, the workgroup name can be
case-sensitive on some PCs).
11) Click on the Access Control tab and make sure that Share-level access
control IS selected.
12) After you have re-booted, make sure that you select what resources you
want to share on each PC. To share the C: drive, double-click the My
Computer icon, Right click on the C: drive, click on the 'Sharing' tab and
select SHARED AS and then click OK. Repeat this process for sharing Printers
(right click on the printer you want to share), or individual directories
(right click on the yellow folder you wish to share). Optional password
protection can be found here as well.
13) Make sure you do steps 2 through 12 on all Win95 and Win98 PC's on your
network as well.
14) When you re-boot, you should be able to double-click My Network Place,
then Double-click Entire Network and click VIEW THE ENTIRE CONTENTS OF THIS
FOLDER (on the left side of the window). If the left side says HIDE THE
CONTENTS OF THIS FOLDER, then you did it right. You should see the name
WORKGROUP here, this should NOT be an empty window.
15) Click Tools, click Folder Options and click on the View tab. Make sure
that 'Automatically search for network folders and printers' IS checked. If
it is not, select it and click Apply. Next, click OK.
16) Close all windows.
17) Click Start, click Run and type REGEDIT and hit enter.
18) Click the "+" symbol next to Hkey_Current_User, click the "+" symbol
next to Software, click the "+" symbol next to Microsoft, click the "+"
symbol next to Windows, click the "+" symbol next to Current Version, click
the "+" symbol next to Explorer, click the "+" symbol next to NetCrawl and
then click on the yellow folder next to Printers.
19) Select each item listed in the window to the right, by clicking once on
it, and then press the delete button. DO NOT REMOVE THE FIRST ITEM LABELED
"(DEFAULT) Value Not Set". Repeat this process until the window on the
right is empty except for "(Default) value not set".
20) Next, just below the yellow 'Printers' folder, you should see another
yellow folder labeled "Shares", click once on the yellow folder.
21) Repeat step 12.
22) Click Registry (at the top of the windows) and Click Exit.
23) Re-boot the PC.
24) The network should now work. I have tried this method with Intel
Pentium, Pentium II, Pentium III, AMD k6-2, k6-3 and Athlon Thunderbird
processors all combined on the same network running Windows ME, Windows 98se
and a mix and match of network cards from Netgear, Dlink, SMC, Realtek,
LinkSys, Soho, and Xircom and this process worked flawlessly so that all of
the above computers running different versions of windows, having different
hardware, on a peer-to-peer network could see each other just fine.
25) If you click on My Network Places, and then double-click on Entire
Network and get the error "Cannot browse network", then do the following
steps:
26) On the computer that will be on most often, Click on Control Panel,
double-click the Network icon, double-click File and Printer Sharing for
Microsoft Networks, and where it says Browse Master, set it to enabled.
27) On all the other PC's on the LAN, set the above setting to DISABLED, so
that only ONE PC is running with Browse Master ENABLED.
28) If you are getting a SCRIPT ERROR when you double-click My Network
Places, then you must have Tweak UI installed and set to replace the first
icon that appears on the screen. Change this option back to it's default
setting, which should be My Documents.
If you are experiencing open windows of networked resources, this can be
caused by Norton Internet Security software. Also, you can delete the
offending drive letters in the contents of this registry setting. It should
help:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPo
ints\_WantUI
(please note: the last part of the key may have a different name on your PC,
but whatever that first yellow folder is called, check it's contents. Remove
the drive letters you don't want to see. And please remember to back up your
registry before modifying it!

29) If this process does not work for you, make sure you have loaded the
latest drivers for your network card, make sure your network settings are
exactly as I described above to the last detail, try changing the slot the
network card is plugged into on the motherboard, make sure your cables are
good, make sure your hub or switch or router is working, and replace your
network card as a last resort.
30) As a side note: The Netgear FA310tx PCI Network Interface Card is
detected by Windows ME as an LNE card, which will not work properly. As long
as this card is plugged into your LAN, no computers will be able to browse
the network until you install the driver from Netgear for their card.


"RG" <ro...@noos.fr> wrote in message news:OuxSuEdYAHA.280@cppssbbsa05...

Robert Kalita

unread,
Dec 9, 2000, 2:31:55 PM12/9/00
to
This specific page solved my same problem (though Win98Se and Win2K).
The part about mapping the drive on the host machine with Win2K, and
enabling the guest account (guest is normally disabled) did the trick.
Later, I read that enabling the guest account is less secure. So I
actually created a user named "baby" on the client machine on the Win98SE
client machine, and created a user called "baby" on the host Win2K
machine, and went back to disable the Guest account. It worked equally as
well. The total time of reading stuff, and trying things, was about 4
hours... so don't give up! Also, Win2K Internet Connection Sharing worked
right from day 1 on both machines, without fiddling with any settings. It
was only file and printer sharing that caused the headaches. Maybe that's
true with you, too.
http://www.wown.com/j_helmig/w2kacces.htm

daysdncunfuuzd

unread,
Dec 9, 2000, 11:34:23 PM12/9/00
to
Couldn't get this link to work

On Sat, 9 Dec 2000 04:39:17 -0700, "Carey Holzman"
<ca...@tweakhardware.com> wrote:

>http://download.microsoft.com/download/winme/update/13387/winme/en-us/272991
>usam.exe

Carey Holzman

unread,
Dec 10, 2000, 2:16:28 AM12/10/00
to
Sorry, it broke the link when it got to the next line... Here is a shorter
link.

http://support.microsoft.com/support/kb/articles/Q272/9/91.ASP


"daysdncunfuuzd" <a...@def.com> wrote in message
news:0F71092CD6815AFD.B1091C54...@lp.airnews.net...

g.

unread,
Dec 10, 2000, 12:54:59 PM12/10/00
to
Hey Carey...I have been watching the threads and all of the comments and
just wanted to say thanks for the info. I just upgraded my 4 computers +
Linux router 486 system from Win98SE to ME all around, except the Linux box
of course, and I was having one heck of a time getting them all back to my
Win98SE setup. I downloaded the patch, installed IPX, (I run networked games
anyway) and made the changes to the LM and everything works beautifully. I
am glad for the additional comments because now I know to watch which
machines must be booted in which order and why.

Thanks again for taking the time to help us all out and for putting your
suggestions "on the line" for the scrutiny of all of the learned people who
couldn't be bothered to help with your initial posts. Like you, I am much
more open to trying a fix that will work, rather than abandoning it because
it shouldn't work, or shouldn't need to work. I know that these fixes can on
occasion cause additional problems in other areas, but often they
inexplicably don't. What do I know anyway? If it works...it's the right fix
for me. Come on...how tough can this stuff be anyway? It's only 0's and
1's...right?

haha

Thanks again.

Gregg Pretzlaff
Edmonton, Alberta, Canada
gpret...@bigfoot.com

"Carey Holzman" <ca...@tweakhardware.com> wrote in message
news:eODjZSdYAHA.292@cppssbbsa04...

Carey Holzman

unread,
Dec 10, 2000, 3:40:28 PM12/10/00
to
Gregg,

Thank you for your kind comments. I agree that there are many others that
are questioning or bashing my ways because they are 'unorthodox', but those
doing the bashing haven't experienced these problems.

It's easy to point a finger, but it requires a bit more effort to lend a
helping hand.

For a while there I thought I was starting to be attacked by everyone for
'helping', no less.

Thank you for informing me that the tips I posted did help you. I took a
lot of time testing to develop and document them and I know they fix many of
the WinME networking issues. But after reading all the self-proclaimed
'experts' post their unsoliticed thoughts against this fix, I'm extremely
happy that you decided to see it for yourself and that it worked for you.

Carey

"g." <gpret...@bigfoot.com> wrote in message
news:TrPY5.52400$sz3.8...@news1.telusplanet.net...

Jason P

unread,
Dec 12, 2000, 11:06:54 AM12/12/00
to
Good notes, I would only make a note that IPX is not required to make the
below work... It will definitely help with general connectivity, but since
you are unbinding NetBIOS from IPX, it is really not helping at all with
File and Print Sharing functionality.

jason


"Carey Holzman" <ca...@tweakhardware.com> wrote in message
news:eODjZSdYAHA.292@cppssbbsa04...

The Tiger

unread,
Dec 16, 2000, 6:42:25 AM12/16/00
to
Thanks, Carey. But your article didn't help me this time. Last time, yes, I
fixed my network because of it. But then I did something and screwed it up.
Thanks anyway, though.

"Carey Holzman" <ca...@tweakhardware.com> wrote in message

news:#TTyKknYAHA.270@cppssbbsa05...

0 new messages