rpc servser not available Taz1972 12/21/2008 7:56:01 PM Hi, I recently created a new subdomain for my company. The creation part of the subdomain went fine, but now when I attempt to connect to the DC of the new subdomain I get the following message: error 1722 rpc service not available My root domain has an internal address range of 172.x.x.x and the subdomain is 192.168.x.x. I can ping both the hostname and ip address of any machine FROM the subdomian to the root domain, but I can only ping the ip address and not the hostname when pinging TO the subdomain. This is most likely a dns configuration issue, but I'm not sure how to solve it. The subdomain is also on a different site, and it is setup to be AD integrated. I setup the subdomain according to these instructions: http://support.microsoft.com/kb/255248 http://technet.microsoft.com/en-us/library/cc780951.aspx http://technet.microsoft.com/en-us/library/cc787706.aspx I checked the rpc/rpc locator services on both sides and they seem fine. I also get the above error when trying to do a replication in AD sites and servcies. I set the subdomain DC to point to itself for dns, and added the root domains internal dns server as a forwarder. We also have some external dns servers but I haven't set these anywhere in the configuration - is this needed? There are also a bunch of AD errors in the event log saying that the root dns server refuses connection from the subdomain for replication. This is kind of urgent so any advise will be appreciated! Thanks, Taz

Re: rpc servser not available "Florian Frommherz [MVP]" <florian[ at ]frickelsoft.DELETETHIS.net> 12/22/2008 6:38:39 AM Howdie! Taz1972 wrote: [Quoted Text] > I recently created a new subdomain for my company. The creation part of the > subdomain went fine, but now when I attempt to connect to the DC of the new > subdomain I get the following message: > > error 1722 rpc service not available Have you restored a backup of one of the domains or were those disconnected for a while? If so, check with netdom et. al. if the trust password between the two domains is still accurate. Have you checked whether the domains are healthy (use netdiag and dcdiag)? > I set the subdomain DC to point to itself for dns, and added the root > domains internal dns server as a forwarder. We also have some external dns > servers but I haven't set these anywhere in the configuration - is this > needed? Not needed - you should have to forwarders - one explicitly for the root domain (parent domain) so that queries go there and one for all other DNS requests. > There are also a bunch of AD errors in the event log saying that the root > dns server refuses connection from the subdomain for replication. What error messages are those? Can you confirm with eventid.net? cheers, Florian -- Microsoft MVP - Group Policy eMail: prename [at] frickelsoft [dot] net. blog: http://www.frickelsoft.net/blog. Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste

Re: rpc servser not available "Paul Bergson" <pbbergs[ at ]nospammsn.com> 12/22/2008 1:38:54 PM What are the exact errors you are getting? "There are also a bunch of AD errors in the event log saying that the root dns server refuses connection from the subdomain for replication." Are the high ports being blocked going either way? This is common, since RPC uses high ports. You may have DNS setup correctly but errors created by firewall issues could easily be the problem. Check out an article I have on Firewall Ports Needed for Replication at: http://www.pbbergs.com/windows/articles.htm Run portqryui from both sides of the domain and see what specifically is going on. -- Paul Bergson MVP - Directory Services MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, 2003, 2000 (Early Achiever), NT4 http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message news:47C3A2CE-6B9E-4E83-9A4B-D36538555D52[ at ]microsoft.com... [Quoted Text] > Hi, > > I recently created a new subdomain for my company. The creation part of > the > subdomain went fine, but now when I attempt to connect to the DC of the > new > subdomain I get the following message: > > error 1722 rpc service not available > > My root domain has an internal address range of 172.x.x.x and the > subdomain > is 192.168.x.x. > > I can ping both the hostname and ip address of any machine FROM the > subdomian to the root domain, but I can only ping the ip address and not > the > hostname when pinging TO the subdomain. This is most likely a dns > configuration issue, but I'm not sure how to solve it. The subdomain is > also > on a different site, and it is setup to be AD integrated. > > I setup the subdomain according to these instructions: > > http://support.microsoft.com/kb/255248 > > http://technet.microsoft.com/en-us/library/cc780951.aspx > > http://technet.microsoft.com/en-us/library/cc787706.aspx > > I checked the rpc/rpc locator services on both sides and they seem fine. I > also get the above error when trying to do a replication in AD sites and > servcies. > > I set the subdomain DC to point to itself for dns, and added the root > domains internal dns server as a forwarder. We also have some external dns > servers but I haven't set these anywhere in the configuration - is this > needed? > > There are also a bunch of AD errors in the event log saying that the root > dns server refuses connection from the subdomain for replication. > > This is kind of urgent so any advise will be appreciated! > > Thanks, > Taz > >

