1

My office has been using the spiceworks helpdesk for a while now and we are now beginning to use the Inventory portion. All of our offices are at remote sites so I have been testing out the Remote Site feature of the network scan.

Everything went just fine with the first remote site… scan data is making it’s way back to our central server… however when I added the 2nd remote site, it is like it is overwriting the previous remote site. Originally the list of “remote sites” on our central server would say “Site1.” Once I went to authenticate my 2nd remote site, all that would show up in the “remote sites” list of the central server was “Site2.” Site1 had completely vanished. All of the actual inventory data was still there… just the original site had disappeared.

The 2 spiceworks remote servers are on two different IP’s.

Any ideas?

4 Spice ups
2

First, are you on the latest version of SpiceWorks? If no I highly recommend updating first. On the dashboard lower left corner hover over the pepper, this will show you your current version and any new ones available.

You can download the latest form here,

http://community.spiceworks.com/topic/163371-spiceworks-update-5-2-75206-now-available

Next, make sure all your remote sites are on the exact same version and upgrade them if needed.

Next, try clearing your browser cache. (this can actually solve many issues seen in SW being a web app)

If that doesn’t help, then try disabling your plugins. On your central server, navigate to settings, manage extensions, and then upper peft click the disable plugins. Restart the server and try again.

I’m also going to include the help guides for remote collectors for you to look over just to make sure nothing was missed.

http://community.spiceworks.com/how_to/show/283

and

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

Good luck, and let me know how it all goes, and what your results are.

-Jay

3

Hi Nic,

Also make sure that you are installing the Remote Collectors from scratch. Using a backup during installation could lead to your central installation having difficulty telling the Remote Collectors apart.

Aaron

4

All three servers are running the latest version. Tried clearing the cache, disabling plugins and restarting the central server to no avail… also have tried uninstalling/reinstalling spiceworks from the 2nd remote site and still does the same thing.

No backup DB’s were used in the creation of the remote sites.

All I did was standard install, then went to remote site settings page and hit “enable remote site mode” and put in the info for the central server.

Attached is what i Think the corresponding log for the 2nd remote site coming in the central server. Was in the production log.

errorRemoteSite.txt (1.91 KB)

5

According to the log it can see it (reachable). So technically both sites have been setup as remote sites to talk back to central at this point correct?

Restart the central server?

-Jay

6

Only thing is that in the logs it says that it is changing the site name from Site1 to Site2. And have already tried restarting the central server.

7

So both sites are up, it’s just that whatever one was the last to be setup seems to be the only one that can see the central site. Something must be conflicting…do these remote collectors have unique machine names?

You said they are different IP’s, can you give some more detail like what are the subnets for each remote collector, how are they connected back to central, etc.

-Jay

8

Correct, whichever is the last to authenticate replaces the other. One is on subnet 10.12.80.0/24, other is 10.12.93.0/24. Central server is on another subnet… won’t give you the real number but let’s just say 10.12.1.0/24 Two different types of machines (1 being an HP server, other is basically a powerful desktop). The two machine names are different. Both of the machines were already scanned by the central server on a network scan (from before i started messing with remote sites) and it sees them as different machines.

Now the thing that has me thinking is that both the remote sites are running on the 9675 http port and https is 9766 for both remote sites. Main server is on 80/443. I can’t use port 80 on these machines because they are already running something on that port.

9

Can you change the central servers ports to match just to test?

And I’m wondering, I always setup my remote sites first, then they scanned and sent the data back, I wonder because they are already in your inventory if that’s causing an issue.

Here is what I would do (if the ports don’t work)

Uninstall SpiceWorks from both remote sites. Remove those machines from inventory from the central server. From the remote sites go and download SW from here,

http://community.spiceworks.com/topic/163371-spiceworks-update-5-2-75206-now-available

Install, and setup as a remote site and connect them back up to central.

-Jay

10

Sorry for the delay, just tried 2 things and still the same thing is happening.

  1. Tried switching the port numbers of the central server to match the remote sites. and no worky.

  2. After moving the central site back to the original settings (80/443) I tried to change the port of one of the remote sites so that each remote site was using different ports and that didn’t work either… they are still overwriting each other.

11

Ok, apparently both of the remote sites have the same UUID. (went to Advanced and International Settings and check the pro settings there). No idea how it got that way.

Going to look up how to change it… anyone know how to?

12

Not sure off hand. An uninstall and reinstall might do the trick if that is an option.

-Jay

13

Ok my problem is solved (actually solved it a few days ago but just adding this in here in case anyone else runs into this issue. On our network, our proxy server freaks out if any URL’s are too long… well the community page that spiceworks likes to go to when installed (to get the unique UUID) is one of those very long locations.

So all we did is allow that website to bypass the proxy server so that it obtained it’s UUID, then blocked access again. Remote sites working fine now.

Thanks for your help Jay.

14

That’s awesome, would have never thought of that, thanks for the update.

-Jay