«

This is failing any time I use the REPAIR for my wireless.
It also fails when when I use IPCONFIG /FLUSHDNS.

I found a KB artticle (919746), but attempting to retrieve it gives me the
NOT AVAILABLE message.

Any suggestions will be appreciated.

--
LPMORGAN

Hi
In General, you can debug the Network Settings of a computer by following
these steps.
Check the Network parameters in the Computer's Device Manager. Make sure
that the Network Card drivers are installed correctly; i.e. there is No IRQ
conflict, and No Ghost installation. http://www.ezlan.net/faq#ghost
Step Two Verify Basic network setting in the OS:
http://www.ezlan.net/Installing#verify If the above two Steps indicates that
every thing looks good but functionally it does not work.
Step Three. Check (and repair if necessary) the Socket Layers, Winsock, and
or refresh the TCP/IP Stack. http://www.ezlan.net/clean#refreshnet
If need to Reinstall; Log to this page it have a lot of links to
instructions for Windows Network
Installation -http://www.ezlan.net/Installing.html
Jack (MVP-Networking).

"LPMORGAN" <> wrote in message
news:E2DF2AB8-B777-4357-B55A-...
> This is failing any time I use the REPAIR for my wireless.
> It also fails when when I use IPCONFIG /FLUSHDNS.
>
> I found a KB artticle (919746), but attempting to retrieve it gives me the
> NOT AVAILABLE message.
>
> Any suggestions will be appreciated.
>
> --
> LPMORGAN

The computer network functions fine.
The DNS cache is the only issue I have found.
--
LPMORGAN


"Jack (MVP-Networking)." wrote:

> Hi
> In General, you can debug the Network Settings of a computer by following
> these steps.
> Check the Network parameters in the Computer's Device Manager. Make sure
> that the Network Card drivers are installed correctly; i.e. there is No IRQ
> conflict, and No Ghost installation. http://www.ezlan.net/faq#ghost
> Step Two Verify Basic network setting in the OS:
> http://www.ezlan.net/Installing#verify If the above two Steps indicates that
> every thing looks good but functionally it does not work.
> Step Three. Check (and repair if necessary) the Socket Layers, Winsock, and
> or refresh the TCP/IP Stack. http://www.ezlan.net/clean#refreshnet
> If need to Reinstall; Log to this page it have a lot of links to
> instructions for Windows Network
> Installation -http://www.ezlan.net/Installing.html
> Jack (MVP-Networking).
>
> "LPMORGAN" <> wrote in message
> news:E2DF2AB8-B777-4357-B55A-...
> > This is failing any time I use the REPAIR for my wireless.
> > It also fails when when I use IPCONFIG /FLUSHDNS.
> >
> > I found a KB artticle (919746), but attempting to retrieve it gives me the
> > NOT AVAILABLE message.
> >
> > Any suggestions will be appreciated.
> >
> > --
> > LPMORGAN
>
>
>

There is a setting in Comodo firewall which will block that. Other security
software might have something similar (monitoring DNS), though I haven't run
into it with the other firewalls I've tried.

"LPMORGAN" <> wrote in message
news:EDBC4130-7006-4943-A90A-...
> The computer network functions fine.
> The DNS cache is the only issue I have found.
> --
> LPMORGAN
>
>
> "Jack (MVP-Networking)." wrote:
>
>> Hi
>> In General, you can debug the Network Settings of a computer by following
>> these steps.
>> Check the Network parameters in the Computer's Device Manager. Make sure
>> that the Network Card drivers are installed correctly; i.e. there is No
>> IRQ
>> conflict, and No Ghost installation. http://www.ezlan.net/faq#ghost
>> Step Two Verify Basic network setting in the OS:
>> http://www.ezlan.net/Installing#verify If the above two Steps indicates
>> that
>> every thing looks good but functionally it does not work.
>> Step Three. Check (and repair if necessary) the Socket Layers, Winsock,
>> and
>> or refresh the TCP/IP Stack. http://www.ezlan.net/clean#refreshnet
>> If need to Reinstall; Log to this page it have a lot of links to
>> instructions for Windows Network
>> Installation -http://www.ezlan.net/Installing.html
>> Jack (MVP-Networking).
>>
>> "LPMORGAN" <> wrote in message
>> news:E2DF2AB8-B777-4357-B55A-...
>> > This is failing any time I use the REPAIR for my wireless.
>> > It also fails when when I use IPCONFIG /FLUSHDNS.
>> >
>> > I found a KB artticle (919746), but attempting to retrieve it gives me
>> > the
>> > NOT AVAILABLE message.
>> >
>> > Any suggestions will be appreciated.
>> >
>> > --
>> > LPMORGAN
>>
>>
>>

