P2P network not functioning correctly

Hi Mike,

why don't u use TCP/IP? i think u'll solve this problem. U should have only TCP/IP installed on every PC. Select obtain automatically an ip address and start the pcs. Check also that names are not duplicated and workgroup is the same. After that if everything work we can speed up the boot giving static ip addresses, if not send me a mail and we'll check the browse master and other things.

Fabio

I also prefer TCP/IP for networking like answer 1, but this may not necessarily be your problem. Another possibility is a hardware problem.
Your description leads me to believe that you may have a chattering NIC, or a bad or out of spec cat 5 cable to machine 2. Have you checked the cable to machine 2 and tried different ports on the switch? I think your 3Com card on machine 2 has an activity indicator. While doing the Network neighborhood query on machine 2, take a look at the back of the machine next to the RJ-45 connector where your cat 5 cable is plugged into the machine, or look at the activity indicator on your switch if it has one. Is the activity indicator flashing a lot? There should be some activity, but I would expect intermittent bursts instead of constant flashing. If machine 2 is just constantly chattering, then check the NIC seating in the machine, or replace the NIC. 3Com has a lifetime warranty if I'm not mistaken.
--Charlie

Mike,
on the 3com web site they suggest the following:
Cause: The following requirements must be met to browse Network Neighborhood in Microsoft Windows 95/
Microsoft Windows 98:
1. Microsoft Windows 95/Microsoft Windows 98 network login scriptmust be accepted to browse Network
Neighborhood
2. A unique computer name must be specified in Network configuration
3. The workgroup name must be specified in Network configuration and should be the same as the other
workstations are using
4. File and Print Sharing must be installed to see yourself in Network Neighborhood
Note: If File and Print Sharing is not listed in Network Configuration on other peers/workstations then you will not
be able to view that machine in Network Neighborhood.
5. If the above requirements have been met, set Browse Master to Disabled or Enabled.

I agree with the others in that you should try TCP/IP. You tend to have less problems than with NETBEUI. Always check the little things first. Try changing the cable, then the port. Then try the 3com suggestions.

Paulette

If and when you do decide to use TCP/IP, check to ensure you are using Static IPs. This may be your problem to begin with. Your computers may be looking for a DHCP server to gain an IP from. If you are running a proxy server (internet sharing) onone of your PCs, the other two may be relying on the one PC to boot up. This is why TCP/IP makes life simple. Assign each of your computers its own IP (all within the same range i.e. 192.168.0.???). If you are not comfortable with setting static IPs, maybe you need to dump your proxy software and invest in a router. You can buy a cheap router which will provide you with a DHCP server and share your internet connection.

Good luck! Hope this helps!
640k

I disagree with the other answers regarding TCP/IP. I would stick with NetBEUI. Without the benefit of a WINs server or LMHOSTS files (which I try to avoid at all costs), TCP/IP networks have far more problems with browsing than NetBEUI.

Windows9x is infamous for having browsing problems. First, I would disable the browse master on 2 of your computers. This is done under Network Neighborhood -> Properties -> File and Print Sharing -> Properties. I would then set the browse master on thePC that is up and running most often to "Enabled" (as opposed to Auto).

If you are still having problems, try the following on computer 2.
1. Open Network Neighborhood.
2. Go to Start -> Find -> Computer.
3. Search for Computer #1.
4. Once found, drag and drop it into Network Neighborhood. You will be asked if you want to create a shortcut.
5. Repeat the process for adding computer #3.

Hope that helps.