Unidentified Network and Limited connectivity

[marsdenprimary]

Hello!

 

We have a Windows 10 machine (Intel Computestick) running some digital signage. It's been working perfectly fine for weeks. Came to it the other day, the machine hadn't rebooted, and it says 'Limited Connectivity' on the wireless icon at the bottom. DHCP isn't dishing out an address to it, it says 'unidentified network' and no matter how many things I try it won't connect.

 

I have tried:

 

ipconfig /release etc...

disable / enable wifi adapter

Disabled IPV6 (just in case it was that)

Reset winsock

flushed the DNS

restarted the WiFi AP (which other devices can connect to successfully)

restarted the machine several times

turned the firewall off

 

Anyone got ANY other ideas? Restarting the router is not a solution in this case.

 

All the Best,

 

A very frustrated Jay

[newpersn]

Tired uninstall and reinstalling the driver?

[linkazoid]

Have you tried entering netsh int ip reset from cmd?

[twin--turbo]

Give it a static in the range and see if it can ping something.

 

Try deleting and re-creating the wireless network on the machine.

 

Check the DHCP loggs.

 

TT

[Homer3334]

Bit obscure but check the remaining space on C of Dhcp server. Had this issue once where the server stopped giving addresses on renewal, but already leased addresses continued fine

[marsdenprimary]

Have you tried entering netsh int ip reset from cmd?

 

Yep tried that but it didn't work

 

- - - Updated - - -

 

Bit obscure but check the remaining space on C of Dhcp server. Had this issue once where the server stopped giving addresses on renewal, but already leased addresses continued fine

 

Plenty of space left on there but thans for this

[marsdenprimary]

Tired uninstall and reinstalling the driver?

 

I haven't tried this yet so I'll let you know how I get on after I've done it. It's a bit weird how it's happened though. Any idea why it may have done it in the first place?

[Homer3334]

Sounds like standard IT gremlins TBH, they've been screwing up networks of mine for years (or maybe that says more about me than the grems)

 

+1 for driver install

+1 also for trying a static address

 

If you have a spare wifi USB adaptor about usually installing that and seeing if that connects (if you have a USB port available in the stick). That would rule out general issues with the stack at least so you can concentrate on other areas

 

Maybe restarting the AP (not the router) might help as well?

 

Sometimes conflicting DHCP addresses cause this too - but seem to be much rarer a problem.

Edited May 12, 2016 by Homer3334

[marsdenprimary]

Well there we have it. Changed the IP address to static and it's working now! Thanks for all your help on this I'm glad it's fixed!

[Homer3334]

Great - Glad you got it working

[twin--turbo]

And back to Dhcp, if not you only fixed part of the issue.

[dry]

And back to Dhcp, if not you only fixed part of the issue.

+1. Check remaining leases. Right-click on 'Scope' and click 'Display statistics'. How many leases have you got free?

[marsdenprimary]

+1. Check remaining leases. Right-click on 'Scope' and click 'Display statistics'. How many leases have you got free?

 

810 remaining... I've not had any other issues anywhere else other than on this machine. I'm putting it down to Windows 10...