Article View: comp.os.netware.misc
Article #180Re: DHCP
From: Mike Avery
Date: Mon, 04 Nov 1996 00:00
Date: Mon, 04 Nov 1996 00:00
47 lines
2629 bytes
2629 bytes
In article <327ADA92.5C4B@fastlane.net>, dcollins@fastlane.net says... > INC. LIMNO-TECH wrote: > > > > Is there a DHCP server for NOvell 4.1? (free would be nice) I am > > looking to give our windows machines long term leases for IP numbers, so I > > don't have to reconfigure the IP numbers when we move computers around. > > Take a look at http://support.novell.com/ > > Search on DHCP. That should point to the latest one. > > Myself, am running it on a 4.10 server. It works fine for us. > However, I don't remember the filename. The above site, should point to > the latest... good luck. I've been using it for a while, and it is not without its warts. One of them interacts with Windows95 in strange and wonderful ways. Let's imagine for a moment that you have a local net that uses IP as well as a dial up PPP connection to the Internet on your Windows 95 PC. For one reason or another, you need a specific address on your Windows 95 PC. So you assign it a static address and all is good. Until... You get your local IP address from the Novell DHCP server. Then you dial up your Internet Service Provider, and nothing happens. A bit of checking reveals that everything is going to the local net. You look around and discover the WINIPCFG.EXE program that was bundled with Windows 95 and see that it will let you release your IP configuration. You do so, then load the dialup PPP package, and VIOLA! - you're on the Internet. Sure, you lost the local IP connection, but that's OK for now, you can get it back when you restore the IP connection. So, you disconnect from the dialup network, click on "renew" and.... get the wrong IP address. Somehow the WINIPCFG "release" command causes the Novell DHCP to discard the static address and then assign a new one when you use the "renew" command. In contrast, OnTechnologies DHCP server remembers who is supposed to have which static addresses, and reassigns the same addresses again and again. This may be a bit far fetched for some, but it has happened to me... caveat emptor. Mike
Technical Details
Message-ID:
<MPG.ce7beeb6e89303e98968f@news.pernet.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<55aqan$8bp@boursy.news.erols.com> <327ADA92.5C4B@fastlane.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,bdb244bafbc9c277 X-Google-Attributes: gidfe659,public X-Google-Thread: f8bf7,bdb244bafbc9c277 X-Google-Attributes: gidf8bf7,public From: mavery@pernet.net (Mike Avery) Subject: Re: DHCP Date: 1996/11/04 Message-ID: <MPG.ce7beeb6e89303e98968f@news.pernet.net> X-Deja-AN: 194322103 references: <55aqan$8bp@boursy.news.erols.com> <327ADA92.5C4B@fastlane.net> organization: GTNC newsgroups: comp.os.netware.misc,bit.listserv.novell