Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

ssh or sshd or what?

Hi. I ain't too computa smart so please take it easy on me.


My problem is with a home network - the following takes place behind a Nat router.


I have a MacBook pro upstairs with the ssh remote login system pref on. I can successfully log in from my iPad if it has not been too long since a reboot. Over time (I don't know how long or any commands to elicit such info, but its in the realm of an hour or two) the server seems to be stopping. I don't think it's the iPad since I have no such prob with another Linux server on the network. I assume it's stopping because I can't login. (The connection fails thru an app called goodreader, but also with a remote desktop app and another remote-y type app which sends nzb jobs to the MacBook.)


If I go to the MacBook and ssh the other server then the MacBook's server is back up and running.


This is not something I wish to do. Can anybody help?


MacBook pro is late 2008 unibody with latest SL.


Cheers in advance

Mac OS X (10.6.7)

Posted on Jun 9, 2011 8:47 AM

Reply
37 replies

Aug 14, 2011 6:45 PM in response to BobHarris

Sorry, I didnt address your questions there. I believe that I have the AEX setup manually to join the existing WIFI network. The channel is set right for the modem/router.


What I dont understand is why (what appears to be) AEX's default self-assigning IP is showing up in my routing table. Is this to fallback on in case of a reset?

Aug 14, 2011 6:51 PM in response to Wagringo

Since Internet Sharing is "Off" (Bridge Mode), my theoies are worthless.


As to DNS, since it is not acting as a router, it should not be serving up DNS addresses. So Yes, leave them empty.


Is the Airport Express connected to the real router via WiFi, or ethernet? If WiFi, then no worries about what channel it is using. If connecting via ethernet, then I would at least check what channel it is using to make sure it is not the same channel as your router/WiFi base station.


With respect to 169.254.159.117, that indicates that the MacBook Pro could not find (or did not play nice with) a DHCP server to get an IP address.


As an experiment, you could add a new MacBook Pro network location and give it a fixed IP address. Something like 192.168.1.200. MacBook Pro -> System Preferences -> Networking -> Location -> Edit Locations ... -> [+] -> Give it a meaningful name -> Done. Now select your new network location, Configure IPv4 -> Manually -> IP address 192.168.1.200, subnet mask 255.255.255.0, Router 192.168???? whatever your router IP address is, which I'm guessing is 192.168.1.254, but I am unsure. DNS server same as your router, search domains, leave blank.


Give it a try. If you still drop out, you can always delete this network location. And anytime you need to leave the house with your MacBook Pro, you swtich your network location back to "Automatic", whcih can easily be done using the Apple Menu -> Locations -> Automatic entry.


Again, this is an experiment based on the MacBook Pro receiving a self assigned IP address because it could not find, or play nice with the DHCP server.

Aug 14, 2011 7:14 PM in response to BobHarris

Firstly, thanks a lot for your time here!

In response: the Express is connected via WiFi to the modem/router.


With regard to MBP not getting along with a DHCP server:

169.254.159.117 f0:b4:79:5:8f:ab UHLW 0 0 en1 1131

Should I be suspicious that this is happening with the airport express MAC address?


And just to re-cap briefly: What is annoying here is that everything DOES work! But only for a few hours, and then I lose WiFi connectivity only between the various Apple devices. Restarting the AEX seems reinstate all connectivity


Cheers

Aug 17, 2011 4:48 AM in response to Wagringo

What follows are things to look at.


Historically, there have been situations where 3rd party WiFi routers and Apple have not always played nice together. Subnets with 192.168.n.n IP addresses are typically used by 3rd party routers, which is why I'm suggesting this.


Another symptom of not playing nice is a Mac not being able to obtain an IP address from the router's DHCP server as indicated by the 169.254.159.117 self assigned address on your MacBook Pro.


You might check that your router has the latest firmware update from the manufacture.


You should also check that the Airport Express and your router's WiFi are not using the same channels. In an ideal world they should be 5 channels apart, but at least not the same.


And it would be a good idea to run a WiFi sniffing utility to see if any of your neighbors are using the same channels you are using (assuming you have neighbors that are really close to you).


WiFi Scanner

<http://www.macupdate.com/info.php/id/33185/wifi-scanner>


AP Grapher

<http://www.macupdate.com/info.php/id/11859/ap-grapher>


iStumbler

<http://www.macupdate.com/info.php/id/11753/istumbler>


KisMAC

<http://www.macupdate.com/info.php/id/10133/kismac>


AirRadar

<http://www.macupdate.com/info.php/id/27740/airradar>


AirMoose

<http://www.macupdate.com/info.php/id/25661/airmoose>


And while I'm going down the WiFi interference path, 2.4GHz cordless phones, 2.4GHz Baby Monitors, Microwave ovens can interfere with 802.11g WiFi. These do not need to be your devices, they could be a neighbor.

Aug 17, 2011 5:42 PM in response to BobHarris

Thanks very much BobHarris for your help.


I think I must have a fundamental lack of understanding in terms of what is going on then...

So Macbook Pro to Airport Express should or should not be communicating through router? I have always assumed the former (ie join existing wireless network). If I assume correctly and we are in agreement then the Airport Express should still be on a different channel to the router? Because that I can fix!


Again, thanks muchly.

Aug 17, 2011 6:12 PM in response to BobHarris

yeah, its wifi. phew...I thought I had absolutely no idea there for a second.


No worries - I have indeed checked local 2.4GHz usage and I have us as far from other users as possible. I guess it must be the router/apple combo. Perhaps I will give away the airtunes idea since everything else works beautifully together.


Thanks for your time

ssh or sshd or what?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.