Yes, I have a support case (712756) and solarwinds has tried everything. The ticket is actually closed now and I am in the process of trying to recreate that environment within our network to eliminate any firewalls and security in between. I see duplicate agent events and warnings. See below
| Event Field | Information |
| Event Name | InternalWarning |
| EventInfo | Agent simon has a duplicate agent of the same name. |
Yes, the connect reset is happening every time it duplicates itself. I have been trying to recreate the issue with other agents. In fact, by pure luck, agents that connected fine before had the same issue, but resetting the spop folder and restarting the service fixed the issue. This one set of agents, I just cannot find out what the issue is. The server is a VM, can you think of anything on an ESX host that can prevent the agent from coming online?