We have been having one heck of a time trying to get the firmware repository setup for NCM. We have one polling engine that is throwing an "unable to connect to polling engine" error every time we try to set this up. We opened a ticket with SolarWinds but they ultimately stated that this storage location has to be accessible from ALL polling engines (and then closed their support ticket). This is a bad design. At any rate, this particular engine being referenced is one related to PCI compliance so our first thought was that something on the network side was preventing access, but that's simply not the case. We can physically access the file server (storage location) from the polling engine itself, it's only when we use the web console to set the storage location that NCM thinks it can't. Does the primary polling engine reach out to the APE's to verify access? If so, there may be something between the primary engine and this APE that is being referenced...
Has anyone else seen this before? I'm open to any ideas or suggestions anyone may have.
Does anyone else have any insight that might be of assistance here? SW support has proven to be of no help in getting this resolved, and my team really needs to start using the firmware repository.
We just encountered a similar problem. Polling engines in two separate domain environments for PCI compliance and couldn't get one to access the other or vice versa. In the end we created the repository on a server in each environment and used the same local account on them so when inputting into solarwinds we used the \\127.0.0.1\pathtorepository file path with the credentials created. This worked for us.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.