<div>
<div class="content wysiwyg-content">
Hello<br />
<br />
We have a customer running Windows 2003 R2 behind a Cisco Pic 501. The server is a fairly new install but over the past few days we've had a few calls where users can log onto pc's but can't access their network drives, getting 169.... IP addresses. I've noticed the following error constantly in Event Viewer<br />
<br />
Event ID<br />
An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.<br />
<br />
It seems that DHCP stops on server but services still say started. This would explain the clients not being able to access the network. I mentioned the PIX earlier because it seems there was an issue last week where all users couldn't access the network and restarting the PIX resolved. <br />
<br />
I was wondering if anyone knew if the error mentioned above would be caused by either the DHCP service craching, possibly caused by the PIX handing out addresses. Haven't had a chance to get access to PIX as we need someone to go onsite and plug into it's console.<br />
<br />
I've ran chkdsk and other things other people have suggested in previous questions.<br />
Thanks in Advance<br />
Matt<br />
OCD
</div>
</div>


Hello

We have a customer running Windows 2003 R2 behind a Cisco Pic 501. The server is a fairly new install but over the past few days we've had a few calls where users can log onto pc's but can't access their network drives, getting 169.... IP addresses. I've noticed the following error constantly in Event Viewer

Event ID
An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.

It seems that DHCP stops on server but services still say started. This would explain the clients not being able to access the network. I mentioned the PIX earlier because it seems there was an issue last week where all users couldn't access the network and restarting the PIX resolved. 

I was wondering if anyone knew if the error mentioned above would be caused by either the DHCP service craching, possibly caused by the PIX handing out addresses. Haven't had a chance to get access to PIX as we need someone to go onsite and plug into it's console.

I've ran chkdsk and other things other people have suggested in previous questions.
Thanks in Advance
Matt
OCD

Event ID 333. Application Pop up. DHCP stops

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Cisco PIX is a dedicated hardware firewall appliance; the Cisco Adaptive Security Appliance (ASA) is a firewall and anti-malware security appliance that provides unified threat management and protection the PIX does not. Other Cisco devices and systems include routers, switches, storage networking, wireless and the software and hardware for PIX Firewall Manager (PFM), PIX Device Manager (PDM) and Adaptive Security Device Manager (ASDM).