WLAN is on, Network Connection status is connected, but no Internet???

[Michael]

Running Windows XP sp2 on a Compaq Presario notebook M2105US with Broadcom
802.11b/g builti-in. Linksys WRT54G wireless router.

I can connect to the Internet no problem but the problem is that after the
computer is idle for something more than 4 hours or so, it will not drop its
conneciton to the Internet after waking up even though everything appears to
be normal. By normal I mean that the router "sees"s the computer, the
computer reports that is connected to the router with excellent signal
strength. But I can't ping anything outside of my local network and I can't
connect to anything on the Internet until I logout out and login again or
restart.

Compaq tech support said this is normal behavior for Windows XP which I find
hard to believe. Microsoft won't talk to me unless I pay them so I'm hoping
someone here might have some ideas.

Here are the last three entries in my events log...

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4202
Date: 8/9/2005
Time: 8:21:22 AM
User: N/A
Computer: COMPAQ
Description:
The system detected that network adapter Broadcom 802.11b/g WLAN - Packet
Scheduler Miniport 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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 6a 10 00 40 ....j..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


Event Type: Information
Event Source: BROWSER
Event Category: None
Event ID: 8033
Date: 8/9/2005
Time: 8:21:22 AM
User: N/A
Computer: COMPAQ
Description:
The browser has forced an election on network
\Device\NetBT_Tcpip_{A4333E2D-06BB-4ABB-8E26-CA03BA5023A4} because a master
browser was stopped.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4201
Date: 8/9/2005
Time: 8:22:27 AM
User: N/A
Computer: COMPAQ
Description:
The system detected that network adapter Broadcom 802.11b/g WLAN - Packet
Scheduler Miniport was connected to the network, and has initiated normal
operation over the network adapter.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

 

[Richard G. Harper]

This is, unfortunately, not uncommon behaviour when you let your network
connection go into standby mode. You could try using the Power Management
tab in Device Manager for the network adapter to tell Windows not to power
it down, or you could try newer drivers, or you could use only standby modes
that don't cause problems.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Michael]

Pardon my ignorance, but what standby modes are available to me that might
not cause this behavior?

I'd also like to know why "repair"ing the connection doesn't reconnect me
to the Internet. Why do I have to fully logout and login in again to
re-establish the connection to the Internet? It seems there should be an
alternate solution, such as "repair"ing the connection...or turning off and
then back on the WLAN... or disabling then renabling the Network Connection.
Yet none of these methods work. Only logging out and then back in, or
restarting will re-establish my INternet connection.

Is this considered a bug in XP? Does XP Professional exhibit this anomaly?
Will sp3 fix this problem.

Questions questions questions.

Michael

This is, unfortunately, not uncommon behaviour when you let your network
connection go into standby mode. You could try using the Power Management
tab in Device Manager for the network adapter to tell Windows not to power
it down, or you could try newer drivers, or you could use only standby
modes that don't cause problems.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Running Windows XP sp2 on a Compaq Presario notebook M2105US with
Broadcom 802.11b/g builti-in. Linksys WRT54G wireless router.

I can connect to the Internet no problem but the problem is that after
the computer is idle for something more than 4 hours or so, it will not
drop its conneciton to the Internet after waking up even though
everything appears to be normal. By normal I mean that the router "sees"s
the computer, the computer reports that is connected to the router with
excellent signal strength. But I can't ping anything outside of my local
network and I can't connect to anything on the Internet until I logout
out and login again or restart.

Compaq tech support said this is normal behavior for Windows XP which I
find hard to believe. Microsoft won't talk to me unless I pay them so I'm
hoping someone here might have some ideas.

Here are the last three entries in my events log...

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4202
Date: 8/9/2005
Time: 8:21:22 AM
User: N/A
Computer: COMPAQ
Description:
The system detected that network adapter Broadcom 802.11b/g WLAN - Packet
Scheduler Miniport 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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 6a 10 00 40 ....j..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


