FYI I solved it, and the solution was the same as that of the fellow in the
"ssh weirdness" thread. The problem was an ISP DNS issue. Namely, a
reverse lookup on my IP yielded a plausible name, but a forward lookup on
that name got nothing. This was causing the hosts.deny file to stop telnet
On Tue, Jul 10, 2001 at 10:47:41PM -0700, Owen G. Emry wrote:
> Yes, it's just got the default .deny and .allow files. Can't see anything
> wrong there. And all other services besides ssh and telnet seem to work
> fine. Very frustrating! Thanks for the suggestion, though.
What does "netstat
Yes, it's just got the default .deny and .allow files. Can't see anything
wrong there. And all other services besides ssh and telnet seem to work
fine. Very frustrating! Thanks for the suggestion, though.
-Owen
At 03:34 2001-07-11 -0300, Linuxero wrote:
> Some more information:
>
> Sinc
> Some more information:
>
> Since apache works perfectly, I stopped it and tried moving telnet to port
> 80. Still no connection. ssh didn't work over port 80, either, so I know
> it's not a firewall problem.
>
> After scouring the net, I read that sometimes having ipv6 enabled in the
> kernel w
Some more information:
Since apache works perfectly, I stopped it and tried moving telnet to port
80. Still no connection. ssh didn't work over port 80, either, so I know
it's not a firewall problem.
After scouring the net, I read that sometimes having ipv6 enabled in the
kernel will confu
5 matches
Mail list logo
