Jump to content
Welcome to our new Citrix community!
  • 0

NetBiosName not found | Unable to retrieve trusted domain


Michael

Question

Hi XenGuru's,

 

as i work more and more with XenMobile 10 i have more and more questions :-)

 

I see the following lines in our LogFiles, i googled and looked here in the forum - but without result. 

Someone an idea where to look? Everything is working fine, so far. I think it is only a beauty mistake?

 

2019-04-09T10:23:13.435+0200 | d4653a21822bd7bf  |  WARN | http-nio-10080-exec-2223 | com.citrix.cg.identity.ldap.LdapManager | NetBiosName not found for managed domain:dc=XXX,dc=XXX,dc=XXX, continuing...
2019-04-09T10:23:13.453+0200 | d4653a21822bd7bf  |  WARN | http-nio-10080-exec-2223 | com.citrix.cg.identity.ldap.LdapManager | Unable to retrieve trusted domain. Reason: %s
2019-04-09T10:23:13.468+0200 | d4653a21822bd7bf  |  WARN | http-nio-10080-exec-2223 | com.citrix.cg.identity.ldap.LdapManager | NetBiosName not found for managed domain:dc=XXX,dc=XXX, continuing...
2019-04-09T10:23:13.482+0200 | d4653a21822bd7bf  |  WARN | http-nio-10080-exec-2223 | com.citrix.cg.identity.ldap.LdapManager | Unable to retrieve trusted domain. Reason: %s

 

best regards from germany,

Michael

Link to comment

2 answers to this question

Recommended Posts

  • 1

Hi Michael,

 

Because everything appears to be working fine, I think these warnings are safe to ignore. There is more that you can do to satisfy yourself that these are truly only cosmetic ('beauty') warnings and nothing more serious. Here are some tips to help guide you when looking more closely in to this...

 

- Search the log file for 'http-nio-10080-exec-2223' at around this time. This is the active thread which is logging these messages. If you search the log for this thread, you will see 'everything' that this thread has been doing. Hopefully, you will find that this thread eventually started logging some 'INFO' level messages about some successful events.

 

- Search the log file for 'com.citrix.cg.identity.ldap.LdapManager'. This is the active module in the software which is logging these 'WARN' level messages. The same reasoning, or way of thinking, is used here as above. You should hopefully find this module reports some successful events later on.

 

- LDAP is used in a few key places in the server. For example, open 'Delivery Groups' on the server and attempt to search Active Directory for some user groups. You should see that the server has no problem with finding groups from AD. This can help to prove that the LDAP connection truly is working fine.

 

- Same thing with enrolments.....if enrolments work fine (and the users are LDAP users in AD), then of course LDAP is proven to work if enrolments work.

 

Best regards,

David

  • Like 1
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...