Event Type: Information
Event Source: BROWSER
Event Category: None
Event ID: 8033
Date: 8/9/2005
Time: 8:21:22 AM
User: N/A
Computer: COMPAQ
Description:
The browser has forced an election on network
\Device\NetBT_Tcpip_{A4333E2D-06BB-4ABB-8E26-CA03BA5023A4} because a
master browser was stopped.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4201
Date: 8/9/2005
Time: 8:22:27 AM
User: N/A
Computer: COMPAQ
Description:
The system detected that network adapter Broadcom 802.11b/g WLAN - Packet
Scheduler Miniport was connected to the network, and has initiated normal
operation over the network adapter.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

 

[Michael]

I'm cautiously optimistic that my problem has been solved. It had nothing to
do with my standby modes and several other suggestions that people were
making.

I read elsewhere that there was a problem with the Broadcom NIC that caused
this problem for many people. Upon checking the driver version I discovered
that there was a newer version available. So I obtained and installed the
new driver. This seems to have fixed the problem for me. Yeah!

I went to my Wireless Network Configuration, where it says "Connect using"
is where it indiates the Broadcom 802.11b/g WLAN. I clicked on the configure
button and then in the properties window, clicked on Update Driver. Voila.
Fixed. I hope.

Michael

Pardon my ignorance, but what standby modes are available to me that might
not cause this behavior?

I'd also like to know why "repair"ing the connection doesn't reconnect me
to the Internet. Why do I have to fully logout and login in again to
re-establish the connection to the Internet? It seems there should be an
alternate solution, such as "repair"ing the connection...or turning off
and then back on the WLAN... or disabling then renabling the Network
Connection. Yet none of these methods work. Only logging out and then back
in, or restarting will re-establish my INternet connection.

Is this considered a bug in XP? Does XP Professional exhibit this anomaly?
Will sp3 fix this problem.

Questions questions questions.

Michael

This is, unfortunately, not uncommon behaviour when you let your network
connection go into standby mode. You could try using the Power
Management tab in Device Manager for the network adapter to tell Windows
not to power it down, or you could try newer drivers, or you could use
only standby modes that don't cause problems.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Running Windows XP sp2 on a Compaq Presario notebook M2105US with
Broadcom 802.11b/g builti-in. Linksys WRT54G wireless router.

I can connect to the Internet no problem but the problem is that after
the computer is idle for something more than 4 hours or so, it will not
drop its conneciton to the Internet after waking up even though
everything appears to be normal. By normal I mean that the router
"sees"s the computer, the computer reports that is connected to the
router with excellent signal strength. But I can't ping anything outside
of my local network and I can't connect to anything on the Internet
until I logout out and login again or restart.

Compaq tech support said this is normal behavior for Windows XP which I
find hard to believe. Microsoft won't talk to me unless I pay them so
I'm hoping someone here might have some ideas.

Here are the last three entries in my events log...

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4202
Date: 8/9/2005
Time: 8:21:22 AM
User: N/A
Computer: COMPAQ
Description:
The system detected that network adapter Broadcom 802.11b/g WLAN -
Packet Scheduler Miniport 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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 6a 10 00 40 ....j..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........


Event Type: Information
Event Source: BROWSER
Event Category: None
Event ID: 8033
Date: 8/9/2005
Time: 8:21:22 AM
User: N/A
Computer: COMPAQ
Description:
The browser has forced an election on network
\Device\NetBT_Tcpip_{A4333E2D-06BB-4ABB-8E26-CA03BA5023A4} because a
master browser was stopped.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4201
Date: 8/9/2005
Time: 8:22:27 AM
User: N/A
Computer: COMPAQ
Description:
The system detected that network adapter Broadcom 802.11b/g WLAN -
Packet Scheduler Miniport was connected to the network, and has
initiated normal operation over the network adapter.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 02 00 50 00 ......P.
0008: 00 00 00 00 69 10 00 40 ....i..@
0010: 02 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........