| Author | Messages | |
AFidel
Posts:75
 | | 04/22/2008 4:10 PM |
| When I run a netdiag on one of my DC's I receive the following error:
DC list test . . . . . . . . . . . : Failed
[WARNING] Cannot call DsBind to server.domain (IP_ADDRESS).
[RPC_S_SERVER_UNAVAILABLE]
Everything else but DNS test passes in both netdiag and dcdiag. All of the
RPC tests I can find for this and related errors passes. How do I
determine what is causing the RPC error?
Thanks,
Andrew
| | | |
| bdesmond
Posts:416
| | 04/22/2008 4:35 PM |
| portqry and portqryui is where I usually start with this.
--brian
On Tue, Apr 22, 2008 at 4:07 PM, <AFidel@ddrc.com> wrote:
>
> When I run a netdiag on one of my DC's I receive the following error:
>
> DC list test . . . . . . . . . . . : Failed
> [WARNING] Cannot call DsBind to server.domain (IP_ADDRESS).
> [RPC_S_SERVER_UNAVAILABLE]
>
> Everything else but DNS test passes in both netdiag and dcdiag. All of the
> RPC tests I can find for this and related errors passes. How do I determine
> what is causing the RPC error?
>
> Thanks,
> Andrew
--
Thanks,
Brian Desmond
brian@briandesmond.com
c - 312.731.3132
| | | |
| arun
Posts:24
| | 04/22/2008 4:40 PM |
| I vaguely remember something about a similar bug in NetDiag; not sure about
DCDiag.
Arun K. Iyer
Solutions Director
Sunsson Technologies
arun@sunsson.com
+1.510.402.4550 Office | +1.415.200.9329 Mobile
_____
From: ActiveDir-owner@mail.activedir.org
[mailto:ActiveDir-owner@mail.activedir.org] On Behalf Of AFidel@ddrc.com
Sent: Tuesday, April 22, 2008 1:08 PM
To: activedir@activedir.org
Subject: [ActiveDir] DsBind issue
When I run a netdiag on one of my DC's I receive the following error:
DC list test . . . . . . . . . . . : Failed
[WARNING] Cannot call DsBind to server.domain (IP_ADDRESS).
[RPC_S_SERVER_UNAVAILABLE]
Everything else but DNS test passes in both netdiag and dcdiag. All of the
RPC tests I can find for this and related errors passes. How do I determine
what is causing the RPC error?
Thanks,
Andrew
| | | |
| deji
Posts:150
| | 04/22/2008 4:46 PM |
| Did you do what's mentioned in this document - http://support.microsoft.com/kb/936263 ?
That was a temp fix that a lot of people used on their MS DNS server some few months ago. Many people have forgotten to remove that setting, even after applying the required patch.
Sincerely,
_____
(, / | /) /) /)
/---| (/_ ______ ___// _ // _
) / |_/(__(_) // (_(_)(/_(_(_/(__(/_
(_/ /)
(/
Microsoft MVP - Directory Services
www.akomolafe.com<x-excid://32780000/uri:x-excid:/32770000/uri:http:/www.akomolafe.com> - we know IT
-5.75, -3.23
Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon
From: ActiveDir-owner@mail.activedir.org [mailto:ActiveDir-owner@mail.activedir.org] On Behalf Of Arun K. Iyer
Sent: Tuesday, April 22, 2008 1:34 PM
To: ActiveDir@mail.activedir.org; activedir@activedir.org
Subject: RE: [ActiveDir] DsBind issue
I vaguely remember something about a similar bug in NetDiag; not sure about DCDiag.
Arun K. Iyer
Solutions Director
Sunsson Technologies
arun@sunsson.com<mailto:arun@sunsson.com>
+1.510.402.4550 Office | +1.415.200.9329 Mobile
[cid:image001.gif@01C8A47F.143E7AE0]
________________________________
From: ActiveDir-owner@mail.activedir.org [mailto:ActiveDir-owner@mail.activedir.org] On Behalf Of AFidel@ddrc.com
Sent: Tuesday, April 22, 2008 1:08 PM
To: activedir@activedir.org
Subject: [ActiveDir] DsBind issue
When I run a netdiag on one of my DC's I receive the following error:
DC list test . . . . . . . . . . . : Failed
[WARNING] Cannot call DsBind to server.domain (IP_ADDRESS). [RPC_S_SERVER_UNAVAILABLE]
Everything else but DNS test passes in both netdiag and dcdiag. All of the RPC tests I can find for this and related errors passes. How do I determine what is causing the RPC error?
Thanks,
Andrew
| | | |
| AFidel
Posts:75
| | 04/22/2008 5:01 PM |
| The only unusual output is:
Starting portqry.exe -n <servername> -e 88 -p BOTH ...
Querying target system called:
<servername>
Attempting to resolve name to IP address...
Name resolved to <IP>
querying...
TCP port 88 (kerberos service): LISTENING
UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n <servername> -e 88 -p BOTH exits with return code
0x00000002.
and
Starting portqry.exe -n <servername> -e 138 -p UDP ...
Querying target system called:
<servername>
Attempting to resolve name to IP address...
Name resolved to <IP>
querying...
UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n <servername> -e 138 -p UDP exits with return code
0x00000002.
Non-zero return codes generally indicate a problem but I can't seem to
find the documentation on what they mean for portqry.
Any help would be apreciated!
Thanks,
Andrew
"Brian Desmond" <brian@briandesmond.com>
Sent by: ActiveDir-owner@mail.activedir.org
04/22/2008 04:32 PM
Please respond to
ActiveDir@mail.activedir.org
To
ActiveDir@mail.activedir.org
cc
Subject
Re: [ActiveDir] DsBind issue
portqry and portqryui is where I usually start with this.
--brian
On Tue, Apr 22, 2008 at 4:07 PM, <AFidel@ddrc.com> wrote:
When I run a netdiag on one of my DC's I receive the following error:
DC list test . . . . . . . . . . . : Failed
[WARNING] Cannot call DsBind to server.domain (IP_ADDRESS).
[RPC_S_SERVER_UNAVAILABLE]
Everything else but DNS test passes in both netdiag and dcdiag. All of the
RPC tests I can find for this and related errors passes. How do I
determine what is causing the RPC error?
Thanks,
Andrew
--
Thanks,
Brian Desmond
brian@briandesmond.com
c - 312.731.3132
| | | |
| bsonposh
Posts:180
| | 04/22/2008 5:11 PM |
| Perhaps testing 135 (RPC EndPoint Mapper)
138 is for Netbios
Testing for UDP seems pointless to me 
http://technet.microsoft.com/en-us/library/bb727063.aspx
Thanks!
Unknown Guy w/ Dean
On Tue, Apr 22, 2008 at 4:57 PM, <AFidel@ddrc.com> wrote:
>
> The only unusual output is:
> Starting portqry.exe -n <servername> -e 88 -p BOTH ...
> Querying target system called:
> <servername>
> Attempting to resolve name to IP address...
> Name resolved to <IP>
> querying...
> TCP port 88 (kerberos service): LISTENING
> UDP port 88 (kerberos service): LISTENING or FILTERED
> portqry.exe -n <servername> -e 88 -p BOTH exits with return code
> 0x00000002.
>
> and
>
> Starting portqry.exe -n <servername> -e 138 -p UDP ...
> Querying target system called:
> <servername>
> Attempting to resolve name to IP address...
> Name resolved to <IP>
> querying...
> UDP port 138 (netbios-dgm service): LISTENING or FILTERED
> portqry.exe -n <servername> -e 138 -p UDP exits with return code
> 0x00000002.
>
> Non-zero return codes generally indicate a problem but I can't seem to
> find the documentation on what they mean for portqry.
> Any help would be apreciated!
>
> Thanks,
> Andrew
>
>
> *"Brian Desmond" <brian@briandesmond.com>*
> Sent by: ActiveDir-owner@mail.activedir.org
>
> 04/22/2008 04:32 PM Please respond to
> ActiveDir@mail.activedir.org
>
> To
> ActiveDir@mail.activedir.org cc
> Subject
> Re: [ActiveDir] DsBind issue
>
>
>
>
> portqry and portqryui is where I usually start with this.
>
> --brian
>
> On Tue, Apr 22, 2008 at 4:07 PM, <*AFidel@ddrc.com* <AFidel@ddrc.com>>
> wrote:
>
> When I run a netdiag on one of my DC's I receive the following error:
>
> DC list test . . . . . . . . . . . : Failed
> [WARNING] Cannot call DsBind to server.domain (IP_ADDRESS).
> [RPC_S_SERVER_UNAVAILABLE]
>
> Everything else but DNS test passes in both netdiag and dcdiag. All of the
> RPC tests I can find for this and related errors passes. How do I determine
> what is causing the RPC error?
>
> Thanks,
> Andrew
>
>
>
> --
> Thanks,
> Brian Desmond*
> **brian@briandesmond.com* <brian@briandesmond.com>
>
> c - 312.731.3132
>
| | | |
| bdesmond
Posts:416
| | 04/22/2008 5:11 PM |
| Get network traces on the source and target and see if that traffic is going
through
On Tue, Apr 22, 2008 at 4:57 PM, <AFidel@ddrc.com> wrote:
>
> The only unusual output is:
> Starting portqry.exe -n <servername> -e 88 -p BOTH ...
> Querying target system called:
> <servername>
> Attempting to resolve name to IP address...
> Name resolved to <IP>
> querying...
> TCP port 88 (kerberos service): LISTENING
> UDP port 88 (kerberos service): LISTENING or FILTERED
> portqry.exe -n <servername> -e 88 -p BOTH exits with return code
> 0x00000002.
>
> and
>
> Starting portqry.exe -n <servername> -e 138 -p UDP ...
> Querying target system called:
> <servername>
> Attempting to resolve name to IP address...
> Name resolved to <IP>
> querying...
> UDP port 138 (netbios-dgm service): LISTENING or FILTERED
> portqry.exe -n <servername> -e 138 -p UDP exits with return code
> 0x00000002.
>
> Non-zero return codes generally indicate a problem but I can't seem to
> find the documentation on what they mean for portqry.
> Any help would be apreciated!
>
> Thanks,
> Andrew
>
>
> *"Brian Desmond" <brian@briandesmond.com>*
> Sent by: ActiveDir-owner@mail.activedir.org
>
> 04/22/2008 04:32 PM Please respond to
> ActiveDir@mail.activedir.org
>
> To
> ActiveDir@mail.activedir.org cc
> Subject
> Re: [ActiveDir] DsBind issue
>
>
>
>
> portqry and portqryui is where I usually start with this.
>
> --brian
>
> On Tue, Apr 22, 2008 at 4:07 PM, <*AFidel@ddrc.com* <AFidel@ddrc.com>>
> wrote:
>
> When I run a netdiag on one of my DC's I receive the following error:
>
> DC list test . . . . . . . . . . . : Failed
> [WARNING] Cannot call DsBind to server.domain (IP_ADDRESS).
> [RPC_S_SERVER_UNAVAILABLE]
>
> Everything else but DNS test passes in both netdiag and dcdiag. All of the
> RPC tests I can find for this and related errors passes. How do I determine
> what is causing the RPC error?
>
> Thanks,
> Andrew
>
>
>
> --
> Thanks,
> Brian Desmond*
> **brian@briandesmond.com* <brian@briandesmond.com>
>
> c - 312.731.3132
>
--
Thanks,
Brian Desmond
brian@briandesmond.com
c - 312.731.3132
| | | |
| AFidel
Posts:75
| | 04/22/2008 5:16 PM |
| 135 was fine, I used the Domains and Trusts default from portqryui and
those were the only anomalous results.
Thanks,
Andrew
"Brandon Shell" <tshell@gmail.com>
Sent by: ActiveDir-owner@mail.activedir.org
04/22/2008 05:07 PM
Please respond to
ActiveDir@mail.activedir.org
To
ActiveDir@mail.activedir.org
cc
Subject
Re: [ActiveDir] DsBind issue
Perhaps testing 135 (RPC EndPoint Mapper)
138 is for Netbios
Testing for UDP seems pointless to me
http://technet.microsoft.com/en-us/library/bb727063.aspx
Thanks!
Unknown Guy w/ Dean
On Tue, Apr 22, 2008 at 4:57 PM, <AFidel@ddrc.com> wrote:
The only unusual output is:
Starting portqry.exe -n <servername> -e 88 -p BOTH ...
Querying target system called:
<servername>
Attempting to resolve name to IP address...
Name resolved to <IP>
querying...
TCP port 88 (kerberos service): LISTENING
UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n <servername> -e 88 -p BOTH exits with return code
0x00000002.
and
Starting portqry.exe -n <servername> -e 138 -p UDP ...
Querying target system called:
<servername>
Attempting to resolve name to IP address...
Name resolved to <IP>
querying...
UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n <servername> -e 138 -p UDP exits with return code
0x00000002.
Non-zero return codes generally indicate a problem but I can't seem to
find the documentation on what they mean for portqry.
Any help would be apreciated!
Thanks,
Andrew
"Brian Desmond" <brian@briandesmond.com>
Sent by: ActiveDir-owner@mail.activedir.org
04/22/2008 04:32 PM
Please respond to
ActiveDir@mail.activedir.org
To
ActiveDir@mail.activedir.org
cc
Subject
Re: [ActiveDir] DsBind issue
portqry and portqryui is where I usually start with this.
--brian
On Tue, Apr 22, 2008 at 4:07 PM, <AFidel@ddrc.com> wrote:
When I run a netdiag on one of my DC's I receive the following error:
DC list test . . . . . . . . . . . : Failed
[WARNING] Cannot call DsBind to server.domain (IP_ADDRESS).
[RPC_S_SERVER_UNAVAILABLE]
Everything else but DNS test passes in both netdiag and dcdiag. All of the
RPC tests I can find for this and related errors passes. How do I
determine what is causing the RPC error?
Thanks,
Andrew
--
Thanks,
Brian Desmond
brian@briandesmond.com
c - 312.731.3132
| | | |
| bsonposh
Posts:180
| | 04/22/2008 5:21 PM |
| Got it... As Brian Says... full network capture on both sides would be good,
but I would at least try kerb tcp by itself first. It should not return an
error. The 2 is because of UDP
On Tue, Apr 22, 2008 at 5:11 PM, <AFidel@ddrc.com> wrote:
>
> 135 was fine, I used the Domains and Trusts default from portqryui and
> those were the only anomalous results.
>
> Thanks,
> Andrew
>
>
> *"Brandon Shell" <tshell@gmail.com>*
> Sent by: ActiveDir-owner@mail.activedir.org
>
> 04/22/2008 05:07 PM
> Please respond to
> ActiveDir@mail.activedir.org
>
> To
> ActiveDir@mail.activedir.org cc
> Subject
> Re: [ActiveDir] DsBind issue
>
>
>
>
> Perhaps testing 135 (RPC EndPoint Mapper)
> 138 is for Netbios
>
> Testing for UDP seems pointless to me
>
> *http://technet.microsoft.com/en-us/library/bb727063.aspx*<http://technet.microsoft.com/en-us/library/bb727063.aspx>
> Thanks!
> Unknown Guy w/ Dean
>
> On Tue, Apr 22, 2008 at 4:57 PM, <*AFidel@ddrc.com* <AFidel@ddrc.com>>
> wrote:
>
> The only unusual output is:
> Starting portqry.exe -n <servername> -e 88 -p BOTH ...
> Querying target system called:
> <servername>
> Attempting to resolve name to IP address...
> Name resolved to <IP>
> querying...
> TCP port 88 (kerberos service): LISTENING
> UDP port 88 (kerberos service): LISTENING or FILTERED
> portqry.exe -n <servername> -e 88 -p BOTH exits with return code
> 0x00000002.
>
> and
>
> Starting portqry.exe -n <servername> -e 138 -p UDP ...
> Querying target system called:
> <servername>
> Attempting to resolve name to IP address...
> Name resolved to <IP>
> querying...
> UDP port 138 (netbios-dgm service): LISTENING or FILTERED
> portqry.exe -n <servername> -e 138 -p UDP exits with return code
> 0x00000002.
>
> Non-zero return codes generally indicate a problem but I can't seem to
> find the documentation on what they mean for portqry.
> Any help would be apreciated!
>
> Thanks,
> Andrew
>
> *"Brian Desmond" <**brian@briandesmond.com* <brian@briandesmond.com>*>*
> Sent by: *ActiveDir-owner@mail.activedir.org*<ActiveDir-owner@mail.activedir.org>
>
> 04/22/2008 04:32 PM
> Please respond to*
> **ActiveDir@mail.activedir.org* <ActiveDir@mail.activedir.org>
>
>
> To
> *ActiveDir@mail.activedir.org* <ActiveDir@mail.activedir.org> cc
> Subject
> Re: [ActiveDir] DsBind issue
>
>
>
>
>
> portqry and portqryui is where I usually start with this.
>
> --brian
>
> On Tue, Apr 22, 2008 at 4:07 PM, <*AFidel@ddrc.com* <AFidel@ddrc.com>>
> wrote:
>
> When I run a netdiag on one of my DC's I receive the following error:
>
> DC list test . . . . . . . . . . . : Failed
> [WARNING] Cannot call DsBind to server.domain (IP_ADDRESS).
> [RPC_S_SERVER_UNAVAILABLE]
>
> Everything else but DNS test passes in both netdiag and dcdiag. All of the
> RPC tests I can find for this and related errors passes. How do I determine
> what is causing the RPC error?
>
> Thanks,
> Andrew
>
>
>
> --
> Thanks,
> Brian Desmond*
> **brian@briandesmond.com* <brian@briandesmond.com>
>
> c - 312.731.3132
>
>
| | | |
|
|