Time Capsule as Proxy

I am a UK resident and want to watch UK TV whilst travelling. I have tried various proxy servers but they're always slow. In the UK I have a Time Capsule that has my router attached and I connect to the internet through the Time Capsule (the old version). When I'm abroad can I connect via the internet connection abroad to my Time Capsule and so connect to UK TV services with a UK IP address?

If they are blocking vpn and dns type services then sorry there is really no way around it unless you can afford very high speed fibre connections so you can get really fast upload speed.
Check forums if there are any services that will work.. but I am guessing the media providers are keeping close tabs and shutting down services pretty quickly that try and by pass it.
Setup DVR at home.. and record the shows.. so you can watch them when you get back.
There are other more naughty methods.. you can figure out.

Similar Messages

DNS Issues with Time Capsule - DNS Proxy periodically dies

hi all .... looking for some suggestions
I have a time capsule 1TB, connected to a linksys adsl modem in bridge mode, with the TC acting as DHCP server for my local clients. In the PPPoE settings I also enter the primary and secondary addresses for DNS that my ISP supplied.
I am able to successfully connect to the internet, and all clients successfully pick up an IP address, and each client picks up the TC as the DNS proxy. Everything works perfectly as it should.
Usually once per day, there seems to be a slight hickup with the internet connection (hard to tell whether I am losing the PPPoE or some other issue). When this happens, the PPPoE connection remains active, as I am able to access anything on the internet from an IP level. However, the DNS proxy service on the TC seems to die and as a result, all internet browsing fails. If I reboot the TC, everything comes back to normal. If I dont reboot, the only way to get browsing working is to manually enter the DNS IP address from ISP into the client PCs. However, this is a manual fix that I should not have to perform.
Looking for advice and guidance. Seems like a bug but I cant tell. If I was able to set the DHCP server to pass out the ISP supplied addresses that would also work, but I cant.

Just got off the phone with support for this very same problem. DNS Proxy is definitely dying in the TC, looks like a firmware issue to me.
This is the 3rd TC I'm on. First was a 500GB, had this problem, replaced it under warranty at Apple's direction, replacement did the same, just upgraded this weekend to 1GB, and same issue still. All on 7.3.2 firmware.
TC 1TB, PPPoE to my ISP, ISP's DNS Servers listed in the PPPoE config in the TC.
When a host gets DHCP from the TC the only DNS returned is the TC itself, since it proxies the ISP DNS servers.
Once every day or two, the DNS proxy dies. local network works, and I can add my ISP's DNS addresses in my host config and I have DNS again, but this is definitely something dying in the DNS proxy in the TC.
Just for kicks trying to switch from my ISP's DNS servers to OpenDNS now since someone said that worked for them, but I am not hopeful... I don't see this as a host DNS issues at all.
The dead proxy is very clear:
$ nslookup apple.com. 192.168.1.1 # that's the TC
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can't find apple.com: SERVFAIL
$ nslookup apple.com. 208.67.222.222 # that's OpenDNS
Server: 208.67.222.222
Address: 208.67.222.222#53
Non-authoritative answer:
Name: apple.com
Address: 17.149.160.49
I replaced a linksys router with the TC and am kind of unhappy that a $500 router dies every couple of days. My cheapo Linksys router never needed to be restarted, it only ever got rebooted once every year or so when the house lost power long enough for the UPS to run out of battery.
Help us out here Apple, I replaced a $50 router with a $500 because I like the flavor of your kool aid, and this thing dies every day or two. Even if you can't fix why the proxy is dying every couple of days, can you please at least update the firmware to maybe restart the proxy if it quits working?

Slow DNS Resolution using Time Capsule

Hello,
I'm using a time capsule as my main internet router and wireless access point, and I've noticed a significant delay before web pages begin to download. In trying to troubleshoot this, I came across a very helpful utilitity called the Netalyzr from Berkley. Using this tool, I'm able to see that there is a significant delay in name lookups using the time capsule DNS proxy capability. There's not a lot of documentation on this, but it appears that instead of handing clients the designated DNS servers configured in DHCP, it hands out its own address to the clients as the DNS server and makes the DNS request to the configured servers. I've included the verbage from the Netalyzer tool below.
Your ISP's DNS resolver requires 2200 msec to conduct an external lookup. It takes 81 msec for your ISP's DNS resolver to lookup a name on our server.
This is particularly slow, and you may see significant performance degradation as a result.
As you can see, this causes almost a 2.5 second "pause" before the lookup is even returned. However, if I hard code the designated DNS servers into this client (Macbook air running Lion), I get the following result.
Your ISP's DNS resolver requires 110 msec to conduct an external lookup. It takes 81 msec for your ISP's DNS resolver to lookup a name on our server.
This is a significant improvement over the lookup using the proxy capabilities of the Time Capsule. This leads me to believe that the DNS "proxying" that the time capsule is doing is really slow.
I'm using opendns as my provider in both scenarios.
Is this a known issue, and if so, is there an existing fix or a planned fix for this?
Best,
Eric

