Portmapper is usefull (and not essential) only for rpc apps. Ftp and telnet are not rpc programs and do not interact with portmapper.
Check your ip connectivety, can you ping the other site? If no, check the network interface and route tables for both machines, then inspect the cable, io cards, or other harware. If ping succeeds, check the hosts.allow/deny again, and failing that check inetd and telnetd. I get this kind of problem all the time, but always, the mistake is mine. Normally, one card fails and interfaces get assigned in the wrong order to the wrong routes, or interupts and ioports get all mangled-up and chaos follows. First check if ping works while watching it with tcpdump. On Apr 13, Alex Romosan wrote > i just realized that i cannot telnet/ftp into my machine although i > can go out with no problems. i've checked to make sure the portmapper > and inetd are running (they are). at the time i realized this is > happening i was running netbase 2.12-1 but in the mean time i > downgraded to 2.10-1 hoping this will solve the problem. i've checked > hosts.allow hosts.deny (nothing changed there), everything is running > as it should but i can't telnet/ftp into this machine. does anybody > have any ideas? > > --alex-- -- Ioannis Tambouras [EMAIL PROTECTED], West Palm Beach, Florida Signed pgp-key on key server.
