Multiple computers connected to internet but "not connected"

[mikeroq]

You might even want to set up a ping (msftconnectest.com) to log to a text file with a timestamp. Let it run all day. You can at least log what time it happens. Ping the ip as well in case it's a DNS issue.

Sent from my SM-N950U using Tapatalk

 

[brandonkick]

What does the network topology look like?

How many gateways / routers / switches are there. Are these hand made cables, or cables that were purchased already terminated.

I had issues before where someone "repaired" an ethernet cable by soldering the individual wires together to splice a cable back together instead of either running a new cable, or punching down a keystone jack. Eventually that connection went dodgy and started causing packet storms, crashing the network.

I've also had someone plug both ends of an ethernet cable into the same switch.


But explaining the topology better, defining what networking hardware exists and how it's configured, and the condition of the network wiring will really help. Often times the kid next door who runs wires cheaper than the pros will use stranded cables for longer runs, bend it in ways it shouldn't be bent, make the runs too long, use the wrong kinds of connectors for terminating, and even do a poor job of terminating in general. If these weren't "store bought" cables, I'd be suspect. If someone did a bunch of punch downs at a patch panel, I'd check those as well.

 

[GTP]

I get this very often. Sometimes it's only an hour or two, sometimes weeks and in some cases months.
It happens on wireless or cabled connections.
It does eventually fix itself so I wouldn't be too concerned.
I have successfully fixed it on a few machines (not all) by completely removing the network adapter (and driver) and reinstalling it/them.
I've spent hours googling all sorts of "fixes" and theories on why it happens but nothing is conclusive.
It usually happens after a bout of updates but isolating to the particular update/s has not been easy.
It's not OS specific either, as I have clients with 7, 8.1 and all versions of 10 doing it at times.
So far have not seen it with 1803, but who knows, we may get lucky?

 

[Slaters Kustum Machines]

It's probably just Microsoft rebooting their Windows 2000 webserver that hosts the sites that Windows uses to test connectivity.

 

[GTP]

It's probably just Microsoft rebooting their Windows 2000 webserver that hosts the sites that Windows uses to test connectivity.

Lol.

 

[DonS]

Catching back up with this thread. Thank you again for all the responses and feedback. Unfortunately, the issue continues. Overall, it would not be much of an issue, except for a few users that are dead set programed into using Outlook recent file list for attachments which, of course, greys out whenever this issue pops up, which is often.

To answer some recent questions:
1) It's a standard modem > router > switch set up. Nothing special.
2) Yes, I have removed the adapter, the drivers, new drivers, etc. No change.

 

[Slaters Kustum Machines]

Have you tried pinging the sites when the issue happens? I don't recall, but have you tried power cycling the modem/router/switch when this happens?

 

[nlinecomputers]

What are the make and models of the switches and router? What DNS is being used? When this goes down does it all go down or just some workstations. Any workstations that have NOT had problems or does it seem to be all of them?

This might be something that Solarwinds Netpath can help diagnose.

 

[brandonkick]

Is the modem a true modem or is it a gateway? If it's a gateway, is it in bridged mode and the router is doing all the DHCP stuff?

Luckily you have only two pieces of hardware involved, both of which should be easily replaceable. The switch / router combo can be swapped out for "spares" you may have on hand to troubleshoot and then purchase replacements if things calm down.

I'd make sure you don't have an issue where both that modem (which is likely a gateway) and the router both have DHCP functionality turned on. I'd probably turn DHCP off all together and statically assign all devices. I'd also be sure that there isn't any other equipment involved, some employee didn't run out and buy their own access point or something...

If it's all of the computers displaying this problem, networking hardware is more likely to blame. If it's only some, I might start to suspect a wiring issue. Are these computers all the same, or is it a mish mash of makes / models ?