I have a problem Mike.

Brand new laptop, trying to connect to my wireless router. I have it security password protected.

The best I can get is "connected but with limited connectivity". No internet connection can be made.

I have disabled the McAfee firewall and it's a Vista (Home Basic). I've also tried disabling IPv6.

I'm going to try direct cable connection, but I want to resolve the wireless issue.
(Direct cable is fine.)

I still have this problem intermittently with my husband's laptop (I've posted details before)

The one sure fire cure for mine is to reboot the router, it then connects no problem - until the next time it doesn't of course

Open the setting up on the router and tel it to transmit its SSID code

Your new lappy should see the router now and connect

I already have SSID broadcasting set. there are two other laptops in the house connecting perfectly. The others are both XP.

It's just this Vista laptop that won't connect with full connectivity rights. I might try disabling all of McAfee and see what happens, but I'm not hopeful.

Dave you could check the speed of the NIC (hope you know what I mean lol , properties of the network card, advanced tab) and try it at half duplex if its set to full duplex .

It might be set to Auto but I would try altering and see if you get a better result.

The network card shouldn't affect it Anne - I can connect OK with ethernet direct to the router. It's only on the wireless I'm having the problem.

I get this:

This computer is connected to <network> but does not have access to the internet.

IP Config tells me this:

C:\Users\Lynda>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Lynda-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 . . . . . . . . . . . : Intel(R) Wireless WiFi Link 5100
Physical Address. . . . . . . . . : 00-21-5D-85-FC-2A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.23.23(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : WAG160N
Description . . . . . . . . . . . : Generic Marvell Yukon 88E8071 based Ether
net Controller
Physical Address. . . . . . . . . : 00-1D-72-E8-D3-29
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.WAG160N
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 . . . . . . . . . . . : 6TO4 Adapter
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 . . . . . . . . . . . : isatap.{99F3D8AE-09AC-426E-BCB9-FA1BCE627
308}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


I've a suspicion that the problem is this:
Autoconfiguration IPv4 Address. . : 169.254.23.23(Preferred)

but no idea what to do now .......

Where's Mike when a boy's in trouble?

Just of of interest, have you made sure the windows firewall is not also activated?

It's like IPV4 is not set to obtain an ip address automatically .... check it's not set to "use the following ip" in the properties.

It is set to obtain automatically Anne.

I'm going out tonight. so will have to resume investigations later/tomorrow.

I posted a reply, but then realised it was complete rubbish. I thought you were suffering from the common problem with Vista where an adapter has "Local" access but not "Internet" access. However, it seems that you are not getting an IP address from the router and that suggests the wireless adapter hasn't "Connected" properly.

You can check whether this is the case, or if it is a DHCP addressing problem, by allocating a fixed IP address in the router's subnet. If it works with a fixed IP address, then the issue is with getting the address automatically by DHCP. If it doesn't work, the problem is that the adapter hasn't "Connected" to the wireless network.

The thought of allocating a fixed IP address had crossed my mind.

I'll give it a try tomorrow.

The fixed IP didn't resolve it, powering off then back on with the router did.

Why, I have no idea. Both of the XP laptops connected fine when I installed this router, it was only a few weeks ago.

Now to get on with installing security software on this new machine.

All's well that ends well