1

Hi All,

Please can someone assist me with my Spiceworks installation.

  • I have a master Spiceworks server located at Head Office.

  • I have 19 remote sites reporting to this Spiceworks instance.

  • I have not had any problems at all in adding other sites, and all has been running well for several months.

  • I have just attempted to add 3 more site. 2 are 100% OK and reporting like all others!

Image_1.png
The issue is with the 3rd site.

  • Setup was identical to all other sites.

  • This site is “stuck” with this status:

Image_2.png
Does anyone have advice?

What I’ve tried so far:

  • Wait.
  • Waited some more.
  • Reboot BOTH remote site and host server.
  • Complete Uninstall of remote site Spiceworks and re-install (twice!)

My Host server CAN “see” the remote host and knows it’s there. But no scans work and no information is transferring between the two - not surprising given the screenshot above.

Any and all assistance greatly appreciated! :slight_smile:

2 Spice ups
2

Update for all. After waiting even longer… the Remote Site now reports the following:

Image_3.png

What does this mean, and how can I correct this please?

3

Hi

That would tell me that the firewall port is not allowing the traffic out/in

Can you telnet from the remote site to your server using the correct port ?

1 Spice up
4

Definitely sounds like a connectivity issue. Verify layer 3 and no firewall/filtering in between.

5

@Philip2292 & @gurulee

Thank you both, I don’t think it’s the firewall. The traffic on the Spiceworks ports has been set to allow. I’ve also turned off the Windows FW to test. Still able to “connect” with the remote site, but unable to get anything more.

*Edit: I can confirm that Telnet on the port works.

6

I had this one time when a naughty space had appeared at the start of the server name/ip address hence I was getting communication error, but as narrow space could not see it, neither could my colleague for ages

7

@Philip2292 - Yeah I’ve had that before, especially when using copy/paste… but that is not the case here. Double checked, no spaces.

8

bugger

9

I am not precious about this misbehaving site. I am happy to trash it’s Spiceworks setup and start over. However, the host Spiceworks server seems to “remember” it.

Is there a way to get the host server can be made to “forget” the problem site entirely and start completely afresh?

I have tried uninstalling Spiceworks at the remote site, and reinstalling twice - but the host server still “remembers” it.

10

Go into Settings for Inventory and click on Remote Sites and Agents

In there click Manage Your Remote Sites and should be able to highlight and delete the troublesome one.

11

Yes, have done that on each occasion… but the host Spiceworks still seems to “remember” the site.

I think it’s related to it still knowing the UUID (or something like that). Is there a way to flush that out the system entirely?

12

The UUID is stored in Settings - Global Settings - Advanced Options and third item down.

When you re-install at the remote site this should generate a different UUID each time

EDITED

Ignore that - just investigating for you and it generates from the machine serial number/mac & IP

if you login with a different Spiceworks user for the first time then it should change the UUID - don’t ask just found that on another post

13

Hi

It is the same version isn’t it ? They released a new version a couple of days ago and just hoping you have not downloaded it each time fresh from each remote site but using the same version as your master

14

Thank you for further investigating… I can confirm that the Spiceworks version is the same as the version running on the host Spiceworks machine.

I guess I cannot change the UUID of the remote site. The machine it’s on cant change, and it’s logging in with the same Spiceworks account as all the other sites.

Any other ideas why this particular remote site will allow remote connection, will “check-in” with the host server at regular intervals, but just will not fully authorise and send data?

15

Hi

If you flick the Remote one into a full blown Spiceworks does it have anything in the inventory/devices etc ?

If it does then bulk delete the lot so there is nothing in it’s own database. Restart the SW service and then flick it back into remote collector and run a discovery scan to see if that clears the issue.

16

I’ve done as suggested and took the remote site and put it back to “full Spiceworks”. I bulk deleted all items in the inventory (all of 5). And then re-converted it back to being a remote site. Still no change!

Update: I have attempted to install Spiceworks at another site of mine. Similar issue. That site does not seem to ge getting a message back from the host server to say that it has been authorised. See image below.

Image_5.png

Something wrong with the Host now, surely??

17

It would look like that but I would worry about taking it down as you may lose connection to your other Remote sites.

You don’t have a new firewall/ISP who monitor your connections and not allowing your external HTTPS connection through are you - I know you tested telnet but if new site doing same that is very odd (or Windows update blocking something - SSL issue maybe ?)

18

No changes at all in regard to the ISP, router, firewall etc. All other 18 sites are all reporting as expected (including the 2 new ones setup at the same time as the problematic one in the initial post above).

This is frustrating and worrisome.

* Update: Good progress. The second site not working must have been a red-herring. It is now communicating the same as all other sites. Back to just the one problematic site from yesterday.

Any ideas?

19

That’s Good on one count.

Can you telnet to your HTTPS port in both directions - just a thought

20

Just tested Telnet from each Spiceworks server to the other’s HTTPS port. Both connect…