I have started using Comodo.
I will check it out.
--
LPMORGAN


"RalfG" wrote:

> There is a setting in Comodo firewall which will block that. Other security
> software might have something similar (monitoring DNS), though I haven't run
> into it with the other firewalls I've tried.
>
> "LPMORGAN" <> wrote in message
> news:EDBC4130-7006-4943-A90A-...
> > The computer network functions fine.
> > The DNS cache is the only issue I have found.
> > --
> > LPMORGAN
> >
> >
> > "Jack (MVP-Networking)." wrote:
> >
> >> Hi
> >> In General, you can debug the Network Settings of a computer by following
> >> these steps.
> >> Check the Network parameters in the Computer's Device Manager. Make sure
> >> that the Network Card drivers are installed correctly; i.e. there is No
> >> IRQ
> >> conflict, and No Ghost installation. http://www.ezlan.net/faq#ghost
> >> Step Two Verify Basic network setting in the OS:
> >> http://www.ezlan.net/Installing#verify If the above two Steps indicates
> >> that
> >> every thing looks good but functionally it does not work.
> >> Step Three. Check (and repair if necessary) the Socket Layers, Winsock,
> >> and
> >> or refresh the TCP/IP Stack. http://www.ezlan.net/clean#refreshnet
> >> If need to Reinstall; Log to this page it have a lot of links to
> >> instructions for Windows Network
> >> Installation -http://www.ezlan.net/Installing.html
> >> Jack (MVP-Networking).
> >>
> >> "LPMORGAN" <> wrote in message
> >> news:E2DF2AB8-B777-4357-B55A-...
> >> > This is failing any time I use the REPAIR for my wireless.
> >> > It also fails when when I use IPCONFIG /FLUSHDNS.
> >> >
> >> > I found a KB artticle (919746), but attempting to retrieve it gives me
> >> > the
> >> > NOT AVAILABLE message.
> >> >
> >> > Any suggestions will be appreciated.
> >> >
> >> > --
> >> > LPMORGAN
> >>
> >>
> >>
>
>
>

I ran into the same symptom the first time I tried to repair my wireless
connection after installing Comodo. There is a settings page in Comodo with
a number of options that are simply checked on or off, with the default
being ON for most of them. Monitoring DNS causes the problem with repairing
the wireless connection and monitoring DLLs can cause problems running
software, ie. some games. Unchecking the option allows the repair to
complete normally. Sorry I can't be more specific at the moment because I've
already uninstalled the firewall.

"LPMORGAN" <> wrote in message
news:8CEF4FD9-BF2D-4C88-AD6E-...
>I have started using Comodo.
> I will check it out.
> --
> LPMORGAN
>
>
> "RalfG" wrote:
>
>> There is a setting in Comodo firewall which will block that. Other
>> security
>> software might have something similar (monitoring DNS), though I haven't
>> run
>> into it with the other firewalls I've tried.
>>
>> "LPMORGAN" <> wrote in message
>> news:EDBC4130-7006-4943-A90A-...
>> > The computer network functions fine.
>> > The DNS cache is the only issue I have found.
>> > --
>> > LPMORGAN
>> >
>> >
>> > "Jack (MVP-Networking)." wrote:
>> >
>> >> Hi
>> >> In General, you can debug the Network Settings of a computer by
>> >> following
>> >> these steps.
>> >> Check the Network parameters in the Computer's Device Manager. Make
>> >> sure
>> >> that the Network Card drivers are installed correctly; i.e. there is
>> >> No
>> >> IRQ
>> >> conflict, and No Ghost installation. http://www.ezlan.net/faq#ghost
>> >> Step Two Verify Basic network setting in the OS:
>> >> http://www.ezlan.net/Installing#verify If the above two Steps
>> >> indicates
>> >> that
>> >> every thing looks good but functionally it does not work.
>> >> Step Three. Check (and repair if necessary) the Socket Layers,
>> >> Winsock,
>> >> and
>> >> or refresh the TCP/IP Stack. http://www.ezlan.net/clean#refreshnet
>> >> If need to Reinstall; Log to this page it have a lot of links to
>> >> instructions for Windows Network
>> >> Installation -http://www.ezlan.net/Installing.html
>> >> Jack (MVP-Networking).
>> >>
>> >> "LPMORGAN" <> wrote in message
>> >> news:E2DF2AB8-B777-4357-B55A-...
>> >> > This is failing any time I use the REPAIR for my wireless.
>> >> > It also fails when when I use IPCONFIG /FLUSHDNS.
>> >> >
>> >> > I found a KB artticle (919746), but attempting to retrieve it gives
>> >> > me
>> >> > the
>> >> > NOT AVAILABLE message.
>> >> >
>> >> > Any suggestions will be appreciated.
>> >> >
>> >> > --
>> >> > LPMORGAN
>> >>
>> >>
>> >>
>>
>>
>>

