Network Configuration for Windows Domain Management Overview
Network Configuration for Windows Domain Management Overview
I have a Pfsense router, Unraid server, and five Raspberry Pi servers plus some Windows PCs. Problems: On my main PC nothing appears except my own device, other Windows PCs just show media items, even though they appear. I want to set up a website like Octopi's local interface so it works from any IP, including my Windows PC. I need to configure the localhost address for a site such as http://Blueiris.Local pointing to my Windows PC's webpage. Should I set the domain and workgroups in Pfsense? Can I use .local as a hostname? Also, can I configure the local.home port to redirect somewhere? Help would be appreciated—I want a cleaner network setup and easy-to-remember names.
The entries visible beneath networks in Windows Explorer typically represent other devices on your network that run services Windows can identify, such as Samba or a printer share. The protocol usually attempts to determine which machines are present but often struggles to recognize unknown systems, particularly when no profile exists for them—like identifying printers based on open ports and responding services. If this doesn’t resolve the issue, it may mean the network devices aren’t supported or network discovery is disabled on your Windows machine. To view web content on your PC, you’ll need to examine hosting services like IIS or Apache. PFSense offers its own web stack but requires you to supply site-specific configurations. For identifying machines via FQDNs, Windows provides a service that attempts to collect hostnames, though results are often unreliable. A more dependable approach is to add entries in the hosts file on each machine. If you manage many devices, consider using a DNS service. Since you’re already running PFSense, simply enable the DNS service, create necessary entries, and configure all machines to use PFSense as their primary DNS.