Hi guys
I must say i nearly gave up...
last try. counting on someone here.
i have a problem in my DC 2003-SP2. it think it started after applying SP2 a week ago.
it was first discovered by failing to log into DHCP mmc on that server (red x shown), although clients CAN register in DHCP!!! then i found that WINS also has red x mark (but availiable as well).
then i ran dcdiag and found lot's of errors which i believe i repaired most of them - except replication problems.
i still have few errors when running dcdiag and netdiag but i have reason to believe that they are all related to the main fact that my server simply doesn't listen to port 135, meaning no netbios/rpc/epmam whatsoever
when i run LOCALY portqry -n server -e 135 on my local DC it fails with
TCP port 135 (epmap service): NOT LISTENING
when i run it on all other remote DCs it is successful!
all services (rpc, netlogon, server' workstation, browser) are up and running.
and of course i can't move FSMO to another server...
i already change maxthreads and some other keys in tregistry. also rebooted the server nearly hundred time..
I'll appreciate any help
one last thing - i think i've read most of MS KB on how to troubleshoot blabla. they actually don't offer any solution...
thanks
LZ
Bookmarks