Frankly I just don't believe those analysers.. not until I can prove it myself.
Do a very simple test..
Open terminal and ping a website you have never opened before.
You should do this from a PC or Mac on the network using ethernet. Just to keep crummy wireless responses out of it. And do it without internet activity going on.
Do it a second time, and it should be instantaneous now having the address resolved and held in the cache.
If you get a significant lag before the address is resolved to actual IP, there maybe something wrong. And the first test then would be to change the DNS server to your local ISP not opendns.. because the routing to opendns might also be an issue.
You can also test by removing the TC from the network..plug a computer directly to the modem and just browse.. compare that to speed with the TC. I know it isn't exactly scientific but a 2.5sec delay in dns resolution you will notice it. It is important to connect to stuff that is outside your normal pattern. Otherwise it should just be in the cache.
Otherwise it is unlikely to really exist.

Time Capsule and a Proxy (VPN)

The main router into my home in Germany does not support proxy. Can I set up my time capsule to send and receive vpn proxy with it connected to my German router (deutsch telecom)?
Also, I can set up a vpn proxy on my Mac book. Could Apple TV get its stuff through that proxy? I ask this question, if I can't get a proxy going through my time capsule.
Thanks

The Time Capsule...and most other newer routers will easily provide more than 200 IP addresses to devices that need to connect, so there's no limitation there.
In most complex networks involving a number of switches, it's often a bad ethernet cable or cable(s) that are the cause of poor or no connections.
Start at the TC and work back. Disconnect everything everywhere after the TC.
Then using a laptop (wireless off) and a "good" ethernet cable, simply test each port on the TC to make sure that you can get an internet connection.
Then, before you plug the ethernet cable from one of the LAN ports on the TC into the "next" switch, plug the cable into your laptop and test again to make sure that you have a good internet connection. Then, test each of the ports on the switch.
You get the idea. You have to test each connection point one at a time working your way back to the end of the network. There are no shortcuts. You have to test each connection before moving to the next.
It's almost always either a bad cable (and I include the RJ-45 connector as part of the cable) or less likely, a switch with a bad port. If you have a collection of older ethernet cables, it's also possible that you have a 'crossover" cable mixed in somewhere. Depending on the capabilities of each switch, this can also cause a "no connection" situation.

Time Capsule as Router via Proxy

Hi all,
Thank you in advance. I recently moved to a new apartment complex that connects each room via proxy.
There is an ethernet cable in each room. IT takes our computers Ethernet ID, puts it in his machine, and then we put the proxy server and port in Firefox to connect to the internet.
I want to use TC as a router in the apartment. I set it up correctly (green light), and I gave the TC Ethernet ID to the IT department. But in Airport Utility I cannot find where I should enter the proxy server for TC.
So, while I can connect to Time Capsule and can backup with Time Machine, I cannot connect to the internet because the proxy server does not go through.
I hope this was clear. Please let me know what else I should tell you.
Thanks,

Hi,
I'm facing exactly the same problem. Could you please tell me where you entered the proxy server for the Time Capsule ?
Thanks,

Time Capsule doesn't work with proxy?

Hello! I have a Time Capsule working with an ethernet connection which is controled by a proxy server. I don't see the option to configure TC in order to download the .pac file, or to configure manually the proxy settings.
Therefore, the internet through TC doesn't work!
Anyone knows a solution?
Thanks

The blurb about Time Capsule not being compatible with some ISPs is no different from the same blurb that Apple has attached to the specs of all previous Airport base station products. So... if your ISP currently works with an older model Base Station, it will work with Time Capsule. ISPs that typically don't work are ones that use uncommon DSL communications or authentication protocols - often found in parts of Europe and the Middle East.
(Speculation on my part) Time Capsule will not function as a wireless client on an existing wireless network. Therefore, users of an existing wireless network will need to either (a) replace their existing wireless router with Time Capsule or (b) cable Time Capsule to their existing wireless router and disable the router built into Time Capsule. These are exactly the same options faced by previous purchasers of Apple's Airport base stations.

