I just moved my server and I changed my network structure. I previously had it running perfectly on its own network, but now I have it set up on the main home network.

 

I currently have it connected to a Airport Extreme which is set to extend the current home network. I used the ifconfig eth0 command and it returned an inet addr of 169.254.88.225 for my server. When I tried to connect to this ip on my mac or ipad it cannot connect.

 

I have already tried restarting everything multiple times and have used multiple browsers. I think the problem lies in the way the network is set up, but I am not sure why it wouldnt work the way it is set up.

 

***Note: I did have the server set up as a static ip (10.0.1.4) where it was running on its own subnetwork within the main network. Maybe that is the issue as well?

169... is not a valid IP for a home network. It is probably not getting DHCP. What are the IPs of your other devices? Probably 10.... or 192...

 

Is anything else working OK with that Airport? You say you are using it to extend your network, so the IP addresses should be coming from some other router, perhaps one provided by your ISP. You should be using the same DHCP server as your mac and ipad.

169... is not a valid IP for a home network.

It is valid, but only if there is no DHCP server, and no gateway to the internet. A 169 address is a last ditch effort to allow TCPIP communication to work on an otherwise non working network. If you were to set up a small test network on a hub with one wire to each PC, but no routers, and none of the PCs had a DHCP server running, all the PCs should eventually give up trying to get a valid DHCP lease and revert to a 169 address. Once that happened, the master browser election would take place, and in a few minutes the windows (and samba) shares should start working.

Thanks, that makes sense. I had seen 169... before when things weren't working and noticed it was 169 and not just something completely random. Now I know why.

 

Tapatalk from CM10.1 Kindle