Multiple computers connected to internet but "not connected"

[DonS]

Hey all!

I am having this issue in particular clients office at the moment. They have about a dozen computers and a majority are showing an exclamation mark over the internet connection showing "not internet access". However, they are connected.

The bigger problem is that they are heavy Outlook users and attach files from the recently used file list. However, when the computers exhibit this "not internet access" error, Outlook thinks it is offline and the recent file list is greyed out (the files are all located on a share drive).

I have tried removing the network cards from device manager, reinstalling them; updating drivers, etc. With no change. However, with the amount of computers exhibiting this, I am feeling it may be more of a network issue.

Any suggestions regarding this issue would be most welcome!

 

[mikeroq]

Oh man I hate when that happens.

Check to see if they can access http://www.msftncsi.com/ncsi.txt on one of those.

Could be a DNS issue.
Any proxies?

Try these commands
net int ip reset
ipconfig /flushdns

and reboot

 

[Slaters Kustum Machines]

Yep, sounds like DNS. Do all of the machines have Eset installed? Have you tried disabling it to see if it makes a difference? Also what are the workstations using for DNS servers?

 

[Markverhyden]

To add to the above. You say the recents are greyed out. How is the share point mounted? Directly via IP or via a M$ server?

 

[glennd]

Hey all!

I am having this issue in particular clients office at the moment. They have about a dozen computers and a majority are showing an exclamation mark over the internet connection showing "not internet access". However, they are connected.

The bigger problem is that they are heavy Outlook users and attach files from the recently used file list. However, when the computers exhibit this "not internet access" error, Outlook thinks it is offline and the recent file list is greyed out (the files are all located on a share drive).

I have tried removing the network cards from device manager, reinstalling them; updating drivers, etc. With no change. However, with the amount of computers exhibiting this, I am feeling it may be more of a network issue.

Any suggestions regarding this issue would be most welcome!

the icon is telling you that the cable seems to be plugged in to something that looks like a network but there's no "network connectivity". So things like dhcp, dns etc are not available. the problem is most likely external to the workstation. check the output of "ipconfig /all" to see if the machine is assigned an ip address, a dns server, a gateway. if any of these are missing, the dhcp server is not available or not doing it's job. in most small/domestic situations the culprit will be the modem/router (but it could be anywhere along the line to the router). power cycle it might fix it. if that fails plug in your spare modem/router. You may have to configure it to be the same subnet as the old modem/router, eg 10.0.0.x or whatever the ip range is. Even without making an internet connection, that should get the LAN working. Then plug in the ISP login details to get internet connection.

 

[DonS]

Hey all, thank you for the input. I will respond next week when I get the opportunity to try these out.

Thank you again.

 

[GTP]

I see this often. Rebooting the router works in 90% of cases.
The other 10% need further investigation.

 

[frase]

Are they each to their own or on a domain server? If not on a server reset router via pin button. This will reset the router and assign new ip addresses - just my 5cents as 2cents are no longer valid

 

[GTP]

If not on a server reset router via pin button.

Doing that will require the router to be setup again with usenrname/password/wifi/passwords etc.

just my 5cents as 2cents are no longer valid

lol, there's talk of them (5 cents) disappearing soon as well, so it will have to be your 10 cents worth!

 

[Altster]

The "Very First Thing" that comes to my mind would be if all of the computers have the same name (for some reason).

This can happen when you "clone computers" and FORGET to rename each computer individually. They may seem to be there, but....

....this is my 37 cents worth.

 

[ComputerRepairTech]

https://blog.superuser.com/2011/05/16/windows-7-network-awareness/ I think its still the same right?

 

[YeOldeStonecat]

https://blog.superuser.com/2011/05/16/windows-7-network-awareness/ I think its still the same right?

Yup that's it..the first reply in this thread, by MikeRoq, nailed it. That yellow exclamation point on the network connection icon in the systray is due to network location awareness service.

The "cause" of it can be several different things, typically DNS related. Some routers do not perform DNS services very well. Or perhaps if this is a domain (a domain controller at the top of the network)...its DNS service needs to be checked, and ensure the clients are setup properly with their DNS (checking DHCP on the server too).

If it's just a workgroup, the router will be performing DHCP and DNS in some form. Update its firmware, check settings, esp DNS.

Try setting the NLA service to delayed start
If the rigs have dual NICs..disable the unused one.
Check network provider order and re-prioritize if needed (see this often on some home make/cloner rigs...ain't done right).

 

[resolvetech]

One thing I do sometimes if I walk into a mess is "hard code" the IP adapter settings (that's what we did in the NT days). Assign as static: IP, DNS, gateway and subnet mask. If you get connectivity you can start looking at other things like mentioned. Router or server DNS, Network awareness, wiring, etc.

If you got a mess and cheap client you can leave static as is. Best practice though is to use domain, point DNS to internal server and have workstations grab dynamic IP from server. If you don't have server then use router like YeOldeStonecat mentions.

 

[G8racingfool]

One thing I do sometimes if I walk into a mess is "hard code" the IP adapter settings (that's what we did in the NT days). Assign as static: IP, DNS, gateway and subnet mask. If you get connectivity you can start looking at other things like mentioned. Router or server DNS, Network awareness, wiring, etc.

On this note, also make sure you don't have some random device using a static IP address that's inside your DHCP range. Especially if your client is using a consumer grade router as most of the time they don't pick up devices that are static meaning they'll still assign that address even if it's being used. And as you know, conflicting IPs can cause all sorts of issues.

 

[DonS]

Hello again all

Thank you all for taking your time to respond and offer suggestions to this thread.

To answer some questions
- The Share is standard Microsoft Mapped drive setup
- I did reset the router when this problem first cropped up. Full reset. The issue continued.
- They are not on a Domain
- Computers all have different names

I have yet to follow up with this week, but when I do will try some of the suggestions
- Net int ip reset and Flush dns to start
- I will also check the www.smftncsi.com link

I will follow up, thank you again.

 

[DonS]

Been a while but had to wait to see if some of the changes put in place worked. After trying the below, the issue continues!! Any other thoughts? Could this be a router issue?

- Netsh int ip reset

- Ipconfig /flushdns

- Locked in a static IP address

 

[mikeroq]

What was your result when going to http://www.msftncsi.com/ncsi.txt on an affected computer?

 

[brandonkick]

So you've statically set each workstation to a fixed ip in the lan adapter settings and you still get no internet access?

Have you done a full recycle of all networking hardware after the static set up on each machine?

 

[HCHTech]

What was your result when going to http://www.msftncsi.com/ncsi.txt on an affected computer?

or

http://www.msftconnecttest.com/connecttest.txt

if you are Win 10 >= Anniversary Update.

 

[DonS]

Static IP set, hardware refreshed.

Again, it can stay connected fine for hours or days, then it will show the Exclamation Point error on the network icon, show "no internet access" but they do indeed continue to have internet access.

Will have them run the new Win10 connection test link tomorrow.

Thank you again for those following.