TCP port 135 (epmap service): NOT LISTENING


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


--
liorz
------------------------------------------------------------------------
liorz's Profile: http://forums.techarena.in/member.php?userid=47574
View this thread: http://forums.techarena.in/showthread.php?t=958043

http://forums.techarena.in

.

Relevant Pages

  • Re: ISA 2004 & companyweb
    ... You cannot access companyweb via http://comanyweb ... By default the Web Listener is listening on the external network adapter. ... Server computer in the selected network". ... Please send the IIS metabase to me for further analysis: ...
    (microsoft.public.windows.server.sbs)
  • Re: Trust Between 2 domain Controllers
    ... Here the netdiag status of the server ripples... ... Testing DNS ... LISTENING ... Binding Paths: ...
    (microsoft.public.win2000.active_directory)
  • share problems
    ... I could not add computers to the domain and I could not access a shared folder on a Windows 2008 Server from Vista and XP 64. ... If I choose diagnose it will say the the computer "is not set up to establish a connection on port "File and printer sharing " with this computer. ... NOT LISTENING ... TCP port 445: ...
    (microsoft.public.windows.server.general)
  • VNC connection closed unexpectedly
    ... BlastWave) running on a test server. ... 23/09/05 19:42:22 Listening for VNC connections on TCP port 5901 ... 23/09/05 19:42:22 Listening for HTTP connections on TCP port 5801 ...
    (comp.unix.solaris)
  • VNC connection closed unexpectedly
    ... BlastWave) running on a test server. ... 23/09/05 19:42:22 Listening for VNC connections on TCP port 5901 ... 23/09/05 19:42:22 Listening for HTTP connections on TCP port 5801 ...
    (comp.sys.sun.admin)