1

I am testing out spiceworks remote monitoring tools for my company. I want to test out a few machines locally before a do any types of mass deployments. I have a local machine as a central server and another machine im trying to install the agent on.

Im setting up my “Remote Site Configuration” with the IP of the Central server (local ip of the machine since im just testing this in house before out of the office.) Central Port number is setup to 9676. But it still says server not responding when trying to save.

I have tried 9675, 80, 443 and changed them around in preferences. It still cannot find it. I have disabled all firewalls and AV’s on this machine.

Any assistance would be appreciated.

Thank you

2 Spice ups
2

You have double checked which ports the local Spiceworks install is using?

3

Untitled.png

These are the ports. Not sure why its not working.

Thank you for the reply

4

I haven’t worked on the remote agents yet myself, but lets see.

Have you checked out this link.

http://community.spiceworks.com/help/Spiceworks_Agent

5

Yes i have. I went through it twice and still nothing. Not sure what im doing wrong.

6

Are you running the connectivity test, or are you skipping that and trying to run the rest of the installer? There is currently a bug around the connectivity tests, having to deal with hostnames instead of IPs, but that might be part of what’s happening here.

1 Spice up
7

I’m going to be useless for debugging here, but the thing that confuses me is you’re talking about configuring your remote site to talk to the Central Server, but you’re also talking about hooking up the agent. Are you trying to hook up your agent to your remote site or the central server? If it’s the central server, then your remote agent and it’s settings don’t really come into play here.

In order to set up your agent, you need to set the Remote Agent Settings (not the Remote Site) from where you want the agent to connect to. And your ports for the agent will be whatever that Spiceworks installation is actually running on.

Jackie.

1 Spice up
8

@Jackie

I apologize for my ignorance as I’m still green when it comes to the spiceworks tools. So my plan is to test the spicework agent on a few laptops here locally. If it can do what I need it to do (which isnt much) then I will test it externally.

Form what you’re saying,

  • I can test it internally by just getting the correct settings for the Remote Agent and making sure its correct there.

-To get it working externally im sure i have to do some nating to the Central server and setup the Remote Site settings there.

Is this the case?

9

Got it. And no need to apologize - learning is good and we’re here to help. I just didn’t quite understand things.

Peter is better than me at this and may have more advice, but here’s what I think. Testing your agent against the Central Server if you intend to move it to a remote site is probably not worth your time - because you’re going to have to reconfigure/redo the agent to point to the remote site.

Note that you aren’t required to have a remote site for agents - you would use this to balance the number of agents you have out or if the agents are more likely to live at another location.

So, if you need the remote site, I would say get that setup and working first. Then, get your agents pointed to that.

Now, if all you’re trying to do is see how Spiceworks and the agents work, then disregard everything I said, and ignore your remote site for now.

Also, what version of Spiceworks are you on? There was a version or two in 7.4 that had a bad agent on it. So I would say you definitely want to ensure you’re at least on 7.4.0119 or upgrade to 7.5.

Jackie.

2 Spice ups
10

@Jackie

Thank you for your help. I am going to be using it for testing internally and Im in no rush, I just want to have something to toy around with to see if it can be utilized for my needs. So I will just work on the Remote Agent and not the Remote site for now.

Im on Spiceworks Version 7.5.00053, hopefully it wont be a problem.

Ill try this out and let you guys know if I have any issues.

Thanks

1 Spice up
11

Angelo,

You might be getting tripped up on the verbiage.

Remote Site = Another Spiceworks install that scans a network and forwards that data back to a “Central” Spiceworks install. This is useful if you have a branch office at the other end of a VPN and you don’t want to send all the scanning traffic over the VPN. The Remote Site (also called a Remote Collector) does the scanning then forwards that data back to your Central Spiceworks install.

Remote Agent = a small app that you install on a laptop (for instance) that will scan that single machine and send that data back to your Central Spiceworks install.

The following is a screenshot of the setup process for the Remote Agent. On this screen, enter the information for your Central Spiceworks server.

1.PNG

The next screenshot is my Remote Sites & Agents settings page on my Central Install. If I wanted to convert this to a Remote Site (AKA Remote Collector), I would press the circled button. However, in your case, I don’t think you want to do that.

2.PNG
2.PNG800×425 122 KB

I hope this helps clear things up. Let me know if not and we’ll see what else we can do!

2 Spice ups
12

@ Peter

Thanks that does help a lot. It makes sense now. It seems pretty straight forward.

Thank you

1 Spice up
13

Sweet! Let us know if you hit any snags along the way, or if you have any other questions!