- Joined
- Jul 17, 2003
OK guys. Not looking for hocus pocus solutions. I know I'm missing something very very basic. My home network can't connect \\firefly\ to 192.168.1.9. I've simplified my network to the following:
Ubiquiti Cloudkey plus Gen 2. Ubiquiti USG v4. 2x Ubiquiti 802.11 AC WAPs. One old Cisco PoE switch. One Netgear non-managed "green" switch. Motorolla MB 8611 cable modem.
I removed my Pihole. I also got rid of my ASUS router which was acting as a WAP for IOT.
Modem ---> USG v4 ---> "green" switch ---> Cisco PoE --->WAPs
Note: On the Cloudkey, I have set static DHCP routes for my managed IOT/Networking and servers. I have an Unraid server called Firefly that will not resolve to the assigned IP. I have power cycled the entire network the other day after making more adjustments.
Again, this is going to be something basic. Something that I should know but don't. It will be embarassing when you guys point me in the right direction. I just know it.
Ubiquiti Cloudkey plus Gen 2. Ubiquiti USG v4. 2x Ubiquiti 802.11 AC WAPs. One old Cisco PoE switch. One Netgear non-managed "green" switch. Motorolla MB 8611 cable modem.
I removed my Pihole. I also got rid of my ASUS router which was acting as a WAP for IOT.
Modem ---> USG v4 ---> "green" switch ---> Cisco PoE --->WAPs
Note: On the Cloudkey, I have set static DHCP routes for my managed IOT/Networking and servers. I have an Unraid server called Firefly that will not resolve to the assigned IP. I have power cycled the entire network the other day after making more adjustments.
Again, this is going to be something basic. Something that I should know but don't. It will be embarassing when you guys point me in the right direction. I just know it.