AIX

Sorry, you are right. Somehow i overlooked that, my bad. Still i think that it causes problems even with NAT because duplicate addresses are duplicate addresses. NAT works only the way it does, because there is a distinction between outside (only public addresses) and inside (only private addresses). If you have the same address inside and outside i am not sure if this will work at all, at least not for systems with access to the outside.

I hope this helps.

bakunin

Yes, BUT the address we are using are not currently allocated in the outer world.

The query is about your system not resolving proper fqdn and hence you are facing issue in rlogin. For tis you have to enter you local hosts in /etc/hosts file and you can mention your dns server in resolve.conf. In any os first it check the hosts file and then it will go to the dns servers.
Hope this resolves your query.

Regards,

vjm

Sorry, but this is outright wrong.

In fact this is what the file /etc/resolv.conf is for: to determine the precedence the various means of name resolution (DNS, host files, NIS, etc.) take. This behavior is in fact common for every OS (with the possible exception of Windows, of which i don't know) because it is the compulsory modus operandi of the gethostbyname() system function mandated by several RFCs (1034, 1035, 2065, 2308 just to name a few).

@herot:

I'm sorry not to be of any more help, but i think without some in-depth debugging you won't find the culprit here. It might be a good idea to install tcpdump (if you haven't already) and start analysing the (attempted) traffic the respective machines are encountering.

I hope this helps.

bakunin