named causes system to reject telnet of ftp

named causes system to reject telnet of ftp

Post by Scott Shu » Thu, 27 Jul 1995 04:00:00



if i run named, anyone with an entry in named.hosts (like me) get rejected if i
try to telnet or ftp to the server.

if i kill the named process, everything works fine.

yes, i already checked hosts.deny.

-shupe
Scott Shupe

"you can do anything, with enough ram"  -Frank Zappa

 
 
 

1. named causes all to be rejected

if i run named, anyone with an entry in named.hosts (like me) get rejected if i
try to telnet or ftp to the server.

if i kill the named process, everything works fine.

yes, i already checked hosts.deny.

-shupe
Scott Shupe

"you can do anything, with enough ram"  -Frank Zappa

2. PacerShare on x86 2.4

3. Telnet & FTP - host name/name mismatch

4. Can't get routing over ppp as needed, can someone help?

5. ftp and telnet connections rejected

6. Squid question

7. ftp/telnet open processes lagging ftp/telnet startup

8. How do I execute control structure statements in Mac OS X?

9. Telnet/Ftp and mail don't use name server

10. named, but no ftp or telnet

11. named locks out telnet/ftp/etc.!

12. no www, no ftp, no telnet but ping and name resolution working after router installation