Wireless adaptor disconnecting at night - how to batch the "repair"option?

Hi
The Repair is a serious of commands.
Quote from, http://technet.microsoft.com/en-us/l.../bb727023.aspx
The tasks that are performed by Network Connection Repair are the following:
Checks whether DHCP is enabled and, if enabled, sends a broadcast DHCP
Request message to refresh the IPv4 address configuration.
Flushes the ARP cache. This is equivalent to the arp -d * command.
Flushest and reloads the DNS client resolver cache with entries from the
Hosts file. This is equivalent to the ipconfig /flushdns command.
Re-registers DNS names using DNS dynamic update. This is equivalent to the
ipconfig /registerdns command.
Flushes and reloads the NetBIOS name cache with #PRE entries in the Lmhosts
file. This is equivalent to the nbtstat -R command.
Releases and then re-registers NetBIOS names with the Windows Internet Name
Service (WINS). This is equivalent to the nbtstat -RR command.
End of Quote
You can write a batch file that would execute most of this process.
Jack (MVP-Networking).


"Jamie Furlong" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Basically, I'm asking the same question as the person in this post:
> http://groups.google.co.uk/group/mic...4da139c5d89e71
>
> Essentially:
> "XP's wireless connection manager has an option to "Repair" wireless
> network connections, that disables then re-enables the adapter. My
> question is this, what's the filen this command runs. I want to create a
> batch file that just runs this command"
>
> In fact, I want to do something extra - I want to run a batch file every
> hour. What happens is that sometime between 3 and 6am, reliably every
> night, my adaptor disconnects, and can't reconnect itself. As soon as I do
> "repair", I'm back.
>
> Later in the thread, someone pointed to
> http://support.microsoft.com/kb/289256/en-us
> But that doesn't seem to actually repair the adaptor. Here's what all
> happens at about the same time (from event viewer)
>
> --------------------------------
> The system detected that network adapter PRISM 802.11g Wireless Adapter
> was disconnected from the network, and the adapter's network configuration
> has been released. If the network adapter was not disconnected, this may
> indicate that it has malfunctioned. Please contact your vendor for updated
> drivers.
> --------------------------------
>
> Well, there's no updated driver, and it uses the windows wireless config,
> not its own config. And....
>
> --------------------------------
> The browser has forced an election on network
> \Device\NetBT_Tcpip_{F2XXXXXX-XXXX-4C1C-XXX-91XXXXX03} because a master
> browser was stopped. (x's my addition!)
> --------------------------------
>
> Also...
>
> --------------------------------
> IPSec Services: IPSec Services failed to get the complete list of network
> interfaces on the machine. This can be a potential security hazard to the
> machine since some of the network interfaces may not get the protection as
> desired by the applied IPSec filters. Please run IPSec monitor snap-in to
> further diagnose the problem.
> --------------------------------
>
> So, what I was hoping was that, if it can't reconnect itself, it might
> just repair itself hourly, so, broken or not, it can come back to life.
>
> Thanks!

Basically, I'm asking the same question as the person in this post:
http://groups.google.co.uk/group/mic...4da139c5d89e71

Essentially:
"XP's wireless connection manager has an option to "Repair" wireless
network connections, that disables then re-enables the adapter. My
question is this, what's the filen this command runs. I want to create a
batch file that just runs this command"

In fact, I want to do something extra - I want to run a batch file every
hour. What happens is that sometime between 3 and 6am, reliably every
night, my adaptor disconnects, and can't reconnect itself. As soon as I
do "repair", I'm back.

Later in the thread, someone pointed to
http://support.microsoft.com/kb/289256/en-us
But that doesn't seem to actually repair the adaptor. Here's what all
happens at about the same time (from event viewer)

--------------------------------
The system detected that network adapter PRISM 802.11g Wireless Adapter
was disconnected from the network, and the adapter's network
configuration has been released. If the network adapter was not
disconnected, this may indicate that it has malfunctioned. Please
contact your vendor for updated drivers.
--------------------------------

Well, there's no updated driver, and it uses the windows wireless
config, not its own config. And....

--------------------------------
The browser has forced an election on network
\Device\NetBT_Tcpip_{F2XXXXXX-XXXX-4C1C-XXX-91XXXXX03} because a master
browser was stopped. (x's my addition!)
--------------------------------

Also...

--------------------------------
IPSec Services: IPSec Services failed to get the complete list of
network interfaces on the machine. This can be a potential security
hazard to the machine since some of the network interfaces may not get
the protection as desired by the applied IPSec filters. Please run IPSec
monitor snap-in to further diagnose the problem.
--------------------------------

So, what I was hoping was that, if it can't reconnect itself, it might
just repair itself hourly, so, broken or not, it can come back to life.

Thanks!

Well, the eventlog message "The system detected that network adapter PRISM
802.11g Wireless Adapter
was disconnected from the network..."
is the standard message issued by tcpip when it sees the netcard medium
disconnected.
It does not indicate any malfunction.

But when the adapter is disconnected, ipconfig /renew won't, so how the
repair works for you?
When you do repair, is the adapter connected or not?

--PA


"Jamie Furlong" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> Basically, I'm asking the same question as the person in this post:
> http://groups.google.co.uk/group/mic...4da139c5d89e71
>
> Essentially:
> "XP's wireless connection manager has an option to "Repair" wireless
> network connections, that disables then re-enables the adapter. My
> question is this, what's the filen this command runs. I want to create a
> batch file that just runs this command"
>
> In fact, I want to do something extra - I want to run a batch file every
> hour. What happens is that sometime between 3 and 6am, reliably every
> night, my adaptor disconnects, and can't reconnect itself. As soon as I do
> "repair", I'm back.
>
> Later in the thread, someone pointed to
> http://support.microsoft.com/kb/289256/en-us
> But that doesn't seem to actually repair the adaptor. Here's what all
> happens at about the same time (from event viewer)
>
> --------------------------------
> The system detected that network adapter PRISM 802.11g Wireless Adapter
> was disconnected from the network, and the adapter's network configuration
> has been released. If the network adapter was not disconnected, this may
> indicate that it has malfunctioned. Please contact your vendor for updated
> drivers.
> --------------------------------
>
> Well, there's no updated driver, and it uses the windows wireless config,
> not its own config. And....
>
> --------------------------------
> The browser has forced an election on network
> \Device\NetBT_Tcpip_{F2XXXXXX-XXXX-4C1C-XXX-91XXXXX03} because a master
> browser was stopped. (x's my addition!)
> --------------------------------
>
> Also...
>
> --------------------------------
> IPSec Services: IPSec Services failed to get the complete list of network
> interfaces on the machine. This can be a potential security hazard to the
> machine since some of the network interfaces may not get the protection as
> desired by the applied IPSec filters. Please run IPSec monitor snap-in to
> further diagnose the problem.
> --------------------------------
>
> So, what I was hoping was that, if it can't reconnect itself, it might
> just repair itself hourly, so, broken or not, it can come back to life.
>
> Thanks!

can you try a different wireless adapter? Prism was bought out a few
times, but no company has existed for several years and there is no
real source for drivers for Prism based cards.

On Wed, 02 Apr 2008 23:05:35 +0100, Jamie Furlong
<(E-Mail Removed)> wrote:

>
>--------------------------------
>The system detected that network adapter PRISM 802.11g Wireless Adapter
>was disconnected from the network, and the adapter's network
>configuration has been released. If the network adapter was not
>disconnected, this may indicate that it has malfunctioned. Please
>contact your vendor for updated drivers.
>--------------------------------
>
>Well, there's no updated driver, and it uses the windows wireless
>config, not its own config.
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

Three replies in one here

Jack (MVP-Networking). wrote:
> Hi
> The Repair is a serious of commands.
> Quote from, http://technet.microsoft.com/en-us/l.../bb727023.aspx
> You can write a batch file that would execute most of this process.
> Jack (MVP-Networking).

Hmm, this seems to only work when the network card hasn't disconnected
itself. It doesn't seem to do the full "disabling network card" that
repair does.

Pavel A. wrote:
> Well, the eventlog message "The system detected that network adapter
> PRISM 802.11g Wireless Adapter
> was disconnected from the network..."
> is the standard message issued by tcpip when it sees the netcard medium
> disconnected.
> It does not indicate any malfunction.
>
> But when the adapter is disconnected, ipconfig /renew won't, so how the
> repair works for you?
> When you do repair, is the adapter connected or not?

The adaptor is on the motherboard - it cannot be physically removed.

Barb Bowman wrote:
> can you try a different wireless adapter? Prism was bought out a few
> times, but no company has existed for several years and there is no
> real source for drivers for Prism based cards.

Tried other adaptors, most recently the netgear WPN111. Despite spending
HOURS making 100% sure I have all the latest motherboard/usb/etc drivers
and firmware, it still reliably blue-screens or freezes my PC, oddly
enough, at around the same time this adaptor put itself out of action
(no, I don't have them enabled at the same time!)

Thanks for help so far

is the blue screen message always the same and what is it?
is there any information in event viewer?
is there anything else attached to the pc?
exactly what pc is this?

On Fri, 04 Apr 2008 00:02:53 +0100, Jamie Furlong
<(E-Mail Removed)> wrote:

>Tried other adaptors, most recently the netgear WPN111. Despite spending
>HOURS making 100% sure I have all the latest motherboard/usb/etc drivers
>and firmware, it still reliably blue-screens or freezes my PC, oddly
>enough, at around the same time this adaptor put itself out of action
>(no, I don't have them enabled at the same time!)
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

Barb Bowman wrote:
> is the blue screen message always the same and what is it?

IIRC, something about usbhci.sys and wpn111.sys - oddly, it almost
always occurs with uploads. I can make it crash reliably by uploading a
video to Facebook, for example. On the other hand, it can happily
download for hours in a row previous to that.

> is there any information in event viewer?

Yes - (from my original post (reply continues below quote))

> (from event viewer)
>
> --------------------------------
> The system detected that network adapter PRISM 802.11g Wireless Adapter
> was disconnected from the network, and the adapter's network
> configuration has been released. If the network adapter was not
> disconnected, this may indicate that it has malfunctioned. Please
> contact your vendor for updated drivers.
> --------------------------------
>
> Well, there's no updated driver, and it uses the windows wireless
> config, not its own config. And....
>
> --------------------------------
> The browser has forced an election on network
> \Device\NetBT_Tcpip_{F2XXXXXX-XXXX-4C1C-XXX-91XXXXX03} because a master
> browser was stopped. (x's my addition!)
> --------------------------------
>
> Also...
>
> --------------------------------
> IPSec Services: IPSec Services failed to get the complete list of
> network interfaces on the machine. This can be a potential security
> hazard to the machine since some of the network interfaces may not get
> the protection as desired by the applied IPSec filters. Please run IPSec
> monitor snap-in to further diagnose the problem.
> --------------------------------

> is there anything else attached to the pc?

Yes, but tried disconnecting all but USB mouse and wireless keyboard (no
choice about having them!)

> exactly what pc is this?

Medion MD8083

PRISM is no longer. It is just going to be painful for you until you
replace the wireless adapter with one that is properly supported and
more recent. It looks like a driver issue and there is no driver
development being done.

On Tue, 08 Apr 2008 18:04:19 +0100, Jamie Furlong
<(E-Mail Removed)> wrote:

>Barb Bowman wrote:
>> is the blue screen message always the same and what is it?
>
>IIRC, something about usbhci.sys and wpn111.sys - oddly, it almost
>always occurs with uploads. I can make it crash reliably by uploading a
>video to Facebook, for example. On the other hand, it can happily
>download for hours in a row previous to that.
>
>> is there any information in event viewer?
>
>Yes - (from my original post (reply continues below quote))
>
> > (from event viewer)
> >
> > --------------------------------
> > The system detected that network adapter PRISM 802.11g Wireless Adapter
> > was disconnected from the network, and the adapter's network
> > configuration has been released. If the network adapter was not
> > disconnected, this may indicate that it has malfunctioned. Please
> > contact your vendor for updated drivers.
> > --------------------------------
> >
> > Well, there's no updated driver, and it uses the windows wireless
> > config, not its own config. And....
> >
> > --------------------------------
> > The browser has forced an election on network
> > \Device\NetBT_Tcpip_{F2XXXXXX-XXXX-4C1C-XXX-91XXXXX03} because a master
> > browser was stopped. (x's my addition!)
> > --------------------------------
> >
> > Also...
> >
> > --------------------------------
> > IPSec Services: IPSec Services failed to get the complete list of
> > network interfaces on the machine. This can be a potential security
> > hazard to the machine since some of the network interfaces may not get
> > the protection as desired by the applied IPSec filters. Please run IPSec
> > monitor snap-in to further diagnose the problem.
> > --------------------------------
>
>> is there anything else attached to the pc?
>
>Yes, but tried disconnecting all but USB mouse and wireless keyboard (no
>choice about having them!)
>
>> exactly what pc is this?
>
>Medion MD8083
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

Hi Barb;

Thanks - yes, I know Prism is no longer, but at least it doesn't bring
down the whole PC when it disconnects. When any USB adaptor crashes, it
bluescreens the whole system. So between clicking "repair" and retyping
a whole document, I know which is less painful. The problem is when it's
5am and it disconnects...

Barb Bowman wrote:
> PRISM is no longer. It is just going to be painful for you until you
> replace the wireless adapter with one that is properly supported and
> more recent. It looks like a driver issue and there is no driver
> development being done.
>
> On Tue, 08 Apr 2008 18:04:19 +0100, Jamie Furlong
> <(E-Mail Removed)> wrote:
>
>> Barb Bowman wrote:
>>> is the blue screen message always the same and what is it?
>> IIRC, something about usbhci.sys and wpn111.sys - oddly, it almost
>> always occurs with uploads. I can make it crash reliably by uploading a
>> video to Facebook, for example. On the other hand, it can happily
>> download for hours in a row previous to that.
>>
>>> is there any information in event viewer?
>> Yes - (from my original post (reply continues below quote))
>>
>>> (from event viewer)
>>>
>>> --------------------------------
>>> The system detected that network adapter PRISM 802.11g Wireless Adapter
>>> was disconnected from the network, and the adapter's network
>>> configuration has been released. If the network adapter was not
>>> disconnected, this may indicate that it has malfunctioned. Please
>>> contact your vendor for updated drivers.
>>> --------------------------------
>>>
>>> Well, there's no updated driver, and it uses the windows wireless
>>> config, not its own config. And....
>>>
>>> --------------------------------
>>> The browser has forced an election on network
>>> \Device\NetBT_Tcpip_{F2XXXXXX-XXXX-4C1C-XXX-91XXXXX03} because a master
>>> browser was stopped. (x's my addition!)
>>> --------------------------------
>>>
>>> Also...
>>>
>>> --------------------------------
>>> IPSec Services: IPSec Services failed to get the complete list of
>>> network interfaces on the machine. This can be a potential security
>>> hazard to the machine since some of the network interfaces may not get
>>> the protection as desired by the applied IPSec filters. Please run IPSec
>>> monitor snap-in to further diagnose the problem.
>>> --------------------------------
>>> is there anything else attached to the pc?
>> Yes, but tried disconnecting all but USB mouse and wireless keyboard (no
>> choice about having them!)
>>
>>> exactly what pc is this?
>> Medion MD8083
> --
>
> Barb Bowman
> MS-MVP
> http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
> http://blogs.digitalmediaphile.com/barb/

smlunatick wrote:

> Have you considered setting up a scheduled XP "reboot" shortly after
> the wireless adapter disappeared. There are numerous examples of
> scheduling a reboot.

Ah, interesting. I didn't realise you could have something act as a
result of something else. I thought scheduling just mean "at 4am, do
this" or "at x interval, do that".

This is new to me - so, how does it work? Does it watch for an event in
eventvwr, then when it sees "the wireless adaptor has disconnected", it
would then do the "repair" option automatically? Sounds like a solution.

Hmmm, now I think of it, would it be possible to batch up a command that
would ping something every minute, and when the destination was
unreachable, it would do the repair?

All the above still leaves me with the problem that the sequence of
events detailed in repair don't seem to actually disable then re-enable
the wireless adaptor in the same way that acutally clicking "repair" does.