• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 442
  • Last Modified:

Network Connections Service & Exchange 2007

Hi everyone,

Got a brand new exchange 2007 sever installed on Windows Server 2008 SP2 x64. For some reason the network connections service, telephone and a few other services fail to start when the server is booted. It works in safe mode with networking support and the very other strange thing is if i uninstall the nic with device manager and reboot it installs and starts to work! I've tried disabling all no-microsoft services with msconfig. its also hosted a vsphearv4 both the e1000 and vmxnet have the same problem.

I've  gone thru this kb: http://support.microsoft.com/kb/825826 with no sucess

I've open a case with MPSS and they have not found a solution yet....
0
KevinA123
Asked:
KevinA123
  • 8
  • 6
1 Solution
 
grantsewellCommented:
When the system starts and the services fail, what is posted in the event log?
0
 
KevinA123Author Commented:
nothing posted in the event logs (sys or app) at all regarding the failing services, just two around exchange DS access and information store fails to start in system and the app log is filled with mstopology errors as.... very odd

also the box can ping in and out and resolve DNS. but the network is shown disconnected in the task bar. and can't be managed. I do get an good ipconfig too.
0
 
grantsewellCommented:
Have you updated the drivers for the NIC? Safe Mode would load generic drivers and removing it would naturally not need to load them as well. It could also be bad hardware.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
KevinA123Author Commented:
Nic drivers are vmware latest, tools. I've uninstalled and reinstalled them. It also has the same problem booth when using the e1000 and vmxnet nics so its no a single driver problem.
0
 
KevinA123Author Commented:
also around hardware, all the other virtual machines on the same box seam to work without issue.
0
 
KevinA123Author Commented:
I've also looked at this blog post,

http://mostlyexchange.blogspot.com/2007/02/network-connections-service-starting.html

But i have not touched the policy around Impersonate a client after authentication
0
 
grantsewellCommented:
So, when you uninstall in DM, and it works, does it stop working later?

Have you looked at this KB? http://support.microsoft.com/kb/825826
0
 
KevinA123Author Commented:
I remove from DM and then reboot it works.

Another oddity is when the server is left alone for hours like 12 it just starts working again.....

I have gone thru that KB on this server.
0
 
grantsewellCommented:
So... does it stop working later after it starts? This really sounds like a driver issue. If you uninstall, it's going to use Windows default drivers when it boots.
0
 
KevinA123Author Commented:
it never starts; but if the NIC is uninstalled and the server boots it works fine till the next restart where it stops working.
0
 
grantsewellCommented:
So the VMWare drivers work fine on other MS 2008 R2 x64 machines?
0
 
KevinA123Author Commented:
yup,
0
 
grantsewellCommented:
If it works with Microsoft Generic drivers - use them! Otherwise there might be something inherently wrong with the OS install. You could try using legacy vSwitch VMkernel NICs as an alternative, but it's not your best option.

After uninstalling, check to see which drivers are being selected and be sure those are the ones being used. Verify the drivers on your working systems, and try those exact versions. The fact that it can ping in and out but can't be managed shows that the OS can't properly communicate with the device - that's what a driver does, it's a driver issue.

You said Win2k8 SP2 x64 - make sure the systems are exactly the same. Don't get confused with Win2k8 R2 x64, these systems operate differently sometimes, especially with driver installs. Be sure to use "Run as Administrator" if you have UAC enabled and are still going to try using third-party drivers.

The topology errors you're receiving are most likely related, since the system can't contact a GC to update and receive topology.

This is the best I've got, I'm out of ideas. Good luck!
0
 
KevinA123Author Commented:
Thanks Grant, I will try. But I may be on to rebuilding the OS install. microosft pss just recommended the same to me on the phone. Now i have another problem....
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now