Re: Still can't replicate (was Hosed DNS??)

If there is a 13509 warning following the 13508 it can be safly ignored. On Thu, Jun 5, 2008 at 3:24 PM, James Edwards [EMAIL PROTECTED] wrote: Ken Schaefer wrote: When you see errors in the event log, please open the event, and there is a little button that looks like two pieces of

Re: Still can't replicate (was Hosed DNS??)SOLVED sort of

KenM wrote: If there is a 13509 warning following the 13508 it can be safly ignored. I turned off the Windows Firewall on both servers (They're both behind a hardware firewall) and the errors went away. Some setting in the firewall appears to have become corrupted. Now I can determine what's

Re: Still can't replicate (was Hosed DNS??)

Terry Fryrear wrote: I would check my sites and services to see how you are replicating. Then try replmon I've been running replmon on both servers. The PDC (Dad) is showing failure errors, the second DC (Mom) is showing success. seems to be a one way error effecting Dad. When I try to

Re: Still can't replicate (was Hosed DNS??)

Ken Schaefer wrote: You need to start providing more information. I looked through the previous thread and you said: so I decided to look at some other logs. In one I discovered that the DC's hadn't replicated in a month a) What log did you look in? Event Viewer-File Replication. b)

Re: Still can't replicate (was Hosed DNS??)

Have you seen this KB article. http://support.microsoft.com/?kbid=839880 On Wed, Jun 4, 2008 at 2:45 PM, James Edwards [EMAIL PROTECTED] wrote: Terry Fryrear wrote: I would check my sites and services to see how you are replicating. Then try replmon I've been running replmon on

Re: Still can't replicate (was Hosed DNS??)

KenM wrote: Have you seen this KB article. http://support.microsoft.com/?kbid=839880 Yes, I ran the diagnostics (except dcdiag, it says it can't find a dll, I need to reinstall it) mentioned in my earlier post, but it doesn't give any fixes. Jim ~ Upgrade to Next Generation

Re: Still can't replicate (was Hosed DNS??)

What were the results of portqry. Are both servers listening on the proper ports? Is there a router, Firewall, or manged switch inbetween the DC's with an ACL applied? Have you tried to tweak the reg keys in step 5? On Wed, Jun 4, 2008 at 4:21 PM, James Edwards [EMAIL PROTECTED] wrote: KenM

RE: Still can't replicate (was Hosed DNS??)

I would check my sites and services to see how you are replicating. Then try replmon -Original Message- From: James Edwards [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2008 5:59 PM To: NT System Admin Issues Subject: Still can't replicate (was Hosed DNS??) Still looking

Still can't replicate (was Hosed DNS??)

Still looking for the cause. When I do a DCDIAG on the one that hasn't been replicated from everything except frsevent passes. On the DC that hasn't received the replication I get the error that replication hasn't occurred for a month with the errors 1753 and 1256 also the frsevent fails. A

RE: Still can't replicate (was Hosed DNS??)

: James Edwards [mailto:[EMAIL PROTECTED] Sent: Tuesday, 3 June 2008 7:59 AM To: NT System Admin Issues Subject: Still can't replicate (was Hosed DNS??) Still looking for the cause. When I do a DCDIAG on the one that hasn't been replicated from everything except frsevent passes. On the DC

Re: Hosed DNS??

mck1012 wrote: Make sure the DC is pointing to either itself or another AD int. DNS server. Next restart the netlogon service and then from the cmd prompt ipconfig /registrerdns. Make sure all clients point to the server for dns. How many DC's do you have? I have 1 1/2 DC's (the 1/2 DC

Hosed DNS??

Recently I attempted to push install an application (Counter Spy) to a computer in my Domain and got an error message about not being able to authenticate. Later, I attempted to join a computer to the Domain and and got an error message about no Domain Controller and the computer couldn't find

RE: Hosed DNS??

First hit the DC's with a command prompt and use ipconfig /registerdns -Original Message- From: James Edwards [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 4:26 PM To: NT System Admin Issues Subject: Hosed DNS?? Recently I attempted to push install an application (Counter

Re: Hosed DNS??

Kennedy, Jim wrote: First hit the DC's with a command prompt and use ipconfig /registerdns Am I going to get lucky and it's that simple to rebuild the _ldap_tcp.dc_msdcs.my.domain entry?? I guess I'll know in about 15 minutes. THANKS ~ Upgrade to Next Generation Antispam/Antivirus with

Re: Hosed DNS??

James Edwards wrote: Kennedy, Jim wrote: First hit the DC's with a command prompt and use ipconfig /registerdns Am I going to get lucky and it's that simple to rebuild the _ldap_tcp.dc_msdcs.my.domain entry?? I guess I'll know in about 15 minutes. THANKS Guess I didn't get that

Re: Hosed DNS??

[EMAIL PROTECTED] To: NT System Admin Issues ntsysadmin@lyris.sunbelt-software.com Sent: Tuesday, May 27, 2008 6:07:14 PM Subject: Re: Hosed DNS?? James Edwards wrote: Kennedy, Jim wrote: First hit the DC's with a command prompt and use ipconfig /registerdns Am I going to get lucky and it's

Re: Hosed DNS??

Here is a KB article that may help. http://support.microsoft.com/kb/310568 - Original Message From: mck1012 [EMAIL PROTECTED] To: NT System Admin Issues ntsysadmin@lyris.sunbelt-software.com Sent: Tuesday, May 27, 2008 7:35:32 PM Subject: Re: Hosed DNS?? Make sure the DC