Chromecast Connected but unable to access internet... - Google Chromecast
Hi Guys,
I've got a rather unusual setup for my home-internet where by I have a main router (192.168.1.1) which provides Wi-Fi to one part of the house and a second router turned into an access point (192.168.1.1) by running an ethernet cable from router 1 to router 2.
I've connected my Chromecast successfully to the TV near the 192.168.1.1 router but when I try to use it on the TV near the 192.168.1.2 router if it connects to the 192.168.1.1 router it's extremely laggy as it only has 1 bar of signal.
However, if it connects to the 192.168.1.2 router and then use my phone to try to cast to the TV it works nicely; however the TV has no internet access so it can't stream via YouTube... etc as you can see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've given the Chromecast a static IP in both routers so that it has the IP of 192.168.1.115, it's rather confusing because the Chromecast shows that it has the right IP as you can see: http://i.imgur.com/7L2RxUj.png and other wireless devices work like my phone does when it's got a static IP connected to the second router.
Here are some side by sides of each router's settings.
WAN Connection Settings: http://i.imgur.com/TtfrgLZ.png
WAN Bridge Connection Settings: http://i.imgur.com/5iEijHk.png
LAN DHCP/Static IP Settings: http://i.imgur.com/YF4V7Mw.png
WLAN Settings: http://i.imgur.com/4k4Pveu.png
ADSL Settings: http://i.imgur.com/ZGDLL0W.png
Routing (RIP) Settings: http://i.imgur.com/WuNWmUQ.png
Firewall Settings: http://i.imgur.com/hSIWSL0.png
NAT Settings: http://i.imgur.com/jFGzmcd.png
IGMP Settings: http://i.imgur.com/bFz5jkr.png
UPnP Settings: http://i.imgur.com/nvsxBjA.png
Power Savings: http://i.imgur.com/fjUz9Tj.png
DLNA Settings: http://i.imgur.com/lQE4hgc.png
Connection Mode: http://i.imgur.com/2181vSs.png
Does anyone know what settings should be changed / are incorrect?
Any help would be much much appreciated!
I just messed around some more and it's because the Chromecast auto-detects gateway information.... if it detects gateway as 192.168.1.2 it wont work because of something to do with the router...
If the gateway was 192.168.1.1 but connected to the 192.168.1.2 router it would function correctly..
How do I get round this?
Would I have to do something with the below:
DSL Access types:
http://i.imgur.com/5lLoimL.png
http://i.imgur.com/2WT6wY7.png
http://i.imgur.com/F4lESv6.png
http://i.imgur.com/7qvkFiW.png
Ethernet Access types:
http://i.imgur.com/EsjOskJ.png
http://i.imgur.com/op9nF3Y.png
http://i.imgur.com/43Azjo5.png
UMTS Access types:
http://i.imgur.com/BPQg1Oz.png
Where do you have the ethernet connection from router 1 connected into router 2?
If it's connected into the WAN port, the problem probably is that your WAN and LAN network interfaces both have the same subnet, which just plain won't work. Even if it did, your NAT firewall on router 2 would probably interfere with proper communication between your Chromecast and your phone/browser.
If it's connected to your LAN port (which is how I'd suggest connecting them), you shouldn't have DHCP enabled on router 2.
Good luck!
muchtall said:
Where do you have the ethernet connection from router 1 connected into router 2?
If it's connected into the WAN port, the problem probably is that your WAN and LAN network interfaces both have the same subnet, which just plain won't work. Even if it did, your NAT firewall on router 2 would probably interfere with proper communication between your Chromecast and your phone/browser.
If it's connected to your LAN port (which is how I'd suggest connecting them), you shouldn't have DHCP enabled on router 2.
Good luck!
Click to expand...
Click to collapse
Hi,
I have the ethernet connected to the LAN1 port on router 2, I've tried connecting it into the fiber port but don't know how to set it up to allow networking via the fibre port.
So your suggestion is to disable DHCP?
It's weird because if I'm connected to Router 2 on my phone I can still control my Samsung TV via the SammyGo app and also my Sky+ Box that are both connected to Router 1.
Yes. My guess is that the DHCP server on the second router is serving up leases with the wrong gateway (.2). Leaving DHCP enabled on router 2 would allow all of your LAN devices to communicate with each other, but any device that gets the .2 gateway lease won't see the internet.
You should only have one DHCP server on a network anyway, unless you know what you're doing and have some sort of redundant server config set up. But in that case you wouldn't be here talking to me
Exactly what muchtall said.
Connect the two routers LAN-LAN, but set the secondary AP's gateway to the first router's LAN address and turn off the secondary AP's DHCP server.
That way everything should get DHCP from the primary AP/router and Internet traffic will route correctly.
Have had to do this many times to get around silly ISP router/modem combos and use my own router.
muchtall said:
Yes. My guess is that the DHCP server on the second router is serving up leases with the wrong gateway (.2). Leaving DHCP enabled on router 2 would allow all of your LAN devices to communicate with each other, but any device that gets the .2 gateway lease won't see the internet.
You should only have one DHCP server on a network anyway, unless you know what you're doing and have some sort of redundant server config set up. But in that case you wouldn't be here talking to me
Click to expand...
Click to collapse
I disabled the DHCP on the second router and it did nothing even with devices and routers rebooted, I then tried to set the LAN Host on the second router to .1 even though I was sure it would just cause a conflict and as soon as I did this the entire network became unstable internet was up then down, up then down... over and over.
I had it set like this: http://i.imgur.com/5Zq8fk6.png
bhiga said:
Exactly what muchtall said.
Connect the two routers LAN-LAN, but set the secondary AP's gateway to the first router's LAN address and turn off the secondary AP's DHCP server.
That way everything should get DHCP from the primary AP/router and Internet traffic will route correctly.
Have had to do this many times to get around silly ISP router/modem combos and use my own router.
Click to expand...
Click to collapse
Either I'm understanding something wrong or I'm doing something wrong...
I tried the following: http://i.imgur.com/5Zq8fk6.png but as I said to muchtall, it just made the network incredibly unstable because of an ip conflict I guess?
EDIT #1, To both...
Do I need to do something in static routing: http://i.imgur.com/mBUeYFQ.png
EDIT #2
I think I've got it working... I disabled DHCP, kept it on .2 and changed the WAN settings to the following:
http://i.imgur.com/axPP5tv.png
The LAN cable is connected in LAN1 and I'm using SSID1 (it appears to be working on my phone and chromecast atm)
I might be getting lost with what you are trying, so let's just lay out the ground rules of what you must have configured to make a double wireless "router" network work:
Both routers must be connected together via a LAN port on Router 1 to a LAN port on Router 2
Router 1 should be connected via the WAN port to the internet
Router 1 should have an IP address of 192.168.1.1
Router 1 should have DHCP enabled
Router 2 should have an IP address of 192.168.1.2 (or any other free address, just NOT .1)
Router 2 should have DHCP disabled
Router 2 does not need any routes configured (default or otherwise) since it is on the same broadcast segment as Router 1, and Router 1 handles routing for the network.
If you are still having problems, try a few tests when connected to Router 2 with a computer:
Can you ping 192.168.1.1?
Can you ping 8.8.8.8?
Can you open http://google.com?
(Assuming you are on Windows) Post the output of "ipconfig /all" here (which you can run in a "cmd" window).
Once we know the results of those tests, and the network config of your computer connected to Router 2, we might be able to determine what's wrong.
Edit: Glad to hear you got it working. Looks like your router supports WAN/LAN bridging. That's nice. Not all routers do. It also got me to thinking that one of the problems you can encounter when doing and LAN port to LAN port conection is htat hte ports may not support auto-MDIX (auto-crossover). Basically the RX pairs need to connect to the TX pairs on the RJ45 connectors. If your router's built-in hub didn't support it, you would have had to have made an ethernet crossover cable. Anyhow, hope everything works out in your testing. Good luck!
Maybe I'm wrong here....
But wouldn't it be better to connect the second router using it's WAN port (connected to LAN Port on main router) and then shutting off DHCP and putting the second router into Bridge mode with the same SSID?
Then it should just act as a repeater and would even stop from having interruptions when switching from one router to another?
muchtall said:
I might be getting lost with what you are trying, so let's just lay out the ground rules of what you must have configured to make a double wireless "router" network work:
Both routers must be connected together via a LAN port on Router 1 to a LAN port on Router 2
Router 1 should be connected via the WAN port to the internet
Router 1 should have an IP address of 192.168.1.1
Router 1 should have DHCP enabled
Router 2 should have an IP address of 192.168.1.2 (or any other free address, just NOT .1)
Router 2 should have DHCP disabled
Router 2 does not need any routes configured (default or otherwise) since it is on the same broadcast segment as Router 1, and Router 1 handles routing for the network.
If you are still having problems, try a few tests when connected to Router 2 with a computer:
Can you ping 192.168.1.1?
Can you ping 8.8.8.8?
Can you open http://google.com?
(Assuming you are on Windows) Post the output of "ipconfig /all" here (which you can run in a "cmd" window).
Once we know the results of those tests, and the network config of your computer connected to Router 2, we might be able to determine what's wrong.
Edit: Glad to hear you got it working. Looks like your router supports WAN/LAN bridging. That's nice. Not all routers do. It also got me to thinking that one of the problems you can encounter when doing and LAN port to LAN port conection is htat hte ports may not support auto-MDIX (auto-crossover). Basically the RX pairs need to connect to the TX pairs on the RJ45 connectors. If your router's built-in hub didn't support it, you would have had to have made an ethernet crossover cable. Anyhow, hope everything works out in your testing. Good luck!
Click to expand...
Click to collapse
Both routers must be connected together via a LAN port on Router 1 to a LAN port on Router 2 Check
Router 1 should be connected via the WAN port to the internet Check
Router 1 should have an IP address of 192.168.1.1 Check
Router 1 should have DHCP enabled Check
Router 2 should have an IP address of 192.168.1.2 (or any other free address, just NOT .1) Check
Router 2 should have DHCP disabled Check
Router 2 does not need any routes configured (default or otherwise) since it is on the same broadcast segment as Router 1, and Router 1 handles routing for the network. Check
I tried this on my third router which is a D-Link DSL-3780; not a Huawei HG533 and when I try to connect my phone to this router it sits there trying to allocate an IP address but sits there trying over and over and constantly failing. I've tried to use the "DHCP Relay" option too but it does seem to solve the issue either.
If I then connect the third router to the computer and set the TCP/IPv4 settings like http://i.imgur.com/n77Gz3R.png then it connects fine, however if I make it obtain automatically like the Chromecast would then it fails to connect.
Pinging the Router
Code:
Pinging 192.168.1.1 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Pinging Google DNS
Code:
Pinging 8.8.8.8 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Obviously unable to access google.
Finally ethernet details (I've changed some addresses & ID's so nothing could potentially be done to my PC...)
Code:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller
Physical Address. . . . . . . . . : 00-24-8C-29-A1-00
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::96x0:df12:e3s2:cb39%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.202.137(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : fe80::1%11
DHCPv6 IAID . . . . . . . . . . . : 236180380
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-89-45-44-00-24-9P-48-A1-DB
DNS Servers . . . . . . . . . . . : 8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Asphyx said:
Maybe I'm wrong here....
But wouldn't it be better to connect the second router using it's WAN port (connected to LAN Port on main router) and then shutting off DHCP and putting the second router into Bridge mode with the same SSID?
Then it should just act as a repeater and would even stop from having interruptions when switching from one router to another?
Click to expand...
Click to collapse
That's what I've done for the secondary router, it works now but my third router doesn't have that. Although not as important.
Hyflex said:
Both routers must be connected together via a LAN port on Router 1 to a LAN port on Router 2 Check
Router 1 should be connected via the WAN port to the internet Check
Router 1 should have an IP address of 192.168.1.1 Check
Router 1 should have DHCP enabled Check
Router 2 should have an IP address of 192.168.1.2 (or any other free address, just NOT .1) Check
Router 2 should have DHCP disabled Check
Router 2 does not need any routes configured (default or otherwise) since it is on the same broadcast segment as Router 1, and Router 1 handles routing for the network. Check
Click to expand...
Click to collapse
Make sure the second router's LAN gateway is set to the LAN address of the first router (192.168.1.1) otherwise it won't know where to send packets for its wireless clients and everything will end up in going nowhere.
bhiga said:
Make sure the second router's LAN gateway is set to the LAN address of the first router (192.168.1.1) otherwise it won't know where to send packets for its wireless clients and everything will end up in going nowhere.
Click to expand...
Click to collapse
Hmm, I can't find anywhere to setup a "LAN Gateway", I would of though the DHCP relay would have done the same thing but it doesn't do anything :/
Internet Setup: http://i.imgur.com/KufkUd5.png
Wireless Setup: http://i.imgur.com/Vqj8x2z.png
LAN Setup: http://i.imgur.com/1mm55I5.png
WLAN Performance: http://i.imgur.com/ATGL7dy.png
Virtual Server: http://i.imgur.com/3i6sJBb.png
Applications: http://i.imgur.com/7hkfG2k.png
Filter: http://i.imgur.com/0UXk2F7.png
Advancaed ADSL: http://i.imgur.com/redgNCY.png and http://i.imgur.com/AQHlo1v.png
Firewall: http://i.imgur.com/km0iXeZ.png
DNS: http://i.imgur.com/YfQ90OO.png
IGMP: http://i.imgur.com/PIuDGgR.png
QOS: http://i.imgur.com/7yBo8yE.png
UPnP & DLNA: http://i.imgur.com/bp2XJ5L.png
Samba: http://i.imgur.com/KXNJgLL.png
Static Routing: http://i.imgur.com/HtR73zu.png
RIP: http://i.imgur.com/F2pVJ5v.png
Hyflex said:
Hmm, I can't find anywhere to setup a "LAN Gateway", I would of though the DHCP relay would have done the same thing but it doesn't do anything :/
Click to expand...
Click to collapse
It would if the wireless clients are getting the primary router LAN address as the gateway, as outbound traffic will go there for the router to determine where to send it.
If the wireless clients are getting a different address, then that device needs to know to send the traffic to the primary router.
Wired clients on the secondary router will have the same issue.
But if your secondary router is connected from its WAN port to the primary router's LAN port in Bridge mode as pictured, no gateway needs to be specified because unknown traffic should route "out and up" through the WAN port.
bhiga said:
Make sure the second router's LAN gateway is set to the LAN address of the first router (192.168.1.1) otherwise it won't know where to send packets for its wireless clients and everything will end up in going nowhere.
Click to expand...
Click to collapse
That's not going to be of any use when the routers are connected LAN port to LAN port. DHCP handles that, and since the networks should be on the same broadcast segment, normal ARP discover handles the rest.
@Hyflex: DHCP Relay isn't going to be applicable either (since both routers should be on the same broadcast domain of the network), and in fact could interfere with proper operation. What is the current state of things? Is your Chromecast working, or no? If it's not working, do your applicable LAN ports show a link when the two routers are connected?
---------- Post added at 06:11 PM ---------- Previous post was at 06:04 PM ----------
bhiga said:
But if your secondary router is connected from its WAN port to the primary router's LAN port in Bridge mode as pictured
Click to expand...
Click to collapse
That alone would break the Chromecast functionality. The Chromecast has to be on the same subnet as the phone, unseparated by NAT.
---------- Post added at 06:14 PM ---------- Previous post was at 06:11 PM ----------
Nevermind. Missed the bridge part.
Related
[Q] Network problems
Hello. Since XDA is the only forum I'm loyal to I decided to ask you guys. I've get my broadband directly from ethernet ports integrated in my walls, and all those ports are connected to a switch. The problem is that I've got a wifi router that I'd like to use so I can connect my laptop and my phone to the network, which works fine if I connect it to one of the ports in my walls, but I also have a XBox 360 connected to one of these ports. And since I always stream music and video from my laptop to my XBox this gives me a problem. I've temporarily solved this by setting up the router right beside my XBox and hooking the XBox to the router, and it works fine, but I can't connect to the wifi if I leave my livingroom. Also tried to connect the router inbetween the switch and the cables that goes to the wall ports, but this was totally useless because then I only had acceptable wifi connection in my hallway and my kitchen. So my question is this, is there anyway to have the router connected to one of these ethernet ports, my computer connected to the router and the XBox connected to another ethernet port and get them to be able to communicate? EDIT: Disabled DHCP on the router as I've found in a guide, but that was only possible to do on the LAN part of the router, no such setting on the wireless page, so still the same problem. Sounds a bit compilcated I guess, but I think it should be possible to use this router as some kind of extender for the already existing network. Regards Izaac
Tell me, how large is your living room again? -____- Jk, alright, from my point of view, just place the router at the farthest point between those three gadgets, and buy a wifi extender for the other two. That thing just a couple of bucks anyway. Problem solved. No need for another router.
What is your switch currently connected to for internet access? If you have it hooked to a modem, then it is probably a 1 port router/modem since you don't have problems drawing an ip on your other items. You are on the right track. Turning off DHCP is correct. There is no dhcp on the wireless portion so don't look for it. Then you want to set your wireless router with a static ip on your lan side so you can get into it if you need(use something out of the normal range like xxx.xxx.xxx.200). Make sure the static IP is part of your LAN subnet. Those two things turn your wireless router into a switch/wireless access point. From here on out forget about the WAN or Internet port on the router. Use only the LAN ports. You can now use this wifi router anywhere you want. Place it where you get the best wireless signal. Wire things up this way wherever you place it: Connect wall ethernet port to one of the LAN ports. Then connect any other devices needing internet access to the other LAN ports.(Computer, XBOX, whatever...) Then connect wirelessly with your wireless device. If you need to modify the router settings, you can browse to xxx.xxx.xxx.200 ( or whatever you set the router static lan ip to) from your computer . Any devices that need DHCP will draw the address from further upstream from the modem/router.
I live in a two floor appartment with the router on the second floor, most of the building is made of concrete, my router is on the second floor, and i have excellent reception all over the place. - How long is your cable (from the router to the wall 1 meter? 5? Make it as short as possible) - Are you using 2.4 GHz or 5 GHz? The most common frequency is 2.4, so if your neighbours are using 2.4, it might disrupt your connection from time to time, so try to change the channel. - Move the router if your wireless phone or any wireless things are operating on 2.4 GHz nearby. They will disrupt the signal.
Oy..... I forgot to tell him to get Wi-Fi Analytics from the play store to check his signal and find the best channel to use.
Problem between chromecast and TP Link AP
Hi I have a problem between my chromecast and my TP link wifi repeter (WA-801ND) I have a livebox (Orange France) but in my room the wifi is bad so I have put a AP to extend the wifi range through ethernet. When I try to configure my chromecast on the wifi (with livebox and TP link ON) I have a problem I have this message : After I have seen that I try to fix : I have disable AP Isolation on the TP link (I haven't found the option on the livebox) and I have done the following things : https://productforums.google.com/forum/#!msg/chromecast/HyxnH4poMzU/i5Km4oP5EZMJ exepted IGMP because I havn't found it on my router and my AP. I have try to put my TP Link in Access Point mode and Repeater mode but it dosen't works I have also try multi ssid on my TP Link : 1 to extend livebox wifi and 1 just for the chromecast but it dosn't work at all After that I have try to configure the chromecast with only the livebox ON so I have powered off the TP link and at this time it works the configuration is finished successfully. And all is working (youtube, plex, play music, podcast addict) but because the TP link was off there was wifi signal loss. So I powered back ON the TP link and the chromecast connect to it successfully but when the TP link is on not everything works Working : -Play Music from chrome desktop and android -Podcast Addict (android app) -Allcast (android app) -cast screen from my Nexus 4 -cast tab from desktop -cast tab with sound from desktop -Youtube from chrome desktop Not Working : -Youtube for android -Plex for android -Chromecast offical android app In youtube, plex the cast button does not appear. How can I solve my problem ? Thanks PS : My router settings : SSID : Livebox-b80d broadcast SSID : Yes security mode : WPA2-PSK/AES channel : 6 easy WiFi : activated Wifi : 802.11bgn WPS : activated MAC filtering : deactivated UPnP IGD : activated DHCP : activated TP link settings : Mode : Access Point SSID : Livebox-b80d Channel: 6 Wifi Mode: 11bgn mixed Channel Width: auto (I can choose 20MHz or 40MHz) [checked] Enable Wireless Radio [checked] Enable SSID Broadcast WPA2-PSK Personal (I can choose entrprise) Encryption : AES Group Key Update Period:0 second Wireless MAC Filtering: Disabled DHCP : activated My chromecast run on official build 17250 (edit : updated to 17977 today)
Sorry, could you translate the error message from your screen grab into English? As for your configuration, having two separate access points with the same SSID that aren't in repeater or mesh mode will cause problems, not just for Chromecast. It's supposed to work with your TP link configured as a repeater, but you need to make sure Multicast packets pass through to the repeater. Chromecast uses multicast for discovery. Also, I'm not sure what "Easy WiFi" on your main router does, but I would look to see if that might be screwing up your repeater configuration.
the message in the screenshot say : Unable to find the chromecast on your network, you might solve the problem by changing some settings on your wifi router. I've just search for easy wifi and it's AOSS : http://en.wikipedia.org/wiki/AOSS Also On my main router I have found UPNP (multicast) but I can't find it on the TP link AP Tomorrow I will try to connect the chromecast to my tp link with an other SSID (different from the main router).
Aloso try using the HDMI extender on Chromecast, if you do not already use it. The closer Chromecast is to the television, the poorer its WiFi signal reception will be.
So I have done a test : I have used the HDMI extender and I have given a different SSID to my TP link and my main router after I have seen the same message on the screenshot and at the end it is write "cliquez ici"' I also change the channel : on the tp link I put channel 13 and on the main router I put channel 6 that mean "click here" and the link is : https://support.google.com/chromecast/answer/3438461 Edit : I've done another try I have an other tp link router/AP unused at my home a TP Link WR702N First try I have powered on the main router with ssid livebox-b80d the TP WA801nd with the SSID livebox-b80d // AP Mode the TP link WR702N with the SSID chromecastwifi //AP mode all connected to the same network I connected the chromecast to chromecastwifi AP and it works but to see the chromecast I have to connect my phone to chromecast wifi So I have done another try I powered off the TP Link 801ND and I change the SSID of the TP link WR702N to livebox-b80d And now all is working great I think the WA801ND hasn't got the UPNP fonction that because it didn't works I think the WR702N has the UPNP because it is recommanded for the SmartTV without wifi So now it works with the WR702N So the conclusion is the WA801ND is not compatible with the chromecast Edit 2 : Because I have 2 AP (the main router and the TP link) when I move in my house and the phone switch between the two AP I lost the connection with the chromecast I can control the chromecast only if I am on the same AP (TP link AP) I will try repeter mode insted of AP mode to try to fix that Edit 3 : The repeter mode dosn't works, the two AP are too far from each other I go back to AP Mode
Sounds like you might do better with a repeater that uses powerline connection to the router rather than WiFi, unless you can move the repeater closer.
Yes I will try to bring it closer I will comeback here if I found a solution
Same problem on WA901ND Tib44 said: Yes I will try to bring it closer I will comeback here if I found a solution Click to expand... Click to collapse I've got the same problem on the TL-WA901ND. Using Powerline doesn't help. I've started a discussion on the TP-link support group. (search TL-WA901ND Chromecast IGMP issues) Did you ever come up with a solution?
bhiga said: As for your configuration, having two separate access points with the same SSID that aren't in repeater or mesh mode will cause problems, not just for Chromecast. It's supposed to work with your TP link configured as a repeater, but you need to make sure Multicast packets pass through to the repeater. Chromecast uses multicast for discovery. Click to expand... Click to collapse I have to agree with @bhiga here....They should not have the same SSID unless you are in repeater or WISP mode. AP mode requires a cable to get internet, Repeater just adds another signal boost in the area the repeater is in...WISP as far as I can tell only works on open public networks that require WebAuth and/or certificates to gain access. I'm not sure about your model but I have the 702 and it does work with CCast, So those settings you posted you can't even be sure you are not connecting to the main router cause when both have the same SSID the strongest signal wins.
Mark phone language to English and try .. Sent from my Nexus 5
I have similar problem. I don't see my chromecast from chromecast app. But when I reboot my router and open app for the first time CC appears but on second open CC cannot be found.
TL-WA901ND with Chromecast gabrielhopkins said: I've got the same problem on the TL-WA901ND. Using Powerline doesn't help. I've started a discussion on the TP-link support group. (search TL-WA901ND Chromecast IGMP issues) Did you ever come up with a solution? Click to expand... Click to collapse i do have the same issue. its very frustrating. i waste hours to try all option with my AP TL-WA901ND. finally i enable hidden SSID on my router (compatible but 54mbps max) to connect with chromecast. connect(smart IP) TPlink AP with Router and broadcast SSID. this way i manage to connect devices with chromcast under same network using two different SSID. i believe we need to wait for some time until there is any update for chromecast to connect with our AP . if you have any other solution please let me know. :crying::crying:
For the WA901ND there's a firmware update that solves the issue. Bug Fixed: Fixed the directory traversal security bug. Fixed the bug that the LAN getway does not take effect when TL-WA901ND is in Client mode. Fixed a display error in the WDS scanning result page. Fixed the bug that chromecast cannot work with TL-WA901ND. Click to expand... Click to collapse
You my man, have saved me hours of frustration. Hats off to you
following instruction is shown 1. ensure you are not connected to VPN 2.if you have dual band router than it is not an ap isolation mode 3. if your router has MAC whitelisting ensure that yourwifi network allow this device and your chromecast to join i m using tp link TD-W8968
This is the solution. You need to buy a router, That TP-link AP-Extender does not do UPNP.
[Q] Configure CC on open WiFi network with click-through requirement (SOLVED)
I am frequently presenting on open WiFi networks, but the catch on these networks is they usually require click-through on a webpage. The CC cannot preform the click-through so using CC on these networks fails. I am looking for alternatives to engineer a working solution to allow the CC to work depending only on the open WiFi network with click-through requirements. There are at least two other (less desirable) working methods. First, create my own WiFi hotspot, but this has a significant disadvantage that the audience wants to connect to my WiFi hotspot to experiment with the CC. Second, connect to a secure WiFi network without click-through requirement, but this is frequently not available at my presentation locations. I realize I can use the CC on a secure network with password, as long as it does not require click-through on a web page. The ideal solution/workaround would allow the CC to connect to some AP or other WiFi point that was bridged or sourced by an "open WiFi network that requires click-through" as these types of networks are most frequently available. Plus the audience is usually already connected to the same network. But, I have not thought of a useful method to accomplish it, likely because of my limited network engineering and hardware knowledge. Two other nice-to-have features would be (1) portability and (2) working with both Windows 7 x64 and Mac OS if a laptop is used to accomplish the bridge or AP. Methods might include something simple I'm overlooking, or an CC application, or a hardware solution (like turning my laptop into an AP after connecting to the "open WiFi network that requires click-through", or anything else. Any suggestions highly appreciated. PS: I am not rooted if recommending an Android device or application. ----- SOLVED. The solution was using TP-Link 150Mbps Wireless N Mini Pocket Router TL-WR710N configured in "WISP Client Router Mode". I bought mine on Amazon here for $27.27 USD plus tax. An extra feature is a USB port which can be used to power the CCast. As discussed in the thread, there is WISP mode *wired* LAN, and WISP mode *wireless* LAN. Some devices implement WISP mode by connecting to a public WiFi network and giving you *wired* local LAN. Alone, these do not work with CCast because CCast requires a *wireless* local LAN. WISP mode to *wired* LAN does NOT work. Yet, the TL-WR710N implements WISP mode by connecting to a public WiFi network and giving you a *wireless* local LAN, complete with new Wireless Network Name (SSID) and IP address scheme served by DHCP. This works 100% with CCast. Once the CCast is configured on the local SSID and local IP (default 192.168.0.1xx) you can cast Youtube, etc., or screen cast from your Android device. No wonder there is confusion about WISP mode implementation. Many thanks to people contributing to this thread's discussion!! Note: Cloning the CCast MAC is *not* required because you can connect any device to the TL-WR710N in WISP mode and use the browser to click-through - authorizing the WR710N MAC on your public WiFi. Then all the clients, including CCast, connecting on the local *wireless* LAN simply work.
You need a program that will let you clone the CCast's MAC address on a computer, unplug the CCast... Clone the Mac Address, Do the click through, Disconnect the computer UnClone the Mac Address. Re-Connect the CCast. Connect the computer as normal. But be warned...Most APs who have a click through page for access also have AP Isolation turned on which makes it impossible to find the CCast to stream to it.
Asphyx said: You need a program that will let you clone the CCast's MAC address on a computer, unplug the CCast... Clone the Mac Address, Do the click through, Disconnect the computer UnClone the Mac Address. Re-Connect the CCast. Connect the computer as normal. But be warned...Most APs who have a click through page for access also have AP Isolation turned on which makes it impossible to find the CCast to stream to it. Click to expand... Click to collapse Okay thanks. I will test cloning. But, if you are correct and most networks have AP Isolation preventing CC, then I need an alternative solution. ------ I was intrigued by this post. But configuring an TL-WR703N with "openwrt+luci web interface" is not clear to me. Yet, this seems a possible good solution. Also, browsing this link at Cisco made me think what user @bagl0312 accomplished is quite good.
Bob Smith42 said: Okay thanks. I will test cloning. But, if you are correct and most networks have AP Isolation preventing CC, then I need an alternative solution. ------ I was intrigued by this post. But configuring an TL-WR703N with "openwrt+luci web interface" is not clear to me. Yet, this seems a possible good solution. Also, browsing this link at Cisco made me think what user @bagl0312 accomplished is quite good. Click to expand... Click to collapse I think there are better options for Remote usage such as Portable routers with the ability to connect to other wireless AP devices for it's WAN, Or if you already have a cellular data account for your phone, adding one of those MiFi wireless hotspot devices that you can use as a router pretty much anywhere including where there is no free WiFi. You just have to be careful with the latter option because Data Charges will apply if you use too much Internet access on them.
Asphyx said: I think there are better options for Remote usage such as Portable routers with the ability to connect to other wireless AP devices for it's WAN, Or if you already have a cellular data account for your phone, adding one of those MiFi wireless hotspot devices that you can use as a router pretty much anywhere including where there is no free WiFi. You just have to be careful with the latter option because Data Charges will apply if you use too much Internet access on them. Click to expand... Click to collapse Does anyone have any recommended models for *portable* routers with "wifi as wan" capability?
Bob Smith42 said: Does anyone have any recommended models for *portable* routers with "wifi as wan" capability? Click to expand... Click to collapse You're looking for what's typically known as a "travel router" and the "WiFi as WAN" feature, as least on my Zyxel routers is called "WISP mode" (Wireless ISP). It does exactly what you said, instead of using a wired connection for WAN, it uses a wireless connection - the router still functions as a router, so you might have some issues with double-NAT-ing in some cases. I have both the MWR211 (single Ethernet port so you can do wired LAN or wired WAN but not both simultaneously) and MWR222 (two Ethernet ports, so you can do both wired LAN and WAN simultaneousl) - they're almost identical, save for lacking SNMP on the MWR211. I have not had opportunity to use the WISP mode though I've used the 3G (they support most USB cell modems) as backup from time to time. Info's a little lacking since they're discontinued models, but I got them off a Woot deal while back for under $50. MWR211/222 manual
bhiga said: You're looking for what's typically known as a "travel router" and the "WiFi as WAN" feature, as least on my Zyxel routers is called "WISP mode" (Wireless ISP). It does exactly what you said, instead of using a wired connection for WAN, it uses a wireless connection - the router still functions as a router, so you might have some issues with double-NAT-ing in some cases. I have both the MWR211 (single Ethernet port so you can do wired LAN or wired WAN but not both simultaneously) and MWR222 (two Ethernet ports, so you can do both wired LAN and WAN simultaneousl) - they're almost identical, save for lacking SNMP on the MWR211. I have not had opportunity to use the WISP mode though I've used the 3G (they support most USB cell modems) as backup from time to time. Info's a little lacking since they're discontinued models, but I got them off a Woot deal while back for under $50. MWR211/222 manual Click to expand... Click to collapse This information was helpful. I read the manual. I will have to test the double-NATing with CC, e.g. issues with WAN accessing private vs public network IP as described in the manual. I found an inexpensive MWR222 to evaluate. I suspect its wireless WAN mode will help, but when set in that mode it looks like it may not (guess) simultaneously have hotspot capability. Still, in that case, I can connect a small AP to its Ethernet LAN and probably get the CC working. I will test my hypothesis and report CC results once I receive the device. I also found an inexpensive TL-WR703N with memory updates (RAM, Flash) that is supposed to support OpenWrt. I will flash it with OpenWrt once I get it and report CC results. Hopefully, I can reproduce @bagl0312 configuration with CC with success. I am starting to understand the networking issues and configurations required. Everyone's help is appreciated. Thanks.
Bob Smith42 said: This information was helpful. I read the manual. I will have to test the double-NATing with CC, e.g. issues with WAN accessing private vs public network IP as described in the manual. I found an inexpensive MWR222 to evaluate. I suspect its wireless WAN mode will help, but when set in that mode it looks like it may not (guess) simultaneously have hotspot capability. Click to expand... Click to collapse You wouldn't want hotspot capability if you are using it in WAN mode anyway since you will be using the Wireless internet connection from the location and not the data plan of your Cell Service. Thats why you want the WAN/WISP option in the first place to stop from having to eat into your Data Allotment on your Cell Carrier account.
Asphyx said: You wouldn't want hotspot capability if you are using it in WAN mode anyway since you will be using the Wireless internet connection from the location and not the data plan of your Cell Service. Thats why you want the WAN/WISP option in the first place to stop from having to eat into your Data Allotment on your Cell Carrier account. Click to expand... Click to collapse No. I need both, unless someone figures out another workaround (see below). The CC has two requirements: (1) connect to public IP (internet) for data, and (2) connect to local IP (android devices, chrome on laptops, iphones, etc) for remote control and mirroring. CC configurations issues with WiFi services offering access to public IP (internet) are: (1) Both open or encrypted networks frequently have web page click-through requirements that CC cannot perform, and (2) CC and connecting WiFi devices must connect point-to-point on the local IP network which is frequently blocked (AP isolation, etc). I agree with you because I do not *want* a dual WiFi network solution, but I have found no alternatives so far. lol We can engineer a dual WiFi network solution for sure, but it might be easier to address some of the core usability issues of the CC in some other (more clever) way. Some other workarounds might include combinations from (or may not be possible): (1) Cloning MAC on CC to bypass click-through requirements. (2) Add BT capability on CC. Overcome AP isolation on the local IP network using high bandwidth BT for remote control and screen mirroring. (3) Add browser capability on CC for click-through, and mouse or touch control for CC. (4) Clever method to defeat WiFi local IP network AP isolation between CC and devices. (5) Others? Hopefully someone is already working on better solutions.
Bob Smith42 said: No. I need both, unless someone figures out another workaround (see below). The CC has two requirements: (1) connect to public IP (internet) for data, and (2) connect to local IP (android devices, chrome on laptops, iphones, etc) for remote control and mirroring. CC configurations issues with WiFi services offering access to public IP (internet) are: (1) Both open or encrypted networks frequently have web page click-through requirements that CC cannot perform, and (2) CC and connecting WiFi devices must connect point-to-point on the local IP network which is frequently blocked (AP isolation, etc). I agree with you because I do not *want* a dual WiFi network solution, but I have found no alternatives so far. lol We can engineer a dual WiFi network solution for sure, but it might be easier to address some of the core usability issues of the CC in some other (more clever) way. Some other workarounds might include combinations from (or may not be possible): (1) Cloning MAC on CC to bypass click-through requirements. (2) Add BT capability on CC. Overcome AP isolation on the local IP network using high bandwidth BT for remote control and screen mirroring. (3) Add browser capability on CC for click-through, and mouse or touch control for CC. (4) Clever method to defeat WiFi local IP network AP isolation between CC and devices. (5) Others? Hopefully someone is already working on better solutions. Click to expand... Click to collapse But the Router will do the proper NAT Translation for you for the Internet access... When the CCast asks for something from the internet it asks the portable router then the portable router will use the location WiFi to get it and then send it to the CCast. The CCast doesn't need a public IP it only needs to be connected to a device that can get internet data. what you do have to do however is use a different IP Range on the DHCP server of the portable router... So if the Router gets an IP like 192.168.1.x from the WiFi you have to use a different set like 192.168.2.x for your DHCP server...
@Bob Smith42 's concern is valid, I didn't think about the fact that WLAN as WAN takes out the AP functionality. I just confirmed this. So, really what we end up needing is still two devices - a wireless bridge to get wireless to wired - either a router in WISP mode or something like Cisco/Linksys WET610N (I keep laughing at the "Up to 300 Mbps" as it only has a 100 Mbps Ethernet port), and a router to provide the AP... IMO, the "local WiFi" network really is the best way to go. It may seem redundant at times, but at least you can still do stuff if you have no WiFi, or WiFi is paid per-client (it's changing, but a number of hotels I've been at were like this). As for other mechanisms, maybe the "Don't need to be on the same WiFi" feature that's coming will address this, but I don't think it will. Then again, I didn't think screen casting would happen on older hardware like my Galaxy S3, and it does (via MirrorEnabler), so maybe I'll be pleasantly proved wrong again.
bhiga said: @Bob Smith42 's concern is valid, I didn't think about the fact that WLAN as WAN takes out the AP functionality. I just confirmed this. Click to expand... Click to collapse Well then I stand corrected and have to add thats just bad design...You should be able to to simply connect the Portable to the WiFi and then use it as your Wireless AP for multiple devices otherwise what is the point of this WISP mode at all? Unless it is to turn Wireless into Wired only... Google does have a solution to solve this in the pipeline...That Proximity streaming we talked about where you can stream to it over Cell data without being connected to the home network. But thats just going to ring up data charges I would think.
Asphyx said: what is the point of this WISP mode at all? Unless it is to turn Wireless into Wired only... Click to expand... Click to collapse That's exactly what WISP is for. The MWR2xx series mainly takes a wired/wireless ISP connection and turns it into a wireless/wired connection with USB modem backup. The MWR222 can also do wired-wired with USB failover since it has two Ethernet ports. Given the age of the design I'm not sure the WiFi chip they use can operate as both client and AP simultaneously.
bump Thread updated. TL-WR710N works 100% with CCast on all (tested so far) WiFi networks.
Bob Smith42 said: bump Thread updated. TL-WR710N works 100% with CCast on all (tested so far) WiFi networks. Click to expand... Click to collapse Thats how I understood those Portable routers were supposed to work so you could add things like Portable Wireless printers all the while having internet access from configured Wireless APs...
Ok so I picked up this 710N router on Amazon since I had a gift certificate I needed to use and while the promise of this router seems to be there I'm having real issues getting it to work properly but part of that has to do with it really requires a WIRED Connection to set up properly. It does seem to do what we would need in a Hotel but I have not been able to mimic that on this unit using my own router and I'm suspecting that maybe my Router is not supporting it or I'm just reading the settings wrong. I'll keep trying here and see what it requires...I Might need to set up the guest network cause the issue might be the click through is not there or my regular router is set to NOT allow another AP to connect...Just got it today so I will continue to play with it.
Asphyx said: Ok so I picked up this 710N router on Amazon since I had a gift certificate I needed to use and while the promise of this router seems to be there I'm having real issues getting it to work properly but part of that has to do with it really requires a WIRED Connection to set up properly. It does seem to do what we would need in a Hotel but I have not been able to mimic that on this unit using my own router and I'm suspecting that maybe my Router is not supporting it or I'm just reading the settings wrong. I'll keep trying here and see what it requires...I Might need to set up the guest network cause the issue might be the click through is not there or my regular router is set to NOT allow another AP to connect...Just got it today so I will continue to play with it. Click to expand... Click to collapse Rest assured, it works great for me. E.g. when I was at Starbucks (requires click through, has AP isolation) I got CCast working with WISP on my private SSID. Testing a few corporate locations today. The CCast took a while to *finish* setup, it hung first time. So I pulled power and tried twice. Second time worked. Not very scientific, sorry. I definitely used my laptop to click through on Starbucks and I was wired during setup. I will attempt to run some configuration tests non-wired too (thanks for update). The big advantage of the 710N is inexpensive, if you have AC power source. Also, I found another awesome portable router, better for CCast in my situation but also more expensive, e.g. $60 USD. I configured this one completely non-wired. ----- UPDATE: The HooToo TM04 does *not* work on certain networks. Do Not Buy!!! Read below... ------ HooToo TM04 product webpage here, and amazon here. It is a really new item. This item costs $60 USD on amazon. It has 6000 mah battery and without external power it can power two USB items (1) CCast plus second USB item (like phone, tablet, drive, pico projector, etc). Has two battery recharging modes: wall AC (faster) or microUsb. Lots of other features. Good review videos on YouTube here. Good luck.
@Asphyx # TL-WR710N I configured my CCast on another network (so it required reconfiguration at Starbucks) and took it back to Starbucks. I plugged the TL-WR710N into AC power, without wiring anything on NIC WAN nor LAN, and waiting about 2 minutes. Since I had already configured the 710N for WISP mode it restarted in that mode. It was the *same* location I had previously configured WISP, so that probably helps. (I will test WISP on new location tonight). At this point I tried CCast setup. I connected my Nexus 7 (2013) to the 710N WiFi SSID. Using the Nexus 7 I attempted to setup the CCast, and completed all the input configuration screens. But, the Setup screen *hangs* after confirming name and entering my WiFi SSID password. By hanging I mean the CCast app big circle keeps spinning and after about 5 minutes returns an error. But, this error is wrong because the CCast device is actually configured and working. I must perform the Starbucks click-through on the Nexus 7 2013 to register the 710N MAC address to access the internet. While the CCast app circle is spinning I switched to YouTube and it casts perfectly. Also, I can screen cast the Nexus 7 2013. I tried a couple tricks but the CCast app never successfully *completed* setup, yet the CCast device works 100%. Hmmmm. # HooToo TM04 ----- UPDATE: The HooToo TM04 does *not* work on certain networks. Do Not Buy!!! Read below... ------ So, I substituted the HooToo TM04 at Starbucks. The configuration was completely wireless (never used NIC cables) and basically the CCast app setup completed successfully! All the CCast device features (YouTube internet cast, local Nexus 7 2013 screen cast) worked 100%. Very simple and smooth configuration with no glitches. # Summary The difference was only the CCast app setup result, The 710N *hangs* with a spinning circle and eventually returns an error dialog, but the CCast device is configured and working 100%. The HooToo completes setup correctly, and CCast device is configured and working 100%. I am now wondering if there is a setting on the TL-WR710N required to allow CCast app setup to complete successfully (even though the CCast device is configured and working)? I will test further. Any comments or feedback requested.
Bob Smith42 said: @Asphyx # TL-WR710N ... But, the Setup screen *hangs* after confirming name and entering my WiFi SSID password. By hanging I mean the CCast app big circle keeps spinning and after about 5 minutes returns an error. But, this error is wrong because the CCast device is actually configured and working. Click to expand... Click to collapse Chromecast setup app has done the same to me a few times - and that's on my home WiFi that works fine. I wouldn't worry about it too much, I think it's just some kind of timing glitch. As long as exiting and returning to the Chromecast setup app reports Ready to Cast and Chromecast works, it's good to go.
Oh I'm sure it does work Bob, I'm just missing something and what makes it worse is I was trying to do this all through Wireless and a mobile device which this unit is difficult to setup with. I set up WISP mode but the issue is on reboot it didn't give me an SSID to reconnect. I'm sure I'm just borking something in the settings so when I have the chance to do this all via wired connection I will play with it a bit more...
[Q] Chromecast setup problems.
So, I'm setting up my new chromecast, but have have run into a problem. I'm able to find and connect my phone/PC to the chromecast itself, but it won't connect to my home (setup hangs at "connecting"). After a while I get an error message a la "can not establish contact with chromecast" (roughly translated from Norwegian). I've made sure uPnP and MAC address filtering both are disabled on my router.*I've already tried factory resetting the chromecast and moving closer to the router, to no help. Worth mentioning is that my router is not exactly new (tilgin vood something), and is not to be found in the list of routers in the chromecast support section.* Any tips?
olfyboy said: So, I'm setting up my new chromecast, but have have run into a problem. I'm able to find and connect my phone/PC to the chromecast itself, but it won't connect to my home (setup hangs at "connecting"). After a while I get an error message a la "can not establish contact with chromecast" (roughly translated from Norwegian). I've made sure uPnP and MAC address filtering both are disabled on my router.*I've already tried factory resetting the chromecast and moving closer to the router, to no help. Worth mentioning is that my router is not exactly new (tilgin vood something), and is not to be found in the list of routers in the chromecast support section.* Any tips? Click to expand... Click to collapse Try reducing the number of units that are connected to the wireless router and try connecting with the CCast again...Sometime on some cheaper routers too many devices connected will prevent new devices from connecting. You can also try rebooting the router or try moving the CCast closer. I do assume you have a Dual Band Wireless N router with the 2.4Ghz band enabled. CCast only connects to 2.4Ghz band.
Asphyx said: Try reducing the number of units that are connected to the wireless router and try connecting with the CCast again...Sometime on some cheaper routers too many devices connected will prevent new devices from connecting. You can also try rebooting the router or try moving the CCast closer. I do assume you have a Dual Band Wireless N router with the 2.4Ghz band enabled. CCast only connects to 2.4Ghz band. Click to expand... Click to collapse Normally there's no more than 2-3 devices connected to the router at the same time, so a lack of available connections to the router shouldn't be a problem. Both 2.4 and 5 Ghz bands are enabled on the router, so that shouldn't be a problem either. Moving the chromecast closer to the router didn't make a difference either. I'm really not sure what's the problem here...Thanks for the reply, though!
Is it simultaneous dual band? I mean does it run both bands on the same network or does it effectively run 2 networks? Simultaneous will work best, but if it isn't you need to make sure that the router allows both networks to speak to each other.
VPN via "server PC"
Hi All, I recently acquired a chromecast and would very much like access to the BBC Iplayer (I live in the netherlands). I can already watch Iplayer on my phone using the VPN option in android but once I try to watch it on chromecast it doesn't start the stream which is probably because the chromecast is connected to my home network which is not behind the VPN. I also can't mirror screen since I loose connection from my phone to the chromecast as soon as I connect my phone to the VPN. Now I read that it is possible to do with a DDWRT router but I do not have one of those and I wouldn't want my whole network to be on a different IP, just the chromecast & if needed my phone. I do however have something that I would like to consider a lot more powerful than a router, namely a "Server PC" running windows XP professional. Would I be able to use this server and enable the VPN on it and then make the chromecast connect to the server? Would I need 2 USB wireless adapters or 1 (so my phone connects to 1 and the chromecast to the second. My server connects via ethernet to my modem)? Could I somehow configure this USB adapter to be connected to the VPN by default? Could I use virtualization software? I would like the most clean option preferably without affecting the rest of my server (but it would be OK if the server is temporarily in the UK until I have watched the show). Perhaps this topic can be extended to other devices with wireless capabilities like NAS and raspberries etc. Your help is greatly appreciated.
Ok so after some digging I found at least 1 way of doing it: http://alphaloop.blogspot.nl/2014/01/raspberry-pi-as-vpn-wireless-access.html However I still think this should be possible on a windows XP machine with a wireless adapter.
On many Windows 7 PCs with wi-fi, you can use the following to create a hosted wifi network that your chromecast can connect to: netsh wlan set hostednetwork mode=allow ssid=XXXX key=YYYY netsh wlan start hostednetwork if you then share your VPN adapter's internet connection with the hosted wifi that you've created, you can connect your phone and chromecast to the same wifi XXXX and that will be connected to the internet via the VPN on the laptop.