Hi,
In this case I advise to implement on switches 802.1x, and the AP WPA2 enterprise!
Please refer this page:
http://en.wikipedia.org/wi
Main Topics
Browse All TopicsI'm looking for some input and advice on the best course of action to prevent the following scenarios based on my small env setup. We're a small LAN with 20-30 users, one subnet, WG firewall 1000, one 2003 AD domain and forest. All things hardwired, we use dynamic IP, while wireless ap assigning IPs to a 8 laptop training lab.
Scenarios I want to prevent:
1. Users plugging in personal laps
2. Users plugging in wireless ap
3. Basically not allowing anything on the nw that isn't a company resource and IT managed.
My immediate thoughts are to nail down wireless to mac address, implement a public wireless in dmz). I'm considering forcing static IP for the ws but that can be a huge pain, but not sure other immediate solutions to consider implementing.
I look forward to hearing how others are dealing with this outside of just telling users not to do it.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
In this case I advise to implement on switches 802.1x, and the AP WPA2 enterprise!
Please refer this page:
http://en.wikipedia.org/wi
By the way, security is a pain. That's just part of life. For wireless, set MAC address access so only those laptops you've specifically allowed will be able to get access. Don't bother with static IP addressing, that won't stop someone from just making up a legit IP address and plugging in . . . which they will do if you try something with DHCP . . . I'd go with MAC level security at the switch port level, and shut down the ports that are not in use by legitimate users.
Good luck,
SteveJ
Thanks experts. Spec01, that's not the ideal work around but a good angle. Ikalmar and SteveJ, The WAP security I'm set with and not a conern. The switch idea/route using 802.1x is a great plan and one of the top best practices in area of security, I'd bet.. StevJ, security and policing the nw in IT is a pain and often make us the bad guys, but whateva! I'm getting some new switches. I already have 2 3com baseline 2924-SFP Plus switches affording me the 802.1x security auth method. My final and possibly less than smart question with this is do i have to combine RADIUS as authentication method or is there another authentication option?
Thanks
Business Accounts
Answer for Membership
by: Spec01Posted on 2009-10-27 at 09:33:32ID: 25674427
The thing that comes to mind is creating a DHCP reservation and assign the DHCP scope to the number of nodes you have on your network. This way when a user plugs something into the network DHCP will not assign an IP address to the computer because of the assigned scope. In this case you will not have to set the IP address manually on every machine. You will need to resize the scope of DHCP reservation if you are going to add more computers or nodes to the network.
hope this helps