General discussion

Locked

Network neighborhood visibility

By Bayk ·
Here?s an interesting case :
I have on my network a NT Server that is configured in workgroup A.
It is on an Ethernet segment that it shares with about ten end stations running Windows NT Workstation. All of these machinesare also in workgroup A.
All the machines running Workstation can see each other in the Network Neighborhood.
The NT Server can only see four NT Workstations in its network neighborhood but not the other six. Of these four NT Workstations only three can see the NT Serverin their network neighborhood but one cannot. The rest of the NT Workstations cannot see or be seen by the NT Server in their respective network neighborhoods.

All NT Workstations can access the NT Server contents by using the search facility andentering the NT server?s IP address.

I have checked the installation of the NETBEUI protocol ; it is installed on all NT Workstations but not on the NT Server. When I attempted an installation of the protocol on the NT Server it refused to connect to the network.

So we?re stuck, for this case, with an NT Server
1- that does not run the NETBEUI protocol
2-that can see four NT Workstations with which it shares an Ethernet segment
3-but cannot be seen by seven of them.

A further element is the IP addressing scheme. It looks something like this :

NT Server 2.0.0.0/24
3NT Workstations 2.0.0.0/24 these see and are seen by the NT Server
1NT Workstation 2.0.0.0/8 This station is seen by the NT Server but cannot see the NT Server in its network Neighborhood.

Other six NT Workstations have 2.0.0.0/16 as an IP address scheme. They cannot see and are not seen by the NT Server in the network neighborhood.

While this does not create any problems it does not make sense. Any explanations?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Reaching...

by Atroxodisse In reply to Network neighborhood visi ...

Its been a while, but I take it the IPs you're using are not real internet IPs. The number after the slash is what? The subnet? Check the subnet masks. Why not keep them all on the same subnet?

Collapse -

Here's my theory please comment

by Bayk In reply to Reaching...

These IP's are on a private network. Also the /8 indicates a 255.0.0.0 mask, /16 indicates 255.255.0.0 etc.

Here's my theory on what is happening, I would appreciate some feedback on it.

I reckon that when the network neighborhood window is called up, NT sends out a broadcast frame requesting all stations on the Ethernet segment to report their IP's. When the NT Server does that it compares the IP's collected to all the IP's of its network interfaces including the ones that are used for multihoming. At this stage I must introduce an element I did not include in my original submission: the NT Server also has on one of its network interfaces an IP address that reads 2.0.0.0/8
Consequently, the NT Server dispalys all the stations with IP addresses that read : 2.0.0.0/24 and those that read 2.0.0.0/8 The rest don?t show up because NETBEUI is not installed.
When the network neighborhood is called up on the NT Workstations that have IP?s in the subnet 2.0.0.0/24 the NT Server shows up because they can compare the server?s IP address to their own and identify it as part of their subnet. However, when our NT Workstation with the IP address that reads 2.0.0.0/8 sends out its broadcasts to identify elements of its network neighborhood the NT Server sends out only the IP adress related to its network interface on the Ethernet segment. When that is comapred to the mask at the NT Workstation it finds that the NT Server is not on its subnet and therefore does not display it.

Does this sound right ?

Collapse -

I have the same case

by apol In reply to Network neighborhood visi ...

In our domain there are certain computers is not visible to the network. I go to Administrative Tools then Server Manager I saw the TYPE column which makes the problem. Those who are visible to the network the type of OS they have is Windows NT 4.0 Workstation. And for the servers Windows NT Workstation or Server. But those computer that unavailable to the network the type of OS is Windows NT Workstation or Server. I have in mind that those computers might have conflicts in their OS thats why they cannot see within the network. Its a problem for us because some PC who is invisible share files to the network. Can you give me some advice for this one. Thanks....

Collapse -

PC using WinNT invisible to the network

by apol In reply to Network neighborhood visi ...

In our domain there are certain computers is not visible to the network. I go to Administrative Tools then Server Manager I saw the TYPE column which makes the problem. Those who are visible to the network the type of OS they have is Windows NT 4.0 Workstation. And for the servers Windows NT Workstation or Server. But those computer that unavailable to the network the type of OS is Windows NT Workstation or Server. I have in mind that those computers might have conflicts in their OS thats why they cannot see within the network. Its a problem for us because some PC who is invisible share files to the network. Can you give me some advice for this one. Thanks....

Collapse -

Its the subnet mask...

by jgee22 In reply to Network neighborhood visi ...

2.0.0.0/8 had a subnet mask of 255.0.0.0
2.0.0.0/16 had a subnet mask of 255.255.0.0
2.0.0.0/24 had a subnet mask of 255.255.255.0
subnet mask indicate the pcs are in the same subnet. Since the subnet mask is different, they belong to different network, thats why you can't see them in network neighborhood. Change the subnet mask.

Collapse -

They have the same sunbnet mask

by apol In reply to Network neighborhood visi ...

We are in class C so we use 255.255.255.0 they are all the same. Is there other problem causing it to be unavailble to the network.

Back to IT Employment Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums