We've run into a seriously odd issue on one of our Exchange Servers (Windows 2003 R2 SP2, Exchange 2003). We'd started having some network connectivity issues on the machine, so had set most services, including the Information Store and MTA to manual, and the then rebooted. What we noticed is that, when we started IS, it pretty much stopped our network connection cold. We were still pingable, but 0 packets going in or out. At the same time, the CPU spiked to 60+%. Stopped IS, and our connectivity came back and the CPU calmed down. I've never seen anything like this before, and a few hours of searching online haven't uncovered anything. Anyone ever run into an issue like this?

Getting anything logged? The event log is a good place to start. If you don't have anything you should increase logging and then see what might be happening. Have you looked at the queues? You're a little light on information here. "RobertAkiraWatts" wrote in message news:39bede47-c83d-48c7-84d4-83abc81828c6... We've run into a seriously odd issue on one of our Exchange Servers (Windows 2003 R2 SP2, Exchange 2003). We'd started having some network connectivity issues on the machine, so had set most services, including the Information Store and MTA to manual, and the then rebooted. What we noticed is that, when we started IS, it pretty much stopped our network connection cold. We were still pingable, but 0 packets going in or out. At the same time, the CPU spiked to 60+%. Stopped IS, and our connectivity came back and the CPU calmed down. I've never seen anything like this before, and a few hours of searching online haven't uncovered anything. Anyone ever run into an issue like this?Mark Arnold, Exchange MVP.