? System not showing in Net. Neighborhood ?

J

Jimmy

Configuration: 10 system peer-to-peer win2k pro network. All
systems are in a workgroup with the name WORKGROUP. TCP/IP works
fine on all systems. All systems appear to have identical network
settings (aside from fixed IP and network name).

There is *one* system in this network of 10 that cannot be seen
Network Neighborhood. Other systems can _not_ see it, it does _not_
see anyone in Net Neighborhood but itself. All other systems are
fully visible to all other systems.

Also, it cannot connect using the "windows" network name for a shared
connection. However, I *was* able to connect it to a share on one of
the other systems by using \\ip-address\sharename. I *was* also able
to connect to it from another system using \\ip-address\sharename.

What would stop it from showing up in 'network neighborhood' and from
being referenced by windows networking name ?

Thanks,
 
M

Marina Roos

You know that 10 workstations really is the maximum for a workgroup? You'll
soon need a server.

Got File and Printersharing loaded on that troubled system? Does the
ipconfig/all look the same compared with the other systems?

Marina
 
J

Jimmy

You know that 10 workstations really is the maximum for a workgroup? You'll
soon need a server.
Click to expand...

I thought it was "10 connections per win2K pro machine" (?) Are they
limited to 10 systems in a workgroup too ? If so, perhaps they hit a
limit ? They might actually have 11 systems there, I'd have to count.

They don't really share much except for a few printers between
adjoining desks and a half dozen of them share a common area so that
they can share data. Unless they are limited as per above then they
don't really need a server.
Got File and Printersharing loaded on that troubled system? Does the
ipconfig/all look the same compared with the other systems?
Click to expand...

Exactly the same. I've been over it a dozen times. I can't see any
differences between the setup of one system vs. another. The weird
thing is that sharing actually works if they use the IP addresses
so it must be there. It's just the visibility in Net Neigh. and the
use of Windows names that is the issue.
 
J

Jimmy

Maybe you need Netbios over TCP/IP enabled on the troubled one.

Marina
Click to expand...

I checked that too. Seems to be there. I also uninstalled all the
networking software, re-installed everything, and it still didn't
work. It did work at one time on this system and then it stopped
working. I suspect that the local users (who don't have a clue and
do have admin passwords) changed something or removed something that
they should not have touched. I can't see it though.

Other ideas ?
 
M

Marina Roos

Hi Jimmy,

Can you give us an ipconfig/all from one machine that is working fine and
the troubled one?

Marina
 
J

Jimmy

Hi Jimmy,

Can you give us an ipconfig/all from one machine that is working fine and
the troubled one?

Marina
Click to expand...

Will do. Give me a couple days, I have to go to a remote site
to grab the into.
 
J

Jimmy

OK, here are the stats. The first one is the system that causes the
problems. The only difference I see is that the "node type" is
"Broadcast" on the troublemaker and "Hybrid" on the other (?)

[Quick recap in case the beginning of this thread is gone. The errant
system cannot see anyone in 'net neighborhood nor can it be seen
by anyone else. However, it can share or be shared by using an IP
address instead of a name i.e. \\IP-address\share. All other network
operations are normal on this system. There are multiple systems
on the network which are all like the second system shown which all
see each other and all shares with no problem.]

Thanks,


*-----------*-----------*-----------*-----------*-----------
system that does not show in net neigh.
*-----------*-----------*-----------*-----------*-----------

C:\>IPCONFIG/ALL

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : mbr1
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI
Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-4F-4E-11-39-4E
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.34.240.136
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 10.34.240.1
DNS Servers . . . . . . . . . . . : 216.41.101.15
216.41.11.17
*-----------*-----------*-----------*-----------*-----------
example: system that works properly
*-----------*-----------*-----------*-----------*-----------

C:\>ipconfig/all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : L1
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI
Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-4F-4E-11-39-4F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.34.240.140
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . : 10.34.240.1
DNS Servers . . . . . . . . . . . : 216.41.101.15
216.41.101.17
 
M

Marina Roos

Subnetmask is different on both clients.

DNS is not right. It should point to your server-IP. In the tab Forwarders
of your DNS-server, you put the ISP-DNS-numbers.
Have you got options 003, 006 and 015 in DHCP-server, Scope options?

Marina

Jimmy said:
OK, here are the stats. The first one is the system that causes the
problems. The only difference I see is that the "node type" is
"Broadcast" on the troublemaker and "Hybrid" on the other (?)

[Quick recap in case the beginning of this thread is gone. The errant
system cannot see anyone in 'net neighborhood nor can it be seen
by anyone else. However, it can share or be shared by using an IP
address instead of a name i.e. \\IP-address\share. All other network
operations are normal on this system. There are multiple systems
on the network which are all like the second system shown which all
see each other and all shares with no problem.]

Thanks,


*-----------*-----------*-----------*-----------*-----------
system that does not show in net neigh.
*-----------*-----------*-----------*-----------*-----------

C:\>IPCONFIG/ALL

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : mbr1
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI
Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-4F-4E-11-39-4E
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.34.240.136
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 10.34.240.1
DNS Servers . . . . . . . . . . . : 216.41.101.15
216.41.11.17
*-----------*-----------*-----------*-----------*-----------
example: system that works properly
*-----------*-----------*-----------*-----------*-----------

C:\>ipconfig/all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : L1
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI
Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-4F-4E-11-39-4F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.34.240.140
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . : 10.34.240.1
DNS Servers . . . . . . . . . . . : 216.41.101.15
216.41.101.17
Click to expand...
 
J

Jimmy

Subnetmask is different on both clients.
Click to expand...

Geez, you're right. I looked at that 6 times and missed it. Thanks.
DNS is not right. It should point to your server-IP. In the tab Forwarders
of your DNS-server, you put the ISP-DNS-numbers.
Have you got options 003, 006 and 015 in DHCP-server, Scope options?
Click to expand...

They have no server. Every system is stand alone and uses the
DNS servers from the ISP. They do no internal addressing at all,
it's strictly peer to peer. All the addresses are fixed, with no
DHCP on the network.


What about the "hybrid" vs. "broadcast" ? Is that of any interest ?
 
M

Marina Roos

Hi Jimmy,

So did it help when you changed the subnetmask?
How are you connecting to the internet?

Marina
 
J

Jimmy

Hi Jimmy,

So did it help when you changed the subnetmask?
How are you connecting to the internet?

Marina
Click to expand...

Sorry, it will be a couple days before I can try it. The site is an
hour from my home and office and I will have to get back out there.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Can't see peers but IP working fine ? 8
Network Issue 1
I can ping other systems but not browse them 8
My Network Neighborhood is EMPTY 2
NETBEUI w/win2k & Win98 ? 2
Network Neighborhood not showing nodes 2
cannot net use - system error 53 4
Network Neighborhood 2

Top