Tony

Thanks much for the info TLAM_FC

that means my box is full. You are posting this in the wrong thread.

That's a thought...

So actually, it's not the Navadmin but the data that is purged, updated and then made available for viewing.

I think he or she got that intel from our past Chief's board threads here on this forum...

yes we are, and team CNP never visits here and has not broken our comm code.

they must be on to our past recon team methods...

You know, I haven't heard a thing yet here about CNP callout...

that could be true. The website/ server issue is about delivering the message.

no, it's still hard down. The certificate error is the Navy not getting on the same page with the rest of the world about encryption.

Nope, BOL is hard down, still showing "dns lookup failed" so serious business.

After all these years of running this forum I can say unequivocally that you are correct - we should fear our own imaginations.

Then I'd have to go on a safari and bet one beer you are wrong.

Folks, I have the smelling salt at the first aid station on the bulkhead below vulture's row.

WOW!!

Don't know, I'm clueless about NEAOS but as far as what ibnfe6 said about profile sheets, I don't see the connection with Triad release as far as data goes. If they are different databases (and I'm sure they are). One would not impact the viewing (or release) of the other.

I don't think this is correct.

Interesting. Here's my thought and don't throw any rotten tomatoes at me. But I don't believe they would skip triad. They would fix BOL first to get it to triad, then do the 24 hr wait to release to the public.

I don't think they would all be on the same server.

now that makes more sense

Thanks for the update

That does not make sense. Taking out the DNS for the server kills the website not the server. Anyone know what is going on? Is there any communication as to why BOL is hard down?

Are people getting a DNS error for BOL?

?