Discussion Locked

Cannot see the LAN or Workgroup members

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Just installed AMD Duron 750mhz machine with 256mb ram to use on LAN in the office of our family business (therefore no qualified IT dept - everyone looks to me :-()
Have installed 13 other PC's in last 2 years - either as extra or replacements. Noproblems. Cannot get this machine to see anything except itself on Network Neighborhood. Have set identification to the name i have allocated to domain account (on Win Nt4.0 server) have installed TCP/Ip, IPX/SPX, NetBui, have checked cables and hubs, have installed new Netcard but still can only see own computer. Help me please.

5 replies

by gmscne

I had a similar problem. I was able to browse other PCs after I told it to "share files and printers" in the correct domain. Is this option available?

by tyrann

This is usually because of mismatching netbios lan number in the network.

This method is fool-proof:

1/ install a wins service on the nt4 server (very easy, no configuration)

On every computer
2/ remove ipx/sx and NetBEUI (useless)
3/ Setthe workgroup to "compagny" on every computer
4/ Give the IP of the wins server in the TCP/IP properties

Alternative:
4/ Remove every informations in TCP/IP properties on client computers. Instead install and configure DHCP on the server (saveslots of time in the future).

by wcraigmiles

Be sure to check that the network cards are running at the correct speed. If you have a mis-match between the machines you will have errors in seeing and or connecting to shares.

You can also try setting the speed of the NIC to match the settings on the other machines.

Enable file and print sharing, then share a directory on the new machine. Give it a couple of minutes and see if any of the other machines see it.

I hate to sound simple, but go to where one of the working machines arelocated and swap the two. This will prove whether you have a wiring issue.

by nutcracker

Try to ping the machine's own IP address so you would know if the NIC is ok. Then crosscheck on your TCP/IP settings if it's on the same subnet as the rest.
If your working with MS operating systems then do install Netbeui since this is a perfectly native protocol for your machine to communicate. Do not install protocols that you don't need.

This discussion is closed to new replies.