File Replication Domain Controller Event Log Error

Receiving error message in Event Viewer File Replication Service, Event ID: 13508, Source: NtFrs. And there is no Event ID: 13509 to follow.  Windows 2003, Any ideas???

The File Replication Service is having trouble enabling replication from Server02 to Server01 for d:\sysvol\domain using the DNS name Server02.domain.com. FRS will keep retrying.  Following are some of the reasons you would see this warning.
 
 [1] FRS cannot correctly resolve the DNS name Server02.domain.com from this
      computer.
 [2] FRS is not running on Server02.domain.com.
 [3] The topology information in the Active Directory for this replica has not yet
       replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

Thanks,
Butch
IGButchAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
arnoldConnect With a Mentor Commented:
You're correct.

The only other thing is that you are using public IPs for your LAN 192.35.x.x is a European Allocated block.  This could cause problem if an external site you try to access has IPs in your range.  Your system will see those as local to your LAN.
Private IPs should be used on a LAN
10.0.0.0 - 10.255.255.255
172.16.0.0-172.31.255.255
192.168.0.0-192.168.255.255.
You can segment each block to the number of hosts/nodes you need.
0
 
arnoldCommented:
Check the DNS records on the system where the error is to make sure the listed DNS servers are responding to queries and that you have more than ONE dns server record.

post the output of runnin ipconfig /all in a command prompt.
0
 
IGButchAuthor Commented:
Here is a print out of my DNS setting on both servers.  Server01 is were I am receiving errors and I can also ping both server.

Server02

Host Name…………………:Server02
Primary DNS Suffix……….:Domain.com
Node Type…………………:Unknown
IP Routing Enabled………..:No
Wins Proxy Enabled……….:No
DNS Suffix Search List…….:Domain.com

Ethernet adapter Local Area Connection:

Connection – specific NSN Suffix….:
Description…………………………..: Intel Pro/100 MT Net. Connection
Physical ……………………………..: MAC Address
DHCP Enabled…………………….....:No
IP Address…………………………...: 192.35.15.2
Subnet……………………………….: 255.255.240.0
Default Gateway……………………..: 192.35.1.1
DNS Servers………………………….: 192.35.15.1
                                                                219.160.20.282
                                                                219.160.21.282
                                                                127.0.0.1
......................................................................................................................................
Server01 - Where I am receiving errors

Host Name………………..:Server01
Primary DNS Suffix……….:Domain.com
Node Type…………………:Hybrid
IP Routing Enabled……….:No
Wins Proxy Enabled………:No
DNS Suffix Search List……Domain.com

Ethernet adapter Local Area Connection:

Connection – specific NSN Suffix….:
Description…………………………..: Intel Pro/100 MT Net. Connection
Physical ……………………………..: MAC Address
DHCP Enabled……………………...:No
IP Address…………………………...:192.35.15.1
Subnet……………………………….: 255.255.240.0
Default Gateway…………………….:192.35.1.1
DNS Servers……………………….: 192.35.15.1
                                                               127.0.0.1
                                                               192.35.15.2
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
arnoldCommented:
Does the local system (127.0.0.1) has a DNS server?
How is server01 have an IP of the router as its IP?
How do 219.160.20.282 and 219.160.21.282 come into play?  If they are external DNS, you should add them to the forwarders section of the DNS server configuration.

server01 also has two references to itself.  Is DNS on server01 configured to listen on all IPs?
I.e. 192.35.15.1 and 127.0.0.1.

on server1 run the following:
nslookup -q=soa <domain.com> 127.0.0.1
nslookup -q=soa <domain.com> 192.35.15.1
nslookup -q=soa <domain.com> 192.35.15.2

note server02 has Node Type: unknown.
http://support.microsoft.com/kb/310570

Check the file replication log on each system for any errors i.e. issue with journaling etc..
0
 
IGButchAuthor Commented:
Sever01 doesn’t have the same route IP, typo my fault.  The 219.160.20 & 21.282 is an external DNS from what I am told but cannot get any good explanation so AT&T thing I am told.  Sorry but what do you mean when you say forward section on the DNS server configuration.

nslookup on 172.0.0.1 = Time out
nslookup on 192.35.15.1 = Ok
nslookup on 192.35.15.2 = Ok

Thanks for the replies
…Butch
0
 
arnoldCommented:
127.0.0.1 (local host) not 172.0.0.1


Withing the DNS server properties, there is a forwarders TAB.

This is where you configure your DNS server to forward requests for information that it is not authoritative for to these servers.  I.e. offload the lookup to an upstream set of servers versus performing the lookups itself.  This is where the external DNS servers belong.  Including them as you have could lead to trouble I.e. when the servers queries these external servers for information about the local domain, it will incur a delay or a false positive response. The external server would either provide the wrong information if you are using a public suffix for your internal domain i.e. domain.com versus domain.local or domain.private. The other delay is if there is no response from  external and your server has to wait out the timeout period before trying the next server.

You can also let your internal DNS servers perform the external lookups, just make sure there are root servers listed under the root server tabs.
This way should the provider change something i.e. replace the current servers with new ones without maintaing the IPs, you forwarding process will stop working until they are taken out/disabled..
0
 
IGButchAuthor Commented:
DNS Forwarding – This is my first time and I went to get this right so here’s what I’m going to do.  Going into the DNS Manger – Right Click the Server02 – Properties – Forwards Tab.  Below I will enter both IP Address’s 219.160.20 & 21.282, Apply/OK than quite the DNS Manager.  Go to the NIC – Properties – and remove the DNS I have Forwarded.  So all I should see is  192.35.15.1 & 127.0.0.1 in this order.   If I am incorrect in any of this please let me know.

Thanks,
Butch
0
 
IGButchAuthor Commented:
That seemed to do the trick,  no more errors or warnings as of now.  Will monitor for a week, then close this question.  Thanks for all the help, appreciate.

....Butch
0
All Courses

From novice to tech pro — start learning today.