Event ID 9176 and 9074

Shutdown the Exchange ... Restart the DC and then up the Exchange and check

- Rancy

Done that, shut down both servers brought up the DC and waited for it to come all the way up, then I started up the exchange server....still got the same event id's on the exchange server....there are no error events on the DC.

If you go to add a new outlook account it will pull up your login name and email address,

If you hit next it will come up and say the connection to Microsoft Exchange is unavailable.

The only errors on the exchange server are 9176, 9074.

Really stumped.

The domain controller also has teamed network cards, do you think if I dissolve the team on the DC would help....grabbing at straws here.

Can you please share a description of that error .... was there some DC that dies or wasnt gracefully removed ?

Can you share event 2080 from the Exchange and run EXBPA to check all is fine

- Rancy

On this domain it has always only been the one DC (named Fender) and the one exchange server (named mail1).  All of this problem started after teaming the network cards in the exchange server....the server fender has always been the GC...it is the only game in town.

I have run best practices and everything looks ok.

Below are the errors from event viewer.

NSPI Proxy can contact Global Catalog Fender.ccso.local but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients.  Reboot Fender.ccso.local as soon as possible.

The Directory Service Referral interface failed to service a client request. RFRI is returning the error code:[0x3f0].

Is the Ipv6 enabled or disabled on the Exchange server ?
Is the remote registry service running ?
Test-serviceHealth (run the command from Exchange shell)

- Rancy

IP6 is disabled.  Remote registry service is running.

I ran the service health and all looked like it was running....I have attached a PIC of the output.



I am going to have to step away from the office for a little bit...If I get back in time I will chime back in....if not I will respond tomorrow.

We get mail, we can send mail, it is just getting outlook setup for users that have not sat at that specific PC will not work....I will work fine at my desk but if I move to a desk that I have not used outlook on before it will not setup.
exchange1.PNG
outlook1.PNG

Just try to enable IPv6 and restart the server of just the Exchange services all of them and check

- Rancy

I enabled IPv6 and restarted, same result.  I enabled IP6 on the DC, shut down the email server, then shut down the DC....restarted the DC waited for it to wake up, then started the mail server again....same result.

Went and made sure both are pached and updated

I am thinking it might come down to one of two problems, in pic3 it says the referral interface cannot contact any GC that supports the NSPI service.....I screwed with the nic's by teaming them...could this be why the "interface" can't talk to the GC.

and/or

In pics 2&4 it is talking about the nspi proxy can talk to the GC but it does not support nspi...could this service be screwed up?  or in pic 4 it says nspi proxy cannot contact any GC that supports the nspi...new clients will be refused until a GC is available.

This is what is happening new clients can't be setup...so I am thinking that the communication to the GC is screwed because I teamed the nic's and un-teaming them left something behind....or the nspi service on the GC is not doing what it is suppose to do (this one I kind of doubt as it started after screwing with the nics on the mail server.

Please help.....really stuck on this one.
exchange2.PNG
exchange3.PNG
exchange4.PNG

Is the time in sycn with DC and Exchange ?
What is the number of NIC's on Exchange\DC at this time and their Binding order

- Rancy

Right now I only have one nic enabled on the exchange server, and it is at the top of the binding order....this is only because I was playing with different things...I have been trying everything here lately.

The number of nics on the exchange server is 4, but right now only one is enabled, and it is listed at the top of the binding order....refer to pic titled mail1nic

There are 6 nics in the DC and they are setup into two teams, those teams have a entry as well called team1 and team2, both teams are on the same network, with identical settings except for the IP address, one is set for 192.168.0.8, the other .9.....refer to pic dcnic to see.

There is another DC that is going to go online, but that has been put on hold till this problem can get figured out.

Thanks again for all your help....and you get to work too early as well :)
mail1nic.PNG
DCnic.PNG

I forgot...the times are spot on.

I havent ever seen and why are we having Teaming of NIC's on DC ?

- Rancy

I figured for load balancing and fail over.....we had one switch go south on us not too long ago, and with a teamed arrangement I figured if I lost a switch or something the DC would still be available.

For testing I have dissolved the teams on the DC and only have two nics enabled, one plugged into one switch and one plugged into another.

Also there is only one nic enabled on the exchange server at this time.

I restarted the exchange server and am still having problems.

I saved off the old logs upon reboot on the exchange server with one nic talking to a DC with two nics I get these errors...the pic called error 6 is given several times.

Again I want to thank you for your help.
error1.PNG
error2.PNG
error3.PNG
error4.PNG
error5.PNG
error6.PNG

It ended up being a driver issue....you could make the selection it would look like it took it but it really did not....I guess the key here is to double check everything by opening it up again.