SSH (using putty) and remote desktop work great with wireless laptop on local network but nothing else can SSH into the Pi; previously was able to SSH in from Android phone using JuiceSSH.
Current set up:
Pi (using Rasbian) directly connected to router
laptop (win 7) wireless
phone (Jelly bean 4.1.1) wireless
[email protected] ~ $ ifconfig
eth0 Link encap:Ethernet HWaddr b5:27:eb:8d:3e:fb
inet addr:192.168.1.73 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:656 errors:0 dropped:0 overruns:0 frame:0
TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:47028 (45.9 KiB) TX bytes:16539 (16.1 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
I had previously set static IP on Pi but decided to try dhcp to see if that might be the culprit that is preventing SSH access via Android phone but this did not solve it. Set static IP through router instead and left Pi using dhcp, could this affect anything?
etc/networks/interfaces set up below:
iface lo inet loopback
iface eth0 inet dhcp
#iface eth0 inet static
iface wlan0 inet manual
iface default inet dhcp
Used installed tightvncserver but decided to kill it and install xrdp and use Windows remote desktop app from accessories. I did give Xauthority back to Pi after logging on to Pi directly with keyboard/mouse and TV and noticing the Pi didn't have access/authority for Xauthority; also could not access internet or package updates locally on Pi until after giving Xauthority back to Pi and rebooting.
I'm sorry if some of my descriptions are not technically accurate. I've just stated using the Pi since yesterday and besides installing Ubuntu on an old computer that refused to run windows anymore a few years ago I'm a noob with Linux too.
I just killed xrdp and rebooted (which I didn't think would matter) but the problem persists. I can only remotely access the Pi through my wireless laptop.