James Knott wrote: > (Ted Harding) wrote: > >> On 14-Oct-07 21:42:59, Aniruddha wrote: >> >> >>> On Sun, 2007-10-14 at 14:34 -0700, joe wrote: >>> >>> >>>> Aniruddha wrote: >>>> >>>> >>>>> My brother get his ip adres through DHCP from a large >>>>> college lan, his ip changes with regular intervals. >>>>> I wonder is it possible reserve one particular ip for >>>>> his machine and if so how do I do this? >>>>> >>>>> >>>> Sure - are you the admin of the dhcp server? >>>> >>>> Joe >>>> >>>> >>>> >>> Errr, I am afraid not. He just receives his ip adress through dhcp. >>> >>> >> There is one thing he could try, which may or may not work often >> enough to to be useful. >> >> Say he gets a particular IP address one time. Let him note that, >> and configure his own machine to have that IP address statically >> configured in his machine (this may involve setting up a static >> DNS and gateway too, so it might not be trivial). >> >> Then, if when he next connects, that particular IP address is >> free the remote server should simply recognise that he is >> using it, and not try to give it to anyone else. Since it's >> static on his mkachine, it would not change so long as he >> remained connected. >> >> (This is exactly what I do on my home LAN, by the way: The ADSL >> router gives out dynamic IPs by DHCP to any connected machine >> that asks for one, but does not interfere with any machines >> that have static IPs configured in them; and whenever I connect >> some other machine -- e.g. I'm trying out different Linux distros >> in virtual machines and off live CDs at the moment, and they all >> ask for DHCP in the first instance -- the router aloways gives >> them an IP different from the statitically configured ones. >> Of course, if one or more of the statically configured machines >> was switched off, then presumably the router could use one of >> their IP addresses, since it's not in use). >> >> Whether this suggestion is useful would depend on the demand >> for IP addresses on that campus. If an idle IP address gets >> snapped up quickly, then it would be no use at all! >> >> On the other hand, if his disconnections are brief, then >> there may be a good chance that this trick could work well >> enough. >> >> If it failed at any time, of course, then he'd just have to >> revert to DHCP for that connection. >> >> >> > > Some networks will refuse connections from a computer that doesn't have > a MAC address that's currently assigned an IP. Also, network admins can > turn into nasty trolls (not that they aren't already <g>) when they find > someone using a static address. > >
I must have gotten into this thread a little too late. Why, exactly, would you want a static ip in a dhcp environment? Sorry for the new question, but it's better than asking people if they prefer "top or bottom" (not in that way, of course) ;-) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
