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't see or find other workstations in Network Neighborhood

Status
Not open for further replies.

pkcom

Technical User
Jul 7, 2000
9
US
3 workstation network through linksys hub.
2 win95b desktops and 1 nt4.0(sp6) laptops.

Only protocol on all three is tcpip. Win95 workstations
can see each other but not the nt machine in network neighborhood. They can't "find" the ntcomputer by name either. They DO get a reply when they ping the ip address of the nt workstation.

From the nt workstation neither win95 workstation shows up in network neighborhood and it can't find either machine.
It does get a reply from both when pinging each ones ip address.

In addition one of the win95 pcs is a proxy server with a cable modem connection to an isp. They nt workstation and the other win 95 workstation can both connect to the web with no problems.

Have already re-installed service pack 6 to no avail.

Would appreciate any suggestions anyone may have to resolve this issue.

Thanks !
 
Have you shared any of the directories? Because it sounds like the network is running fine, just file and print sharing isn't.

If the only protocol running on the machines is tcp/ip, then you have to enable netbios running in order to "see" the other computers in network neighborhood. That should do it.
 
Troy, thanks for the reply, yes tcpip is the only protocol
I have running on the nt workstation.

Please advise how to enable netbios running.

I checked under protocols and it's not there, I understand
that it's a component of netBEUI does that mean I should install netBEUI ?

I did find "netbios interface" in bindings it shows
winsclient (tcp/ip) enabled.

Please advise.

Thanks !
Phil
 
Check under your services tab and see if it is there. I check mine and it is there. I highlighted it and went to properties and it indicates that it is bound to my nic. I made the mistake, under the protocol section on my NT boxes, tcp/ip is the only one running. The netbios is under the services tab and should be there by default. On the win95 workstations you will have to add them as I don't think they are there by default.

 
Not sure what WINS is, but I did make progress by adding
netBeui to the NT workstation. Now if I try to find each windows 95 workstation it can even though they still don't show up in network neighborhood. On the Win 95 workstations, they still can' see/find the NT workstation.
 
Problem has been resolved by (I think) adding NetBeui
to both Win95 pcs. In addition I re-install service pack 6
on the NT machine and used "private net" ip address on all three workstations (10.10.10.1, 10.10.10.2 etc)
 
Someone taught me recently that Network Neighborhood isn't altogether reliable...but a quick check can be accomplished by typing: \\share name (ours are set up as Mike, John, etc.) at Start|Run. If sharing is up and the network is up and Zone Alarm isn't running you'll see their hard drive. [sig]<p> <br><a href=mailto: > </a><br><a href= > </a><br> [/sig]
 
You may have already checked this, but is the NT box logging on to a domain and the 95 boxes on to a workgroup. You can have the same name for a domain and a workgroup, and thiscan create problems. It is worth checking. [sig][/sig]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top