Did you configure your Splunk server to use a different port than standard (i.e. 80 instead of 8000)?
If so, you might have 2 different web servers on port 80 - the default IIS page and Splunk. You could disable IIS to resolve that, assuming this is the case. Also, it seems that:
https://<yourDNShostname>/en-US/app/launcher/home
should work from anywhere in the environment if your DNS is set correctly. Assuming you set Splunk to run its web interface on port 80, here's how I'd troubleshoot:
Is the Splunk server running?
- Check it under Services.msc
- Hit it on the Splunk server with the localhost URL you are using on the Splunk server
- You can also confirm what port it's listening on at the CMD with netstat -abn | findstr splunk (if you see results, then run without the findstr and look for Splunk to ID its associated port)
Is the Splunk server sharing its port with another web server?
- http://localhost should tell you if something else is running on port 80
- Disable IIS or change ports for Splunk or IIS
Can you hit the Splunk web interface from another system?
- use http:///en-US/app/launcher/home
- Is your Windows firewall or a network firewall blocking traffic to this site
Assuming the above works, can you resolve the DNS name you've set up?
- From the Splunk server, ping and see if it resolves
- From another machine, ping and see if it resolves
- If not, DNS isn't setup right
If Splunk is running and you can hit it locally with localhost or by IP, then it's probably a port conflict with IIS, host/network firewall issue, or name resolution issue.
-Andrew
... View more