Discussion Locked

Computer Name not in NetNeighborhood

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have NT 4.0 SP6 along with workstations that are all w/98 2ed. Some of the WS are not showing their id in the network neighborhood, even on the w98 itself. however, when I issue a FIND|COMPUTER, I will get a display back. Display shows that all other computers are in Network Neighborhood. The missing computer is listed as being in the domain of the NT. But all computers are issuing NT logins successfully. What causes these w/98s not to show on NetNeighborhood?

17 replies

by jmstitt

HI. First thing to check is the length of the computer's ID. Windows 98 only supports computer ID names of 12 characters (I think it's 12, maybe 13). Anyway, rename the computer with less than 12 characters. If the character length is the problem, that will fix it and the computer will show up in Windows 98 network neighborhood.

by jonsf1

I'm not sure whether this can help or not, but try to check and see whether you install the NetBEUI Protocol or not? Because without this protocol sometimes you cannot see others PC in the Network Neighbourhood as well as your own PC.

by russ werner

Make sure the workstations have file and printer sharing turned on. Try sharing a drive on eack of these computers, even if it is A: or a cd-drive.

by maxtec

The WIN98 WS name or ID showing on the any PC within the same network-zone.
First, you must have Files and Print services installed on those WS.
Second, the name or ID showing by using the system broadcasting method to notistfy within the network-zone. If you use WINS server or disable the broadcast. It also will not show as well.

Regards

by nettek

According to Microsoft's Knowledge Base article, Q210327, "Browse lists often do not consistently contain all computers in a Windows NT network. This is caused by a variety of factors that range from individual computer configurations to inadequate name resolution." In other words, even Microsoft can't give you a complete answer.

NetBT (NetBios over TCP/IP) is often unreliable. Having a WINs server would help, but even WINs has a tendency for corruption. If your problem is limited to only afew workstations, you can use the steps in article Q210327 to manually populate network neighborhood with the missing computers.

by philthegreat

Oh, mine! It is hundreds of possibilities.
1) If only some WS are continually not shown on the network neighorhood; there may connection problems in these WS; please check the cable (yes, I am not joking.) and the connectivity setting.

2) Second, the computer name may be the problem too.

3) Also, but bad news: It is the NT's (including win2000)problem; the unstability is a bug that has not been fixed yet.

by flan

probably cuz you need to enable network file and print share on win98 machines. by default they are workstations only. so if you want to them to pop up you need to turn them into servers (that's by turning one the file and print share) but if you not gonna share files, it better they are not seen (security issues)

by shanepri

You will be able to see any machine on a lan that has/have the same protocol/s running that the other machines have, regardless of sharing, domain, etc. It is even possible to log on to the server regardless of domain or workgroup, just as long as you have a valid user/pass on that server. You could also have a license shortage! Are you serving ip's with dhcp, or do you have static addresses being handed out? Hope I could help a little!

This discussion is closed to new replies.