Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can get on internet, but cannot see others in Net. Neighborhood.

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
Ok. well, here is the full problem.... where I work we just recieved 14 new computers all running windows 98. They are all comparable, but not the same models or anything, as NIC'S they are all either d-link 220P, or 3com Etherlink III.

I setup 12 of the computers with little or no troubles getting on the internet, or getting the computers to see the network (which is necessary for printing, etc.).

The last 2, both can connect to the internet, meaning that the NIC's are functional, except that they cannot find any other computers on the network.

I setup all the properties of the network and am certain that it is the same configuration as those computers that do see the network, and even went so far as to compare all the data related to each protocol.

Any suggestions??? I have run out of ideas completely. Thanks a lot in advance.
 
What sort of a network are you running? Are you using DHCP? It sounds as though you are not getting authenticated or that your file and print sharing is not registering. I would start by going to a DOS prompt and running NET DIAG and from there removing your protocols and NIC driver etc and reloading all your networking info. But try NET DIAG first.
 
Does UNC (Universal Naming Convention) work? Try going to Start->Run after logging into the network and type:

\\computername\sharename

where computername is the name of a pc that is currently sharing a folder or resource and sharename is the name of the folder being shared (sharename is optional)
 
We are using tcp/ip throughout the network... and yes it is using DHCP.

When I ran Net Diag, I got 3 different results... for 3 different computers (the third cannot even connect to the internet, but that is a different story)
1) Got the Bad command or Filename when I tried to run NET DIAG.

2) Gave the following :
\dev\ms2000$ error: hardware does not respond
Error 7306 : Driver Init failed. There could be a problem with Net.exe or in the initilization program

Error 7321: Failure to load the Network card manager.

3) Gave the following :
IPX or NetBios must be executed to load network services. Your computer can be configured to use a monolithic driver, like IPX or XNS, and the driver is not loaded.

(sorry if that looks bad, but I had to translate it from french... I hope it is good enough to understand)
The problem is that I am not exactly sure what to do with this information... it gives me new light of things to try, but I still need an expert opinion.

For cdogg, is that similiar to Start -> Find Computer ??? If it is then I have already tried that, but just in case I will try the way you suggested. Even though with the previous errors I have doubts that it will work.

Thanks again.
 
Using UNC from the RUN menu is more efficient that going to Start->Find.

Is NetBIOS installed on ANY of the pc's? If it's on some, but not on others, consider trying to add that protocol to the 3 that don't work. It may or may not make a difference...
 
Allright, the UNC did not work. I tried reinstalling the drivers for the NICs, I also tried installing NetBios, and / or IPX... all of these things did not work. Although the computers are still able to connect to the internet.

What are techniques to get hardware to respond, because that seems to be the simplist of the problems to fix at this point in time.
Once again, thanks for the help.
 
So, you actually ran the command \\computername from the RUN dialog box? What was the error message?

In order to go further, post back with what's listed in your network stack (Client for MS Networks, File and Printer Sharing, etc...)
 
I believe that you need to uninstall the NICs in these PCs and then reinstall them. You said that trying to change the drivers did not work, have you physically removed and then reinstalled the NICs? If not that would be a good idea.
 
Can you ping the local loopback? Other computers? Are you using a password? Logging into the same domain or workgroup? Workgroup or domain name spelled correctly? If you can connect to the internet, it's not the NIC. I had this problem with a small workgroup when no passwords were entered. Entering passwords solved the problem. There's an article on the MS support website. Look under the error message "unable to browse network".
Bill Burnette
A+, Network+
 
A couple of quick suggestions...

Check device manager and make certain taht the NIC is shown, w/o a red X or yellow !

"Start" "find" "computer" [name of PC that is on and up]

if this works, the problem is in the choice of workgroups, domain, protocol, etc.

at a c:\, type:

ping localhost

or

ping 127.0.0.1

if this returns data, then your network card is ok. Otherwise, check NIC drivers, PCI busmastering conflicts, i/o conflicts, IRQ, DMA, etc.

ping [known computer on nearest hub]

If this does NOT work, but "ping localhost" did work, check your physical layer CAREFULLY! Use a cable tester with remote to test from the wall to the hub, and test the patch cords on both ends. A Seimens STM-8 is a good choice, though an Ideal tester is much cheaper and works well also (~$100).

Hope that helps track it down. Keep reducing the possible area where the problem may lie, and you will eventually find the bug.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top