Hi there,
I recenctly bought a new machine that has Vista Basic installed
on it. I installed the latest drivers for my Netgear wireless adapter which
are supposed to be Vista compatible. However, although I can get connected,
I often have to mess around with the networking settings first and then the
connection will only last around 15 minutes before the adapters led stops
flashing. I then have to reboot to get a connection again. I tried the
adapter back n my old XP machine and it is fine. As soon as the XP machine
boots, the led indicator starts flashing and it doesn't stop until you shut
down. With the Vista machine, the adapter often doesn't start flashing
until you actually connect and then it will just stop after a short while.
I've been messing around with this for weeks now and got nowhere. I would
have suspected the adapter drivers, but it seems as though there are a lot
of other people with the same problem on different adapters, which would
suggest a fundamental problem with Vista.

Can anyone shed any light?

which netgear adapter? what router exactly and what version firmware
is in the router? please post text results of ipconfig /all as a
reply to this post
http://digitalmediaphile.wordpress.c...t-text-output/


On Tue, 26 Feb 2008 11:54:30 -0000, "Waldy"
wrote:

Hi there,
I recenctly bought a new machine that has Vista Basic installed
on it. I installed the latest drivers for my Netgear wireless adapter which
are supposed to be Vista compatible. However, although I can get connected,
I often have to mess around with the networking settings first and then the
connection will only last around 15 minutes before the adapters led stops
flashing. I then have to reboot to get a connection again. I tried the
adapter back n my old XP machine and it is fine. As soon as the XP machine
boots, the led indicator starts flashing and it doesn't stop until you shut
down. With the Vista machine, the adapter often doesn't start flashing
until you actually connect and then it will just stop after a short while.
I've been messing around with this for weeks now and got nowhere. I would
have suspected the adapter drivers, but it seems as though there are a lot
of other people with the same problem on different adapters, which would
suggest a fundamental problem with Vista.

Can anyone shed any light?

--

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

Hi
First make sure that you Wireless Router is Vista compatible (some Wireless
Routers are Not).
If it is compatible look at the advanced Power saving setting in Vista and
tale the Wireless card out of the saving system.
I.e it should be always On. Not saving power.
Jack (MVP-Networking).

"Waldy" wrote in message
...
Hi there,
I recenctly bought a new machine that has Vista Basic
installed on it. I installed the latest drivers for my Netgear wireless
adapter which are supposed to be Vista compatible. However, although I
can get connected, I often have to mess around with the networking
settings first and then the connection will only last around 15 minutes
before the adapters led stops flashing. I then have to reboot to get a
connection again. I tried the adapter back n my old XP machine and it is
fine. As soon as the XP machine boots, the led indicator starts flashing
and it doesn't stop until you shut down. With the Vista machine, the
adapter often doesn't start flashing until you actually connect and then
it will just stop after a short while. I've been messing around with this
for weeks now and got nowhere. I would have suspected the adapter
drivers, but it seems as though there are a lot of other people with the
same problem on different adapters, which would suggest a fundamental
problem with Vista.

Can anyone shed any light?

On Tue, 26 Feb 2008 11:54:30 -0000, "Waldy"
wrote:

Hi there,
I recenctly bought a new machine that has Vista Basic installed
on it. I installed the latest drivers for my Netgear wireless adapter which
are supposed to be Vista compatible. However, although I can get connected,
I often have to mess around with the networking settings first and then the
connection will only last around 15 minutes before the adapters led stops
flashing. I then have to reboot to get a connection again. I tried the
adapter back n my old XP machine and it is fine. As soon as the XP machine
boots, the led indicator starts flashing and it doesn't stop until you shut
down. With the Vista machine, the adapter often doesn't start flashing
until you actually connect and then it will just stop after a short while.
I've been messing around with this for weeks now and got nowhere. I would
have suspected the adapter drivers, but it seems as though there are a lot
of other people with the same problem on different adapters, which would
suggest a fundamental problem with Vista.

Can anyone shed any light?


This has just started happening on my Sony Vaio too. I know it worked
fine about a month ago, so something has changed quite recently to
cause it. I see there have been several other threads in this
newsgroup over the last few days also reporting the same problem, or
something very similar.

On my Vista system I can initially connect wirelessly and everything
works fine for a while. Sometimes its okay for 10 minutes, sometimes
for up to an hour or so, but then the problem starts. The networking
icon in the notification area then gets a yellow triangle with an
exclamation mark in it and the connection stops working. In Network
Connections, the Wireless Network Connection turns to "Disabled".
Enabling it does nothing, and the only way to reset it is to reboot.

