Ubuntu

wrong ip address being used in ping

Asked by cygnus

When I try to ping/ssh/sftp another machine from my laptop it uses some other ip to identify itself to the other machine. As expected some problem occurs and it shows the denstination host unreachable in the case of ping and does not accept the correct password in the case of ssh/sftp. The ip it uses to identify itself is that of the static connection of my desktop. However, when I do ifconfig or graphically see my ip it seems to be okay.
As a consequence I cannot login into any of the networked machines from my laptop. Please help. I use Intrepid Ibex.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
cygnus
Solved:
Last query:
Last reply:
Revision history for this message
cygnus (cygnus2) said : 		#1

I forgot to mention something in my last post: the reason the ip address of the static connection of my desktop is there in my laptop at all is because at some point of time I had connected it to the LAN using the static connection of my Desktop.

Revision history for this message
Matthew Lye (matthew.lye) said : 		#2

ok, for the ip addresses, are they on the same subnet? Im assuming they will all look something like 192.128.y.x. Is the other machine connected via a bridge or to a switch or router? Are they all using linux?

Its possible that somewhere something is getting confused.

So far we assume the path goes your pc -> switch -> other pc. If this is the case your have something funny happening. If not, we need to know where the difference is.

Revision history for this message
cygnus (cygnus2) said : 		#3

My laptop id when I log in to a WiFi is 192.168.x.y.
My desktop has the ip 158.144.w.z (static ip)
Does that help?

Revision history for this message
cygnus (cygnus2) said : 		#4

Sorry, I forgot to mention: I use Ubuntu Linux 8.10 (I already mentioned this at the end of my first post on this topic!)

Revision history for this message
cygnus (cygnus2) said : 		#5

Hi, thanks for all your efforts. The system administrator of my network solved the problem. The porblem was that the eth0 was configured to be that of the static ip address and thus being the default gateway it was trying it through the static ip address. But of course, not being on that ip, it could not connect. We had to set the eth0 to be on the auto-configure and then it works fine now.