Basically, my domain is just filling up with this specific error (and a few others) everywhere:
Active directory replication monitor (Replication Failure: The reason is: Logon failure: unknown username or bad password)
when transferring the schema role:
the transfer of the operations master role cannot be performed because: The requested FSMO operation failed. The current FSMO holder could not be contacted
Application Event log (eventID: 1000, Userenv, Windows cannot determine the user or computer name. return value (1326))
and when i do a "netstat -n" in a command prompt i get:
TCP 192.168.1.43:4648 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4649 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4823 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4824 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4828 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4829 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4836 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4837 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4838 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4839 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4869 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4870 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4872 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4873 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4874 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4875 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4887 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4888 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4918 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4919 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4927 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4928 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4929 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4930 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4931 192.168.1.43:389 CLOSE_WAIT
TCP 192.168.1.43:4932 192.168.1.43:389 CLOSE_WAIT
I have a feeling some of them are not related problems.
NTDS general , Event ID: 1126, Unable to establish connection with global catalog
another piece of information that may be useful: the last successful replication occurred back in february, and it is now July!!
I've tried many things, i found some posts saying it was their backup, or user logged on, or something that doesn't make sense.
OMG Please somebody Help!