Forum Discussion
Getting error after creating NTLM machine account
After we created an NTLM machine account we are getting this error. When looking into AD we see the account have been created. Is there anything else we need to look at?
May 19 13:26:35 f5boxname err nlad[12196]: 01620000:3: <0x55d61b90> nlclnt[13f04640a] init: Error [0xc000006d,NT_STATUS_LOGON_FAILURE] connecting to DC x.x.x.x (IP of domain controller) May 19 13:26:35 f5boxname err nlad[12196]: 01620000:3: <0x55e62b90> nlclnt[13f04640a] init: Error [0xc000006d,NT_STATUS_LOGON_FAILURE] connecting to DC x.x.x.x May 19 13:26:36 f5boxname err nlad[12196]: 01620000:3: <0x56064b90> nlclnt[12a35640a] init: Error [0xc000006d,NT_STATUS_LOGON_FAILURE] connecting to DC x.x.x.x May 19 13:26:36 f5boxname err nlad[12196]: 01620000:3: <0x56266b90> nlclnt[12a35640a] init: Error [0xc000006d,NT_STATUS_LOGON_FAILURE] connecting to DC x.x.x.x May 19 13:26:36 f5boxname err nlad[12196]: 01620000:3: <0x56468b90> nlclnt[12b35640a] init: Error [0xc000006d,NT_STATUS_LOGON_FAILURE] connecting to DC x.x.x.x May 19 13:26:36 f5boxname err nlad[12196]: 01620000:3: <0x56569b90> nlclnt[12b35640a] init: Error [0xc000006d,NT_STATUS_LOGON_FAILURE] connecting to DC x.x.x.x May 19 13:26:36 f5boxname err nlad[12196]: 01620000:3: <0x56367b90> nlclnt[12b35640a] init: Error [0xc000006d,NT_STATUS_LOGON_FAILURE] connecting to DC x.x.x.x
21 Replies
- kunjan
Nimbostratus
Are you able to "Renew Machine Password".. Access Policy ›› Access Profiles : NTLM : Machine Account
The error seems to show the account created is having issues.For client side NTLM auth debug logs, following db key should help:
.tmsh sys modify db log.eca.level value debug - Peter_Baumann
Cirrostratus
Hi kj07208, I have exactly the same problem here. And when I enabled debug I see the following:
Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> nlclnt[40d148d0a]: is now initializing. Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> NLAD_TRACE: cli_full_connection(output_cli = 0x9392a68, my_name = "CHSRV035", dest_host = "chsrv113.ads.domain.com", port = 445, service = "IPC$", service_type = "IPC", user = "CHSRV035$", domain = "ADS") Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> NLAD_TRACE: cli_full_connection(output_cli = 0x9392a68) = 0x0 Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> NLAD_TRACE: cli_rpc_pipe_open_ntlmssp(cli = 0x9392a68, domain = "ADS", username = "CHSRV035$", presult = 0x9390d20) Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> NLAD_TRACE: cli_rpc_pipe_open_ntlmssp(cli = 0x9392a68, presult = 0x9390d20) = 0x0 Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> NLAD_TRACE: rpccli_netlogon_setup_creds(cli(pipe) = 0x9390d20, server_name = "chsrv113.ads.domain.com", domain = "ADS", clnt_name = "CHSRV035", machine_account = "CHSRV035", neg_flags_inout = 0x600FFFFF) Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> NLAD_TRACE: rpccli_netlogon_setup_creds(cli(pipe) = 0x9390d20) = 0x0 Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> NLAD_TRACE: cli_rpc_pipe_open_schannel_with_key(cli = 0x9392a68, domain = "ADS", pdc.mach_acct = "CHSRV035$", pdc.remote_machine = "\chsrv113.ads.domain.com", pdc.domain = "ADS", presult = (nil)) Jan 20 16:27:56 chsrv035 debug nlad[6717]: 01620000:7: <0x56805b90> NLAD_TRACE: cli_rpc_pipe_open_schannel_with_key(cli = 0x9392a68, presult = (nil)) = 0xC00000CA Jan 20 16:27:56 chsrv035 err nlad[6717]: 01620000:3: <0x56805b90> nlclnt[40d148d0a] init: error [0xc00000ca,NT_STATUS_NETWORK_ACCESS_DENIED] setting up secure pipeI don't know how to fix that. What I will do is delete the NTLM Machine Object in AD and recreate it again. If it is not working, I will open a case at F5.
- Peter_Baumann
Cirrostratus
I just tested it in another environment with standard AD install (No changes in Tree). I have exactly the same problem here. Is think this feature is not working in general. I will open a case and post the answer here when I have news...
- SL
Cirrus
Hi Anyone have an update on this issue?
- Peter_Baumann
Cirrostratus
Hi all, According to F5 this problem will be fixed in the upcoming v12.
- kunjan
Nimbostratus
May be can try restarting nlad.
There is an open bug when Netbios name doesn't match AD FQDN. Otherwise it should work.
- SL
Cirrus
I resetart nlad, no luck.
The issue is that I am being tasked to configure the F5 to replace the RDP Gateway Servers. I am following the following, http://www.f5.com/pdf/deployment-guides/microsoft-remote-desktop-gateway-dg-rc1.pdf
It is not working and I believe it has to do with the device not able to connect properly to AD.
- kunjan
Nimbostratus
have you tried enabling debug? What does the log say?
- kunjan
Nimbostratus
What is the NetBios name for the domain?
- SL
Cirrus
the NetBios name would be 'sub' so it looks like the Netbios Name that the device is trying to use is not correct. Is there anyway i can update what Netbios name to use?
- kunjan_118660
Cumulonimbus
What is the NetBios name for the domain?
- SL
Cirrus
the NetBios name would be 'sub' so it looks like the Netbios Name that the device is trying to use is not correct. Is there anyway i can update what Netbios name to use?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com