On Thu, 2 Feb 2012 14:37:49 -0600, Tim Mooney <Tim.Mooney AT NDSU DOT EDU> 
wrote:

>Unfortunately, this still hasn't fixed the issue.
>
>I've also now tried replacing the nsrladb with the recovered copy, and
>that also hasn't fixed the issue.

Actually, it did fix the issue, but there was a second issue that was
masking that.

What I didn't recognize right away is that all of the clients that were
still failing, after replacing the nsrladb with a recovery copy, were
clients that were outside of our datacenter subnets.

It turns out my puppet rules for the new backup server activated our
default server firewall.  I just needed to poke an additional hole in
the firewall and all is now right with the world.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER