F5F Stay Refreshed Power Users Networks Do you have trouble connecting to your network? Are you getting constant breaks with Wi-Fi and wired connections?

Do you have trouble connecting to your network? Are you getting constant breaks with Wi-Fi and wired connections?

Do you have trouble connecting to your network? Are you getting constant breaks with Wi-Fi and wired connections?

Pages (2): Previous 1 2
A
Aladrox
Junior Member
40
10-20-2026, 07:45 PM
#11
Usually, an internet connection stays up for 24 hours. But in business places, sometimes it's just two hours before they cut you off.
A
Aladrox
10-20-2026, 07:45 PM #11

Usually, an internet connection stays up for 24 hours. But in business places, sometimes it's just two hours before they cut you off.

K
Kid_Jason
Junior Member
12
10-22-2026, 12:49 AM
#12
Try 24 hours. = = = = With the whole network broken, everyone needs to check everything again. I don't know if the ISP really tested the cables, connectors, and stuff like that. Technicians are often under a lot of pressure and will swap out splitters. Everything seems okay and is happening with intermittent problems. They leave, problem "resolved". Then you get errors again. After reading back, noted that splitters had been taken out which made me think of other things. How do any unused coax cables get connected? There are special plugs for this versus just some "dust caps". NOTE: https://blog.solidsignal.com/tutorials/t...sed-ports/ = = = = Sketch a diagram of your network starting with where ISP service enters your house. Include ISP devices. Note makes and models. lnclude all cables, splitters, wall ports, and devices. Including electrical connections to wall outlets. Plus surge protectors, power strips, UPSs, as much as you can find and record them. Check for any grounding (earth) wires. Make note of their locations. Physically inspect everything so much as possible. No climbing on roofs or similar dangerous things. Look for signs of damage: rust spots, kinked or pinched wires, bare metal showing up, loose connections, rodent chewing, nails/staples cutting into wires. Connections to "nothing". Connections that are not expected or recognized. Include any remaining splitters. If you only have ports used on a four port splitter, then replace the splitter with a two port one. Splitters are cheaply made and can and do fail. Or become very problematic while they last. More info: https://www.flukenetworks.com/knowl... Note that "to" means to the other output port . Look for any sort of loop where Device A connects to Device B which then connects to Device C which is somehow connected back to Device A again. No matter what type of cables or path involved. The main goal is to exclude some physical problem with network and device connections.
K
Kid_Jason
10-22-2026, 12:49 AM #12

Try 24 hours. = = = = With the whole network broken, everyone needs to check everything again. I don't know if the ISP really tested the cables, connectors, and stuff like that. Technicians are often under a lot of pressure and will swap out splitters. Everything seems okay and is happening with intermittent problems. They leave, problem "resolved". Then you get errors again. After reading back, noted that splitters had been taken out which made me think of other things. How do any unused coax cables get connected? There are special plugs for this versus just some "dust caps". NOTE: https://blog.solidsignal.com/tutorials/t...sed-ports/ = = = = Sketch a diagram of your network starting with where ISP service enters your house. Include ISP devices. Note makes and models. lnclude all cables, splitters, wall ports, and devices. Including electrical connections to wall outlets. Plus surge protectors, power strips, UPSs, as much as you can find and record them. Check for any grounding (earth) wires. Make note of their locations. Physically inspect everything so much as possible. No climbing on roofs or similar dangerous things. Look for signs of damage: rust spots, kinked or pinched wires, bare metal showing up, loose connections, rodent chewing, nails/staples cutting into wires. Connections to "nothing". Connections that are not expected or recognized. Include any remaining splitters. If you only have ports used on a four port splitter, then replace the splitter with a two port one. Splitters are cheaply made and can and do fail. Or become very problematic while they last. More info: https://www.flukenetworks.com/knowl... Note that "to" means to the other output port . Look for any sort of loop where Device A connects to Device B which then connects to Device C which is somehow connected back to Device A again. No matter what type of cables or path involved. The main goal is to exclude some physical problem with network and device connections.

B
Bamlak_Bekele
Member
63
10-22-2026, 06:52 AM
#13
I turned it on for 24 hours and checked it out a few times. It looks like that helped. No more disconnects since then, and the errors are gone too. I'm giving it another day to make sure everything is really stable and working. If I am happy with it, I'll say the thread is closed. If not, I will reply to all your questions later.
B
Bamlak_Bekele
10-22-2026, 06:52 AM #13

I turned it on for 24 hours and checked it out a few times. It looks like that helped. No more disconnects since then, and the errors are gone too. I'm giving it another day to make sure everything is really stable and working. If I am happy with it, I'll say the thread is closed. If not, I will reply to all your questions later.

Pages (2): Previous 1 2