No network connection when fiber optic cable is connected to router

No network connection when a router is connected to fiber can result from physical cable issues, faulty hardware, or configuration errors.

Check Physical Connections

Ensure the fiber optic cable is properly connected to the router or ONT (Optical Network Terminal). Inspect the cable for visible damage, sharp bends, or loose connectors, and clean connectors with lint-free wipes and isopropyl alcohol if necessary. If possible, test the fiber signal strength using a power meter or OTDR; values outside the normal range (-15dBm to -30dBm) may indicate a problem.

Verify Router and SFP Modules

Confirm the router is fiber-compatible and connected to the correct LAN/WAN port. Check the status lights: a solid green light usually indicates proper connection, while blinking or red lights may signal issues. If using SFP modules, ensure they are compatible with both the router and fiber type.

Swapping with known-good modules can help isolate faulty hardware.

Test Network Configuration

Check that the router is receiving an IP address from the ISP. If not, reboot the router and any upstream modem or ONT. Ensure there are no IP conflicts or rogue DHCP servers on the network.

For devices connected to switches, try assigning a static IP to test connectivity and ping other devices to confirm the link is functional.

Inspect Switches and Intermediate Devices

If the fiber runs through switches, verify that the switches are operational and compatible. Even if link lights are on, dumb switches may not forward traffic correctly if there is a mismatch in SFP modules or configuration. Consider temporarily connecting devices directly to the router to isolate the problem.

Environmental and Hardware Considerations

Check for power issues, tripped breakers, or GFCI outlets if the fiber terminal is outdoors. Environmental factors like temperature extremes, moisture, or physical damage can degrade fiber performance. If all else fails, contact your ISP or fiber provider for advanced diagnostics, as persistent issues may require professional testing or replacement of components.

By systematically checking physical connections, hardware, configuration, and environmental factors, you can identify the root cause of the no-network issue and restore connectivity.