- From: "Craft, Steve" <SCraft@xxxxxxxxxxx>
- To: "'isalist@xxxxxxxxxxxxx'" <isalist@xxxxxxxxxxxxx>
- Date: Fri, 3 May 2002 11:39:56 -0400
In setting up an ISA system for a branch office, the external interface is on DHCP. Sometimes, the DHCP service/driver can't get a proper corporate IP number, so it reverts to 169.xxx.xxx.xxx. Of course then the ISA services choke, and no one on the internal network can get back to the main office until the machine is rebooted - asking for an ipconfig /release /renew combo never lets it get past the router, but a reboot always fixes it. Is there a way to trap for that to make the machine forcibly reboot? It's not like the ISA services don't start, so I can't make Win2K reboot on their "error"; it's that they don't really have connectivity. All help would be appreciated. Thanks.
Other related posts:
- » DHCP Issue
- » Re: DHCP Issue