Forum Discussion
lcw1982_107422
Nimbostratus
Aug 14, 2009Problem joining domain behind NAT environment
Hi,
I am using the LTM to do NAT for all my servers, including the Domain Controller. (e.g phy IP is 10.10.10.10; virtual IP is 100.20.20.10). It seems that when the clients (in subnet 100.20.20.x) try to join domain, there is problem with DNS resolution.
Is there a workaround for this? This may not be due to the LTM configuration, but rather on teh client or DC server itself. Appreciate any advice or help.
Thanks
2 Replies
- dennypayne
Employee
I have found that a lot of the Windows AD stuff doesn't survive a NAT. There may be configuration options on the DC to help with this, but I'm not that knowledgeable about AD. - marras_58269
Nimbostratus
Make sure you do a fully qualified domain name for it - what is often happening is that behind a firewall (including F5s) browsing doesn't work. So adding to "DOMAINNAME" fails, but adding to "DOMAINNAME.something" will work because that will use straight DNS to resolve. (Okay, at least in Win2000+, which I'm assuming you are talking about.)
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects