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

ICS(37 steps)

0 views
Skip to first unread message

JYC

unread,
Mar 24, 2001, 7:27:57 PM3/24/01
to
Looking for a post that explained how to set up a network in 37 steps.If you
have a copy ,it would be much appreciated.
Thanx
jyc


Brian Biggs

unread,
Mar 24, 2001, 7:32:31 PM3/24/01
to
It's on the T&D

--
Brian ©¿©
Tweaks and Downloads at
http://homepage.ntlworld.com/brian.biggs
http://mercury.beseen.com/chat/rooms/j/21496

"JYC" <j....@videotron.ca> wrote in message
news:hYav6.6802$A01.8...@wagner.videotron.net...

Don Kelly

unread,
Mar 24, 2001, 7:37:20 PM3/24/01
to
Here it is then.
37 steps to fixing peer-to-peer network problems in Windows Millennium by
Carey Holzman

1) The first rule is to follow each of these steps. Do not skip any for ANY
reason.
2) If you are connecting one computer directly to another (without using a
hub, switch or router) using a single cable, you MUST use a Cross-Over
cable. You CANNOT use a regular Ethernet cable.
3) For all Windows ME PCs, download and install the networking patch
(whether you think you need it or not, it won't hurt anything) from
Microsoft at http://support.microsoft.com/support/kb/articles/Q272/9/91.ASP
4) 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

5) 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.
6) 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.
7) 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.
8) 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.
9) Double-click on File and Printer Sharing for Microsoft Networks. Click
once on Browse Master and make sure its value is set to Automatic. Click
once on LM Announce and make sure its value is set to NO. Click OK.
10) 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".
11) 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.
12) 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).
13) Click on the Access Control tab and make sure that Share-level access
control IS selected.
14) 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.
15) Make sure you do steps 4 through 14 on all Win95 and Win98 PC's on your
network as well.
16) 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.
17) 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.
18) Close all windows.
19) Click Start, click Run and type REGEDIT and hit enter.
20) 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.
21) 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".
22) Next, just below the yellow 'Printers' folder, you should see another
yellow folder labeled "Shares", click once on the yellow folder.
23) Repeat step 21.
24) Click Registry (at the top of the window) and Click Exit.
25) Re-boot the PC.
26) 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.
27) 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:
28) 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.
29) 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.
30) If you are getting a SCRIPT ERROR when you double-click My Network
Places, then you must have Tweak UI installed and configured it to replace
the first icon that appears on the screen. Change this option back to it's
default setting, which should be My Documents.
31) If you cannot see the other computers in the network neighborhood, but
you can do a Search and find them (and you are able to ping them) try this:
The problem might be that during the set up of Home Networking Wizard,
Microsoft somehow names your Workgroup to be "Mshome" (the default
value) EVEN THOUGH you have specified your own name. Here is the fix:

- Start -> Run -> regedit
- Find "Mshome" (which should be in My
Computer\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP)
- Right click on Workgroup (on the right hand panel) -> Modify
- Change the "Value Data" to whatever your Workgroup Name is.

32) 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.
33) 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.
34) If NetBEUI and IPX/SPX are not listed as available protocols:
35) It seems that something in the C:\Backup\MB directory prevents you from
seeing most of the contents of the Network Properties \ Add button. When the
directory was renamed (to anything), create a blank folder named MB,
restart, then you could access NetBEUI and IPX/SPX, but first the adapter
hardware needed to be recognized. If this does not occur automatically ,
you will need to reinstall the adapter first.
36) If the above step does not work for you, try this instead: Click Start,
click Run, type MSCONFIG (hit enter), click the button labeled "Extract
File." For the name of the file you want to restore, type NETBW.INF. Restore
from your Windows Millennium CD (if your CD is your D: drive, type:
D:\WIN9X). Save File In: C:\WINDOWS. Once the file is restored, repeat this
process with NETTRANS.INF, then back in your network properties, click Add,
click Protocol, click Add, click the Have Disk button, click the Browse
button, go to C:\Windows and on the left you should see NETTRANS.INF, click
once on it and click OK. NetBEUI should now be available as a protocol
option in your network properties.
37) If you are experiencing open windows of networked resources, this can be
caused by Norton Internet Security software. Please see this link for more
info:

http://service1.symantec.com/SUPPORT/nip.nsf/docid/2000040412261536&src=w
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!)

Carey

"JYC" <j....@videotron.ca> wrote in message
news:hYav6.6802$A01.8...@wagner.videotron.net...


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.240 / Virus Database: 116 - Release Date: 24/03/2001


JYC

unread,
Mar 24, 2001, 7:40:35 PM3/24/01
to
Wow ! That was fast.
Thank you


Brian Biggs

unread,
Mar 24, 2001, 7:45:34 PM3/24/01
to
We are here to serve,

The bill is in the post ;-)

"JYC" <j....@videotron.ca> wrote in message

news:%7bv6.6869$A01.8...@wagner.videotron.net...

Carey Holzman

unread,
Mar 24, 2001, 10:00:16 PM3/24/01
to
It's been updated:
50 tips on fixing peer-to-peer network problems in Windows Millennium by Carey Holzman

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\MountPoints\_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!)

38) Network Is Slow (Linksys cards)
39) In some cases when the driver is installed properly and no errors are reported in Device Manager, some users may experience delays with transferring files or having problems browsing the network. If the protocols and the File and Print Sharing are setup properly, try changing the Transmit setting in the card. Go to Control Panel and open Network. Highlight the Linksys driver in the list and click Properties. Click on the Advanced tab. Highlight Transmit Threshold and change the value option to Store and Forward (this setting will solve most problems, you can also try other values). Click OK. Click OK again. Windows may ask for the installation files and ask you to restart the computer. Click Yes to restart.
40) Other reasons why your network may not function correctly:
41) Make sure that the network adapter is plugged firmly into your PC's interface slot.
42) Use a PCI bus master slot. Most PCI local bus computers have master slots, slave slots, and/or "combo" slots that can act as either masters or slaves. The EtherFast card should be inserted into a master slot. See your PC's user guide to see which slots are which.
43) Avoid interference. Network cabling can be run under floors, around offices dividers, or over dropped ceilings. When planning your wiring layout, try to keep cables away from power outlets, florescent lighting fixtures, uninterruptable power supplies, and other sources of strong electromagnetic interference.
44) Mind your cabling. The EtherFast card must be connected with category 5 RJ-45 cabling to a 100Base-TX hub, a standard 10BaseT hub, or an autosensing 10/100 hub. It should never be directly connected to another computer. Your RJ-45 cabling can be either straight-through or cross-over, but cross-over cabling is neither supported nor recommended by Linksys. Linksys recommends that pins 1, 2, 3, and 6 at the PC line up pin-for-pin at the hub.
45) Don't use Cyrix. 586 Cyrix processors on 486 motherboards, don't work properly with the EtherFast LAN Card. Cyrix doesn't utilize a plug-and-play BIOS at this time, so there is no way for Cyrix users to configure the card's I/O and interrupt settings.
46) Computers with Cyrix 686 CPUs. The bus speed on these computers may have to be lowered from 75Mhz to 66Mhz (or lower).
47) Compaq Compters. If your computer has 1 PCI slot, contact Compaq to see if the slot is a Bus-Mastering Slot. Some models will not support PCI network cards.
48) Check your BIOS. Because the EtherFast is a plug-and-play card, it is reliant upon your PC's BIOS for its IRQ and memory I/O information. Make sure that your BIOS is set up to automatically configure plug-and-play devices.
49) Avoid conflicts. If your BIOS allows you to specify an particular IRQ or memory I/O address for a card, be sure to pick values that are not already in use by other devices in your computer. Good IRQ values to try are 10, 11, 12 (if you do not have a Bus mouse), 9, and 5 (in that order). For I/O address, use values higher than 6000 if your BIOS allows you to set this value, otherwise one will be assigned automatically.
50) VIA Motherboards with Windows 95 and 98. Some VIA motherboards (with VT8C586B chipset) require driver patches to be downloaded and installed, so Windows 95 and 98 can recognize the PCI chipset on the motherboard and assign the proper IRQ to PCI Ethernet Cards.