Thanks RalfG.

Once you put me on to it, I joined a Comodo forum and posted the question.
Someone suggested disabling "Security->Advanced->Monitor DNS requests" can
solve this problem. I tried it and found it worked.

You put me on the trail to the answer.

Comodo is a pretty good free firewall for a frequent traveler.
--
LPMORGAN


"RalfG" wrote:

> I ran into the same symptom the first time I tried to repair my wireless
> connection after installing Comodo. There is a settings page in Comodo with
> a number of options that are simply checked on or off, with the default
> being ON for most of them. Monitoring DNS causes the problem with repairing
> the wireless connection and monitoring DLLs can cause problems running
> software, ie. some games. Unchecking the option allows the repair to
> complete normally. Sorry I can't be more specific at the moment because I've
> already uninstalled the firewall.
>
> "LPMORGAN" <> wrote in message
> news:8CEF4FD9-BF2D-4C88-AD6E-...
> >I have started using Comodo.
> > I will check it out.
> > --
> > LPMORGAN
> >
> >
> > "RalfG" wrote:
> >
> >> There is a setting in Comodo firewall which will block that. Other
> >> security
> >> software might have something similar (monitoring DNS), though I haven't
> >> run
> >> into it with the other firewalls I've tried.
> >>
> >> "LPMORGAN" <> wrote in message
> >> news:EDBC4130-7006-4943-A90A-...
> >> > The computer network functions fine.
> >> > The DNS cache is the only issue I have found.
> >> > --
> >> > LPMORGAN
> >> >
> >> >
> >> > "Jack (MVP-Networking)." wrote:
> >> >
> >> >> Hi
> >> >> In General, you can debug the Network Settings of a computer by
> >> >> following
> >> >> these steps.
> >> >> Check the Network parameters in the Computer's Device Manager. Make
> >> >> sure
> >> >> that the Network Card drivers are installed correctly; i.e. there is
> >> >> No
> >> >> IRQ
> >> >> conflict, and No Ghost installation. http://www.ezlan.net/faq#ghost
> >> >> Step Two Verify Basic network setting in the OS:
> >> >> http://www.ezlan.net/Installing#verify If the above two Steps
> >> >> indicates
> >> >> that
> >> >> every thing looks good but functionally it does not work.
> >> >> Step Three. Check (and repair if necessary) the Socket Layers,
> >> >> Winsock,
> >> >> and
> >> >> or refresh the TCP/IP Stack. http://www.ezlan.net/clean#refreshnet
> >> >> If need to Reinstall; Log to this page it have a lot of links to
> >> >> instructions for Windows Network
> >> >> Installation -http://www.ezlan.net/Installing.html
> >> >> Jack (MVP-Networking).
> >> >>
> >> >> "LPMORGAN" <> wrote in message
> >> >> news:E2DF2AB8-B777-4357-B55A-...
> >> >> > This is failing any time I use the REPAIR for my wireless.
> >> >> > It also fails when when I use IPCONFIG /FLUSHDNS.
> >> >> >
> >> >> > I found a KB artticle (919746), but attempting to retrieve it gives
> >> >> > me
> >> >> > the
> >> >> > NOT AVAILABLE message.
> >> >> >
> >> >> > Any suggestions will be appreciated.
> >> >> >
> >> >> > --
> >> >> > LPMORGAN
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>