Please help me with this network black magic stuff.

I'm not sure what's going on with our network.

We have a LAN with roughly 100-150 devices. This LAN has two Ubiquiti Access Points, a couple of Netgear Routers in AP mode, consists of 3 gigabit switches, and a Cisco ASA that handles our firewall and routing.

For some reason, every morning, it's a guessing game as to which computers can reach the internet. The only ones that seem to always work are the ones that are running or being used 100% of the time, which is only 3-4 machines. I spent the better half of 3 hours this morning trying to get 5 machines back online. They can reach anything on LAN perfectly fine, which is great. Pinging a host resolves IP address, but get no reply. Path ping and traceroute are useless, they go nowhere. Routes are correct, 0.0.0.0 through 192.168.55.1 which is our router, with the lowest metric.

Usually, I'll end up just running ping -t google.com, and within 30 minutes I'll suddenly see packets. Then we won't have another issue till the next day.

I'd assume it was the computers themeselves, but this happens on numerous machines randomly. Some have the same problem frequently though.

Side note, our DHCP server is on a Windows 2008 R2 machine, and it shows numerous BAD ADDRESS fields. Some of the machines that are having these issues though are given reservations, so I wouldn't think it's a numerous IP issue??

I'm not an expert and get a little lost with the ASA, but it doesn't seem to show anything out of the ordinary...I'm only using the ASDM software to manage it though.

Can someone please help?

Also, here is what I mean by I'll start a ping and after waiting some time will get connected. I would say it's just time but if I leave the computer be and do nothing it'll never get back online. Sometimes the network icon in the taskbar will also SHOW that it has connection, and not be able to reach out.

C:\WINDOWS\system32>ping -t google.com Pinging google.com [216.58.195.14] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 216.58.195.14: bytes=32 time=106ms TTL=51 Reply from 216.58.195.14: bytes=32 time=30ms TTL=51 Reply from 216.58.195.14: bytes=32 time=138ms TTL=51 Reply from 216.58.195.14: bytes=32 time=31ms TTL=51 Reply from 216.58.195.14: bytes=32 time=42ms TTL=51 Reply from 216.58.195.14: bytes=32 time=45ms TTL=51 Reply from 216.58.195.14: bytes=32 time=29ms TTL=51 Reply from 216.58.195.14: bytes=32 time=32ms TTL=51 Reply from 216.58.195.14: bytes=32 time=30ms TTL=51 Ping statistics for 216.58.195.14: Packets: Sent = 40, Received = 9, Lost = 31 (77% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 138ms, Average = 53ms