showing machines on different vlans

ok, we can access machines by ping and running apps over 2x different vlans.
Problem i have is that i am unable to see machines in the other vlan in network places or in dameware.
i can see them by unc name and ip fine so the routing is working.

i added dns entries for IPs for the vlan on our dns servers.

Ideas why the machines can be seen?

thanks
LVL 1
CHI-LTDAsked:
Who is Participating?
 
Daniel HelgenbergerConnect With a Mentor Commented:
I would say leave it. I consider it only as a minor nuisance if you are not able to see the other computers in the Network Tab. Other more imported things work well.
Normally I have this feature turned off anyway as it poses a security risk.

You can however use directed broadcasts for things like WOL. If you're interested, read this Cisco KB - article, though I do think it helps litte with your current problem: http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a008084b55c.shtml

Please keep in mind you potentially enable smurf and fraggle attacks.
http://en.wikipedia.org/wiki/Smurf_attack
0
 
CHI-LTDAuthor Commented:
to add, the server on vlan20 is on a 172.16.0.0 with static of 172.16.10.30.
GW (switch) of 172.16.4.5
DNS servers 172.19.10.17 and .18 (on vlan1)
0
 
Daniel HelgenbergerConnect With a Mentor Commented:
In Windows, you 'see' network places because of a broadcast the machine sends witch other clients respond to.
I think for starters, there are two posible things to check:
1. Is network discovery switched on in  Windows:
http://windows.microsoft.com/en-us/windows7/enable-or-disable-network-discovery 

2. Does your switch permit broadcasts?

HTH,
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Red-KingConnect With a Mentor IT ManagerCommented:
As helge000 said, Windows Network Discovery uses broadcasts to see other devices on the network.
When you are using VLANs your traffic needs to go to a router to get a route to the other VLAN.
By default, most routers disable the routing of broadcast traffic. Normally a VLAN will coincide with a subnet i.e. one subnet to one VLAN. Subnets break up broadcast domains.

If you want to allow broadcast traffic to route between VLANs you need to specifically enable that on your router.
If you do enable broadcast routing you are enabling it for all broadcast traffic so use this with care as you'll increase the traffic across your entire network.
0
 
Daniel HelgenbergerConnect With a Mentor Commented:
Hello,

Red-King, thanks, I overlooked this (for some reason I seem to have difficulties reading the headlines ;) - you want to 'see' the machines in different VLANs.

This is, however:
a) not desirable at all (see above) and
b) I think not even possible with Windows.  At least LLTD does only work in its own segment:
http://en.wikipedia.org/wiki/Link_Layer_Topology_Discovery

Please keep in mind routing broadcasts is something which should never been done. The permutations are endless; please see broadcast storming:
http://en.wikipedia.org/wiki/Broadcast_storm

Think of broadcasts as a thing of the past for troubles and overheads it can cause. IPv6 for instance depreciated broadcasts in favor for multicasts - which are much more efficient.
0
 
CHI-LTDAuthor Commented:
so recommended leave as is?
0
 
Craig BeckCommented:
If you want to discover hosts on other VLANs you could try using WINS.
0
 
CHI-LTDAuthor Commented:
could try, as in it works or are you guessing?
we have it installed with push/pull to another wins server..
0
 
Red-KingConnect With a Mentor IT ManagerCommented:
Something else you could try, which may or may not work, would be to configure a Trunk port from the switch to your PC.
If the NIC on your PC has the feature available to specify VLANs (usually in device properties, under the advanced tab) you may be able to specify multiple VLANs for your NIC.
You'd then add an alias IP for each VLAN/Subnet to the NIC and try running the broadcast again.

This might not work as your broadcast traffic out may get tagged with just one VLAN ID meaning it would be dropped from the other VLANs.

That's complete speculation on my part. It might be fun to try it if you enjoy that kinda thing but Helge000 has you covered with the definitive information.
0
 
Daniel HelgenbergerConnect With a Mentor Commented:
Of course, Multi-Homing the PCs should work. You would see all the network places. Just put them in both VLANs; eg. tag the other VLAN accordingly. Today any NIC is VLAN capable with the correct drivers.

I did point this not out because I think your VLAN setup would be rather pointless if you do that; but may be a valid solution for you.
0
 
CHI-LTDAuthor Commented:
wins enabled and running.  left itr as is...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.