"Eduardo M KALINOWSKI" <[EMAIL PROTECTED]> writes:
> However, I see 192.168.0.3 (zero) in /etc/hosts_allow, and 169.168.1.3
> (one) in the hosts file. If this is not a typo, could as well be the
> cause.
Yes! That was it. It was a typo, and correcting it lets me now use the
laptop to get into my
On Wed, Apr 2, 2008 at 1:57 PM, Haines Brown <[EMAIL PROTECTED]> wrote:
> Eduardo M KALINOWSKI <[EMAIL PROTECTED]> writes:
>
>
> > Haines Brown wrote:
> >> debug1: Server will not fork when running in debugging mode.
> >> debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7
> >> debug1
Eduardo M KALINOWSKI <[EMAIL PROTECTED]> writes:
> Haines Brown wrote:
>> debug1: Server will not fork when running in debugging mode.
>> debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7
>> debug1: inetd sockets after dupping: 3, 3
>> debug1: Connection refused by tcp wrappe
>
> The
Haines Brown wrote:
> Eduardo, I did this:
>
> $ sudo /usr/sbin/sshd -d -p
> ...
> Server listening on :: port .
> debug1: Bind to port on 0.0.0.0.
>
> Then in an other terminal I did this:
>
> $ sudo /usr/bin/ssh -p localhost
> ssh_exchange_identification: Connecti
Eduardo M KALINOWSKI <[EMAIL PROTECTED]> writes:
> With that sshd running in debug mode in port (or any other), try
> also connecting to locahost on port (ssh -p localhost) to see
> if any helpful messages come out.
Eduardo, I did this:
$ sudo /usr/sbin/sshd -d -p
...
S
Haines Brown wrote:
> Well, this might be useful. When you say that I should try ssh
> localhost, this is what I understand you to mean:
>
> $ ssh localhost
> ssh_exchange_identification: Connection closed by remote host
>
This rules out problems with the network, at least.
> If I understo
Eduardo M KALINOWSKI <[EMAIL PROTECTED]> writes:
> So we can assume the machines are communicating, it's just ssh that
> does not work. (It'd be interesting to try some other service,
> though.)
>
> See if there is any kind of firewall or access control, check the sshd
> configuration (try ssh'ing
Haines Brown wrote:
Yes, my desktop connects to the wireless router by CAT5, while the
laptop connects to the router by wifi. So I should simply be able to do
$ ssh teufel and be taken to the user's home directory on teufel, and
when prompted for PW, supply teufel user's PW. Right?
Right.
Ca
On Tue, Apr 01, 2008 at 03:39:11PM -0400, Haines Brown wrote:
> I have a laptop (sidux on Thinkpad X61s) that connects via wi-fi to
> the wireless router connected to my desktop machine (etch) via CAT5,
> which has the name "teufel".
>
> I can connect to the router, which I name "router", by:
>
>
Jeff D <[EMAIL PROTECTED]> writes:
> You might need to access the router from your desktop at first.
I'm not sure I follow you. Are you suggesting that I connect my laptop
via CAT4 to the router rather than rely on wifi? In any case, I'll try
it.
> I seem to remember a lot of routers only allow
"Eduardo M KALINOWSKI" <[EMAIL PROTECTED]> writes:
> On Tue, Apr 1, 2008 at 4:39 PM, Haines Brown <[EMAIL PROTECTED]> wrote:
>> I have a laptop (sidux on Thinkpad X61s) that connects via wi-fi to
>> the wireless router connected to my desktop machine (etch) via CAT5,
>> which has the name "teufe
On Tue, 1 Apr 2008, Haines Brown wrote:
> I have a laptop (sidux on Thinkpad X61s) that connects via wi-fi to
> the wireless router connected to my desktop machine (etch) via CAT5,
> which has the name "teufel".
>
> I can connect to the router, which I name "router", by:
>
> $ ssh router
>
> but
On Tue, Apr 1, 2008 at 4:39 PM, Haines Brown <[EMAIL PROTECTED]> wrote:
> I have a laptop (sidux on Thinkpad X61s) that connects via wi-fi to
> the wireless router connected to my desktop machine (etch) via CAT5,
> which has the name "teufel".
>
> I can connect to the router, which I name "route
13 matches
Mail list logo
