Hi, i am new to splunk , so there is a few question i would like to ask. I got two computer A and B.
Computer A is install with splunk. How should i configure my computer so that i am able to access my splunk content(installed in computer A) using computer B remotely. Thanks!
I had this issue and after creating an inbound rule to allow TCP port 8000 on the firewall on the system where Splunk is installed. For an "Enterprise" product, one would think simple check boxes will make this happen, same goes for issues everyone is having discovering and getting data from remote machines, even on a Windows AD domain controller. Not so "enterprise", if you ask me.
MuS, you may be right. I removed the allowRemoteLogin entry form server.conf and am still able to remotely access splunk web UI. I guess its simply having to allow inbound traffic to port 8000 (or whatever you may change it to in Splunk) in the firewall on the system hosting Splunk. I have updated my earlier how-to response.
Splunk is accessed with a browser so any computer on your network should be able to connect to it provided you don't have firewalls blocking them. If you haven't made any changes, point your browser to port 8000 on the other computer.
Same way you would access any other service on your network. How you would go about doing that varies wildly depending on your network setup. Again, this is not really a Splunk issue so you should post this question with details on your network setup in a forum that deals with this kind of issues.
Also allowRemoteLogin in server.conf has nothing to do with Splunk's web interface, it controls access to splunkd (which if you do not know what it is you likely don't need to at this time either).
Hi , using server .conf and putting the allowRemoteLogin = Always. i can use computer B to access the splunk of computer A under the same network . Is it possible to access it with different network?
If the network knows that computer by the name world then yes. Quite often a computer will use a name for itself that the network does not understand and this may be the case here. If this is on a private network you may have to use the ip address.
To find out the computers ip address open a cmd, dos or terminal window and run the command
You wil see a set of 4 numbers seperated by dot probably starting 192.168. Use this in place of the computer name.