"Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...
> In news:0Z62b.7565$(E-Mail Removed),
> TIM ROBERTS <(E-Mail Removed)> posted their thoughts, then I offered
> mine
>
> Tim, not sure if you're aware of it, but there has been some anamolies
> reported based on SP4. The main issue is if a DC with the AD DNS name being
> a single label name (no TLD), will not allow registration without modifying
> a reg entry to allow single label names. There are also some minor issues
> with AD names with a valid DNS names with a correct DNS configuration.
> That's the one I'm concerned about. In a case like this, an nslookup may not
> return the correct response from your own domain name, but of a return of an
> external name would be correct (provided the Forwarders have the RA bit
> o"on").
>
> I was concerned of the latter, DC or not, with SP4, but apparently it was
> the personal firewall that was the problem.
>
> I have reported it to my MVP lead and will post the results in the public
> forum once I get the go-ahead.
>
> --
> Regards,
> Ace
>
> Please direct all replies to the newsgroup so all can benefit.
>
> Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
> Microsoft Windows MVP - Active Directory

I have the same problem, same scenario on my home Win2K machine. Recently
updated to SP4 with the MSBlast patch installed and running ZoneAlarm 4
Pro. Even with ZA4 disabled I still cannot connect to the dialup
PPP server at work. Dialup starts and then before the terminal login
window displays I get a "Cannot load dialog error 0XC000007A". This
configuration was fine prior to the SP4/MSBlast patch install.

News diving seems to indicate others have experienced this same
problem and it is a result of DNS config issues introduced in SP4. I
just need a workaround at this point. Should have backed up system
completely b4 SP4 install. Oh well, hopefully someone will provide
a fix or workaround suggestion.

Thanks,
Scott

In news:(E-Mail Removed),
Scott Kay <(E-Mail Removed)> posted their thoughts, then I offered mine
> "Ace Fekay [MVP]"
> <PleaseSubstituteMyActualFirstName&(E-Mail Removed)> wrote in
> message news:<#(E-Mail Removed)>...
>> In news:0Z62b.7565$(E-Mail Removed),
>> TIM ROBERTS <(E-Mail Removed)> posted their thoughts, then I
>> offered
>> mine
>>
>> Tim, not sure if you're aware of it, but there has been some
>> anamolies
>> reported based on SP4. The main issue is if a DC with the AD DNS
>> name being
>> a single label name (no TLD), will not allow registration without
>> modifying
>> a reg entry to allow single label names. There are also some minor
>> issues
>> with AD names with a valid DNS names with a correct DNS
>> configuration.
>> That's the one I'm concerned about. In a case like this, an nslookup
>> may not
>> return the correct response from your own domain name, but of a
>> return of an
>> external name would be correct (provided the Forwarders have the RA
>> bit
>> o"on").
>>
>> I was concerned of the latter, DC or not, with SP4, but apparently
>> it was
>> the personal firewall that was the problem.
>>
>> I have reported it to my MVP lead and will post the results in the
>> public
>> forum once I get the go-ahead.
>>
>> --
>> Regards,
>> Ace
>>
>> Please direct all replies to the newsgroup so all can benefit.
>>
>> Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
>> Microsoft Windows MVP - Active Directory
>
> I have the same problem, same scenario on my home Win2K machine.
> Recently
> updated to SP4 with the MSBlast patch installed and running ZoneAlarm
> 4
> Pro. Even with ZA4 disabled I still cannot connect to the dialup
> PPP server at work. Dialup starts and then before the terminal login
> window displays I get a "Cannot load dialog error 0XC000007A". This
> configuration was fine prior to the SP4/MSBlast patch install.
>
> News diving seems to indicate others have experienced this same
> problem and it is a result of DNS config issues introduced in SP4. I
> just need a workaround at this point. Should have backed up system
> completely b4 SP4 install. Oh well, hopefully someone will provide
> a fix or workaround suggestion.
>
> Thanks,
> Scott

Sorry Scott, can't help at this point other than suggesting to remove ZA,
delete your PPP connection, and recreate the PPP connection to see if that
helps.

That error:
Cannot load dialog error 0XC000007A
Is normally a "Procedure not found" error which I've seen from a
misconfigured installation or parameter. Hence, the suggestion to recreate
the connection.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Scott,
Based on a thread in .networking, I resolved a similar
problem by creating a new dial entry. I can only guess
that the old one was either damaged or refers to a now non
existing dialog.
---Paul

>-----Original Message-----
>"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&(E-Mail Removed)
> wrote in message
news:<#(E-Mail Removed)>...
>> In news:0Z62b.7565$(E-Mail Removed),
>> TIM ROBERTS <(E-Mail Removed)> posted their
thoughts, then I offered
>> mine
>>
>> Tim, not sure if you're aware of it, but there has been
some anamolies
>> reported based on SP4. The main issue is if a DC with
the AD DNS name being
>> a single label name (no TLD), will not allow
registration without modifying
>> a reg entry to allow single label names. There are also
some minor issues
>> with AD names with a valid DNS names with a correct DNS
configuration.
>> That's the one I'm concerned about. In a case like
this, an nslookup may not
>> return the correct response from your own domain name,
but of a return of an
>> external name would be correct (provided the Forwarders
have the RA bit
>> o"on").
>>
>> I was concerned of the latter, DC or not, with SP4, but
apparently it was
>> the personal firewall that was the problem.
>>
>> I have reported it to my MVP lead and will post the
results in the public
>> forum once I get the go-ahead.
>>
>> --
>> Regards,
>> Ace
>>
>> Please direct all replies to the newsgroup so all can
benefit.
>>
>> Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
>> Microsoft Windows MVP - Active Directory
>
>I have the same problem, same scenario on my home Win2K
machine. Recently
>updated to SP4 with the MSBlast patch installed and
running ZoneAlarm 4
>Pro. Even with ZA4 disabled I still cannot connect to the
dialup
>PPP server at work. Dialup starts and then before the
terminal login
>window displays I get a "Cannot load dialog error
0XC000007A". This
>configuration was fine prior to the SP4/MSBlast patch
install.
>
>News diving seems to indicate others have experienced
this same
>problem and it is a result of DNS config issues
introduced in SP4. I
>just need a workaround at this point. Should have backed
up system
>completely b4 SP4 install. Oh well, hopefully someone
will provide
>a fix or workaround suggestion.
>
>Thanks,
>Scott

[TheGuitarCustomShop]

I have had this problem lately... a Windows2000 machine recently just started intermittently "losing DNS".

I could NSLOOKUP anything, and get the correct answer from the command line. But somehow this information was not getting passed on to the operating system - web browsers could not get DNS resolution! (connectivity was OK, as I could surf to any website just fine if i knew it's actual IP address...)

DNS resolver cache kept showing EMPTY- wierd!

Anyway, i finally found a WORKAROUND - to get DNS back, I just made a little batch file containing one line:

ipconfig /registerdns

run this, and DNS WORKS AGAIN INSTANTLY!!!

i hope this helps somebody out there... :-)