Re: rpc servser not available Taz1972 12/24/2008 9:01:00 PM Here is the result of a dcdiag: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: <site>\<server> Starting test: Connectivity ......................... <server> passed test Connectivity Doing primary tests Testing server: <site>\<server> Starting test: Replications [Replications Check,<server>] A recent replication attempt failed: From MAIL to FJBVDC1 Naming Context: DC=ForestDnsZones,DC=<domain>,DC=local The replication generated an error (1256): The remote system is not available. For information about network tr oubleshooting, see Windows Help. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:45:44. 7 failures have occurred since the last success. [Replications Check,<server>] A recent replication attempt failed: From MAIL to <server> Naming Context: CN=Schema,CN=Configuration,DC=fugro-jason,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 07:47:34. The last success occurred at 2008-12-22 15:45:43. 6 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. fugro-jason.local is not registered on one or more DNS servers. [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: CN=Configuration,DC=<domain>,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:56:47. 10 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. fugro-jason.local is not registered on one or more DNS servers. REPLICATION-RECEIVED LATENCY WARNING <server>: Current time is 2008-12-23 16:00:19. DC=ForestDnsZones,DC=fugro-jason,DC=local Last replication recieved from <server> at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:44. Last replication recieved from DC2 at 2008-12-22 15:29:38. Last replication recieved from DC3 at 2008-12-22 15:19:50. Last replication recieved from DC4 at 2008-12-22 15:44:37. CN=Schema,CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:43. Last replication recieved from DC2 at 2008-12-22 15:45:44. Last replication recieved from DC3 at 2008-12-22 15:44:36. Last replication recieved from DC4 at 2008-12-22 15:29:37. Last replication recieved from DC5 at 2008-12-22 15:19:50. Last replication recieved from DC6 at 2008-12-22 15:44:36. CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:19:57. Last replication recieved from DC at 2008-12-22 15:56:47. Last replication recieved from DC2 at 2008-12-22 15:58:25. Last replication recieved from DC3 at 2008-12-22 15:44:32. Last replication recieved from DC4 at 2008-12-22 15:29:32. Last replication recieved from DC5 at 2008-12-22 15:20:23. Last replication recieved from DC6 at 2008-12-22 15:44:34. ......................... <server> passed test Replications Starting test: NCSecDesc ......................... <server> passed test NCSecDesc Starting test: NetLogons * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test NetLogons Starting test: Advertising ......................... <server> passed test Advertising Starting test: KnowsOfRoleHolders ......................... <server> passed test KnowsOfRoleHolders Starting test: RidManager ......................... <server> passed test RidManager Starting test: MachineAccount Could not open pipe with [<server>]:failed with 1219: Multiple connectio ns to a server or shared resource by the same user, using more than one user nam e, are not allowed. Disconnect all previous connections to the server or shared resource and try again. Could not get NetBIOSDomainName Failed can not test for HOST SPN Failed can not test for HOST SPN * Missing SPN :(null) * Missing SPN :(null) ......................... <server> failed test MachineAccount Starting test: Services Could not open Remote ipc to [<server>]:failed with 1219: Multiple conne ctions to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or sha red resource and try again. ......................... <server> failed test Services Starting test: ObjectsReplicated ......................... <server> passed test ObjectsReplicated Starting test: frssysvol * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test frssysvol Starting test: frsevent ......................... <server> failed test frsevent Starting test: kccevent Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test kccevent Starting test: systemlog Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test systemlog Starting test: VerifyReferences ......................... <server> passed test VerifyReferences Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : <site> Starting test: CrossRefValidation ......................... <site> passed test CrossRefValidation Starting test: CheckSDRefDom ......................... <site> passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running enterprise tests on : <domain.local> Starting test: Intersite ......................... <domain.local> passed test Intersite Starting test: FsmoCheck ......................... <domain.local> passed test FsmoCheck Hope this gives more info in solving this issue for me. Thanks, Taz "Paul Bergson" wrote: [Quoted Text] > What are the exact errors you are getting? > > "There are also a bunch of AD errors in the event log saying that the root > dns server refuses connection from the subdomain for replication." > > > > Are the high ports being blocked going either way? This is common, since RPC > uses high ports. You may have DNS setup correctly but errors created by > firewall issues could easily be the problem. > Check out an article I have on Firewall Ports Needed for Replication at: > http://www.pbbergs.com/windows/articles.htm > > Run portqryui from both sides of the domain and see what specifically is > going on. > > -- > Paul Bergson > MVP - Directory Services > MCTS, MCT, MCSE, MCSA, Security+, BS CSci > 2008, 2003, 2000 (Early Achiever), NT4 > > http://www.pbbergs.com > > Please no e-mails, any questions should be posted in the NewsGroup This > posting is provided "AS IS" with no warranties, and confers no rights. > "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message > news:47C3A2CE-6B9E-4E83-9A4B-D36538555D52[ at ]microsoft.com... > > Hi, > > > > I recently created a new subdomain for my company. The creation part of > > the > > subdomain went fine, but now when I attempt to connect to the DC of the > > new > > subdomain I get the following message: > > > > error 1722 rpc service not available > > > > My root domain has an internal address range of 172.x.x.x and the > > subdomain > > is 192.168.x.x. > > > > I can ping both the hostname and ip address of any machine FROM the > > subdomian to the root domain, but I can only ping the ip address and not > > the > > hostname when pinging TO the subdomain. This is most likely a dns > > configuration issue, but I'm not sure how to solve it. The subdomain is > > also > > on a different site, and it is setup to be AD integrated. > > > > I setup the subdomain according to these instructions: > > > > http://support.microsoft.com/kb/255248 > > > > http://technet.microsoft.com/en-us/library/cc780951.aspx > > > > http://technet.microsoft.com/en-us/library/cc787706.aspx > > > > I checked the rpc/rpc locator services on both sides and they seem fine. I > > also get the above error when trying to do a replication in AD sites and > > servcies. > > > > I set the subdomain DC to point to itself for dns, and added the root > > domains internal dns server as a forwarder. We also have some external dns > > servers but I haven't set these anywhere in the configuration - is this > > needed? > > > > There are also a bunch of AD errors in the event log saying that the root > > dns server refuses connection from the subdomain for replication. > > > > This is kind of urgent so any advise will be appreciated! > > > > Thanks, > > Taz > > > > >

Re: rpc servser not available Taz1972 12/24/2008 9:19:01 PM FRom dcdiag: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: <site>\<server> Starting test: Connectivity ......................... <server> passed test Connectivity Doing primary tests Testing server: <site>\<server> Starting test: Replications [Replications Check,<server>] A recent replication attempt failed: From MAIL to FJBVDC1 Naming Context: DC=ForestDnsZones,DC=<domain>,DC=local The replication generated an error (1256): The remote system is not available. For information about network tr oubleshooting, see Windows Help. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:45:44. 7 failures have occurred since the last success. [Replications Check,<server>] A recent replication attempt failed: From MAIL to <server> Naming Context: CN=Schema,CN=Configuration,DC=fugro-jason,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 07:47:34. The last success occurred at 2008-12-22 15:45:43. 6 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. fugro-jason.local is not registered on one or more DNS servers. [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: CN=Configuration,DC=<domain>,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:56:47. 10 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. fugro-jason.local is not registered on one or more DNS servers. REPLICATION-RECEIVED LATENCY WARNING <server>: Current time is 2008-12-23 16:00:19. DC=ForestDnsZones,DC=fugro-jason,DC=local Last replication recieved from <server> at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:44. Last replication recieved from DC2 at 2008-12-22 15:29:38. Last replication recieved from DC3 at 2008-12-22 15:19:50. Last replication recieved from DC4 at 2008-12-22 15:44:37. CN=Schema,CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:43. Last replication recieved from DC2 at 2008-12-22 15:45:44. Last replication recieved from DC3 at 2008-12-22 15:44:36. Last replication recieved from DC4 at 2008-12-22 15:29:37. Last replication recieved from DC5 at 2008-12-22 15:19:50. Last replication recieved from DC6 at 2008-12-22 15:44:36. CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:19:57. Last replication recieved from DC at 2008-12-22 15:56:47. Last replication recieved from DC2 at 2008-12-22 15:58:25. Last replication recieved from DC3 at 2008-12-22 15:44:32. Last replication recieved from DC4 at 2008-12-22 15:29:32. Last replication recieved from DC5 at 2008-12-22 15:20:23. Last replication recieved from DC6 at 2008-12-22 15:44:34. ......................... <server> passed test Replications Starting test: NCSecDesc ......................... <server> passed test NCSecDesc Starting test: NetLogons * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test NetLogons Starting test: Advertising ......................... <server> passed test Advertising Starting test: KnowsOfRoleHolders ......................... <server> passed test KnowsOfRoleHolders Starting test: RidManager ......................... <server> passed test RidManager Starting test: MachineAccount Could not open pipe with [<server>]:failed with 1219: Multiple connectio ns to a server or shared resource by the same user, using more than one user nam e, are not allowed. Disconnect all previous connections to the server or shared resource and try again. Could not get NetBIOSDomainName Failed can not test for HOST SPN Failed can not test for HOST SPN * Missing SPN :(null) * Missing SPN :(null) ......................... <server> failed test MachineAccount Starting test: Services Could not open Remote ipc to [<server>]:failed with 1219: Multiple conne ctions to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or sha red resource and try again. ......................... <server> failed test Services Starting test: ObjectsReplicated ......................... <server> passed test ObjectsReplicated Starting test: frssysvol * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test frssysvol Starting test: frsevent ......................... <server> failed test frsevent Starting test: kccevent Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test kccevent Starting test: systemlog Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test systemlog Starting test: VerifyReferences ......................... <server> passed test VerifyReferences Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : <site> Starting test: CrossRefValidation ......................... <site> passed test CrossRefValidation Starting test: CheckSDRefDom ......................... <site> passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running enterprise tests on : <domain.local> Starting test: Intersite ......................... <domain.local> passed test Intersite Starting test: FsmoCheck ......................... <domain.local> passed test FsmoCheck Thanks, Taz "Paul Bergson" wrote: [Quoted Text] > What are the exact errors you are getting? > > "There are also a bunch of AD errors in the event log saying that the root > dns server refuses connection from the subdomain for replication." > > > > Are the high ports being blocked going either way? This is common, since RPC > uses high ports. You may have DNS setup correctly but errors created by > firewall issues could easily be the problem. > Check out an article I have on Firewall Ports Needed for Replication at: > http://www.pbbergs.com/windows/articles.htm > > Run portqryui from both sides of the domain and see what specifically is > going on. > > -- > Paul Bergson > MVP - Directory Services > MCTS, MCT, MCSE, MCSA, Security+, BS CSci > 2008, 2003, 2000 (Early Achiever), NT4 > > http://www.pbbergs.com > > Please no e-mails, any questions should be posted in the NewsGroup This > posting is provided "AS IS" with no warranties, and confers no rights. > "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message > news:47C3A2CE-6B9E-4E83-9A4B-D36538555D52[ at ]microsoft.com... > > Hi, > > > > I recently created a new subdomain for my company. The creation part of > > the > > subdomain went fine, but now when I attempt to connect to the DC of the > > new > > subdomain I get the following message: > > > > error 1722 rpc service not available > > > > My root domain has an internal address range of 172.x.x.x and the > > subdomain > > is 192.168.x.x. > > > > I can ping both the hostname and ip address of any machine FROM the > > subdomian to the root domain, but I can only ping the ip address and not > > the > > hostname when pinging TO the subdomain. This is most likely a dns > > configuration issue, but I'm not sure how to solve it. The subdomain is > > also > > on a different site, and it is setup to be AD integrated. > > > > I setup the subdomain according to these instructions: > > > > http://support.microsoft.com/kb/255248 > > > > http://technet.microsoft.com/en-us/library/cc780951.aspx > > > > http://technet.microsoft.com/en-us/library/cc787706.aspx > > > > I checked the rpc/rpc locator services on both sides and they seem fine. I > > also get the above error when trying to do a replication in AD sites and > > servcies. > > > > I set the subdomain DC to point to itself for dns, and added the root > > domains internal dns server as a forwarder. We also have some external dns > > servers but I haven't set these anywhere in the configuration - is this > > needed? > > > > There are also a bunch of AD errors in the event log saying that the root > > dns server refuses connection from the subdomain for replication. > > > > This is kind of urgent so any advise will be appreciated! > > > > Thanks, > > Taz > > > > >

Re: rpc servser not available Taz1972 12/25/2008 8:51:00 AM Hi, From dcdiag: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: <site>\<server> Starting test: Connectivity ......................... <server> passed test Connectivity Doing primary tests Testing server: <site>\<server> Starting test: Replications [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: DC=ForestDnsZones,DC=<domain>,DC=local The replication generated an error (1256): The remote system is not available. For information about network tr oubleshooting, see Windows Help. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:45:44. 7 failures have occurred since the last success. [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: CN=Schema,CN=Configuration,DC=<domain>,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 07:47:34. The last success occurred at 2008-12-22 15:45:43. 6 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. <domain>.local is not registered on one or more DNS servers. [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: CN=Configuration,DC=<domain>,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:56:47. 10 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. <domaon>.local is not registered on one or more DNS servers. REPLICATION-RECEIVED LATENCY WARNING <server>: Current time is 2008-12-23 16:00:19. DC=ForestDnsZones,DC=<domain>,DC=local Last replication recieved from <server> at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:44. Last replication recieved from DC2 at 2008-12-22 15:29:38. Last replication recieved from DC3 at 2008-12-22 15:19:50. Last replication recieved from DC4 at 2008-12-22 15:44:37. CN=Schema,CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:43. Last replication recieved from DC2 at 2008-12-22 15:45:44. Last replication recieved from DC3 at 2008-12-22 15:44:36. Last replication recieved from DC4 at 2008-12-22 15:29:37. Last replication recieved from DC5 at 2008-12-22 15:19:50. Last replication recieved from DC6 at 2008-12-22 15:44:36. CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:19:57. Last replication recieved from DC at 2008-12-22 15:56:47. Last replication recieved from DC2 at 2008-12-22 15:58:25. Last replication recieved from DC3 at 2008-12-22 15:44:32. Last replication recieved from DC4 at 2008-12-22 15:29:32. Last replication recieved from DC5 at 2008-12-22 15:20:23. Last replication recieved from DC6 at 2008-12-22 15:44:34. ......................... <server> passed test Replications Starting test: NCSecDesc ......................... <server> passed test NCSecDesc Starting test: NetLogons * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test NetLogons Starting test: Advertising ......................... <server> passed test Advertising Starting test: KnowsOfRoleHolders ......................... <server> passed test KnowsOfRoleHolders Starting test: RidManager ......................... <server> passed test RidManager Starting test: MachineAccount Could not open pipe with [<server>]:failed with 1219: Multiple connectio ns to a server or shared resource by the same user, using more than one user nam e, are not allowed. Disconnect all previous connections to the server or shared resource and try again. Could not get NetBIOSDomainName Failed can not test for HOST SPN Failed can not test for HOST SPN * Missing SPN :(null) * Missing SPN :(null) ......................... <server> failed test MachineAccount Starting test: Services Could not open Remote ipc to [<server>]:failed with 1219: Multiple conne ctions to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or sha red resource and try again. ......................... <server> failed test Services Starting test: ObjectsReplicated ......................... <server> passed test ObjectsReplicated Starting test: frssysvol * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test frssysvol Starting test: frsevent ......................... <server> failed test frsevent Starting test: kccevent Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test kccevent Starting test: systemlog Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test systemlog Starting test: VerifyReferences ......................... <server> passed test VerifyReferences Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : <site> Starting test: CrossRefValidation ......................... <site> passed test CrossRefValidation Starting test: CheckSDRefDom ......................... <site> passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running enterprise tests on : <domain.local> Starting test: Intersite ......................... <domain.local> passed test Intersite Starting test: FsmoCheck ......................... <domain.local> passed test FsmoCheck DC=root domain AD DNS server <server>=subdomain DC DC2.3.4 etc= other DC's in other locations domain.local=root domain Thanks, Taz "Paul Bergson" wrote: [Quoted Text] > What are the exact errors you are getting? > > "There are also a bunch of AD errors in the event log saying that the root > dns server refuses connection from the subdomain for replication." > > > > Are the high ports being blocked going either way? This is common, since RPC > uses high ports. You may have DNS setup correctly but errors created by > firewall issues could easily be the problem. > Check out an article I have on Firewall Ports Needed for Replication at: > http://www.pbbergs.com/windows/articles.htm > > Run portqryui from both sides of the domain and see what specifically is > going on. > > -- > Paul Bergson > MVP - Directory Services > MCTS, MCT, MCSE, MCSA, Security+, BS CSci > 2008, 2003, 2000 (Early Achiever), NT4 > > http://www.pbbergs.com > > Please no e-mails, any questions should be posted in the NewsGroup This > posting is provided "AS IS" with no warranties, and confers no rights. > "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message > news:47C3A2CE-6B9E-4E83-9A4B-D36538555D52[ at ]microsoft.com... > > Hi, > > > > I recently created a new subdomain for my company. The creation part of > > the > > subdomain went fine, but now when I attempt to connect to the DC of the > > new > > subdomain I get the following message: > > > > error 1722 rpc service not available > > > > My root domain has an internal address range of 172.x.x.x and the > > subdomain > > is 192.168.x.x. > > > > I can ping both the hostname and ip address of any machine FROM the > > subdomian to the root domain, but I can only ping the ip address and not > > the > > hostname when pinging TO the subdomain. This is most likely a dns > > configuration issue, but I'm not sure how to solve it. The subdomain is > > also > > on a different site, and it is setup to be AD integrated. > > > > I setup the subdomain according to these instructions: > > > > http://support.microsoft.com/kb/255248 > > > > http://technet.microsoft.com/en-us/library/cc780951.aspx > > > > http://technet.microsoft.com/en-us/library/cc787706.aspx > > > > I checked the rpc/rpc locator services on both sides and they seem fine. I > > also get the above error when trying to do a replication in AD sites and > > servcies. > > > > I set the subdomain DC to point to itself for dns, and added the root > > domains internal dns server as a forwarder. We also have some external dns > > servers but I haven't set these anywhere in the configuration - is this > > needed? > > > > There are also a bunch of AD errors in the event log saying that the root > > dns server refuses connection from the subdomain for replication. > > > > This is kind of urgent so any advise will be appreciated! > > > > Thanks, > > Taz > > > > >

Re: rpc servser not available Taz1972 12/26/2008 11:29:00 AM Hi, From dcdiag: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: <site>\<server> Starting test: Connectivity ......................... <server> passed test Connectivity Doing primary tests Testing server: <site>\<server> Starting test: Replications [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: DC=ForestDnsZones,DC=<domain>,DC=local The replication generated an error (1256): The remote system is not available. For information about network tr oubleshooting, see Windows Help. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:45:44. 7 failures have occurred since the last success. [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: CN=Schema,CN=Configuration,DC=<domain>,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 07:47:34. The last success occurred at 2008-12-22 15:45:43. 6 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. <domain>.local is not registered on one or more DNS servers. [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: CN=Configuration,DC=<domain>,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:56:47. 10 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. <domaon>.local is not registered on one or more DNS servers. REPLICATION-RECEIVED LATENCY WARNING <server>: Current time is 2008-12-23 16:00:19. DC=ForestDnsZones,DC=<domain>,DC=local Last replication recieved from <server> at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:44. Last replication recieved from DC2 at 2008-12-22 15:29:38. Last replication recieved from DC3 at 2008-12-22 15:19:50. Last replication recieved from DC4 at 2008-12-22 15:44:37. CN=Schema,CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:43. Last replication recieved from DC2 at 2008-12-22 15:45:44. Last replication recieved from DC3 at 2008-12-22 15:44:36. Last replication recieved from DC4 at 2008-12-22 15:29:37. Last replication recieved from DC5 at 2008-12-22 15:19:50. Last replication recieved from DC6 at 2008-12-22 15:44:36. CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:19:57. Last replication recieved from DC at 2008-12-22 15:56:47. Last replication recieved from DC2 at 2008-12-22 15:58:25. Last replication recieved from DC3 at 2008-12-22 15:44:32. Last replication recieved from DC4 at 2008-12-22 15:29:32. Last replication recieved from DC5 at 2008-12-22 15:20:23. Last replication recieved from DC6 at 2008-12-22 15:44:34. ......................... <server> passed test Replications Starting test: NCSecDesc ......................... <server> passed test NCSecDesc Starting test: NetLogons * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test NetLogons Starting test: Advertising ......................... <server> passed test Advertising Starting test: KnowsOfRoleHolders ......................... <server> passed test KnowsOfRoleHolders Starting test: RidManager ......................... <server> passed test RidManager Starting test: MachineAccount Could not open pipe with [<server>]:failed with 1219: Multiple connectio ns to a server or shared resource by the same user, using more than one user nam e, are not allowed. Disconnect all previous connections to the server or shared resource and try again. Could not get NetBIOSDomainName Failed can not test for HOST SPN Failed can not test for HOST SPN * Missing SPN :(null) * Missing SPN :(null) ......................... <server> failed test MachineAccount Starting test: Services Could not open Remote ipc to [<server>]:failed with 1219: Multiple conne ctions to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or sha red resource and try again. ......................... <server> failed test Services Starting test: ObjectsReplicated ......................... <server> passed test ObjectsReplicated Starting test: frssysvol * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test frssysvol Starting test: frsevent ......................... <server> failed test frsevent Starting test: kccevent Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test kccevent Starting test: systemlog Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test systemlog Starting test: VerifyReferences ......................... <server> passed test VerifyReferences Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : <site> Starting test: CrossRefValidation ......................... <site> passed test CrossRefValidation Starting test: CheckSDRefDom ......................... <site> passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running enterprise tests on : <domain.local> Starting test: Intersite ......................... <domain.local> passed test Intersite Starting test: FsmoCheck ......................... <domain.local> passed test FsmoCheck DC=root domain AD DNS server <server>=subdomain DC DC2.3.4 etc= other DC's in other locations domain.local=root domain Looks like the main issue maybe with the error: The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. <domaon>.local is not registered on one or more DNS servers. So please tell me step by step how to solve this. Thanks, Taz "Paul Bergson" wrote: [Quoted Text] > What are the exact errors you are getting? > > "There are also a bunch of AD errors in the event log saying that the root > dns server refuses connection from the subdomain for replication." > > > > Are the high ports being blocked going either way? This is common, since RPC > uses high ports. You may have DNS setup correctly but errors created by > firewall issues could easily be the problem. > Check out an article I have on Firewall Ports Needed for Replication at: > http://www.pbbergs.com/windows/articles.htm > > Run portqryui from both sides of the domain and see what specifically is > going on. > > -- > Paul Bergson > MVP - Directory Services > MCTS, MCT, MCSE, MCSA, Security+, BS CSci > 2008, 2003, 2000 (Early Achiever), NT4 > > http://www.pbbergs.com > > Please no e-mails, any questions should be posted in the NewsGroup This > posting is provided "AS IS" with no warranties, and confers no rights. > "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message > news:47C3A2CE-6B9E-4E83-9A4B-D36538555D52[ at ]microsoft.com... > > Hi, > > > > I recently created a new subdomain for my company. The creation part of > > the > > subdomain went fine, but now when I attempt to connect to the DC of the > > new > > subdomain I get the following message: > > > > error 1722 rpc service not available > > > > My root domain has an internal address range of 172.x.x.x and the > > subdomain > > is 192.168.x.x. > > > > I can ping both the hostname and ip address of any machine FROM the > > subdomian to the root domain, but I can only ping the ip address and not > > the > > hostname when pinging TO the subdomain. This is most likely a dns > > configuration issue, but I'm not sure how to solve it. The subdomain is > > also > > on a different site, and it is setup to be AD integrated. > > > > I setup the subdomain according to these instructions: > > > > http://support.microsoft.com/kb/255248 > > > > http://technet.microsoft.com/en-us/library/cc780951.aspx > > > > http://technet.microsoft.com/en-us/library/cc787706.aspx > > > > I checked the rpc/rpc locator services on both sides and they seem fine. I > > also get the above error when trying to do a replication in AD sites and > > servcies. > > > > I set the subdomain DC to point to itself for dns, and added the root > > domains internal dns server as a forwarder. We also have some external dns > > servers but I haven't set these anywhere in the configuration - is this > > needed? > > > > There are also a bunch of AD errors in the event log saying that the root > > dns server refuses connection from the subdomain for replication. > > > > This is kind of urgent so any advise will be appreciated! > > > > Thanks, > > Taz > > > > >

Re: rpc servser not available Taz1972 12/27/2008 11:19:01 AM Hi, From dcdiag: Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: <site>\<server> Starting test: Connectivity ......................... <server> passed test Connectivity Doing primary tests Testing server: <site>\<server> Starting test: Replications [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: DC=ForestDnsZones,DC=<domain>,DC=local The replication generated an error (1256): The remote system is not available. For information about network tr oubleshooting, see Windows Help. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:45:44. 7 failures have occurred since the last success. [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: CN=Schema,CN=Configuration,DC=<domain>,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 07:47:34. The last success occurred at 2008-12-22 15:45:43. 6 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. <domain>.local is not registered on one or more DNS servers. [Replications Check,<server>] A recent replication attempt failed: From DC to <server> Naming Context: CN=Configuration,DC=<domain>,DC=local The replication generated an error (8524): The DSA operation is unable to proceed because of a DNS lookup failu re. The failure occurred at 2008-12-23 10:46:38. The last success occurred at 2008-12-22 15:56:47. 10 failures have occurred since the last success. The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. <domaon>.local is not registered on one or more DNS servers. REPLICATION-RECEIVED LATENCY WARNING <server>: Current time is 2008-12-23 16:00:19. DC=ForestDnsZones,DC=<domain>,DC=local Last replication recieved from <server> at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:44. Last replication recieved from DC2 at 2008-12-22 15:29:38. Last replication recieved from DC3 at 2008-12-22 15:19:50. Last replication recieved from DC4 at 2008-12-22 15:44:37. CN=Schema,CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:20:01. Last replication recieved from DC at 2008-12-22 15:45:43. Last replication recieved from DC2 at 2008-12-22 15:45:44. Last replication recieved from DC3 at 2008-12-22 15:44:36. Last replication recieved from DC4 at 2008-12-22 15:29:37. Last replication recieved from DC5 at 2008-12-22 15:19:50. Last replication recieved from DC6 at 2008-12-22 15:44:36. CN=Configuration,DC=<domain>,DC=local Last replication recieved from DC01 at 2008-12-22 15:19:57. Last replication recieved from DC at 2008-12-22 15:56:47. Last replication recieved from DC2 at 2008-12-22 15:58:25. Last replication recieved from DC3 at 2008-12-22 15:44:32. Last replication recieved from DC4 at 2008-12-22 15:29:32. Last replication recieved from DC5 at 2008-12-22 15:20:23. Last replication recieved from DC6 at 2008-12-22 15:44:34. ......................... <server> passed test Replications Starting test: NCSecDesc ......................... <server> passed test NCSecDesc Starting test: NetLogons * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test NetLogons Starting test: Advertising ......................... <server> passed test Advertising Starting test: KnowsOfRoleHolders ......................... <server> passed test KnowsOfRoleHolders Starting test: RidManager ......................... <server> passed test RidManager Starting test: MachineAccount Could not open pipe with [<server>]:failed with 1219: Multiple connectio ns to a server or shared resource by the same user, using more than one user nam e, are not allowed. Disconnect all previous connections to the server or shared resource and try again. Could not get NetBIOSDomainName Failed can not test for HOST SPN Failed can not test for HOST SPN * Missing SPN :(null) * Missing SPN :(null) ......................... <server> failed test MachineAccount Starting test: Services Could not open Remote ipc to [<server>]:failed with 1219: Multiple conne ctions to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or sha red resource and try again. ......................... <server> failed test Services Starting test: ObjectsReplicated ......................... <server> passed test ObjectsReplicated Starting test: frssysvol * You must make sure there are no existing net use connections, you can use "net use /d \\<server>\ipc$" or "net use /d \\<machine-name>\<share-name>" ......................... <server> failed test frssysvol Starting test: frsevent ......................... <server> failed test frsevent Starting test: kccevent Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test kccevent Starting test: systemlog Failed to enumerate event log records, error Multiple connections to a server or shared resource by the same user, using more than one user name, are n ot allowed. Disconnect all previous connections to the server or shared resource and try again. ......................... <server> failed test systemlog Starting test: VerifyReferences ......................... <server> passed test VerifyReferences Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : <site> Starting test: CrossRefValidation ......................... <site> passed test CrossRefValidation Starting test: CheckSDRefDom ......................... <site> passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running enterprise tests on : <domain.local> Starting test: Intersite ......................... <domain.local> passed test Intersite Starting test: FsmoCheck ......................... <domain.local> passed test FsmoCheck DC=root domain AD DNS server <server>=subdomain DC DC2.3.4 etc= other DC's in other locations domain.local=root domain Looks like the main issue maybe with the error: The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. <domaon>.local is not registered on one or more DNS servers. So please tell me step by step how to solve this. Thanks, Taz "Paul Bergson" wrote: [Quoted Text] > What are the exact errors you are getting? > > "There are also a bunch of AD errors in the event log saying that the root > dns server refuses connection from the subdomain for replication." > > > > Are the high ports being blocked going either way? This is common, since RPC > uses high ports. You may have DNS setup correctly but errors created by > firewall issues could easily be the problem. > Check out an article I have on Firewall Ports Needed for Replication at: > http://www.pbbergs.com/windows/articles.htm > > Run portqryui from both sides of the domain and see what specifically is > going on. > > -- > Paul Bergson > MVP - Directory Services > MCTS, MCT, MCSE, MCSA, Security+, BS CSci > 2008, 2003, 2000 (Early Achiever), NT4 > > http://www.pbbergs.com > > Please no e-mails, any questions should be posted in the NewsGroup This > posting is provided "AS IS" with no warranties, and confers no rights. > "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message > news:47C3A2CE-6B9E-4E83-9A4B-D36538555D52[ at ]microsoft.com... > > Hi, > > > > I recently created a new subdomain for my company. The creation part of > > the > > subdomain went fine, but now when I attempt to connect to the DC of the > > new > > subdomain I get the following message: > > > > error 1722 rpc service not available > > > > My root domain has an internal address range of 172.x.x.x and the > > subdomain > > is 192.168.x.x. > > > > I can ping both the hostname and ip address of any machine FROM the > > subdomian to the root domain, but I can only ping the ip address and not > > the > > hostname when pinging TO the subdomain. This is most likely a dns > > configuration issue, but I'm not sure how to solve it. The subdomain is > > also > > on a different site, and it is setup to be AD integrated. > > > > I setup the subdomain according to these instructions: > > > > http://support.microsoft.com/kb/255248 > > > > http://technet.microsoft.com/en-us/library/cc780951.aspx > > > > http://technet.microsoft.com/en-us/library/cc787706.aspx > > > > I checked the rpc/rpc locator services on both sides and they seem fine. I > > also get the above error when trying to do a replication in AD sites and > > servcies. > > > > I set the subdomain DC to point to itself for dns, and added the root > > domains internal dns server as a forwarder. We also have some external dns > > servers but I haven't set these anywhere in the configuration - is this > > needed? > > > > There are also a bunch of AD errors in the event log saying that the root > > dns server refuses connection from the subdomain for replication. > > > > This is kind of urgent so any advise will be appreciated! > > > > Thanks, > > Taz > > > > >

Re: rpc servser not available "Paul Bergson" <pbbergs[ at ]nospammsn.com> 12/30/2008 1:21:02 PM This doesn't help. The failure was understood, but the cause of this error is probably the high ports being blocked. Did you run portqryui as I already pointed out? -- Paul Bergson MVP - Directory Services MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, 2003, 2000 (Early Achiever), NT4 http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message news:00448C7A-C192-48E3-8AE4-FE1BD3494513[ at ]microsoft.com... [Quoted Text] > Hi, > > From dcdiag: > > Domain Controller Diagnosis > > Performing initial setup: > Done gathering initial info. > > Doing initial required tests > > Testing server: <site>\<server> > Starting test: Connectivity > ......................... <server> passed test Connectivity > > Doing primary tests > > Testing server: <site>\<server> > Starting test: Replications > [Replications Check,<server>] A recent replication attempt failed: > From DC to <server> > Naming Context: DC=ForestDnsZones,DC=<domain>,DC=local > The replication generated an error (1256): > The remote system is not available. For information about > network tr > oubleshooting, see Windows Help. > The failure occurred at 2008-12-23 10:46:38. > The last success occurred at 2008-12-22 15:45:44. > 7 failures have occurred since the last success. > [Replications Check,<server>] A recent replication attempt failed: > From DC to <server> > Naming Context: CN=Schema,CN=Configuration,DC=<domain>,DC=local > The replication generated an error (8524): > The DSA operation is unable to proceed because of a DNS lookup > failu > re. > The failure occurred at 2008-12-23 07:47:34. > The last success occurred at 2008-12-22 15:45:43. > 6 failures have occurred since the last success. > The guid-based DNS name > 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. > <domain>.local > is not registered on one or more DNS servers. > [Replications Check,<server>] A recent replication attempt failed: > From DC to <server> > Naming Context: CN=Configuration,DC=<domain>,DC=local > The replication generated an error (8524): > The DSA operation is unable to proceed because of a DNS lookup > failu > re. > The failure occurred at 2008-12-23 10:46:38. > The last success occurred at 2008-12-22 15:56:47. > 10 failures have occurred since the last success. > The guid-based DNS name > 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. > <domaon>.local > is not registered on one or more DNS servers. > REPLICATION-RECEIVED LATENCY WARNING > <server>: Current time is 2008-12-23 16:00:19. > DC=ForestDnsZones,DC=<domain>,DC=local > Last replication recieved from <server> at 2008-12-22 > 15:20:01. > > Last replication recieved from DC at 2008-12-22 15:45:44. > Last replication recieved from DC2 at 2008-12-22 15:29:38. > Last replication recieved from DC3 at 2008-12-22 15:19:50. > Last replication recieved from DC4 at 2008-12-22 15:44:37. > CN=Schema,CN=Configuration,DC=<domain>,DC=local > Last replication recieved from DC01 at 2008-12-22 15:20:01. > > Last replication recieved from DC at 2008-12-22 15:45:43. > Last replication recieved from DC2 at 2008-12-22 15:45:44. > Last replication recieved from DC3 at 2008-12-22 15:44:36. > Last replication recieved from DC4 at 2008-12-22 15:29:37. > Last replication recieved from DC5 at 2008-12-22 15:19:50. > Last replication recieved from DC6 at 2008-12-22 15:44:36. > CN=Configuration,DC=<domain>,DC=local > Last replication recieved from DC01 at 2008-12-22 15:19:57. > > Last replication recieved from DC at 2008-12-22 15:56:47. > Last replication recieved from DC2 at 2008-12-22 15:58:25. > Last replication recieved from DC3 at 2008-12-22 15:44:32. > Last replication recieved from DC4 at 2008-12-22 15:29:32. > Last replication recieved from DC5 at 2008-12-22 15:20:23. > Last replication recieved from DC6 at 2008-12-22 15:44:34. > ......................... <server> passed test Replications > Starting test: NCSecDesc > ......................... <server> passed test NCSecDesc > Starting test: NetLogons > * You must make sure there are no existing net use connections, > you can use "net use /d \\<server>\ipc$" or "net use /d > \\<machine-name>\<share-name>" > ......................... <server> failed test NetLogons > Starting test: Advertising > ......................... <server> passed test Advertising > Starting test: KnowsOfRoleHolders > ......................... <server> passed test KnowsOfRoleHolders > Starting test: RidManager > ......................... <server> passed test RidManager > Starting test: MachineAccount > Could not open pipe with [<server>]:failed with 1219: Multiple > connectio > ns to a server or shared resource by the same user, using more than one > user > nam > e, are not allowed. Disconnect all previous connections to the server or > shared > resource and try again. > Could not get NetBIOSDomainName > Failed can not test for HOST SPN > Failed can not test for HOST SPN > * Missing SPN :(null) > * Missing SPN :(null) > ......................... <server> failed test MachineAccount > Starting test: Services > Could not open Remote ipc to [<server>]:failed with 1219: Multiple > conne > ctions to a server or shared resource by the same user, using more than > one > user > name, are not allowed. Disconnect all previous connections to the server > or > sha > red resource and try again. > ......................... <server> failed test Services > Starting test: ObjectsReplicated > ......................... <server> passed test ObjectsReplicated > Starting test: frssysvol > * You must make sure there are no existing net use connections, > you can use "net use /d \\<server>\ipc$" or "net use /d > \\<machine-name>\<share-name>" > ......................... <server> failed test frssysvol > Starting test: frsevent > ......................... <server> failed test frsevent > Starting test: kccevent > Failed to enumerate event log records, error Multiple connections > to a > server or shared resource by the same user, using more than one user name, > are n > ot allowed. Disconnect all previous connections to the server or shared > resource > and try again. > ......................... <server> failed test kccevent > Starting test: systemlog > Failed to enumerate event log records, error Multiple connections > to a > server or shared resource by the same user, using more than one user name, > are n > ot allowed. Disconnect all previous connections to the server or shared > resource > and try again. > ......................... <server> failed test systemlog > Starting test: VerifyReferences > ......................... <server> passed test VerifyReferences > > Running partition tests on : DomainDnsZones > Starting test: CrossRefValidation > ......................... DomainDnsZones passed test > CrossRefValidation > > Starting test: CheckSDRefDom > ......................... DomainDnsZones passed test CheckSDRefDom > > Running partition tests on : <site> > Starting test: CrossRefValidation > ......................... <site> passed test CrossRefValidation > Starting test: CheckSDRefDom > ......................... <site> passed test CheckSDRefDom > > Running partition tests on : ForestDnsZones > Starting test: CrossRefValidation > ......................... ForestDnsZones passed test > CrossRefValidation > > Starting test: CheckSDRefDom > ......................... ForestDnsZones passed test CheckSDRefDom > > Running partition tests on : Schema > Starting test: CrossRefValidation > ......................... Schema passed test CrossRefValidation > Starting test: CheckSDRefDom > ......................... Schema passed test CheckSDRefDom > > Running partition tests on : Configuration > Starting test: CrossRefValidation > ......................... Configuration passed test > CrossRefValidation > Starting test: CheckSDRefDom > ......................... Configuration passed test CheckSDRefDom > > Running enterprise tests on : <domain.local> > Starting test: Intersite > ......................... <domain.local> passed test Intersite > Starting test: FsmoCheck > ......................... <domain.local> passed test FsmoCheck > > DC=root domain AD DNS server > <server>=subdomain DC > DC2.3.4 etc= other DC's in other locations > domain.local=root domain > > Looks like the main issue maybe with the error: > > The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. > <domaon>.local > is not registered on one or more DNS servers. > > So please tell me step by step how to solve this. > > > Thanks, > Taz > > > > "Paul Bergson" wrote: > >> What are the exact errors you are getting? >> >> "There are also a bunch of AD errors in the event log saying that the >> root >> dns server refuses connection from the subdomain for replication." >> >> >> >> Are the high ports being blocked going either way? This is common, since >> RPC >> uses high ports. You may have DNS setup correctly but errors created by >> firewall issues could easily be the problem. >> Check out an article I have on Firewall Ports Needed for Replication at: >> http://www.pbbergs.com/windows/articles.htm >> >> Run portqryui from both sides of the domain and see what specifically is >> going on. >> >> -- >> Paul Bergson >> MVP - Directory Services >> MCTS, MCT, MCSE, MCSA, Security+, BS CSci >> 2008, 2003, 2000 (Early Achiever), NT4 >> >> http://www.pbbergs.com >> >> Please no e-mails, any questions should be posted in the NewsGroup This >> posting is provided "AS IS" with no warranties, and confers no rights. >> "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message >> news:47C3A2CE-6B9E-4E83-9A4B-D36538555D52[ at ]microsoft.com... >> > Hi, >> > >> > I recently created a new subdomain for my company. The creation part of >> > the >> > subdomain went fine, but now when I attempt to connect to the DC of the >> > new >> > subdomain I get the following message: >> > >> > error 1722 rpc service not available >> > >> > My root domain has an internal address range of 172.x.x.x and the >> > subdomain >> > is 192.168.x.x. >> > >> > I can ping both the hostname and ip address of any machine FROM the >> > subdomian to the root domain, but I can only ping the ip address and >> > not >> > the >> > hostname when pinging TO the subdomain. This is most likely a dns >> > configuration issue, but I'm not sure how to solve it. The subdomain is >> > also >> > on a different site, and it is setup to be AD integrated. >> > >> > I setup the subdomain according to these instructions: >> > >> > http://support.microsoft.com/kb/255248 >> > >> > http://technet.microsoft.com/en-us/library/cc780951.aspx >> > >> > http://technet.microsoft.com/en-us/library/cc787706.aspx >> > >> > I checked the rpc/rpc locator services on both sides and they seem >> > fine. I >> > also get the above error when trying to do a replication in AD sites >> > and >> > servcies. >> > >> > I set the subdomain DC to point to itself for dns, and added the root >> > domains internal dns server as a forwarder. We also have some external >> > dns >> > servers but I haven't set these anywhere in the configuration - is this >> > needed? >> > >> > There are also a bunch of AD errors in the event log saying that the >> > root >> > dns server refuses connection from the subdomain for replication. >> > >> > This is kind of urgent so any advise will be appreciated! >> > >> > Thanks, >> > Taz >> > >> > >>

Re: rpc servser not available Taz1972 12/30/2008 6:28:05 PM Hi, I'm on leave right now until next week - will try it out then and let you know the results. But strange that the error The guid-based DNS name 1e5fb0dc5d86-4467-9d43-055d890145f2._msdcs.<domaon>.local [Quoted Text] > is not registered on one or more DNS servers. is not relevant in this case? P.S. Re the multiple posts - my replies wouldn't show up here for some reason but did later. Looks like there might have been a problem with this site. Thanks, Taz "Paul Bergson" wrote: > This doesn't help. The failure was understood, but the cause of this error > is probably the high ports being blocked. Did you run portqryui as I > already pointed out? > > -- > Paul Bergson > MVP - Directory Services > MCTS, MCT, MCSE, MCSA, Security+, BS CSci > 2008, 2003, 2000 (Early Achiever), NT4 > > http://www.pbbergs.com > > Please no e-mails, any questions should be posted in the NewsGroup This > posting is provided "AS IS" with no warranties, and confers no rights. > "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message > news:00448C7A-C192-48E3-8AE4-FE1BD3494513[ at ]microsoft.com... > > Hi, > > > > From dcdiag: > > > > Domain Controller Diagnosis > > > > Performing initial setup: > > Done gathering initial info. > > > > Doing initial required tests > > > > Testing server: <site>\<server> > > Starting test: Connectivity > > ......................... <server> passed test Connectivity > > > > Doing primary tests > > > > Testing server: <site>\<server> > > Starting test: Replications > > [Replications Check,<server>] A recent replication attempt failed: > > From DC to <server> > > Naming Context: DC=ForestDnsZones,DC=<domain>,DC=local > > The replication generated an error (1256): > > The remote system is not available. For information about > > network tr > > oubleshooting, see Windows Help. > > The failure occurred at 2008-12-23 10:46:38. > > The last success occurred at 2008-12-22 15:45:44. > > 7 failures have occurred since the last success. > > [Replications Check,<server>] A recent replication attempt failed: > > From DC to <server> > > Naming Context: CN=Schema,CN=Configuration,DC=<domain>,DC=local > > The replication generated an error (8524): > > The DSA operation is unable to proceed because of a DNS lookup > > failu > > re. > > The failure occurred at 2008-12-23 07:47:34. > > The last success occurred at 2008-12-22 15:45:43. > > 6 failures have occurred since the last success. > > The guid-based DNS name > > 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. > > <domain>.local > > is not registered on one or more DNS servers. > > [Replications Check,<server>] A recent replication attempt failed: > > From DC to <server> > > Naming Context: CN=Configuration,DC=<domain>,DC=local > > The replication generated an error (8524): > > The DSA operation is unable to proceed because of a DNS lookup > > failu > > re. > > The failure occurred at 2008-12-23 10:46:38. > > The last success occurred at 2008-12-22 15:56:47. > > 10 failures have occurred since the last success. > > The guid-based DNS name > > 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. > > <domaon>.local > > is not registered on one or more DNS servers. > > REPLICATION-RECEIVED LATENCY WARNING > > <server>: Current time is 2008-12-23 16:00:19. > > DC=ForestDnsZones,DC=<domain>,DC=local > > Last replication recieved from <server> at 2008-12-22 > > 15:20:01. > > > > Last replication recieved from DC at 2008-12-22 15:45:44. > > Last replication recieved from DC2 at 2008-12-22 15:29:38. > > Last replication recieved from DC3 at 2008-12-22 15:19:50. > > Last replication recieved from DC4 at 2008-12-22 15:44:37. > > CN=Schema,CN=Configuration,DC=<domain>,DC=local > > Last replication recieved from DC01 at 2008-12-22 15:20:01. > > > > Last replication recieved from DC at 2008-12-22 15:45:43. > > Last replication recieved from DC2 at 2008-12-22 15:45:44. > > Last replication recieved from DC3 at 2008-12-22 15:44:36. > > Last replication recieved from DC4 at 2008-12-22 15:29:37. > > Last replication recieved from DC5 at 2008-12-22 15:19:50. > > Last replication recieved from DC6 at 2008-12-22 15:44:36. > > CN=Configuration,DC=<domain>,DC=local > > Last replication recieved from DC01 at 2008-12-22 15:19:57. > > > > Last replication recieved from DC at 2008-12-22 15:56:47. > > Last replication recieved from DC2 at 2008-12-22 15:58:25. > > Last replication recieved from DC3 at 2008-12-22 15:44:32. > > Last replication recieved from DC4 at 2008-12-22 15:29:32. > > Last replication recieved from DC5 at 2008-12-22 15:20:23. > > Last replication recieved from DC6 at 2008-12-22 15:44:34. > > ......................... <server> passed test Replications > > Starting test: NCSecDesc > > ......................... <server> passed test NCSecDesc > > Starting test: NetLogons > > * You must make sure there are no existing net use connections, > > you can use "net use /d \\<server>\ipc$" or "net use /d > > \\<machine-name>\<share-name>" > > ......................... <server> failed test NetLogons > > Starting test: Advertising > > ......................... <server> passed test Advertising > > Starting test: KnowsOfRoleHolders > > ......................... <server> passed test KnowsOfRoleHolders > > Starting test: RidManager > > ......................... <server> passed test RidManager > > Starting test: MachineAccount > > Could not open pipe with [<server>]:failed with 1219: Multiple > > connectio > > ns to a server or shared resource by the same user, using more than one > > user > > nam > > e, are not allowed. Disconnect all previous connections to the server or > > shared > > resource and try again. > > Could not get NetBIOSDomainName > > Failed can not test for HOST SPN > > Failed can not test for HOST SPN > > * Missing SPN :(null) > > * Missing SPN :(null) > > ......................... <server> failed test MachineAccount > > Starting test: Services > > Could not open Remote ipc to [<server>]:failed with 1219: Multiple > > conne > > ctions to a server or shared resource by the same user, using more than > > one > > user > > name, are not allowed. Disconnect all previous connections to the server > > or > > sha > > red resource and try again. > > ......................... <server> failed test Services > > Starting test: ObjectsReplicated > > ......................... <server> passed test ObjectsReplicated > > Starting test: frssysvol > > * You must make sure there are no existing net use connections, > > you can use "net use /d \\<server>\ipc$" or "net use /d > > \\<machine-name>\<share-name>" > > ......................... <server> failed test frssysvol > > Starting test: frsevent > > ......................... <server> failed test frsevent > > Starting test: kccevent > > Failed to enumerate event log records, error Multiple connections > > to a > > server or shared resource by the same user, using more than one user name, > > are n > > ot allowed. Disconnect all previous connections to the server or shared > > resource > > and try again. > > ......................... <server> failed test kccevent > > Starting test: systemlog > > Failed to enumerate event log records, error Multiple connections > > to a > > server or shared resource by the same user, using more than one user name, > > are n > > ot allowed. Disconnect all previous connections to the server or shared > > resource > > and try again. > > ......................... <server> failed test systemlog > > Starting test: VerifyReferences > > ......................... <server> passed test VerifyReferences > > > > Running partition tests on : DomainDnsZones > > Starting test: CrossRefValidation > > ......................... DomainDnsZones passed test > > CrossRefValidation > > > > Starting test: CheckSDRefDom > > ......................... DomainDnsZones passed test CheckSDRefDom > > > > Running partition tests on : <site> > > Starting test: CrossRefValidation > > ......................... <site> passed test CrossRefValidation > > Starting test: CheckSDRefDom > > ......................... <site> passed test CheckSDRefDom > > > > Running partition tests on : ForestDnsZones > > Starting test: CrossRefValidation > > ......................... ForestDnsZones passed test > > CrossRefValidation > > > > Starting test: CheckSDRefDom > > ......................... ForestDnsZones passed test CheckSDRefDom > > > > Running partition tests on : Schema > > Starting test: CrossRefValidation > > ......................... Schema passed test CrossRefValidation > > Starting test: CheckSDRefDom > > ......................... Schema passed test CheckSDRefDom > > > > Running partition tests on : Configuration > > Starting test: CrossRefValidation > > ......................... Configuration passed test > > CrossRefValidation > > Starting test: CheckSDRefDom > > ......................... Configuration passed test CheckSDRefDom > > > > Running enterprise tests on : <domain.local> > > Starting test: Intersite > > ......................... <domain.local> passed test Intersite > > Starting test: FsmoCheck > > ......................... <domain.local> passed test FsmoCheck > > > > DC=root domain AD DNS server > > <server>=subdomain DC > > DC2.3.4 etc= other DC's in other locations > > domain.local=root domain > > > > Looks like the main issue maybe with the error: > > > > The guid-based DNS name 1e5fb0dc-5d86-4467-9d43-055d890145f2._msdcs. > > <domaon>.local > > is not registered on one or more DNS servers. > > > > So please tell me step by step how to solve this. > > > > > > Thanks, > > Taz > > > > > > > > "Paul Bergson" wrote: > > > >> What are the exact errors you are getting? > >> > >> "There are also a bunch of AD errors in the event log saying that the > >> root > >> dns server refuses connection from the subdomain for replication." > >> > >> > >> > >> Are the high ports being blocked going either way? This is common, since > >> RPC > >> uses high ports. You may have DNS setup correctly but errors created by > >> firewall issues could easily be the problem. > >> Check out an article I have on Firewall Ports Needed for Replication at: > >> http://www.pbbergs.com/windows/articles.htm > >> > >> Run portqryui from both sides of the domain and see what specifically is > >> going on. > >> > >> -- > >> Paul Bergson > >> MVP - Directory Services > >> MCTS, MCT, MCSE, MCSA, Security+, BS CSci > >> 2008, 2003, 2000 (Early Achiever), NT4 > >> > >> http://www.pbbergs.com > >> > >> Please no e-mails, any questions should be posted in the NewsGroup This > >> posting is provided "AS IS" with no warranties, and confers no rights. > >> "Taz1972" <Taz1972[ at ]discussions.microsoft.com> wrote in message > >> news:47C3A2CE-6B9E-4E83-9A4B-D36538555D52[ at ]microsoft.com... > >> > Hi, > >> > > >> > I recently created a new subdomain for my company. The creation part of > >> > the > >> > subdomain went fine, but now when I attempt to connect to the DC of the > >> > new > >> > subdomain I get the following message: > >> > > >> > error 1722 rpc service not available > >> > > >> > My root domain has an internal address range of 172.x.x.x and the > >> > subdomain > >> > is 192.168.x.x. > >> > > >> > I can ping both the hostname and ip address of any machine FROM the > >> > subdomian to the root domain, but I can only ping the ip address and > >> > not > >> > the > >> > hostname when pinging TO the subdomain. This is most likely a dns > >> > configuration issue, but I'm not sure how to solve it. The subdomain is > >> > also > >> > on a different site, and it is setup to be AD integrated. > >> > > >> > I setup the subdomain according to these instructions: > >> > > >> > http://support.microsoft.com/kb/255248 > >> > > >> > http://technet.microsoft.com/en-us/library/cc780951.aspx > >> > > >> > http://technet.microsoft.com/en-us/library/cc787706.aspx > >> > > >> > I checked the rpc/rpc locator services on both sides and they seem > >> > fine. I > >> > also get the above error when trying to do a replication in AD sites > >> > and > >> > servcies. > >> >