ted ping, removed it and saved,
ping resolution immediately failed again; just like it is supposed to.
As I requested in my previous post, please provide us with detailed
instructions on how to recreate this issue.
t
On 4/19/06 4:43 PM, "John Biederstedt" <[EMAIL PROTECTED]
Actually, according to microsoft, the dns client in XP was *intended* to
check to see if a dns lookup had failed earlier before going to the
hosts file.
We did ping the internal domain controller, added the bogus FQDN, and
tried again. None of that worked, because prior to the VPN working, and
lo