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
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
>
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
>
