Re: DNS resolve problem with ping but not nslookup

"tng" <> wrote in message news:...
>
> Something with AD configuration?
>
> I got the same problem with my two new virtual redhat and suse. It was
> the directory LDAP client which was the problem. Now both servers are
> running correctly.
>
> If using linux (redhat or suse):
> look at nsswitch.conf & ldap.conf
>
> 1) put "bind_policy soft" in /etc/ldap.conf
> 2) nsswitch.conf must minimum have:
>
> passwd: compat
> group: compat
> hosts: files dns
> networks: files dns
> services: files
> protocols: files
> rpc: files
> ethers: files
> netmasks: files
> netgroup: files
> publickey: files
> bootparams: files
> automount: files nis
> aliases: files
>
> 3) reboot
> 4) check with: ping, nmap localhost.
> 5) now you can enable your ldap client again. (RH: authconfig ; suse:
> yast2 ldap). It will modify your nsswitch.conf
>
> ref:
> https://bugzilla.redhat.com/show_bug.cgi?id=221199
> https://bugzilla.redhat.com/show_bug.cgi?id=186527
> http://www.flyn.org/laptopldap/index.html
>

TNG,

I don't know what you're responding to, becaues we can only see your post in the Microsoft DNS newsgroup because the original or prior posts in this thread have expired in the newsgroups (they're older than 90 days), but based on the subject line, I can say that pings and nslookup problems are not related to AD, rather they are based on the client's network configuration and the client side resolver service.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.