February 25, 2013
Posted by on
I was just looking at one of my posts from last March about mobile lab connectivity. One thing I can add is that we set our lab laptops so that Windows cannot turn off the wireless. This way students are less likely to lose their network connection once they get one. We have also greatly increased the number of access points in the buildings (which has led to new issues with wireless interference and channel selection).
I wanted to add the link for MAC address filtering on Server 2003. Despite doubling the number of addresses available, we have again started to run out occasionally at one location. Blocking DHCP access to non district computers using MS Callout Filter is discussed here. Found the download and instructions here on Mark M Manning’s blog. Thanks Mark!
October 18, 2011
Posted by on
IP address conflicts pop up here and there, sporadically. Sloppiness borne of haste on our part, outside devices on our network, or the occasional access point that resets to its defaults. These can all lead to IP address conflicts. These are generally just an annoyance, and don’t result in any difficulties. Tracking them down can be frustrating and not worth the effort. But I recently got a little frustrated with a persistent conflict and decided to find a tool to help track it down. I found a handy little utility called Zenmap (ver 5.51) that provides a handy GUI for Nmap. Available from Nmap.org, this utility spits out useful information gleaned from the item connected to the network at the IP address you enter into the program. It can show info about the type and name of the device that help identify what is causing an IP conflict on the network. Helped me find the wireless access point that I had set up with a static IP and no reservation in DHCP (sloppiness, as I said). Zenmap was kinda fun to use, and other than the single eye logo for the program, I am pleased with it. (Not so much the logo, just not a favorite of mine.)