Troubleshooting a Connection Issue in Instant Clone Pool with ControlUp

Having trouble connecting to an instant clone pool, users discussed a variety of potential causes including a DNS resolve issue, a NetBios name not matching the machine name, and a DNS scavenging issue. Troubleshooting advice included running the Agent diagnostic in the RTC, pinging the PC running the console and from the monitor server, flushing DNS, and looking for information in the log.

Read the entire ‘Troubleshooting a Connection Issue in Instant Clone Pool’ thread below:

Having trouble connecting to an instant clone pool. Pings from the Agent diagnostic in the RTC are returning the wrong IP. Pinging from the PC running the console and from teh monitor server are correct.

i have seen that before meant to raise a ticket on it. i think you see wrong results in nslookup as well

yes,

its working now. we’ve had DNS issues all morning.

try flushdns

It’s a DNS resolve issue

it happens when the NetBios name is not the same as the machine name

for those with SentinelOne, if you use S1 to disable S1, its supposed to block ALL network traffic except traffic to the S1 cloud. This means it blocks traffic to local DNS. still trying to figure out how that allows S1 to function without access to dns

yeah like you experienced thats 99,99% of the times a dns issue

yeah put i think question is why when you use command prompt from with controlup dianostics thise it get different reults. is the DNS stuiff cached in the agent?

good question

been meaning to ask this for ages @member thanks for the reminder

FYI Netbios name is 6001-ccts-1

Machine name is 6001-ccts-1

This is strange because the check that we perform for DNS resolution is comparing the Netbios and machine name of the agent computer.

By the way, you should see more information in the log, containing the expected and actual name.

The name returned from the remote machine does not match the expected Netbios name.\r\nRemote name: {0}, expected: {1}.\r\nMake sure the Dns resolve process is correct, and that there are not IP conflicts.", agentInfo.MachineName, _sNetBiosName)

Where is the log?

it could also be a dns scavenging issue: multiple ip records for the same dns name. We get one returned connect to that ip and it turns out to be a different system as the ipw as already re-used

Continue reading and comment on the thread ‘Troubleshooting a Connection Issue in Instant Clone Pool with ControlUp’.  Not a member? Join Here!