Carey

"Don Kelly" <donk...@ntlworld.com> wrote in message news:C2bv6.36599$bL.33...@news6-win.server.ntlworld.com...

Don Kelly

unread,
Mar 25, 2001, 3:18:37 AM3/25/01
to
Oy mate. I am still trying to memorize the 37 steps. you are getting like
Microsoft with your rapid upgrades...LOL
"Carey Holzman" <ca...@tweakhardware.com> wrote in message
news:t6dv6.2716$Mf6.5...@news.uswest.net...

Carey

Version: 6.0.240 / Virus Database: 116 - Release Date: 23/03/2001


Iceman

unread,
Mar 25, 2001, 5:30:27 AM3/25/01
to
He is showing off his 1 G fancy computer...I am envy...:)

--

"Brian Biggs" <brian...@ntlworld.com> wrote in message
news:jbbv6.27232$Q4.47...@news2-win.server.ntlworld.com...

Brian Biggs

unread,
Mar 25, 2001, 5:38:45 AM3/25/01
to
First time I've seen Green Ice ;-)

"Iceman" <co...@cool.net> wrote in message
news:99kh9l$vrk$1...@bugstomper.ihug.com.au...

Karl E Lundstrom

unread,
Mar 25, 2001, 3:34:45 PM3/25/01
to
Puh.... All this just to configure a home network in "user friendly"
Windows? ;-)

In "hard to configure" Linux, you enter IP adress and submask, and that's
it. No rebooting and other MS bullshit. And it works even after three hours!
To comunicate with Windows, you have to tell Linux that it is talking to
retards, so you have to configure Samba, a matter of filling in workgroup
names and paths in a conf.file , and the Windows machines "see" an NT
server. The only difference that perhaps confuse the Win's is that this
server never crashes, or goes down for reboot because the user happend to
( unsuccessfully ) open notepad! Hence the absence of an array of backup
servers.

Please don't get me wrong. Your posting to the group was indeed useful. It
just strikes me that it should be possible to get two Win's to talk without
getting the urge to beat the wife and kill the dog.
After the big mistake of installing Win ME, the first global disaster of
this millenium, I finally realized that MS never will succeed in delivering
a stable OS, and by now my Linux server has been running for four months.
And this, gentlemen, is running on hardware that probably still would be
busy booting Win2000. Yet more than enough to serve the two "clients"
connected to it.
Cheap hardware and free software is a hard-to-beat deal! Two for the price
of none.

Again I thank you for your very detailed guide of setting up Me Net.

"Carey Holzman" <ca...@tweakhardware.com> wrote in message
news:t6dv6.2716$Mf6.5...@news.uswest.net...

:It's been updated:


:50 tips on fixing peer-to-peer network problems in Windows Millennium by
Carey Holzman

<Snip>


Sam

unread,
Mar 25, 2001, 4:23:31 PM3/25/01
to
It is a shame that Linux has so many holes that accept virus's
though...Isn't it?

--
http://personal.mem.bellsouth.net/mem/s/o/soffer/

Reply via this newsgroup or email me at: DerNe...@nospam.myrealbox.com
Be sure to remove the "nospam" from the address
All spam is reported to abuse.net


"Karl E Lundstrom" <torqu...@privat.cybercity.no> wrote in message
news:98555399...@news2.cybercity.dk...

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).

Version: 6.0.240 / Virus Database: 116 - Release Date: 3/23/2001


Carey Holzman

unread,
Mar 25, 2001, 7:26:00 PM3/25/01
to
There are so many different kinds of networks, network cards, drivers and protocols/clients to choose from, I think being able to get ALL of them working in 50 steps is pretty miraculous...

Carey



"Karl E Lundstrom" <torqu...@privat.cybercity.no> wrote in message news:98555399...@news2.cybercity.dk...

Carey Holzman