I suspect it might have something to do with the windows updates that
Microsoft released earlier this month. Something else I noticed is
that the Network and Sharing Center now takes a long time to display
anything in its window (at least a minute), whereas it was previous
much faster. I'm not sure if this is related to the same problem or
not, but someone else in this group reported the same thing after
installing this month's updates.

Chris

"Barb Bowman" wrote in message
...
which netgear adapter? what router exactly and what version firmware
is in the router?

The adapter is a WG111T and the router is a DG834GT. The firmware version
was 1.02.04, but I upgraded it last night to 1.02.13. I actually managed to
use it last night for about an hour without a problem. I was dreading it
failing half way through the firmware upgrade. I will have to see if that
has had any effect.

please post text results of ipconfig /all as a reply to this post

Do you want to see that output from a working system or when the problem
happens?

"Jack (MVP-Networking)." wrote in message
...
Hi
First make sure that you Wireless Router is Vista compatible (some
Wireless Routers are Not).

It's not listed on the HCL list, but according to Netgear it is OK.

If it is compatible look at the advanced Power saving setting in Vista
and tale the Wireless card out of the saving system.
I.e it should be always On. Not saving power.

That was the first thing that I did.

if it happens again, when it is in the problem state..

On Wed, 27 Feb 2008 09:44:03 -0000, "Waldy"
wrote:


Do you want to see that output from a working system or when the problem
happens?
--

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

"Barb Bowman" wrote in message
...
which netgear adapter? what router exactly and what version firmware
is in the router? please post text results of ipconfig /all as a
reply to this post

Windows IP Configuration

Host Name . . . . . . . . . . . . : eMachine
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR WG111T 108Mbps Wireless
USB2.0 Ad
apter
Physical Address. . . . . . . . . : 00-14-6C-5E-50-65
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::a53f:c14d:7696:2c5%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 29 February 2008 21:25:36
Lease Expires . . . . . . . . . . : 03 March 2008 21:25:36
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 218109036
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet
NIC
Physical Address. . . . . . . . . : 00-15-58-C2-42-8A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{A357B583-2F7C-46E7-B58F-D80F20F9E
7E6}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{C1A5B560-CF6C-44D3-97A7-0B595A684
BA3}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.2%14(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4137:9e66:87e:1bf0:3f57:fffd(Prefe
rred)
Link-local IPv6 Address . . . . . :
fe80::87e:1bf0:3f57:fffd%10(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

first step is to unbind IPv6
http://digitalmediaphile.wordpress.c...windows-vista/

second step is to go into device manager and uncheck the box to let
the computer turn off the adapter to save power. right click the
adapter in device manager, then properties.

On Fri, 29 Feb 2008 21:44:20 -0000, "Waldy"
wrote:


"Barb Bowman" wrote in message
.. .
which netgear adapter? what router exactly and what version firmware
is in the router? please post text results of ipconfig /all as a
reply to this post

Windows IP Configuration

Host Name . . . . . . . . . . . . : eMachine
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR WG111T 108Mbps Wireless
USB2.0 Ad
apter
Physical Address. . . . . . . . . : 00-14-6C-5E-50-65
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::a53f:c14d:7696:2c5%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 29 February 2008 21:25:36
Lease Expires . . . . . . . . . . : 03 March 2008 21:25:36
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 218109036
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet
NIC
Physical Address. . . . . . . . . : 00-15-58-C2-42-8A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{A357B583-2F7C-46E7-B58F-D80F20F9E
7E6}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{C1A5B560-CF6C-44D3-97A7-0B595A684
BA3}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.2%14(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4137:9e66:87e:1bf0:3f57:fffd(Prefe
rred)
Link-local IPv6 Address . . . . . :
fe80::87e:1bf0:3f57:fffd%10(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
--

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

Hi Barb,
thanks for replying.

"Barb Bowman" wrote in message
...
first step is to unbind IPv6
http://digitalmediaphile.wordpress.c...windows-vista/

That seems to be a popular suggestion, but I've yet to come across anyone
reporting a successful outcome by removing it. I have done it though. I'll
see if it makes a difference.

second step is to go into device manager and uncheck the box to let
the computer turn off the adapter to save power. right click the
adapter in device manager, then properties.

That was the first thing I did, as I thought it might be that what was
causing the problem.