Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InstallAgent will not function correctly in environments where outbound ICMP is disabled #38

Closed
AngryProgrammerInside opened this issue May 26, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@AngryProgrammerInside
Copy link
Owner

In some environments ICMP outbound is blocked for security purposes, in these cases the default behavior of InstallAgent is to fail the install or go into offline repair mode of services.

In either case these environments need another method for determining connectivity to the server.
For backwards compatibility The System.Net.Sockets TCP class could possibly be used, but this class gives errors while running under CLI/Scripting due to some kind of .Net configuration issue, similar to the issue experienced.

Another less backwards compatible option is the Test-NetConnection -Port option, this only works on later versions of PowerShell and has some compat issues on Server 2012.

The last method may be to simply perform a https web request against the N-Central server itself, there are basic .Net methods that are compatible with all versions of powershell .

@AngryProgrammerInside AngryProgrammerInside added the enhancement New feature or request label May 26, 2021
@AngryProgrammerInside AngryProgrammerInside self-assigned this May 26, 2021
@AngryProgrammerInside
Copy link
Owner Author

Added resolution via WSDL verfication in 6.0.2a WSDL Verfication branch, pending testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant