That helped. In summary, as pointed by Lothar, for proper operation of rexecd the hostname of the connecting host should be known to the server through any means like DNS lookup, /etc/hosts etc. On 8/15/06, Lothar Braun <mail@xxxxxxxxxx> wrote:
On Tuesday 15 August 2006 14:27, jassduec@xxxxxxxxx wrote: > I checked the output using netstat and it does match to 0.0.0.0:* > > Infact when i do telnet 192.168.1.2 512, i do get a reply but the > reply is "Where are you?" followed by connection lost. Ok. The problem is, that your rexecd doesn't know the hostname that belongs to your private address. And rexecd needs a hostname to operate properly. Add an dns-entry into the servers /etc/hosts for your private address, and everything should work fine. Best regards, Lothar
- To unsubscribe from this list: send the line "unsubscribe linux-config" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
