Ask a question
Search in U-verse Forums

U-verse Forums

Reply
Posted Apr 5, 2011
4:49:32 PM
View profile
Vista (64-bit) and U-Verse via Wireless LAN

The gentleman that kindly installed my family's U-Verse hardware finished a couple hours back, and I have since then been attempting to troubleshoot the known issue with Vista-laptops and wireless connectivity to a 2WIRExxx network.

 

I have tried the commonly referred "fix" listed at Microsoft relating to the computer being unable to obtain an IP address, which did not work (though I tried it, despite believing it inapplicable to my computer). I have attempted rebooting, connecting/disconnecting from teh network, and removing previously managed wireless connections. My wireless connection earlier today was flawless prior to this installation (using a Linksys modem and Cisco wireless router).

 

As of now, I am posting to this forums using an ethernet cable, so my wired connection is working on this computer (wireless and wired connections are working on other computers in the household running Windows XP, Windows 7, and whatever the latest Mac OS is these days). I've been consistently checking my ipconfig/all settings within CMD, and I have noticed a change in my Autoconfiguration IPv4 address, which is included in the below information. Previously, it was showing as 192.168.1.xx. I am careful to revert settings I've changed back to their previous state if the change doesn't seem to fix the problem, but it is possible I changed something and forgot to change it back (and I've tried a lot of things this evening). However, after rebooting the computer again and attempting to obtain a new IP, I am still stuck with a 169 IP address.

 

As far as hardware goes, I am running an HP dv5 notebook with Windows Vista Home (64-bit) as my OS. My wireless card's driver is up to date, and my service packs are up to date, as well. Below I have included my current settings as listed in ipconfig/all. If any of you can offer assistance, it would be sincerely and utterly appreciated. (*Note: Select All --> CTRL + C --> CTRL + P from CMD omits some of the information listed under my Ethernet adapter Local Area Connection)

 

 

 

Windows IP Configuration
   Host Name . . . . . . . . . . . . : Owner-PC
   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 . . . . . . . . . . . : Atheros AR5007 802.11b/g WiFi Adapter
   Physical Address. . . . . . . . . : 00-23-4D-A3-01-CD
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e545:9a0c:8718:a001%11(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.160.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : gateway.2wire.net
   Description . . . . . . . . . . . : Realtek RTL8102E Family PCI-E Fast Ethern
et NIC (NDIS 6.0)
   Physical Address. . . . . . . . . : 00-1E-68-89-A5-23
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 6:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.gateway.2wire.net
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 7:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 13:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{FADEF0BE-888B-4A5F-B3CA-BA969F210
6F2}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

 

The gentleman that kindly installed my family's U-Verse hardware finished a couple hours back, and I have since then been attempting to troubleshoot the known issue with Vista-laptops and wireless connectivity to a 2WIRExxx network.

 

I have tried the commonly referred "fix" listed at Microsoft relating to the computer being unable to obtain an IP address, which did not work (though I tried it, despite believing it inapplicable to my computer). I have attempted rebooting, connecting/disconnecting from teh network, and removing previously managed wireless connections. My wireless connection earlier today was flawless prior to this installation (using a Linksys modem and Cisco wireless router).

 

As of now, I am posting to this forums using an ethernet cable, so my wired connection is working on this computer (wireless and wired connections are working on other computers in the household running Windows XP, Windows 7, and whatever the latest Mac OS is these days). I've been consistently checking my ipconfig/all settings within CMD, and I have noticed a change in my Autoconfiguration IPv4 address, which is included in the below information. Previously, it was showing as 192.168.1.xx. I am careful to revert settings I've changed back to their previous state if the change doesn't seem to fix the problem, but it is possible I changed something and forgot to change it back (and I've tried a lot of things this evening). However, after rebooting the computer again and attempting to obtain a new IP, I am still stuck with a 169 IP address.

 

As far as hardware goes, I am running an HP dv5 notebook with Windows Vista Home (64-bit) as my OS. My wireless card's driver is up to date, and my service packs are up to date, as well. Below I have included my current settings as listed in ipconfig/all. If any of you can offer assistance, it would be sincerely and utterly appreciated. (*Note: Select All --> CTRL + C --> CTRL + P from CMD omits some of the information listed under my Ethernet adapter Local Area Connection)

 

 

 

Windows IP Configuration
   Host Name . . . . . . . . . . . . : Owner-PC
   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 . . . . . . . . . . . : Atheros AR5007 802.11b/g WiFi Adapter
   Physical Address. . . . . . . . . : 00-23-4D-A3-01-CD
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e545:9a0c:8718:a001%11(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.160.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : gateway.2wire.net
   Description . . . . . . . . . . . : Realtek RTL8102E Family PCI-E Fast Ethern
et NIC (NDIS 6.0)
   Physical Address. . . . . . . . . : 00-1E-68-89-A5-23
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 6:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.gateway.2wire.net
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 7:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 13:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{FADEF0BE-888B-4A5F-B3CA-BA969F210
6F2}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

 

Vista (64-bit) and U-Verse via Wireless LAN

631 views
0 replies
(0) Me too
(0) Me too
Reply
Advanced
You must be signed in to add attachments
Share this post
Share this post