How do I configure Time Capsule to recognize my Denon receiver?

Hi all,
New to the forums but have spent the past few days perusing them to no avail - your help is appreciated from a networking newbie!
I have a Denon AVR 2312ci which I'd previously had hard-wired to an old Belkin router. The only hiccup I'd had at the time was the requirement that I disable UPnP. I have an Apple TV that I use to stream music via airplay to the receiver, which works quite well. However, it requires me to turn on the receiver, whereas directing airplay to the receiver itself would "wake on LAN", a feature I like.
Since then, I've upgraded to a 2TB Time Capsule. However, following the router change I am no longer able to find the Denon on my home network, nor do any of the networking capabilities of the receiver work any longer. I tried disabling DHCP on the Denon and assigning a static IP address, but this didn't work. I tested multiple Cat5e cables using various LAN ports on the router - no luck there, either. I tried to reset the network card on the Denon - same result.
I'm beginning to wonder whether the problem lies with the way the Time Capsule is configured - any thoughts or suggestions out there?

LP,
IT WORKS!
To summarize for anyone who might have this problem, here's what fixed it:
1) Time Capsule --Cat5e--> LAN port of router/switch (in my case, an old Netgear 10/100 with DHCP and NAT disabled) --Cat5e--> Denon receiver
2) Through Airport Utility, made an IP reservation for an IP outside of the DHCP range (in my case 10.0.1.2 through 10.0.1.200, so I chose 10.0.1.202). You will need your AV receiver's MAC address to do this.
3) Disabled DHCP on the Denon
4) Manually entered the IP address (e.g. 10.0.1.202), subnet mask 255.255.255.0, default gateway 10.0.1.1 (e.g. the TC's local IP), primary DNS 8.8.8.8, secondary DNS left blank, proxy off
This worked after I left the unit on standby for a period of a few hours (did not immediately work). I did not need to do any port forwarding, DMZ, etc.
I am now able to access the unit from my web browser in my local network and am able to airplay directly to the unit using my other airplay enabled apps/iTunes.
Much thanks to LaPastenague for his very helpful advice!!
KS

Connecting remotely to Time Capsule

I want to be able to connect to the time capsule over the internet from any location without my mac being switched on at home, will this be possible so i can access files on the drive.
Thanks Steve

Let me see ... do you have a static IP address from your ISP? If not, then No, you won't. If you get a static IP, you should be able to see the TimeCapsule from anywhere, but I am not sure you would be able to connect to it. All in all, this is really, really, really a bad idea. If you want to see it/use it from anywhere, you should set up proxy to sit between the drive and your modem and configure it as a DHCP server (control your network). Then mount the TC to that machine. You can use an old cheap PC (yes, they are actually good for something), set up a free linux dist (like Ubuntu), and then configure it to let you into your network and use the available resources (like the TC). Off course, like I said, you would require a static IP from your ISP.

Using Time Capsule as a second, separate wifi network?

I hope someone can solve this little riddle that I've been mucking around with for a couple of days now.
I have an existing wireless network, connected to the internet via an old Belkin wireless modem/router. I have an iMac and various other devices successfully connected to this Belkin network. But the other day I purchased a HD media player to stream vidoes, etc from my iMac to my TV. The problem is that the media player won't connect to the Belkin wireless network no matter what I try.
I also have a Time Capsule that I use solely as a back-up disk, connected via ethernet cable directly to my iMac, with wifi switched off. So I had the bright idea to use the TC to set up a wholly separate wifi network simply to connect the media player to my iMac, Long story short, it kinda worked but ended up spiralling me into a whole world of pain with the TC which I've only just managed to correct.
Basically I was in fact able to connect the media player to the TC wifi network but was only able to navigate my way to the Time Capsule itself, not to the actual iMac. So I aborted but that's when all the trouble started; trying to switch off the wifi on the Time Capsule...!
So my question comes down to this: Is it possible to have the iMac connected to the internet via the Belkin wifi router/modem and also have the TC act as a secondary wifi network which is solely an access point for other devices to connect to the iMac? Ideally the iMac might also then act as a gateway/proxy for the other devices to connect to the internet (but this is not critical, just an idea to possibly take full advantage of the capabilities of the new media player...).
It sounds feasible to me but I think I'm getting a little out of my depth...

If the Belkin is acting as a modem, put it in bridge mode and turn off its wifi, connect the TC to it via Ethernet cable, set up PPPoE on the TC to connect to your ISP and use the TC as the router for everything on your LAN.

My PC isn't accessing the internet via my Time Capsule.

I just got the new AirPort Time Capsule 3TB with 802.11ac WiFi and set it up. My iMac and my iPhones and my PC laptop are all connecting to the network just fine; however, the PC (a Toshiba Sattelite running Windows Vista) is the only device unable to access the internet.
I've been on the phone with Apple Support and MicroSoft Windows support, and neither has an answer. I have tried several things that have been posted on other discussion threads on this issue. None of those has worked for me, and the previous discussions on this issue (that I've found) have all originated from before the current TC model and before the current firmware version (7.1.1).
My iMac is running OSX 10.9 (Mavericks).
I am currently using all one-word alphanumeric names for my networks (I checked the 5Ghz box to make that a separate network, and I also have the Guest network set up).
I am currently using 10-character passwords.
I am currently using WPA2 Personal network security.
I am currently connecting using DHCP (and the PC is DHCP enabled), and the router mode is DHCP and NAT.
I am currently using fixed channels for both networks, and I have tried several different channels.
I ran the following diagnostics on the PC Command Prompt:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\user>
C:\Users\user>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : user-PC
   Primary Dns Suffix . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : hsd1.wa.comcast.net.
