Q:

SSH networking issues on raspbian

I am trying to connect to my headless RaspberryPi using SSH via putty but have some networking problems, although it used to work sometimes.
The Pi is running Raspbian and is connected to my router with an ethernet cable. In '/boot/cmdline.txt' I have added ip=[RandomIP] so it now looks like this:
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ip=192.168.2.41

But when I ping that IP with a laptop (connected with W-Lan, so it should be the same network) to check it, it doesn't respond and with putty I of course get a timeout error.
Here is the output of "ipconfig", I'm sorry it's not english, perhaps some of you can read it though:
    Windows-IP-Konfiguration

Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:

   Verbindungsspezifisches DNS-Suffix: 
   Verbindungslokale IPv6-Adresse  . : fe80::2448:1306:b3f6:3dd%12
   IPv4-Adresse  . . . . . . . . . . : 192.168.2.117
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.2.1

Tunneladapter Teredo Tunneling Pseudo-Interface:

   Verbindungsspezifisches DNS-Suffix: 
   IPv6-Adresse. . . . . . . . . . . : 2001:0:9d38:6abd:2081:ab3:3f57:fd8a
   Verbindungslokale IPv6-Adresse  . : fe80::2081:ab3:3f57:fd8a%13
   Standardgateway . . . . . . . . . : ::

Tunneladapter 6TO4 Adapter:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix: 

Tunneladapter isatap.{F887DD4E-BA4E-468A-A603-1DA21AD0DC84}:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix: 

Unfortunately my Router has no DHCP so I can't check if the IP really is the one I've set, but I actually think so.
I have already set up Raspbian again several times, but didn't get any further. Also I tried connecting it directly to my laptop - Again, first it worked, but after reinstalling Raspbian (for other reasons) I had the same problem.
So I can't figure out what to do now. My Goal is of course to connect to it with a SSH client, which is currently not working (it doesn't even respond on ping).

A:

OK, it works now. I've installed a nice tool named "Fing" on my android phone and immediately found out the pi's ip, which was not the one I've set, so I edited the cmdline.txt with SSH and found out that the ip was set in the second line, so I changed it and rebooted and it works just fine!
There is also a good RPi-Doc article about this problem. It describes how to use nmap to scan your local network and find the Pi's ip. 

