That's exactly what hit me: I was trying to federate node to deployment manager when I got this error:
ADMU0036E: The Deployment Manager cannot lookup by name host .. at address 127.0.0.2
I checked local config: no 127.0.0.2 address was there.
I found this thread on developerWorks, and it helped me - I just needed to turn of loopback interface with:
/etc/init.d/network stop lo
After that addNode went smoothly.
Software version: WAS 18.104.22.168, SLES 11.1
24 November 2011
09 November 2011
Ever been stuck in tech problem? Google is no use in your case? Get ready for the new Experts Exchange! Thousands of experts just waiting for your call!
07 November 2011
What I was trying to do this morning was to get my LDAP proxy going. By LDAP proxy I mean simple port 389 forwarding from one machine to the 389 port on actual LDAP server.
After intial attmpt to set up iptables to do what I wanted, I started to look through internet, as this posed to be non-trivial task, at least for me.
Eventually, after putting together instructions found on numerous web pages and forums I put together my Golden Instruction!!! TaDAM!
It looks like that:
echo "1" > /proc/sys/net/ipv4/ip_forward
iptables -A INPUT -p tcp --dport 389 -j ACCEPT
iptables -t nat -A POSTROUTING -d ldap_ip_number -j MASQUERADE
iptables -t nat -A PREROUTING -i bond0 -d box_ip_number -p tcp --dport 389 -j DNAT --to ldap_ip_number:389
It does the following:
you connect on port 389 of the "box" machine and you can use LDAP running on "ldap" machine.
Simple as it is, but finally I got my satisfaction.
Hope this helps! Good luck.