FQDN vs NetBIOS Domain Name

Reply
L2 Linker

FQDN vs NetBIOS Domain Name

Hi,

I have a PA-3020 running agentless user-id. When I examine the traffic log, some user id's are displayed as netbios_domainname\userid and others displayed as FQDN\userid.

ie:

domain\billw

vs.

domain.somewhere.com\billw

Any ideas as to why this happens?

Thanks

M

L4 Transporter

Re: FQDN vs NetBIOS Domain Name

I ran into a similar situation with extra long names.  I would check your setting in AD for the accounts in question.  In my case the "user logon name:" did not match the "user logon name (pre-Windows 2000).

Hope that helps,

Bob

L5 Sessionator

Re: FQDN vs NetBIOS Domain Name

Hi,

Make sure that in the ldap profile configuration under Device ----> server profile ---->ldap. Where it says Domain  you have netbios domain name here and not the domain.somewhere.com.

If you do please change that to netbios domain name.

Also if you make the change make sure to clear user cache by using the following command

clear user-cache all

Hopefully this resolves your issue.

Thank you

L2 Linker

Re: FQDN vs NetBIOS Domain Name

Thanks for the replies.

BobW:

The "user logon name:" and the "user logon name (pre-Windows 2000) are identical so I don't think that is the issue.

mbutt:

I don't any LDAP server profiles configured. It is my understanding that these are only needed if user->group mapping is desired or LDAP authentication profiles are being used. Neither of which is the case for me. Am I mistaken in this?

M

L2 Linker

Re: FQDN vs NetBIOS Domain Name

mbutt had the fix for me.

L4 Transporter

Re: FQDN vs NetBIOS Domain Name

When utilizing the agentless User-ID on PAN-OS 5.0 and above a LDAP group mapping profile must be configured in order for the firewall to resolve FQDN domain names to the Netbios equivalent.  When the LDAP server profile and group mapping settings are configured the firewall will query some LDAP attributes in the configuration schema to resolve the Netbios name configured on the domain controller. 

The external, standalone agent behaves similarly but uses a different mechanism on the local machine to resolve the domain's Netbios name.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!