Connected With Limited Access pains.

This problem is driving me up a wall.
I try to connect, and I get a "Connected with Limited Access" or "Limited Connectivity" error.
I have a NETGEAR_WPN284v3 and I'm on Vista.


Windows IP Configuration

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

Wireless LAN adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1510 Wireless-N WLAN Mini-Card
Physical Address. . . . . . . . . : 00-22-68-A8-32-ED
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::39fd:205f:cb61:1a34%14(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.26.52(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:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 00-21-70-82-4B-9A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c9c2:30ae:d685:ad4e%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.74(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, March 11, 2009 8:43:48 PM
Lease Expires . . . . . . . . . . : Thursday, March 12, 2009 8:43:48 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

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* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{BCB28159-C625-4F7B-A45A-C907BD1EC426}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{2F37C621-F808-49C3-B564-2639AFDC8118}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


-----
HELPPPPP!

I'm electronically challenged -could someone could tell me what exactly is wrong, how to fix it, specifically.

When I run a diagnostic, it says my Gateway IP ping failed.

Laparoscopy is used to determine the cause of pelvic pain or .... that is
usually connected to a video camera (single chip or three chip) or ... Prior to
its conception, laparoscopy was a surgical approach with very limited
application and .... port access surgery, also known as single incision
laparoscopic surgery ...

Your config has both wireless and wired active. Turn off or disable your wireless connection. If a laptop, turn off the wireless switch on the machine. Otherwise,

CONTROL PANEL-->NETWORK AND SHARING CENTER-->MANAGE NETWORK CONNECTIONS

Right click the wireless adaptor in the list, and click disable.

NOte that you will have to enable it again later if you want to use wireless, but this is the best way to make sure it is out of the picture.

Reboot your computer and try again. If it doesn't work, paste the new ipconfig results like you did in your first post...

Lots of problems with "Wired" internet connections especially on 64 bit OS'es (VISTA and Windows 7 -- click the Windows 7 Forum button to check for similar posts as well).

I think that for the moment some cards just WON'T work properly even thow windows reports driver as working fine.

Get around is temporarily to use wireless connections, or a USB===>LAN adapter or if you have a laptop a PCI express LAN card (APIOTEK / Agere systems do a good one). These all work on 64 bit systems.

Your Router is OK -- believe me I've plugged in and unplugged different routers till the cows come home. The next time I even THINK of a router I'm swigging a LARGE glass of Scotch.

Have a look at similar posts in this forum.

For the moment we just have to live with "incompatable cards" or (not what I would do) go back to a 32 bit OS.


For the limited connectivity problem you'll get a totally strange IP address (if you even get one at all) and it doesn't matter if you use DHCP or manually set the connection to use a fixed IP address.

IPCONFIG / RENEW, FLUSHDNS, etc etc don't work -- I've spent AGES on this stuff and whist it goes against the craw I'm giving up on this as "an unsolvable problem" until Windows 7 retail comes out -- and by then I'll probably have a different laptop with a working network card in it.


Cheers
jimbo


Added thies notes -- even though your COMPUTER can run a 64 bit OS it might be that some of the cheaper mobo components like LAN cards aren't actually 64 bit compatable.

Windows XP 64 bit version drivers worked a bit differently -- the WOW system allowed some "legacy" 32 bit drivers to work seamlessly with the OS.

Windows VISTA and Windows 7 have much tighter driver policies -- and if your laptop / mobo is even a few months old and came pre-installed with a 32 bit OS then you could be unlucky.

(Most wireless connections seem to work ok however).

--tr laa
jimbo