problem: auto assign ip address giving 'limited or no connectivity'

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › problem: auto assign ip address giving "limited or no connectivity"

cjp17

4 posts

Wannabe Geek

#15705 4-Sep-2007 06:26

Hey folks,

I've been having some issues with my internet connection to a public wi-fi spot. I did a google search and found some info on this site and thought I'd ask my question. The problem I am having seems to occur at all public wi-fi spots.

About a week ago, I installed some security software on my PC laptop. Before this, I was able to connect to this public wi-fi quite easily, my computer would assign an ip address automatically as well as default gateway and dns servers. It would assign the usual ip as 168.192.0.xxx and subnet mask as 255.255.255.0. No problem, all worked well.

After I installed the security software, when my computer assigned an ip address, it changed it to 169.254.xxx.xxx and subnet mask 255.255.0.0. This left me with a "limited or no connectivity" that prevented my from accessing the internet.

I proceeded to uninstall the security software, and the issue persisted. I then went to my TCP/IP settings and manually assigned an ip as 192.168.0.xxx and subnet mask as 255.255.255.0, hoping this would solve the issue. After doing this, I received a full internet connection. But when I tried to load a page, nothing comes up, "server not found".

I've been tweaking with different ip addresses, default gateways, and dns servers. I tried opendns.com, and that did not solve the issue.

I just want to be able to have my laptop auto assign an ip address without it giving me "limited or no connectivity" message, like prior to installing the security software. Any help at all would be greatly appreciated. Thanks a lot.

-Chris

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41029

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#85214 4-Sep-2007 07:44

The first thing is to change your network configuration back to automatic. Each different network uses a different configuration and manually assigning addresses will reduce your chance of connecting.

Also, when you say "public hotspot" are these hotspot services (such as T-Mobile, Boingo, AirPort) or just some wireless networks you find? If these are paid services you only have full access after you login or pay - and if they are just open wireless networks, then it is probable they are not configured to share the Internet with non-authenticated machines.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

cjp17

4 posts

Wannabe Geek

#85273 4-Sep-2007 11:43

First let me make a correction to my original post. Whenever I would be assigned an ip address automatically, it was 192.168.xxx.xxx, not 168.192.xxx.xxx.

When you say "public hotspot" are these hotspot services (such as T-Mobile, Boingo, AirPort) or just some wireless networks you find?

There are two wireless hotspots in my range, one from a coffee shop and one from an unknown source. Neither requires any sort of login info or pay.

if they are just open wireless networks, then it is probable they are not configured to share the Internet with non-authenticated machines.

The one I've been connecting to for weeks is an unsecured wireless network, probably from a neighbor. It was working fine up until I installed the security software, which changed the the ip address it assigned when using the "obtain ip address automatically." But it is not just this one public spot. I've tried numerous public, free wi-fi spots while trying to "obtain an ip address automatically", and it consistently gives me "limited or no connectivity" on all wi-fi spots. Sounds like an issue with my computer settings and not the various networks.

I changed it back to "obtain an ip address automatically" and it is still giving me "limited or no connectivity" with an ip address of 169.254.xxx.xxx and subnet mask 255.255.0.0. If I goto manually change my ip and keep the same ip address but change the subnet mask to 255.255.255.0, it says I'm connected, but no page loads. It is sending packets, but not receiving anything.

Any ideas?

Thanks

gished

276 posts

Ultimate Geek
+1 received by user: 10

#85318 4-Sep-2007 16:28

What security software did you install and which components?

What o/s?

Any firewalls installed?

JonC

425 posts

Ultimate Geek

#85356 4-Sep-2007 19:40

Hi,

If your local IP address is returned as 169.254.y.z with a subnet mask of 255.255.0.0, the IP address was assigned by the Automatic Private IP Addressing (APIPA) feature of Windows XP Professional. This assignment means that TCP/IP is configured for automatic configuration, that no DHCP server was found, and that no alternative configuration is specified.

Typically this happens when security (WEP, WPA) is turned on at the AP and you're trying to connect without a password or an incorrect password. Either that or MAC filtering has been enabled on the AP, only allowing authorised computers to use the internet connection.

cjp17

4 posts

Wannabe Geek

#85429 5-Sep-2007 13:20

Thanks for the replies.

I installed bit defender 2008, full package, firewall, adware blocker, the whole thing. I'm using windows xp.

If your local IP address is returned as 169.254.y.z with a subnet mask of 255.255.0.0, the IP address was assigned by the Automatic Private IP Addressing (APIPA) feature of Windows XP Professional. This assignment means that TCP/IP is configured for automatic configuration, that no DHCP server was found, and that no alternative configuration is specified.

Typically this happens when security (WEP, WPA) is turned on at the AP and you're trying to connect without a password or an incorrect password. Either that or MAC filtering has been enabled on the AP, only allowing authorised computers to use the internet connection.

I'm not sure that is the case because my friend's laptop is able to access the wi-fi without a password or login info. It is not necessarily a consistent connection, but it does load web pages and allows for simple browsing.

I just find it strange that before the automatic ip address it was giving me was 192.168.0.xxx and now all of a sudden its 169.254.x.x and I can't connect.

Thanks for the info guys, I'll keep messing with it.

JonC

425 posts

Ultimate Geek

#85441 5-Sep-2007 13:46

The 169.254 address is set by your own computer when it's set up to automatically get assigned an IP address (DHCP), but no DHCP server (router) is found.

Have a look here for some possible solutions. You may have a corrupt winsock or your firewall might be blocking the communication required for DHCP to work.

New World

Shop on-line at New World now for your groceries (affiliate link).

cjp17

4 posts

Wannabe Geek

#85563 6-Sep-2007 10:22

Have a look here for some possible solutions. You may have a corrupt winsock or your firewall might be blocking the communication required for DHCP to work.

Yes! Got it working. For others who have had this problem, here is what causes it:

" Basically some viruses and ad-ware (New.net for example), modify your tcp/ip or internet connectivity settings. Removed said program can leave lingering entries and that may be causing problems. I've used this tool successfully for over a year now, just to make sure that network settings where restored. "

I had used Norton (prior to Bit Defender) to quarantine new.net and apparently this is what caused the problem. I downloaded winsockfix 1.1.0.13 here, ran the program, and problem was solved.

Thanks a lot to JonC for the info. I appreciate the help.

Take care everybody.

-Chris