Q: Latest AirPort Utility on Mac OS X 10.8 does not see latest 7.3 Firmware Time Capsule, while iPad AirPort Utility can

Reset the TC to factory settings..

This will not harm any data on the hard disk.. you just need to start over after that worst possible firmware upgrade you did.

I recommend in the new setup.. plug in the TC with ethernet to the laptop.

Give it all SMB compatible names. Short, no spaces, pure alphanumeric.

Finish the setup, update and put the TC back into the network.. reconnect the wireless to the new name.

And locate the hard disk.

You might need to reset TM.. but start by just setting the target disk again.

It will generally work fine.. at least for a few days and then need a reboot to remind Mountain Lion of where everything is.. it is a dumb lion.

Factory reset is not the same as standard reset.

Please do plug the TC into the computer.. and do a factory reset..

Turn off wireless and leave out all other connections.

6.2 utility has nothing to do with it.

Make sure you get an IP from the TC.. if not the ethernet cable is plugged into wrong port.. use LAN on the TC.. or is dead.. is it a Gen3.. the wireless can work but not ethernet which fails.

Tell me exactly what version of TC it is.. A1xxx from the rubber mat.

Load 5.6 utility into Mountain Lion. it is far superior to any v6 utility.

How to load 5.6 into ML.

1. Download 5.6 for Lion.

http://support.apple.com/kb/DL1482

Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.

2. Download and install unpkg.

http://www.timdoug.com/unpkg/

Run unpkg on the desktop.. it is very simple.. drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. drill down.. applications utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.

You cannot uninstall 6.1 (now 6.2 if you updated) so don't try.. and you cannot or should not run them both at the same time.. so just ignore the toyland version.. the plastic hammer.. and start using 5.6.. a real tool.

For screen shots see this post.

https://discussions.apple.com/thread/4668746?tstart=0

I am not sure why you are swapping wireless networks in your second screen shot.

Do you have static IP set or any fixed DNS like using opendns in the computer?

I am really at a loss why the TC should not show up by ethernet.. although it finds it ok, unless the IP addressing is not working correctly. There is a discovery mechanism which the Mac uses, but if the IP is set statically to the wrong IP range it will give that result.

If you open the IP settings what IP is the ethernet getting in the computer.

This would be the standard setup with the first IP 10.0.1.2 delivered to the computer and the router and dns getting 10.0.1.1

If you have something else either set back to auto, or manually set to the above settings.

Did you upgrade the TC firmware to 7.6.3 when you also updated the utility?

Can you please take the TC firmware back to 7.6.1.. just hold the option key when you select firmware and it will allow you to pick earlier firmware.. if your TC is an older Gen4 ie more than 12months old you could also try going back to 7.5.2.. you can upgrade again later. This is just a test.

Are you using the reset button to reset or doing it via the utility? Whichever way you do it, can you do it the other way.. I have seen unusual things happen.

Once you have taken the firmware back, turn off wireless again in the computer.. and do the test again in complete isolation. Nothing else but the TC plugged into the computer.. ensure you are getting IP.

Open a terminal and ping the TC ip address.

Then try pinging it by name.

In finder, try and mount the TC. If it doesn't appear.. use the manual method.. Go in the top menu, Connect to Server. And type in the actual connection AFP://10.0.1.1

Tell me if that works.

Or at what step it fails.

 

But I still get the same error as before, scan with AirPort Utility 5.6 does not work.

Sorry scan in the airport utility locates the TC.. the TC is already located.

You stated your original problem was the airport utility could not locate the TC.. now it does.

Explain what you are doing in the network to stop the TC being located or explain the problem again as I am confused with the issue.. which I thought the Airport utility couldn't find the TC.

Can you please try using the manual setup instead.

You have already got into the manual setup to get to the summary page.. that is why i thought the issue was fixed.

Just go to the internet tab and make sure it has the correct value for your system.. ie share a public IP or bridge mode..

Go to the wireless tab and fill in the wireless details, and security in particular.

Then the disk / filesharing page to complete anything necessary there.. but the defaults will be fine for that.

The TC will then complain about a few things.. using default password.. that is not a problem for most people.

Just ignore that.. unless you actually do need better security for TC access.

Then usually it will complain about access over wan which is somehow on by default.. turn that off usually.

All the rest should be fine.. update and put the TC back in the network.. I would hope once you complete the setup then the normal edit via the v6 utility will also work fine.

Forgive my slow understanding.. I am trying hard to help.. not irritate.

I haven't seen the issue before..

What you saw the summary page it was because I got there through File > Configure Other, and then entered the IP of TC manually The settings there are the same you described, mostly default ones.

 

I am starting to think I have to reinstall Mac OS X....

So from that manual summary page,, if you click on time capsule .. it immediately starts saying it has to find it via wireless?? Something is really wrong if that is the case. And I don't see how it can affect 5.6 utility even if the files loaded by 6.2 are somehow the cause..

I don't know of any way to get around the issue.. and so a clean install of OS might be the way to go. Although it seems excessive to get past a simple issue of not accepting the ethernet connection.