>Or you could just edit the registry to disable remote access as noted in the >workaround section of the KB article. Takes about 2 minutes a server. >Nah, better to panic.
In my experience nothing will strike panic into the hearts of IT managers like the prospect of getting their big butts out of their chairs. "Disable remote access" you have got to be kidding. It won't be done. Anyone who relies on it getting done is asking for trouble. It is much safer to switch to a reliable DNS. Perhaps we need a way to cross check the results from multiple DNS servers? If one were polluted the inconsistent results would be a tip off that something is wrong. ************************************************************************ * ==> QUICK LIST-COMMAND REFERENCE - Put the following commands in <== * ==> the body of an email & send 'em to: [EMAIL PROTECTED] <== * Join the list: SUBSCRIBE COMPUTERGUYS-L Your Name * Too much mail? Try Daily Digests command: SET COMPUTERGUYS-L DIGEST * Tired of the List? Unsubscribe command: SIGNOFF COMPUTERGUYS-L * New address? From OLD address send: CHANGE COMPUTERGUYS-L YourNewAddress * Need more help? Send mail to: [EMAIL PROTECTED] ************************************************************************ * List archive at www.mail-archive.com/[email protected]/ * RSS at www.mail-archive.com/[email protected]/maillist.xml * Messages bearing the header "X-No-Archive: yes" will not be archived ************************************************************************
