Has anyone experienced any proplems with using PROSet and Windows 2003, I am experiencing event id 22 and 13 source iANSMiniport also eventid 1053 source Userenv on member servers in a domain. The DC's are also 2003 and it is a completely new build. Any ideas would be great before I commit to...
I would be inclined to agree with acl03, however there is a quite good article about placement of fsmo roles dependent on your infrastructure here: http://support.microsoft.com/default.aspx?scid=kb;en-us;223346
Hope this helps
There are no more endpoints available from the endpoint mapper."
Has anyone experienced this error and got to the bottom of the problem?
I am experiencing this problem on the DC on the domain that holds the FSMO roles and eventually the domain grinds to a halt and the only cure is to down all...
Has anyone experienced this problem with single processor machines? I have 3 servers all experiencing this problem on a gigabit backbone running SP3 for contract reasons. Is it something that SP4 would fix?
Thanks SilviaS I will check out the netlogon aspect as that would make sense although I not sure that is definitely it.
Mikesid, I don't think that it is the password as the services start manually after the boot up of the server.
Very confused. If server is rebooted exchange fails to start as the services fail, but if they are then started manually then they start!!
The exchange server is the only DC and there is a message in the event log that it is unable to contact any DC's in the domain?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.