Unsolved
7 Posts
0
162
Secure Connect Gateway could not determine the IP Address
Hi Everyone,
I am attempting to deploy Secure Gateway, latest version, on a Hyper V Cluster (2022). The deployment seems to go fine and the YAST2 window opens. There I am adding the IP address this VM will use, the gateway, and DNS entries. Also create the "admin" account and password. That part appears to go well.
Once that is all done however, the webUI does not come up. I am not able to ping the VM either (not sure if that should work or not?). I cannot sign into Linux with the "admin" account either.
Only message I get is the one mentioned in the Title.
I am on my 4th attempt...not sure what I am missing?
DELL-Young E
Moderator
Moderator
•
3.7K Posts
0
November 21st, 2023 04:11
Hello thanks for choosing Dell.
If a user is unable to ping the IP address, they will not be able to access both the UI and the CLI (via Putty)
Also, to login to the SSH session, they need to be using the “root” account and not “admin”
Make sure that the IP address specified does not clash with the default docker.
There’s a public-facing KB article which explains this
Managed devices cannot communicate with Secure Connect Gateway, and/or the SCG cannot communicate with the Policy Manager for SCG due to network conflict with internal Docker network | Dell US
We can also refer to Chapter 3 - Unable to access the Secure Connect Gateway user interface of the Secure Connect Gateway — Virtual Edition Troubleshooting Guide (https://dell.to/3SRuqGW)
Respectfully,