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
I just set up a new machine and for some infernal reason I can't ssh or
telnet to it. Here are the details:
-- both machines have static IPs, proper DNS entries, and are up to date
with latest Debian potato ssh and telnetd
-- new-machine is a fresh vanilla install, running the stock 3.19pre1
Because ssh is only in the non-US distro... Something to do with cryptography
inport/export law. I don't know much about it.
-Aaron Solochek
[EMAIL PROTECTED]
Sam Babak wrote:
> Why use non-US Debian if I'm in the US ?
> thanks guys for your help.
>
> Aaron Solochek wrote:
>
> > Well... I woul
Why use non-US Debian if I'm in the US ?
thanks guys for your help.
Aaron Solochek wrote:
> Well... I would say add the following line to your /etc/apt/sources.list
>
> deb http://non-us.debian.org/debian-non-US stable non-US
>
> Then, run dselect, update, then select search ( use / ) for ssh.
Well... I would say add the following line to your /etc/apt/sources.list
deb http://non-us.debian.org/debian-non-US stable non-US
Then, run dselect, update, then select search ( use / ) for ssh. I think
there are
3 ssh packages. The ones you want are obvious by the description. This is
easi
On Sun, 14 Nov 1999, Sam Babak wrote:
> I was given a job to administer sendmail v8.7 on Debian/Linux and I am
> new to Linux.
wow , great! In everybody's opinion , if you're new to linux , stick to
redhat for awhile...and then try debian ... but looks like you're like me
;-)
> location. When
Hi,
I was given a job to administer sendmail v8.7 on Debian/Linux and I am
new to Linux. I must be able to telnet since the server is at a distant
location. When I telnet to the Linux machine in order to add email
accounts, I get connected and it tells me that I have new mail and it
disconnect.
11 matches
Mail list logo
