tag:blogger.com,1999:blog-6690994337395244641.post968757172962938970..comments2022-03-30T14:14:56.448-05:00Comments on Paul Melson's Blog: The Great NAC RobberyPaulMhttp://www.blogger.com/profile/02530533566781746778noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6690994337395244641.post-47961062102716122122007-08-31T09:57:00.000-05:002007-08-31T09:57:00.000-05:00I agree, it sounds like a big win for the sales pe...I agree, it sounds like a big win for the sales person but money better spent on other things.<BR/><BR/>On a sort of related note, do you have a suggestion (besides NAC) for pinpointing a rogue access point on a lan from the wired side? I worked on an issue recently where someone plugged in a (non-rogue) access point wrong after an office move, and suddenly we had unwanted DHCP traffic that caused some issues.<BR/><BR/>It was actually found by wardriving the remote sites, but I wondered if there was another way. If we had better management software for our network hardware that would have helped, and of course moving to segmented VLANs is high on the to do list. Filtering DHCP was one thing that came to mind, but that is more of a workaround. Setting up the switches to only allow approved MAC addresses was another thought, but the hassle factor is pretty high.Doug Nibbelinkhttps://www.blogger.com/profile/01572317625118995604noreply@blogger.com