Reply to thread

Message

<blockquote data-quote="Rob Timmerman" data-source="post: 96774" data-attributes="member: 172">Re: CL5 and Nuendo LiveThis.&nbsp; Or perhaps better is setting static IPs for all the production equipment and running a DHCP server for your laptop (perhaps on whatever WAP you&#039;re using).Far more frustrating than having to manually set the IP address on your laptop (you know that you can set a fall-back static IP for Windows to use if no DHCP server is found, right?) is having to use Nmap or Wireshark to find a headless server that got it&#039;s DHCP reservation hosed (was *supposed* to have a reservation, but...).Another problem with forcing DHCP in a production environment is that you need a single DHCP server in every system.&nbsp; So now you have a &quot;one of these things is different&quot; problem in your inventory and can&#039;t use your network until the DHCP server is on the network (and this probably also means you can&#039;t just plug directly into a rack for troubleshooting).</blockquote>

[QUOTE="Rob Timmerman, post: 96774, member: 172"] Re: CL5 and Nuendo Live This. Or perhaps better is setting static IPs for all the production equipment and running a DHCP server for your laptop (perhaps on whatever WAP you're using). Far more frustrating than having to manually set the IP address on your laptop (you know that you can set a fall-back static IP for Windows to use if no DHCP server is found, right?) is having to use Nmap or Wireshark to find a headless server that got it's DHCP reservation hosed (was *supposed* to have a reservation, but...). Another problem with forcing DHCP in a production environment is that you need a single DHCP server in every system. So now you have a "one of these things is different" problem in your inventory and can't use your network until the DHCP server is on the network (and this probably also means you can't just plug directly into a rack for troubleshooting). [/QUOTE]

Verification