Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Second router as access point - WIFI problem

Jul 27, 2013 9:29AM PDT

Last year I successfully added a second wifi router to my home network, with it setup to be an access point. The apartment I live in used to be a chocolate factor so the walls are very solid and the wifi signal from the lounge where the modem is to the bedrooms is poor.

I have ethernet sockets in each room so I have a direct cable connection between the modem and the router. It all works well save for accessing my airplay enabled printer, for example, or my baby monitor/ip camera, or accessing my mac via my iPhone.

Whilst the SSID is the same on both router and modem, which enables seamless WIFI usage, my iphone/ipad clearly connect to one of the two devices. Since my airplay printer is connected to the access point router, if my iphone is connected to the main modem it doesn't see the airplay printer. Similarly, my mac is connected directly to the access point via ethernet but when I'm using my iphone in the lounge (connected to the main modem again) I can't remote into it.

Is this simply a limitation of using a second router as an access point, or have I missed a step somewhere?

I have a baby due next month and have a wifi ip camera. At the moment this would be a problem for me as the app I have to login to it doesn't show any connected cameras as the camera will be connected to the access point. However, it's when I'm in the lounge that I want to be able to see it.

I have considered a range extender but heard they aren't very good. I have somewhat limited options regarding modem placement (it's a cable modem with only two possible locations in the apartment. Where it is now is more convenient).

Thanks in advance for any help anyone can offer (even if it's to say "tough").

Sean

Discussion is locked

- Collapse -
Answer
Seamless.
Jul 27, 2013 10:46AM PDT

I don't set it up as you noted and have no issues with the LAN. I'm left to wonder if the second router has anything in it's WAN port.
Bob

- Collapse -
WAN
Jul 27, 2013 8:00PM PDT

Nope. WAN port isn't in use on the second router.

- Collapse -
Then a stumper. But I'll share.
Jul 27, 2013 8:02PM PDT

I don't name the SSID the same. Remember that with 802.11n we only have 2 non-overlapping channels. You may want to check the web on that issue and if that's fine, then consider the old fashioned different SSID setup.
Bob

- Collapse -
Answer
DHCP off?
Jul 27, 2013 11:09PM PDT

Please post the make and model of the routers.

Have you turned off DHCP on the second router?

You may want to check that your devices are receiving IP addresses in the same subnet.

- Collapse -
Partial success
Jul 28, 2013 2:18AM PDT

Yes. Dhcp off. Tried updating firmware and aside from AirPlay the baby monitor is working now.

Cheers

- Collapse -
I have the same issue!!
Jun 24, 2015 1:27PM PDT

Hi,

I am digging up this old thread to say that I have basically the same setup you have, and I have a VERY similar issue.

I have a netgear routing running DD-WRT as my main router and another router connected as an AP through one of the LAN ports. I have DHCP turned off on the AP and the channels set to non-interfering channels.

My PLEX server is connected to the main router as well as my "living room" chromecast. My "bedroom" chromecast is connected through the AP and when my laptop or phone is connected to the AP, I cannot see my PLEX server and frequently can't see the living room chromecast. I also cannot remotely connect to the host computer for the PLEX.

When I am downstairs with my phone connected to the router I can see the PLEX server and the living room chromecast, but often can't see the bedroom chromecast.

I was discussing my issue with a co-worker who has a background in computer science and the only suggestion he could offer was that perhaps the AP was not properly communicating UPNP requests to the router because the router saw it as an IP and not an AP. I have not yet tried replacing the AP with an actual dedicated AP because I would need to buy one. That will likely be my next step if this discussion or others do not bear fruit.