Assign an OU to a certain RODC

From technet:
"When a client that is searching for a domain controller receives the list of domain controller IP addresses from DNS, the client begins querying the domain controllers in turn to find out which domain controller is available and appropriate. Active Directory intercepts the query, which contains the IP address of the client, and passes it to Net Logon on the domain controller. Net Logon looks up the client IP address in its subnet-to-site mapping table by finding the subnet object that most closely matches the client IP address and then returns the following information:

1. The name of the site in which the client is located, or the site that most closely matches the client IP address.

2. The name of the site in which the current domain controller is located.

3. A bit that indicates whether the found domain controller is located (bit is set) or not located (bit is not set) in the site closest to the client.

The domain controller returns the information to the client. The response also contains various other pieces of information that describe the domain controller. The client inspects the information to determine whether to try to find a better domain controller. The decision is made as follows:

1. If the returned domain controller is in the closest site (the returned bit is set), the client uses this domain controller.

2. If the client has already tried to find a domain controller in the site in which the domain controller claims the client is located, the client uses this domain controller.

3. If the domain controller is not in the closest site, the client updates its site information and sends a new DNS query to find a new domain controller in the site. If the second query is successful, the new domain controller is used. If the second query fails, the original domain controller is used."

"the LDAP query hit both local..." How are you using to query AD? What server shows up if you type print %logonserver% from a cmd prompt?

Take a look into converting from FRS to DFS-R replication. Along the way you'll probably figure out what's going on and why things are taking so long, and move away from the now deprecated FRS sysvol replication.

Here's the article from Microsoft outlining the process: http://technet.microsoft.com/en-us/library/dd640019(v=ws.10).aspx

In particular you can take note of the health checks at the beginning. This might also be a good time to repadmin and be sure that AD itself is resolving all SRV records properly and replicating as it should.