LaPastenague wrote:
That is an interesting one.
That the TC is pingable but not discovered by airport.. stranger and stranger.
But I am guessing that internet is still working?? Just the TC has now disappeared off the scene.
Internet is working very well π
Try opening the TC share directly. ie in Finder, on the top menu, go, go to server,
Then try using AFP://IPoftheTC
If that fails, try using SMB://IPoftheTC
Works, both...
If that doesn't get anywhere, you need to really work through the whole network and obviously the TP-Link is the point of issue. This would all work properly using an airport device to extend the network. Since it is not apple and not able to actually work as MacBook requires, to give things like country code correctly.
Your other big issue here is MAC address of the MacBook (don't mix up MAC and Mac),
I know what a Mac is and what a MAC is π
can be hidden behind the TP-Link due to repeater.. ie universal repeater has an issue that from the main router, all clients connected to the TP-Link repeater are in fact the TP-Link itself. That may end up making internet available but not the TC.
TP-Link is working as Uni-Repeater, cause Repeater needs a AP with WDS enabled. TC is working as 802.11b/g and WDS seems to not working here.
Describe the whole network..
Main router?
I use a Fritz!Box 7112, this one shares its internet to the "main"-switch. This switch is connected to the TC, and the TC shares the connection (bridge) to all users.
What is its IP and what is connected?
I'm working with 172.31.30.x network.
Router: 172.31.30.1
TC: 172.31.30.4
TP-Link: 172.31.30.2
TC as AP in bridge? What is its IP?
yep ; see above π
TP-Link repeater, what model? What is its IP?
Model: WA-801ND - up-to-date
Experiment.
If you plug the Macbook by ethernet directly into the TC by ethernet, does it get IP address.. what IP?
Not tested, but an XBox is connected to my TC via LAN, it get an IP from the DHCP over the FritzBox.
Gateway and DNS address?
Gate: FritzBox, DNS: FritzBox (both 172.31.30.1)
open terminal and type arp -a.. you might need to ping the TC to populate the arp table.. what does it list the TC as and its MAC address. Check that airport can find the TC.
Ouput:
fritz.box (172.31.30.1) at bc:5:43:12:40:57 on en1 ifscope [ethernet]
time-capsule.fritz.box (172.31.30.4) at 0:1f:f3:3d:99:ff on en1 ifscope [ethernet]
Do a shutdown and restart of the MacBook and connect back in your room via the repeater.
When you are connected by wireless via the repeater what address do you get, with gateway and dns?
Got IP/DNS from FritzBox, always the same (repeater or not, the FritzBox know my MacBook MAC and give me my IP, cause the lease is not timedout.)
If you open a terminal and go arp -a is the TC listed or not..
Connected via repeater: visible, see above.
I think it will have disappeared. And even if you attempt to open it, or some other device connects via the repeater it will get lost.
The answer is to replace the TP-Link with an airport extreme or express .. even another second hand TC.. only remember the ethernet doesn't work when it is in this mode except the express.
Edit..
Another way around the problem.. buy a pair of EOP adapters.. or even better run ethernet, but I am guessing the whole reason you have the repeater is difficult to do that. The EOP adapters are available around $100 or so.. then you can run the TP link also in AP mode. You can set the same wireless settings but different channels to enable roaming. It will also work far better than repeater mode which halves the speed immediately.
Another expense, sorry, but if you want it to work that is the best way.
Sorry for the long post. I often figure these things out half way through.
I'm not an beginner about networking, of course, I'm learning this currently. And it seems logical that this issue above should work. TC is pingable and accessible over repeater, but not for Airport or TimeMachine.
Dont worry about your long post π