Philippe,
How are you able to get faculty/staff to move off dependencies on L2
printing, SMB shares, etc? and onto L3 based services? Is there general
acceptance of wireless services vs. wired services?
Do you restrict any protocols/services on the wireless network in an
academic building?
Does offering wireless users the same subnet/vlan as the building wired
network makes sense or is it a bad idea? Are there dhcp lease issues
betwwen wired and wireless users?
There appears to be a lot of local sharing and low-cost (non-L3)
printing going on in departments. It's unclear what effect adding
wireless coverage with no L2 connectivity will have on these departments.
Thanks!
Mike
***************************************************************
Michael Dickson Phone: 413-545-9639
Network Analyst [EMAIL PROTECTED]
University of Massachusetts
Network Systems and Services
***************************************************************
Philippe Hanset wrote:
Michael,
One of the caveat of mixing wireless and wired on the same VLAN
for a builing is IP contention. Your number of wired ports is fixed, your
number of clients on APs can vary greatly. You will have to redesign the
IP assignment of all those wired networks!
What's wrong with IP printing or even Netbios over IP ;-)
If you move to a Centralized Wireless Architecture, that Wired/Wireless
separation gets exacerbated even more! (IP tunnels back to the
controller!)
Philippe Hanset
----------------------------------
Philippe Hanset
University of Tennessee, Knoxville
Office of Information Technology
Network Services
108 James D Hoskins Library
1400 Cumberland Ave
Knoxville, TN 37996
----------------------------------
On Thu, 4 Oct 2007, Michael Dickson wrote:
Hi all,
We currently put all wireless clients into a unique set of wireless-only
vlans. As we expand our coverage into more staff/faculty areas on
campus, however, we are start to get the same questions surrounding
layer 2 connectivity.
Specifically, clients want to print to their local printers and access
their local shares on devices which reside on their building's wired
infrastructure, but connect their laptops via wireless while in the
office. Novell, AD, local shares, shared L2 local printers, etc., all
face the same issues.
From an IT perspective this could be seen as a feature, but I'm not
sure the clients are agreeing. How are others dealing with L2
connectivity issues? We are not sure if simply putting the SSID in the
building native 'wired' vlan is the best practice. Telling them to "plug
back in" isn't getting a lot of traction, either.
Thanks,
Mike
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Michael Dickson
Network Analyst
OIT - Network Systems and Services
University of Massachusetts Amherst
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
