Help [SOLVED] Connected to wifi but cant see to local devices connected to router via ethernet

[bigwoof]

I have been having trouble with this for the last week.

Basically I can connect to my home wifi network and access the internet fine.

My problem is that my nexus 4 no longer is able to see any devices on my network that are connected to the network by Ethernet (raspery pi and home server). I am able to see other wifi devices and ping them (using fing), but I am unable to see any devices that are wired to my router.

I have tried to reboot my router, and chacked that it does not isolate my phone from the rest of the network.
I have tested other android devices and they can see the wired devices.
I have done a factory reset and reflashed my rom (slimkat 6.6).

I am really confused here - I was expecting the factory reset to solve the problem as form my deductions it seems to be the phone, but I am perplexed.

It is as if there is some sort of firewall in the phone preventing me from accessing wired devices on the local network.

Any thoughts?

 

[bigwoof]

It seems that the issue was with my wifi router/modem.
I needed to turn of wifi N then reboot.
annoying but at lease i can share files across the network again.

 

[John Bean]

Thanks for letting us know. I was going to chip in and say it was most likely the router but you seemed to have eliminated that possibility in your OP - but apparently not

 

[bigwoof]

Thanks for letting us know. I was going to chip in and say it was most likely the router but you seemed to have eliminated that possibility in your OP - but apparently not

Yes - it is strange how one setting on the router can change a whole lot of things. After doing some more goggling I saw some mentions of turning of wireless N helping.

 

[John Bean]

Budget wi-fi routers can be a nightmare to debug routing between wired and wireless devices, which isn't all as straightforward as it is on upmarket routers that have a more fine-grained configuration.

As an example my router often renders my wired DLNA server undiscoverable to my wi-fi music player as a DLNA device even though the same server can be browsed as a CIFS share from the same player. If I connect the player by wire DLNA works every time.

Although my example is not directly related to your problem they are both instances of partial failures of routing inside the router itself and are surprisingly common. I doubt that switching off wireless-N was the real fix, rather that it changed something else as a side effect and that change resolved the internal routing problem. I say this because my N4 works fine with my router without needing to disable any wi-fi protocols, so it's not a N4 issue as such.

 

[bigwoof]

Budget wi-fi routers can be a nightmare to debug routing between wired and wireless devices, which isn't all as straightforward as it is on upmarket routers that have a more fine-grained configuration.

I agree with you 100% - I bought the Linksys/Cisco X3000 thinking that if it says Cisco on it it must be good. sadly the firmware is dramatically lacking and it has never seen any firmware upgrade from the manufacturer. Also because it has an ADSL modem in it there is no chance that it will ever get DD-WRT or anything similar as they generally don't support the modem part of the router.

I guess you live and learn - well at least I can get it to work properly again - I will try turning wireless-N back on to see what happens. Perhaps the gremlin has vacated the router.