I have a VLAN dedicated to one department and things are working fine. There is going to be a practice drill in the near future and I would like to have wireless in the conference room. The VLAN is 10.15.16.X with a 255.255.255.0 subnet. The DHCP pool is ending at 10.15.16.150 for that VLAN/department.
What I've done is hook up a Linksys Wireless router to the VLAN giving it a static IP of 10.15.16.151, outside the DHCP range. I continued the DHCP from the router for the wireless users. The wireless users get an IP, are able to surf the net, and even Remote Desktop to a computer on another VLAN. The issue is that I can't print to a network printer that is on the same VLAN, or access servers that are normally accesable from this VLAN.
Is there something that I'm missing? Haven't looked into setting up static routes in the Linksys yet. Wasn't sure if this was something that would be fixed by a static route. Any help would be greatly appreciated.
ah... wireless router....
what's the point of a wireless "router" in the infrastructure residing on a VLAN? A wireless access point connected to the switch and assigned an address in the VLan pool would do the same thing as a router but without allowing traffic to other VLans on the switch. For that matter, why have VLans at all one the switch if your going to allow the router to route traffic between them?
Updated - 10th May 2007
DHCP scope on wireless router
Is the VLAN feeding the WAN port on the wireless router? What is the DHCP scope on the wireless router? It almost sounds like you continued with something like 10.15.16.152 ... the same subnet. That would make the router very unhappy since it's trying to route to the same network. If that's what you did, set the wireless router scope to a different subnet so it can route to it.
22nd May 2007