Most systems that use DHCP to obtain their IP address will be affected by this and will not be able to connect to the network after reboot or lengthy disconnection from the network.
Systems that use DHCP but have already obtained an address may be able to stay on the network during this service malfunction – this depends on how individual systems are configured. Systems that do not rely upon DHCP (statically configured hostnames/addresses) should be unaffected by this problem.
Staff are looking into the cause of this problem.
UPDATE
[2008-05-30 01:21:52 | Jon Kuroda]
DHCP service was restored late Thursday evening via a temporary fix around 11:30PM. However, it appears that there are still problems with obtaining DHCP leases for many systems.
Staff are still looking into the problem and into a more permanent solution.
UPDATE
[2008-05-30 09:42:54 | Jon Kuroda]
An attempt at around 8:15am this morning to revert to an earlier version of the DHCP software as a more permanent solution to last night’s DHCP service outage proved unsuccessful.
Last night’s temporary fix was put back into place at 8:45am and DHCP service was restored.
Staff are still looking into the cause and for a more permanent solution.
Also, apologies for the confusing dates on the previous update(s)
Resolved as of 2008-05-30 09:44:00