LDAP not yet initialized #29071
-
|
I am working on setting up a local instance of Teleport with Active Directory. When I start the Desktop Service, I get " WARN [WINDOWS_D] skipping desktop discovery: LDAP not yet initialized pid:18134.1 desktop/discovery.go:93" I found the article on the troubleshooting page (https://goteleport.com/docs/desktop-access/troubleshooting/) with this exact message and following the steps in the solution, my certificate does show up. I exported it again from the Auth service and reimported it on the DC as the instructions indicate. I am still getting the same warning when I run "journalctl -fu teleport". Are there logs elsewhere that could point me in the right direction? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 25 replies
-
|
I have also verified that I can connect over LDAPS on port 636 from the DC itself and another windows machine. |
Beta Was this translation helpful? Give feedback.
-
|
To make sure I am clear, I ran this on the teleport node that I am trying to setup with the Windows Desktop Server. Not on the main teleport server. |
Beta Was this translation helpful? Give feedback.
-
|
dont know if i'm breaking rules here but you got discord? we can take this convo off github for better troubleshooting if you'd like because i got a full teleport node working with windows desktop ssh DB and kube i'm fairly interested whats different about urs |
Beta Was this translation helpful? Give feedback.
-
|
added! vlan |
Beta Was this translation helpful? Give feedback.
-
|
Update. I was able to resolve the issue when I discovered that the svr-teleport AD account that was created by the install script was disabled. When I went to enable it, I received a warning that the auto-generated password did not meet the complexity requirements. I changed the password, and enabled. AD connection now works as expected. Thanks everyone for your assistance! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the comment. This solved my issue. |
Beta Was this translation helpful? Give feedback.
Update. I was able to resolve the issue when I discovered that the svr-teleport AD account that was created by the install script was disabled. When I went to enable it, I received a warning that the auto-generated password did not meet the complexity requirements. I changed the password, and enabled. AD connection now works as expected. Thanks everyone for your assistance!