Wireless LAN adapter Wireless Network Connection:
   Connection-specific DNS Suffix . : hsd1.wa.comcast.net.
   Description . . . . . . . . . . . : Atheros AR5007EG Wireless Network Adapter
   Physical Address. . . . . . . . . : 00-21-63-5A-9C-07
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2601:8:b700:84d:9c97:bc23:1cc3:b795(Prefe
rred)
   Temporary IPv6 Address. . . . . . : 2601:8:b700:84d:21b7:cc6b:3e70:8e25(Prefe
rred)
   Link-local IPv6 Address . . . . . : fe80::9c97:bc23:1cc3:b795%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.0.1.3(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, October 27, 2013 6:33:11 AM
   Lease Expires . . . . . . . . . . : Monday, October 28, 2013 6:54:09 AM
   Default Gateway . . . . . . . . . : fe80::9272:40ff:fe08:1e6c%11
                                       10.0.1.1
   DHCP Server . . . . . . . . . . . : 10.0.1.1
   DHCPv6 IAID . . . . . . . . . . . : 285221219
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-10-47-D7-A5-00-1E-33-5F-2E-18
   DNS Servers . . . . . . . . . . . : 10.0.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Realtek RTL8102E Family PCI-E Fast Ethern
et NIC (NDIS 6.0)
   Physical Address. . . . . . . . . : 00-1E-33-5F-D5-60
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 7:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{BD700D70-4407-43E8-AA8B-DDA1E4D7C
854}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : hsd1.wa.comcast.net.
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
C:\Users\user>ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.1.3: Destination host unreachable.
Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
C:\Users\user>ping 98.237.184.1
Pinging 98.237.184.1 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 10.0.1.3: Destination host unreachable.
Request timed out.
Ping statistics for 98.237.184.1:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
C:\Users\user>
My thought is that it's either a case of the TC somehow blocking the PC from internet access, or else the PC not being able to make sense of the access information provided. The latter is the conclusion of Apple technical support, while Windows tech support concluded that I must have a defective router.
Any help will be much appreciated!

You can use the E1000 as wireless AP.
This is the method that will generally work with any wireless router. We term it Wan Bypass.. it is not an official method.. but works fine in vast majority of cases.
Leave your existing setup as is.. modem with TC plugged in.. keep the TC as the main router (at least I presume it is).
Let me work on real numbers as it is easier.. and you can adjust the setup according to your actual setup.
The TC has IP of 10.0.1.1 by default and dhcp passes IP from 2-200.
Plug the Linksys into a computer and setup the IP as 10.0.1.202 ... Please write this down as it will be hidden and if you forget it .. you will need to recover the Linksys by reset and start over.
Turn off the DHCP server in the Linksys. When you do this, and save the setting the computer will no longer be able to connect to the Linksys.. that is fine. Plug the Linksys now into the TC.. LAN port to LAN port. (Hence the name WAN BYPASS).
Back onto a computer connected as normal to the network.. access the Linksys at the address you just set.
Setup its wireless to have a different name to the TC and I would also recommend you fix its channel.. make it say 11. So the two routers don't fight each other.
Names should be short, no spaces and pure alphanumeric. Set up the wireless security as you normally do.
Remember this is wan bypass so plug LAN TC to LAN E1000.
If you run into issues.. post again.

New 2t Time Capsule shuts down: light is off, doesn't show up in network

2T Time Capsule completely shuts down: no activity light at all, doesn't show up in network registry, and is cold to the touch.
If I unplug and replug, it will work again, but will eventually shut down again.
Is this a problem with a sleep proxy service?
This unit is less than a week old.
I appreciate the help.

The internal power supply on the Time Capsule is defective. Soon, the Time Capsule will not turn on at all.
Please contact Apple for a replacement Time Capsule as soon as possible.

MacBook Pro - 802.11n, WPA2-Personal and Time Capsules

I recently moved to using 802.11n (5GHZ) mode on my Time Capsule using WPA2-Personal security. I am unable to connect to the wireless network which is extremely frustrating since this is all Apple hardware. I have no problem connecting to the 802.11n 5GZ network using one of my PCs.
My MacBook Pro has the latest software updates available and does have 802.11n enabled.
I have been looking for similar issues on the forum and have tried a few things that were suggested by others, but nothing works. I've reset the router. Reset the SMU. Haven't reset NVRAM yet.
I have a mix of Apple and PC hardware that is connecting to this network. My 24" Intel iMac (Core 2 Duo) connects just fine.
I'm hoping there is a GURU on this forum that can assist me.
Thanks,
J.d.

I would try:
1. Examine your system.log for the error you are getting, if you cannot authenticate with the router it will say why. Go to the Apple icon, select "About this Mac", select "more info" button in the center, select "Log" under Software on the left panel side, select "system.log" then scroll to the bottom, look for errors in the log related to "airport" or 802.11...
2. Go to Finder/Utilities, pull up keychain access.app, click on System on the left, you should see an entry for your WIFI network, delete that entry, close Keychain access.
3. Try removing, reboot then re-add your Aiport entry. Go to System Parameters, Network, highlight "Airport" click on the minus button and remove it. Reboot your computer. When it comes back up go back to System Parameters, Network, then click on the button and re-add the Airport, when it says Airport 2, over write that with just "Airport", then click on Advanced, click on button to add the Preferred Network back in, type the name of the SSID on your router, then select WPA2 Personal from the drop down menu type. You can also display the password to confirm it matches what you input in the router for the password for WPA2 Personal.
Under TCP/IP, if you are getting a private IP address from the router via DHCP, then set IPv4 to DHCP. I would not use IPv6 for time being, set that to Off. Next click on your DNS and input your DNS if not automatically filled in by the router with DHCP, I always like to add a DNS not provided by the router that way if it fails or you go to Starbucks you will always have a DNS entry that works, I would input OpenDNS's entries, so those would be under IPv4:
208.67.222.222 and other is
208.67.220.220
So to connect, your computer needs to have an IP address, either DHCP or manually input (like 192.168.1.xxx) etc.
Next you need a DNS entry if not provided for by your router (should be if it is dishing out DHCP client addresses).
WINS and Proxies are only used in corporate environments where they are using a windows domain and/or proxy servers as a gateway to the WAN.
WPA2 Personal offers much better security than WPA or WEP shared, if you use a password make it at least 8 characters in length 10 is better. The longer you make it the higher the security, but it must match exactly what the password was set for WPA2 on the router.
TO make sure you are not having signal/noise problems get as close to your router as you can to establish the connection once that is done you can move farther away.

Time Capsule - Share over WAN

My Time Capsule is connected to another router through Ethernet as bridge mode and wireless. Therefor the option to Share disc over WAN and i can't access it over the internet. Is it possible to set up the same Share over WAN feature on my routers web interence?

Ok, lets get down and dirty.
What modem router are you running?
Does it have a DMZ and have you tried placing the TC in the DMZ?
Many routers do not allow a connection to be made even after you have port forwarded because the firewall is turned on. Turn off the firewall in the router. Turn off the firewall in the router on the wan connection. Check that the computer firewall is also not preventing the connection.
*Firewall is a key issue for failure to connect over WAN connections*
Sometimes upnp in the router can mess up with manual port forwarding. Try turning off upnp.
I would also try reset of the modem and if possible see if you can get something to ping respond to you. If the modem has a ping responder in it, turn it on to ensure you can actually get packets to the router and back again.
I also have to ask you are actually testing from a different internet connection?? You cannot test wan port opening from LAN.. well not without nat loopback or remote proxy setup.

Time Capsule started randomly blocking sites

Hello
Earlier this week, in the middle of a browsing session on a discussion forum i'm on, i lost access to the site. I assumed it was a server crash or connection issue to the server, but a traceroute showed otherwise. I've also been able to access the site by using a proxy server, or by connecting using my iPhone with the WiFi turned off.
My next assumption was that my ISP waqs blocking it for some reason. I was on hold with them, and had just connected my MacBook Pro directly to the cable modem, and lo and behold, the site came up no problem. That immediately suggested that it was in fact the Time Capsule that was the issue.
Further research here suggested that this happens on AirPort and Time Capsule devices from time to time, and is most often remedied with a firmware update. However, my Time Capsule was already running the most recent version of the firmware (v7.6.3).
I have tried:
Restarting the Time Capsule
Restoring to factory defaults
Downgrading the firmware to 7.6.1 and then to 7.5.2
... all to no avail.
Is there anything else i can try, or do i have to sit tight until Apple issues yet another firmware update to resolve these issues? I'd really like to get back to using some of my favourite sites without having to use up my wireless data or run everything through a proxy server.
Thanks,
darren.

We are seeing a number of complaints like this.
The other site Bob referenced they talk about clearing the arp cache.. you should also clear the browser cache. It is surprising how often browser cache does cause issues.. I think you should do those things as matter of course but I doubt that is where the problem is.
Try turning off ipv6 in the computer. You cannot actually turn it off in the TC.. or none that I can see.. as IPv6 does start to creep its way into the net we are going to face lots of issues in the change over.
No fix with the above, I recommend you simply get another router for the meantime.. a cheap Netgear like the WNDR3800, has reasonable firmware itself plus runs several excellent 3rd party firmware. Bridge the TC and you can continue to use it as wireless and TM backup alongside the Netgear.. but Apple need to do some investigation of the problem so report it to them via the feedback.
BTW does the same thing happen on another computer.. particularly a PC if you happen to have one.. since you tried former firmware which were ok, maybe there is an OS upgrade recently that is causing it.. nice to check on a pc. Or en if your Mac is older and still has a CD drive you could boot linux live CD ?? I am not sure if that is poosible but I imagine you should be able to do it.. anything just to see if it is common across OS. Then the finger is definitely pointed at the TC.. although running previous firmware, makes no sense to me at all.

Connecting to Time Capsule via Ethernet AND wireless

I have connectivity through an Ethernet network to which my Time Capsule is connected. I connect wireless to TC, but another Mac which is out of wireless range -but still in the same Ethernet network,- cannot connect to TC via ethernet. Is there a way to have access to TC both wireless and via ethernet?
Thanks
Nilde

Hello Nadjia. Welcome to the Apple Discussions!
Is there a way to have access to TC both wireless and via ethernet?
Yes, the TC supports both wireless and Ethernet clients simultaneously. Let's double-check the Built-in Ethernet settings on the Mac that you are trying to connect via Ethernet.
System Preferences > Network > Show > Network Port Configurations
o Verify that a Built-in Ethernet option exists. If it does not, click "+" to create one. (Note: If you are unable to create a Built-in Ethernet configuration, the Ethernet card in your computer either doesn't exist or it is not recognized.)
o Verify that Built-in Ethernet is at the top of the list. If it isn't, you can drag it to the top.
Advanced > TCP/IP tab
o Configure IPv4: Using DHCP
o Configure IPv6: Off
Advanced > DNS tab
o Verify that your ISP's DNS server(s) appear. If they do not, click "+" add them.
Advanced > Proxies tab
o Configure Proxies: Manually
o Select a proxy server to configure: <All proxies should be unchecked unless you specifically require a proxy for Internet access.>
o Exclude simple hostnames (unchecked)
o Bypass proxy settings for these Hosts & Domains: <leave blank>
o Use Passive FTP Mode (PASV) (checked)
Ethernet tab
o Configure: Automatically

Time Capsule as Proxy

Similar Messages

Maybe you are looking for