windows 7 64 bit wireless

[capitan]

I have a laptop that is not connecting properly to an open WAP. The
laptop can connect to other wireless networks, and other laptops can
connect to this open WAP. The signal strength has only 2 bars. When we
try to connect to this open WAP, the Network sharing center shows that
the laptop has a successful connection to the WAP, but no internet access:

'this computer' ------> Open WAP ---X Internet

What does that mean, and how do I go about fixing this issue? Thanks.

 

[kevpan815]

I have a laptop that is not connecting properly to an open WAP. The
laptop can connect to other wireless networks, and other laptops can
connect to this open WAP. The signal strength has only 2 bars. When we
try to connect to this open WAP, the Network sharing center shows that
the laptop has a successful connection to the WAP, but no internet access:

'this computer' ------> Open WAP ---X Internet

What does that mean, and how do I go about fixing this issue? Thanks.

RE-FORMAT YOUR COMPUTER AND INSTALL OPEN SOURCE LINUX UBUNTU 10.10 RTW!

 

[Big Steel]

I have a laptop that is not connecting properly to an open WAP. The
laptop can connect to other wireless networks, and other laptops can
connect to this open WAP. The signal strength has only 2 bars. When we
try to connect to this open WAP, the Network sharing center shows that
the laptop has a successful connection to the WAP, but no internet access:


'this computer' ------> Open WAP ---X Internet

What does that mean, and how do I go about fixing this issue?

Thanks.

Just because the machine can connect to the WAP does it mean it's
compatible with Win 7.

If the IP you get form the WAP device, it can be a router as an
example, starts with 169., then the computer cannot get a valid IP
from a DHCP server and the machine cannot connect to the Internet.
You enter IPconfig /all at the Command prompt to see what IP the
machine has.

As far as fixing the problem, you may be out of luck, since it's not
your WAP device.

 

[Tim Slattery]

If the IP you get form the WAP device, it can be a router as an
example, starts with 169., then the computer cannot get a valid IP
from a DHCP server and the machine cannot connect to the Internet.

How do you figure? There's a DHCP server embedded in the router/WAP,
that's what dishes our the 169... IP address. Regardless of what
address you've been given it's up to the router to figure out what to
do with it. In a normal home setup, the router gets a "real" IP
address from the ISP, then translates between the IPs it hands out and
the real IP.

 

[Big Steel]

How do you figure? There's a DHCP server embedded in the router/WAP,
that's what dishes our the 169... IP address. Regardless of what
address you've been given it's up to the router to figure out what to
do with it.

If the computer nic is setup to get a DHCP IP from a DHCP sever on
the network, and it cannot get it for whatever reason, then the
computer's O/S assigns the 169. IP to the nic. The 169. IP will allow
the computer to access and communicate with other computers on a LAN.
The computer will not be able to access the WAN, since it doesn't
have an IP that is assigned by the DHCP server on the LAN. The DHCP
server can be at the ISP or it can be on a router as well in a home
network setup.

In a normal home setup, the router gets a "real" IP
address from the ISP, then translates between the IPs it hands out and
the real IP.

I know this. And that router can get that 169. IP too if the router
is set to obtain a DHCP IP from the ISP and it can't get one. In this
situation, no machine connected to the router has Internet access.

 

[Seth]

How do you figure? There's a DHCP server embedded in the router/WAP,
that's what dishes our the 169... IP address. Regardless of what
address you've been given it's up to the router to figure out what to
do with it. In a normal home setup, the router gets a "real" IP
address from the ISP, then translates between the IPs it hands out and
the real IP.

No router (or any DHCP server for that matter) would ever give out a 169
address as that is non-routable. That's the first octet of the IP address a
machine will give itself via AutoConfigure because it couldn't reach a DHCP
server (or more specifically one didn't respond within the timeout period).

 

[Char Jackson]

No router (or any DHCP server for that matter) would ever give out a 169
address as that is non-routable.

I agree that it would be very unusual to configure a DHCP server to
hand out 169.x.x.x IP's, but I don't see any technical reason why IP's
in that range wouldn't work just fine in a NAT situation. The fact
that they are non-routable certainly isn't a disadvantage, as the same
can be said for the rest of the RFC1918 IP ranges.

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)