New
#11
I read somewhere that 169.254.*.* has some significant meaning but I don't remember what it is. It's up there in my ipconfig /all cmd.
Any help is appreciated
I read somewhere that 169.254.*.* has some significant meaning but I don't remember what it is. It's up there in my ipconfig /all cmd.
Any help is appreciated
Are your wireless connection set to auto-detect. If not try it.
"Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-22-FB-55-F5-74
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::448a:838f:f47d:777a%19(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.119.122(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 251667195
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-5A-34-61-00-1D-BA-B8-13-D4"
You won't be able to get out to your ISP if you don't have the default gateway IP. And where is your Ipv4 IP? you only have Ipv6 which could be a giveaway.
A 169.254.x.x is just a dummy Windows IP address. Basically telling you that there's a problem connecting to your network and obtaining a valid IP address.
Are you able to see your Network? Have you made sure you're putting in the correct password? Have you tried removing the password from your network to see if you can connect to it with no security in place?
This Networking is a laugh, I have to scarp my router and still can't get 3 units to talk. Tomorrow no TV for me , it's back to XP, yes XP . To be fair Win7 is great for one person on one computer, my grandaughter. for networking wait for sevice pack 1. Sure glad I didn't spend a paycheck on this parlor game.
Alright guys I'll make some things clear:
1- Yes I see my network
2- Yes there IS an internet connection that actually works
3- Yes I am using the correct password
All this because I manage to connect to the router often and get an internet connection but always end up in Limited Connectivity mode after some time. Arbitrary time. See now it's working for instance and here's my ipconfig /all:
Windows IP Configuration
Host Name . . . . . . . . . . . . : Karim-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-22-FB-55-F5-74
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::448a:838f:f47d:777a%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.104(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, October 25, 2009 11:47:06 AM
Lease Expires . . . . . . . . . . : Monday, October 26, 2009 11:47:06 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 251667195
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-5A-34-61-00-1D-BA-B8-13-D4
DNS Servers . . . . . . . . . . . : 193.227.177.53
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Marvell Yukon 88E8055 PCI-E Gigabit Ether
net Controller
Physical Address. . . . . . . . . : 00-1D-BA-B8-13-D4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.lan:
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 Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{F36DD096-4326-4EB5-A9C5-838473878B62}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Kiko, your ips details for wireless looks pretty good. The Limited Connectivity can be due to weak connection or driver issue for wireless card.
I'm not a fan of ipv6 and ipv4 both running together, see how u go with disabling ipv6.
I actually had it off all this time so I though I'd turn on Homegroup for a little while to see what happens. The thing is that I already got my wireless card's Win 7 drivers both from Intel AND my notebook's manufacturer.
I have no idea what else I can do but my signal is at its peak, and I see no reason for it to do what it's doing.
Just curious, how did u get it to say "Ian" in Connection-specific DNS Suffix . : lan
Mine is saying my ISP DNS suffix (Optusnet.com.au).
When you get the Limited Connectivity, was it when the signal is at full strength?