Net View not showing ALL PC's in the network.

[Guest]

We are running WinXPPro on the desktops, and DNS is enterprise Win2003
server. A little history: we had a flat network of 200 PC's and some servers
on 192.168.111.0/24 - we could run the command net view and see all the names
of the desktops and servers. Then we added a layer-3 router, and two vlans.
vlan-111 was servers and IT desktops, vlan-116 is end-user desktop PC's. If
we are on a PC in 111 segment and issue the netview command we only see the
111 servers/clients. None of the 116 clients appear. If we then do a RDP to a
desktop in 116 vlan, then go back to net view command, ALL the desktops in
the 116 segment appear from the 111 PC. My understanding is that layer-2 and
layer-3 do not play a role in this problem. All other function work, the 116
clients can print to a shared printer in 111 no prob.

Any ideas where we should look for the problem.?

Thanks

 

[Chuck [MVP]]

We are running WinXPPro on the desktops, and DNS is enterprise Win2003
server. A little history: we had a flat network of 200 PC's and some servers
on 192.168.111.0/24 - we could run the command net view and see all the names
of the desktops and servers. Then we added a layer-3 router, and two vlans.
vlan-111 was servers and IT desktops, vlan-116 is end-user desktop PC's. If
we are on a PC in 111 segment and issue the netview command we only see the
111 servers/clients. None of the 116 clients appear. If we then do a RDP to a
desktop in 116 vlan, then go back to net view command, ALL the desktops in
the 116 segment appear from the 111 PC. My understanding is that layer-2 and
layer-3 do not play a role in this problem. All other function work, the 116
clients can print to a shared printer in 111 no prob.

Any ideas where we should look for the problem.?

Thanks

A VLAN is like a subnet, but segmented at layer-2 (Ethernet) instead of layer-3
(IP). The browser ("net view") depends upon broadcast SMBs, and a VLAN or
subnet is a broadcast domain (ie doesn't pass broadcast SMBs, by default).

If you can configure your VLANs to pass netbios-dgm (tcp/udp 138), you should
have cross VLAN browser packets, and "net view" will show servers on each VLAN
from the other.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html
<http://nitecruzr.blogspot.com/2005/08/browsing-across-subnets.html>
http://nitecruzr.blogspot.com/2005/08/browsing-across-subnets.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

 

[Guest]

We are running WinXPPro on the desktops, and DNS is enterprise Win2003
server. A little history: we had a flat network of 200 PC's and some servers
on 192.168.111.0/24 - we could run the command net view and see all the names
of the desktops and servers. Then we added a layer-3 router, and two vlans.
vlan-111 was servers and IT desktops, vlan-116 is end-user desktop PC's. If
we are on a PC in 111 segment and issue the netview command we only see the
111 servers/clients. None of the 116 clients appear. If we then do a RDP to a
desktop in 116 vlan, then go back to net view command, ALL the desktops in
the 116 segment appear from the 111 PC. My understanding is that layer-2 and
layer-3 do not play a role in this problem. All other function work, the 116
clients can print to a shared printer in 111 no prob.

Any ideas where we should look for the problem.?

Thanks

A VLAN is like a subnet, but segmented at layer-2 (Ethernet) instead of layer-3
(IP). The browser ("net view") depends upon broadcast SMBs, and a VLAN or
subnet is a broadcast domain (ie doesn't pass broadcast SMBs, by default).

If you can configure your VLANs to pass netbios-dgm (tcp/udp 138), you should
have cross VLAN browser packets, and "net view" will show servers on each VLAN
from the other.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html
<http://nitecruzr.blogspot.com/2005/08/browsing-across-subnets.html>
http://nitecruzr.blogspot.com/2005/08/browsing-across-subnets.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

Excellent, I am using Dell layer-3 router, so will have to see they syntax
of the command.