 |
 |
Dak, It is the case that 35.8.225.0/24 is assigned to the Music and Music Practice buildings, and also to the College of Music. Given that, you're free to use any available 35.8.225.x IP address for static assignment. In general, most IP addresses have been assigned *to buildings* in /24 (class C) IP blocks. From there, the IP blocks are assigned to specific departments, either as the full /24 or some subset thereof. There are some IP allocations that have been done in smaller chunks (/25, /26, etc.), often in conjunction with firewall setups, or in areas where a small number of IP addresses is expected to last indefinitely. The most accurate source of information on the allocation of IP addresses to buildings and units at MSU can be found at: https://network.msu.edu/msu/dns/ipadministrators-msu.html You can also find the listings of all registered DNS names, but these lists are not a definitive list of IPs which are in use. Each unit should be tracking their own assignment of static IPs from within their allocated IP space. Doug On Fri, Feb 27, 2009 at 09:56:16AM -0500, Aldrich, Dak wrote: > Nick: > > That?s why I run pings and other tests, as well as check the IP Admin site at network.msu.edu, first. That way I make sure I?m not using a router address. So far I?ve not had a problem. > > Is it possible that multiple buildings have the same 3rd octet? 225 seems to be Music and Music Practice. But... Would it really be possible that any other building on campus has 225? Or does each building/building set have it?s own 3rd octet? How that all set up on campus? > > -dak > > > > On 2/27/09 7:59 AM, "Kwiatkowski, Nicholas" <[log in to unmask]> wrote: > > Dak, > > If you plan to use an IP address in the static range, you MUST let the ATS Network Management group know. A simple email to [log in to unmask] will sufficie. Believe it or not, they actually do track these things and coordinate IP addresses across departments and the University. An IP address that you randomly grab might be the address of my firewall or device that is temporarly unavailable, causing the same issue you were trying to avoid. Just as Jeff Utter said earlier -- just because something dosen't respond it ICMP requests (PING), dosen't mean that it's not out there. > > -Nick Kwiatkowski > MSU Telecom Systems > > ________________________________ > From: MSU Network Administrators Group on behalf of Aldrich, Dak > Sent: Thu 2/26/2009 8:53 PM > To: [log in to unmask] > Subject: Re: [MSUNAG] How to force a new IP address from DHCP? > > Ok. Here's what I'd do in the short term... > > I don't know about anyone else, but my two buildings each have two IP > ranges. One, the 35.10.89.x, is the DHCP address range. 35.8.225.x is my > static ip range. I'd find an ip in the static range that is not in use, and > set the machine that can't connect to one of those for now, until you find > the rogue machine. That way, you are not creating another possible conflict > by setting a DHCP address as static. > > Just my 2 cents... > > -dak > > > On 2/26/09 4:06 PM, "David McFarlane" <[log in to unmask]> wrote: > > > How can we force the campus DHCP server to assign a new dynamic IP > > address to a machine, instead of just re-assigning it its latest IP address? > > > > We seem to have rogue machine in the building set up to use an IP in > > the dynamic range as its static IP address, so when DHCP gives that > > address to our machine we get an IP conflict error. We have tried > > releasing & renewing the IP, but that just gets us back the same IP > > address that has the confilict. We also tried unregistering the > > machine from the campus DHCP server, then re-registering it, with the > > same result. > > > > So we want to tell the DHCP server, "Please give us a dynamic IP that > > is different from the one we already have, thanks." How do we do that? > > > > Thanks, > > -- dkm > > ******************** > * dak aldrich > * network admin > * college of music, msu > * [log in to unmask] > * 517.432.5045 > * comit.music.msu.edu > > > > ******************** > * dak aldrich > * network admin > * college of music, msu > * [log in to unmask] > * 517.432.5045 > * comit.music.msu.edu > -- Doug Nelson, Network Architect | [log in to unmask] Academic Technology Services | Ph: (517) 353-2980 Michigan State University | http://www.msu.edu/~nelson/