On 05/12/2009 04:50:57 PM, Shashank wrote:
> See your issue?
> No matter who (m?) you try to nslookup, it returns the same IP
> address:
> 63.251.179.5
>
> Can you provide cat /etc/nsswitch output? Please provide this output
> on both system A and B.
>
> Specifically we are looking for the follow
See your issue?
No matter who (m?) you try to nslookup, it returns the same IP address:
63.251.179.5
Can you provide cat /etc/nsswitch output? Please provide this output
on both system A and B.
Specifically we are looking for the following entry:
hosts: files dns (Your file may have it in
Geoffrey Leach wrote:
> r...@mtranch[25]->cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 localhost.localdomain localhost mtranch.mtranch.com
> mtranch
> ::1 localhost6.localdomain6 localhost6
> 19
Additional info: see below.
On 05/12/2009 03:50:27 PM, Geoffrey Leach wrote:
On 05/12/2009 03:08:26 PM, Shashank wrote:
> So let me see if I understand it correctly. Let's also drop the
> domain name
>
>
> System A :
>
> mtranch eth0 - 192.168.10.2
> mtranchw wlan0 - 192.168.10.4
>
On 05/12/2009 03:08:26 PM, Shashank wrote:
> So let me see if I understand it correctly. Let's also drop the
> domain
> name
>
>
> System A :
>
> mtranch eth0 - 192.168.10.2
> mtranchw wlan0 - 192.168.10.4
>
> System B:
> pvreth0 ??
> wlan0192.168.10.3
So let me see if I understand it correctly. Let's also drop the domain name
System A :
mtranch eth0 - 192.168.10.2
mtranchw wlan0 - 192.168.10.4
System B:
pvreth0 ??
wlan0192.168.10.3
So far so good...
Now you are connected to system A:
You type ssh
On 05/12/2009 01:20:03 PM, Shashank wrote:
> Can you provide the output of following commands on both A and B?
>
> netstat -nr
> traceroute host (A when logged in to B and viceversa)
> arp -a ( on both A and B)
> ifconfig (on A) eliminate the public IP/GATEway before you post it
> here.
>
>
> Y
Can you provide the output of following commands on both A and B?
netstat -nr
traceroute host (A when logged in to B and viceversa)
arp -a ( on both A and B)
ifconfig (on A) eliminate the public IP/GATEway before you post it here.
You may not have the correct path to the network (private) .
-S
On 05/12/2009 11:12:42 AM, Christopher K. Johnson wrote:
> Geoffrey Leach wrote:
> > Two systems A and B, connected via wireless. A and B both have the
> same
> > /etc/hosts. Connecting from B to A, "ssh A", works fine. However on
> A,
> > "ssh B" logs me into A. This used to work fine; the only
Tom Horsley wrote:
On Tue, 12 May 2009 14:12:42 -0400
Christopher K. Johnson wrote:
The stored key issue was symptomatic of the problem resolving host to ip
address incorrectly.
There is a command who's name I forget for printing the arp tables,
so you can find out what mac address th
On Tue, 12 May 2009 14:12:42 -0400
Christopher K. Johnson wrote:
> The stored key issue was symptomatic of the problem resolving host to ip
> address incorrectly.
There is a command who's name I forget for printing the arp tables,
so you can find out what mac address the system thinks is hooked
Geoffrey Leach wrote:
Two systems A and B, connected via wireless. A and B both have the same
/etc/hosts. Connecting from B to A, "ssh A", works fine. However on A,
"ssh B" logs me into A. This used to work fine; the only clue I have is
that ssh did not like the stored RSA key. I let it fix it,
Two systems A and B, connected via wireless. A and B both have the same
/etc/hosts. Connecting from B to A, "ssh A", works fine. However on A,
"ssh B" logs me into A. This used to work fine; the only clue I have is
that ssh did not like the stored RSA key. I let it fix it, and that's
when the t
13 matches
Mail list logo