Results 1 to 4 of 4

Thread: TCP port 135 (epmap service): NOT LISTENING

  1. #1
    Join Date
    Apr 2008
    Posts
    5

    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

  2. #2
    Meinolf Weber Guest

    Re: TCP port 135 (epmap service): NOT LISTENING

    Hello liorz,

    Please post annunedited ipconfig /all from all DC/DNS servers. Also post
    an complete dcidag and netdiag output from the error machine.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

    > 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
    >
    > http://forums.techarena.in
    >




  3. #3
    Join Date
    Apr 2008
    Posts
    5
    Thanks Meinolf.
    attached the files as is - no change. the bad machine name is apollo.
    another symptom - i CAN'T PING other hosts nor DC's nor external addresses from the problem machine (i get resolve error), but i get correct response while using nslookup to resolve them.


    thanks
    Lior

  4. #4
    Meinolf Weber Guest

    Re: TCP port 135 (epmap service): NOT LISTENING

    Hello liorz,

    Sorry, BUT even if i could see a file, i will NEVER download it!!! Post the
    output here as text as anybody will do.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

    > Thanks Meinolf.
    > attached the files as is - no change. the bad machine name is apollo.
    > another symptom - i _CAN'T_PING_ other hosts nor DC's nor external
    > addresses from the problem machine (i get resolve error), but i get
    > *correct respons*e while using *nslookup *to resolve them.
    > thanks
    > Lior
    > +-------------------------------------------------------------------+
    > |Filename: Apollo.rar |
    > |Download:
    > http://forums.techarena.in/attachment.php?attachmentid=6608|
    > +-------------------------------------------------------------------+
    >
    > http://forums.techarena.in
    >




Similar Threads

  1. XP Port 3389 Not Listening
    By Harnoor in forum Networking & Security
    Replies: 6
    Last Post: 30-12-2010, 10:51 PM
  2. When Listening port vs Proxy SOCKS port are used?
    By rooki in forum Windows Software
    Replies: 3
    Last Post: 24-06-2010, 04:05 PM
  3. Port Not Listening
    By Thomas R Grassi Jr in forum Windows Server Help
    Replies: 4
    Last Post: 13-12-2008, 03:47 PM
  4. DNS listening port?
    By mcRon in forum Windows Server Help
    Replies: 5
    Last Post: 07-11-2008, 04:15 PM
  5. Port 135/Epmap connections
    By Adnank5 in forum Windows Server Help
    Replies: 1
    Last Post: 16-05-2007, 03:25 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,966,259.07934 seconds with 17 queries