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

problem with home network

1 view
Skip to first unread message

keliguana

unread,
Apr 24, 2001, 5:12:17 PM4/24/01
to
We recently bought a notebook, that came with Windows ME. Since we want to
be able to share the printer and share files we wanted to set up our home
network.
We did the networking wizard on the notebook and created the disk for our
desktop PC, since this machine is running on Windoes 98 second edition.
Both computers see only themselves in their "network neighborhood", the
other computer doesn`t show up. We reran the wizard two times, installed the
client in the network two times, nothing helps.

What could be the problem? (Cables are attached, no obvious
hardwareproblems)


Harvey VanMeter

unread,
Apr 24, 2001, 5:34:57 PM4/24/01
to
Did you enable file/printer sharing on both machines?
How are the machines connected? Hub or crossover cable?

"keliguana" <jg.k...@verizon.net> wrote in message
news:R_lF6.383$jJ5.1...@dfiatx1-snr1.gtei.net...


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.250 / Virus Database: 123 - Release Date: 4/18/2001


Carey Holzman

unread,
Apr 24, 2001, 6:55:46 PM4/24/01
to
50 tips on 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\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

"keliguana" <jg.k...@verizon.net> wrote in message news:R_lF6.383$jJ5.1...@dfiatx1-snr1.gtei.net...

Mark Lloyd

unread,
Apr 24, 2001, 7:45:15 PM4/24/01
to
In article <R_lF6.383$jJ5.1...@dfiatx1-snr1.gtei.net>,
jg.k...@verizon.net says...

Make sure the connection LEDs (one on each network card) are lit. Also,
in can help to add the IPX/SPX protocol (keep TCP/IP if you're going to
share internet access).

--
Mark Lloyd
http://148.75.72.214
http://go.to/notstupid

jgkelley

unread,
Apr 24, 2001, 9:50:53 PM4/24/01
to
I followed all the steps - it works beatifully! Thank you so much for your
quick reply.

PS: Instructions are printed for future network problems.

"Carey Holzman" <ca...@tweakhardware.com> wrote in message
news:lwnF6.3852$sA2.5...@news.uswest.net...

Carey Holzman

unread,
Apr 25, 2001, 12:25:56 AM4/25/01
to
Glad to hear it helped. Thanks for letting me know.

Carey

"jgkelley" <jg.k...@verizon.net> wrote in message news:14qF6.1712$ul5.4...@paloalto-snr1.gtei.net...

0 new messages