Limited or Low connectivity message

[TechSupp]

Right, all started with a netbook not connecting via our Ruckus wifi, it connects but wont pick up an ip from the server dhcp and give the title message, says its connected but not fully. So though I would check it out via the LAN, now got same message when I plug a cable in, (cable connection checked ok). Changed the driver, removed driver and let it reinstall, using zero config and Atheros config all to no avail. Any more suggestions?

[mac_shinobi]

For windows XP I did the following :

 

winsock reset both using winsock fix util :

 

|MG| WinSock XP Fix 1.2 Download

 

From a command prompt running with admin rights

 

netsh winsock reset

 

netsh int ip reset c:\resetlog.txt

 

As per

 

How to reset Internet Protocol (TCP/IP)

 

Repair/Reset Winsock settings

 

If this is windows 7 or a different OS then may have to use different utils / commands etc

 

The winsock fix exe also resets the host file back to default

 

I generally use winsock fix exe first ( create a backup of the reg button and then run it, then run the 2 commands ) Then reboot / restart windows and test again.

Edited May 1, 2012 by mac_shinobi

[Michael]

Re-image the netbook if you can, bearing in mind everything else connects OK.

[mac_shinobi]

Re-image the netbook if you can, bearing in mind everything else connects OK.

 

Thats probably the faster and easier way

[Michael]

Thats probably the faster and easier way

 

I just find these days that with each OS release it gets more complex and starting from new 9 times out of 10 resolves the issue, unless it's hardware related! It typically takes 30 mins including imaging and Sysprep which is a good turnaround in my opinion.

[theriver]

Are you getting any errors at the DHCP end (e.g. scope full)?

[TechSupp]

Yes, would probably do that in the end but didnt have the image with me (keep it on a usb drive). Thanks for the hints. Will get back on it next week.

[TechSupp]

Bumping this thread as although mac_shinobi's fix worked a treat I've now just had to do this on another two PC's today, thought it was isolated to a specific make/model of PC, but one today was one of our netbooks! Anyone got a clue as to why this has suddenly started to appear?

[mac_shinobi]

Bumping this thread as although mac_shinobi's fix worked a treat I've now just had to do this on another two PC's today, thought it was isolated to a specific make/model of PC, but one today was one of our netbooks! Anyone got a clue as to why this has suddenly started to appear?

 

Only thing I can think of is malware or viral that is corrupting the registry key(s) that are related to the fixes ( excluding the hosts file ), obviously the only other times I get the above symptoms is when said device is set to static ip address instead of to use dhcp ( but that's a manual thing of making sure said nic is set to use dhcp for both the ip address, subnet mask, default gateway and dns servers instead of being manually configured ). That is a given obvious though.

[TechSupp]

Nothing has been picked up by Sophos so may look at getting it to scan for malware and see how we go. Hthanks for the help anyway, got me out of a hole. Must be a specific site as it was y5 and y6 and they had also had the netbooks out.

[mac_shinobi]

I was just guessing - @Michael or @Arthur or someone else may have a better idea of something else other then malware / viruses etc that may have caused this to occur ?

[TechSupp]

Thats ok, needs checking anyway but as you say, open to any other suggestions.

[Michael]

To be honest I think registry or system file corruption is probably the most likely culprit. Typically malware keeps your network connection active to send/receive malicious content or indeed content about the user, rather than disabling the network connection so it's unable to get an IP.

 

I suppose the other thing to check is the availability of IPs on your DHCP server.