Re: Static IP outside of router DHCP range

"VanguardLH" <V@xxxxxxxxx> wrote in message news:h9930n$oh2$1@xxxxxxxxxxxxxxxxxxxx
Smarty wrote:

"VanguardLH" <V@xxxxxxxxx> wrote in message
news:h987jc$ea5$1@xxxxxxxxxxxxxxxxxxxx
Smarty wrote:

The interest in Mac addresses I stated was merely
to explore the ironic fact that each of my 8 media player boxes has a
clearly defined MAC address which my video server "could" use to
facilitate
and stabilize my re-boot problem, yet there is no (apparent) way to take
advantage of them. This would avoid the need for DHCP entirely, whereas
now
each of these 8 devices has to initiate a DHCP, then BootP process which
can
take tens of minutes after a power glitch. I am hoping that fixing the
video
server IP statically will at least avoid the problem of the clients
finding
the server after a server IP address change.

As I recall (been a long time), the clients that use BootP will pull
their code from a configured server. So once you fix to a static IP
address for the server, DHCP isn't involved anymore. Well, it's still
involved for the clients if they are still using DHCP but you could
change them to static IP addresses, too, and complete get rid of DHCP.
However, I don't think DHCP is what is taking so long. Do the clients
actually still want to use BootP to get an IP address assigned to them
if they were also using a static IP address? Unless you actually need
DHCP from the router, you could turn it off in the router and use static
IP addresses for all your hosts. With them all using static IP
addresses, none of them would need to use DHCP and probably not BootP.

Unfortunately my 8 clients are little $50 boxes with an Ethernet port and
yellow, red, and white outputs for composite NTSC video and stereo audio,
but no provisions whatsoever to flash their NVRAM. I think they are actually
PROM'ed with soldered-in firmware, and they have no ability to have static
IP assignments in their boot code. My 8 boxes have the so-called "Rev 1.0"
boot ROM which makes them the least capable of all the ones which Hauppage
offers. They are vintage-1995 hardware.

So I have no way to either reserve IP addresses based on Mac addresses,

To have your router use a table of fixed IP addresses that its DHCP
server will assign to specific MAC addresses, it looks like you'll need
a new router (or some other host running a more capable DHCP server).

Assignment of IP address by MAC address was a handy feature in my old
D-Link router. I didn't have to do anything regarding TCP/IP changes on
my hosts but I could fix an IP address to specific hosts by my router's
DHCP server. When the D-Link died (which seems typical of them at the
3-year interval), I got a Linksys which was missing this IP-to-MAC
feature. This forced me to configure my hosts to static IP addresses
rather than always getting the same one from the router's DHCP server.
It was more convenient doing the IP mapping from the router.

I only got the Linksys because I needed an immediate replacement when
the D-Link died (it first went flaky regarding connectivity and then
eventually wouldn't permit any connections; it was a known heat bug with
that model). The Linksys was available in a retail store so I could
replace it in an hour. However, even if they had the better models of
Linksys, they still were missing the IP-to-MAC feature. Even the
low-end Netgear RP614 has their "Address Reservation" feature to assign
a specific IP address to a MAC address.


I am still committed to using this Linksys router, since it is the only router I have found which is rock solid despite a lot of network and wireless devices I use here. I presently have 25 nodes on this network, and it does a great job except for this specific reboot issue I have been posting here, not really a router flaw. I have been through a lot of other stuff here including so-called MoCa routers for use with coax and FIOS, specifically the Actiontec, along with Apple and D-Link models, so this Linksys will stay a keeper... (until it dies)...

.

Relevant Pages

  • Re: SBS 2003 Misconfigured?
    ... I've thrown quite a bit at them, and just have to disagree that they are inherently less secure than the netgear. ... setup DHCP and I have also gone in and manually created a new scope ... when I first used the Netgear router with SBS 2003, ... than one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... Yeah, maybe it's not that different from the Netgear, for all that. ... that when I first used the Netgear router with SBS 2003, ... tech spend 4+ hours on my system, and then tell me to enable DHCP ... more than one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I configure SBS 2003 as a DHCP server?
    ... To disable the private "LAN" side DHCP service (not the DHCP service on the ... of the PPPoE adapter and enable your Speedstream as a DSL modem and router. ... For the Vista computer to interact with SBS, ... Windows Small Business Server 2003: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... OK, yes, I've struck a router which would only allow DHCP clients access to ... no internet connection from the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... setup DHCP and I have also gone in and manually created a new scope ... when I first used the Netgear router with SBS 2003, ... one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
Loading