unread,
Mar 25, 2001, 7:25:06 PM3/25/01
to
Except I am not doing it for profit... Just sheer masochism.

Carey

"Don Kelly" <donk...@ntlworld.com> wrote in message news:wRhv6.36941$bL.34...@news6-win.server.ntlworld.com...

Shane McGough

unread,
Mar 26, 2001, 9:21:25 AM3/26/01
to
why ipx/spx? even novell changed to tcp\ip...i only use tcp/ip but i am not
a network guru by far....the reason i ask is that in my A+ class last week
we were told that using more than one protocol just slows things down.

shane

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

news:0Xvv6.1231$Go6.5...@news.uswest.net...

Don Kelly

unread,
Mar 26, 2001, 3:31:28 PM3/26/01
to
Yea dont we all. keep up the good work.

"Carey Holzman" <ca...@tweakhardware.com> wrote in message
news:0Xvv6.1231$Go6.5...@news.uswest.net...

Don Kelly

unread,
Mar 26, 2001, 3:38:19 PM3/26/01
to
As a relative newbie, compared to Carey, it is because if you only use
tcp/ip on a network for sharing files, your file sharing is more easily
attacked by a hacker. By switching off file and printer sharing in tcp/ip
and allowing it in ipx/spx it allows network sharing whilst reducing the
hackers chances off getting access to your files if they get through your
firewall. I dont whether or not this slows things down but I have noticed no
speed loss, and if there were a slight loss it would be a small price to pay
for extra seccurity.
"Shane McGough" <smcg...@rochester.rr.com> wrote in message
news:FfIv6.303825$o91.42...@typhoon.nyroc.rr.com...

Don Kelly

unread,
Mar 26, 2001, 3:44:24 PM3/26/01
to
And I might add that by following your Original "37 steps" I was able to get
my network up and running (4 PC's) in less than one hour. Most of that was
reading the instructions. Once learned it will probably take half that time.
A worthwhile investment in time.

"Carey Holzman" <ca...@tweakhardware.com> wrote in message
news:SXvv6.1235$Go6.5...@news.uswest.net...

Carey

---


Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).

Version: 6.0.240 / Virus Database: 116 - Release Date: 23/03/2001


Brian Biggs

unread,
Mar 26, 2001, 3:52:01 PM3/26/01
to
Please keep out of Chat room Rose and I are busy.

"Don Kelly" <donk...@ntlworld.com> wrote in message
news:ESNv6.42254$bL.40...@news6-win.server.ntlworld.com...

Carey Holzman

unread,
Mar 26, 2001, 4:11:33 PM3/26/01
to
Depends on the Network card and the network configuration. If you are using TCP/IP to access the internet, then it is recommended to 'unbind' file and printer sharing from that protocol to help prevent hackers from accessing your files and printers through the internet. In that case, you would add either IPX or Netbeui so that File and Printer Sharing on your LAN can be distributed through that protocol, while the internet can be distributed through TCP/IP.

Also, some games require NetBEUI or IPX to run and many LinkSYS cards require all three protocols to run properly.

It may slow things down, but I don't believe the speed difference is measureable by a human being. You would need to run benchmarks to see the difference in most cases.

Carey

"Shane McGough" <smcg...@rochester.rr.com> wrote in message news:FfIv6.303825$o91.42...@typhoon.nyroc.rr.com...

Carey Holzman

unread,
Mar 26, 2001, 4:12:52 PM3/26/01
to
Thank you Don. It only took me about 97 hours to learn it myself. I'm glad the results leading to my writing that document is saving others from going through what I had to go through.

Carey

"Don Kelly" <donk...@ntlworld.com> wrote in message news:ESNv6.42254$bL.40...@news6-win.server.ntlworld.com...

RoseSong

unread,
Mar 26, 2001, 4:11:44 PM3/26/01
to
Very funny....now they will all jump in there...rofl

"Brian Biggs" <brian...@ntlworld.com> wrote in message
news:5%Nv6.42289$bL.40...@news6-win.server.ntlworld.com...
0 new messages