No Luck Connecting to Boombox

i recently purchased a Memorez mi3005 (imove boombox) that is specifically meant to be compatible with ipods.
however, my ipod will not work properly on the boombox. i have one of the first ipods to come out (15gb model # A1040) and when i place it on the boombox connector it freezes, won't play, and won't charge.
I played a friends brandnew video ipod on the boombox perfectly fine.
is there anyway for my old ipod to play on this boombox? is there a different boombox that works with the older ipods? do i have to buy a new ipod for this to work correctly? is there a download that i need to get my ipod up to date?
please help!

Did you ever figure this out? I purchased the IMove Boombox and it will only play one song. It will not progress to the next song nor will it let me change songs by remote or touch.

Similar Messages

Why won't my new 5s work with my Audi (cable connection) or boombox even though my 5 did?

My new iPhone 5s will not play music via my Boombox or my Audi car connection (using cable that connects where headphones connect) sound plays fine through apple headphones but if I connect up to the other devices it goes silent but no sound comes from the car or boombox, my iPhone 5 running the same operating system work perfectly OK? Can anyone help with this as I am about to sell my iPhone 5 but am pretty miffed to now have a device that I can't connect up to listen to music.
Thanks

Other users have had the same problem. Here are two possiblities:
1) get both the iPhone and Bluetooth in car to forget each other and then reintroduce as a new device.
2) It's possible that iOS7 has an updated Bluetooth that is not compatible with older versions used in cars. Contact the dealer to see if there's an upgrade for the car's firmware.

32 GB iPad 2 WiFi--no luck connecting to the internet

My iPad is "UNABLE TO CONNECT" to my wireless router.
I've already:
1) Reset my router.
2) Checked to make sure my PW is correct.
3) Reset my network settings on the iPad.
4) Reset my iPad.
Still no luck with connection.
All other devices have easily connected to my wireless router.
What can I do to resolve this issue?

You didn't indicate if it ever worked. If it NEVER did, the problem could be caused by a firewall in the router. For reasons that I do not understand, that will affect IOS (iPod/iPad) communication but will not affect computers or other devices.
You will need administrative access to the router. If a firewall is present, turn it off and test the iPod again. If it works, turn the firewall back on but weaken it a notch and test the iPod again. Repeat as required.

Anyone with Win XP Home Edition - SP2 have any luck connecting to Zen Micro???

Has anyone out there that has Windows XP Home Edition with SP2 had any success with the following:
. Using Zen Media Explorer with the Zen Micro successfully?
2. Actually having the Zen Micro recognized by the Windows XP Home Edition (using USB2.0)?
Since my first attempt at connecting to the Zen Micro without the software and firmware updates was unsuccessful, I upgraded Zen Media Explorer to 4.00.8 (from 4.00.3) and upgraded firmware to v2.00.2 (from v). Still no luck!!!
I need a savior here before I decide to start looking into return policys.
My problems are:
. I plug in the zen micro into the usb2.0 port, and it states, "Found New Hardware: Creative Zen Micro."
2. But then it immediately says there is a problem with the device and takes me to the "Welcome to the Found New Hardware Wizard."
3. I step through the wizard, point it to search for the appropriate drivers on the Zen install cd rom and also to search the C:\Windows\System32, only to have it tell me that "The hardware was not installed because the wizard cannot find the necessary hardware."
Any suggestions? There must be something in XP Home Edition that is not jiving with the zen and its software because I have used the Micro successfully at work on a XP Professional machine with no issue.
I will call Creative tomorrow if I don't get things settled out.

Ok I had the same problem. It's most likely a driver installation error.
Insert the software CD.
After it starts exit the installation and go to My Computer. Right click the D:\ (or whichever letter is your CD dri've) and select Explore..
From there you will look for a Folder named Drivers.
From there you should see 3 files and double click the first of the three,( If it's not the first one try the second or third)
This should be the driver installation pack for Creative Zen microdri've players ( Which includes the Zen Micro) After it should say something abuot re-connecting the player to make the changes fully effecti've. I restarted my computer and the player and plugged the player into the same USB port and XP recognized the player and Zen Media Explorer said teh player was connected.

Mountain Lion and Brother Wireless printers. NO LUCK CONNECTING!!!

Have a Brother MFC-7860DW and a Brother HL-3075CW. Cannot use EITHER wirelessly with my iMac. Please help...I'm about ready to chuck all of it into the pool. I've downloaded drivers from the Brother website, manuals, network connection "wizards", verified my interface, SSID, key passwords and the rest and STILL I cannot use these printers wirelessly. Not being able to use them wirelessly defeats the entire purpose of purchasing them. SOMEONE must know the answer to this! PLEASE HELP!!

Assuming that you have been able to connect both printers to your wireless access point (router), when you open Print & Scan and select to Add, are the printers failing to appear in the Default view?
If yes, then some printers offer an alternate means to connect to them. The Default view relies on the Bonjour protocol to advertise the printer on the local network. If the Mac is having an issue with Bonjour, which happens too often, then you will not see it. But, if you know the IP address of the printer, then you can add the printer by selecting the IP icon instead of the Default view. You can then enter the IP address of the printer, set the protocol to LPD or HP Jetdirect-Socket and select the supporting driver in the Use menu. Click Add to complete the setup and then see if you can print.

No luck connecting 2 macs

so i have my non-wireless tower hooked up to my wireless macbook pro via firewire 400 and i have the personal filesharing box in prefrences turned on on both machines....but for some reason, the computer doesnt show up in the network window from the go pull down menu.....is there something I missed? also firewall IS turned off.

Have you configured IP over FireWire?
Just connecting the machines via FireWire isn't sufficient. You need to configure the FireWire port with IP addresses, etc. via System Preferences -> Network.

Frustration of connecting a NAS to macbook pro

Hello friends, I have been having hard time trying to directly connect my newly purchased ds111 to my macbook pro via ethernet cable. It needs to be connected directly rather than going through router as the route is currently at another room. Basically, I have set a static ip for my ds111 at 192.168.1.50 with the subnet 255.255.255. and a static ip for my macbook pro at 192.168.1.51 with the same subnet, 255.255.255.0. I have luck connecting my ds111 to my macbook pro but whenever that happened, i will not be able to connect to internet and vice-versa. It has been getting really frustrating! Would really appreciate it if someone could offer some advice on the setup, thanks!

Does the Airport give you the same IP scheme as you are using for the NAS? In other words, does it start with a 192.168.1.x range with a 255.255.255.0 subnet? If so, you will need to change one or the other. If you changed the NAS to 192.168.0.32 and your Ethernet to 192.168.0.40, for example, with a subnet of 255.255.255.0, you may be able to get everything to work. If it still does not seem to want to work, you could give yourself and the NAS an IP within the 169 range. What this does is that your computer KNOWS that is not an internet routable path, so it should not go in that direction. You could assign your Ethernet port to 169.254.145.112 and give the NAS 169.254.145.118 with a subnet of 255.255.255.0. That should work.

Can't scan or connect to WPA network since kernel upgrade

Hi guys,
I upgraded to kernel 2.6.29 earlier today and have been having trouble with scanning and connecting to WPA encrypted networks since. I'm stuck with a wired connection for the minute, but I can't have the wire going through the house for so long otherwise somebody will trip over it - probably me.
I usually use netcfg to connect to the network, but since the update that has failed.
My network called is a Belkin USB Wireless G, model number F5D705ed version 5000ed. It worked perfectly fine on 2.6.28 using the rtl8187 native drivers.
dmesg output for 2.6.29
usbcore: registered new interface driver rtl8187
rtl8187: 8187B chip detected.
wmaster0 (rtl8187): not using net_device_ops yet
wlan0 (rtl8187): not using net_device_ops yet
phy0: hwaddr 00:1c:df:47:44:c0, RTL8187BvE V0 + rtl8225z2
I can start the card up using
sudo ifconfig wlan0 up
When I attempt to scan for a wireless network, I get
sudo iwlist wlan0 scan
wlan0 No scan results
The network is WPA, and would scan fine on 2.6.28.
wpa_supplicant.conf looks like this
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="Arazmataz"
psk="*****************"
priority=5
I should note though, that since the update - /var/run/wpa_supplicant seems to have disappeared.
network.d/profile looks like
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa"
ESSID="Arazmataz"
GATEWAY="192.168.1.1"
KEY="**************"
IP="dhcp"
IWCONFIG="rate 54M"
TIMEOUT=120
dhcpcd times out also and netcfg fails to connect. Going back to WEP seems to work ok.
iwconfig
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Please help!
Thanks.
Last edited by paulingham (2009-04-09 19:04:23)

brain0 wrote:So everyone whose issue is NOT solved by installing crda and configuring it, please raise your hand (paulingham, I guess you will be one of them).
*raises hand*
I've made some progress though - but still can't connect. I can now scan for a network though.
/etc/conf.d/wireless-regdom
WIRELESS_REGDOM="GB"
/var/run/wpa_supplicant still didn't exist, so I created a /var/run/wpa_supplicant folder - and saw a few success messages in the log. This allowed me to bring the card up again and scan for a network.
At this point, I was getting excited until netcfg2 still kept telling me that it couldn't associate with the network.
I installed wicd and gave that a go and got the following. I did a 'tail -f /var/log/wicd/wicd.log' and got this;
2009/04/10 15:17:10 :: Connecting to wireless network Arazmataz
2009/04/10 15:17:10 :: Putting interface down
2009/04/10 15:17:10 :: ifconfig wlan0 down
2009/04/10 15:17:10 :: Releasing DHCP leases...
2009/04/10 15:17:10 :: Setting false IP...
2009/04/10 15:17:10 :: ifconfig wlan0 0.0.0.0
2009/04/10 15:17:14 :: ifconfig eth0 0.0.0.0
2009/04/10 15:17:14 :: Stopping wpa_supplicant and any DHCP clients
2009/04/10 15:17:14 :: killall wpa_supplicant
2009/04/10 15:17:14 :: iwconfig wlan0
2009/04/10 15:17:14 :: Flushing the routing table...
2009/04/10 15:17:14 :: route del dev wlan0iwconfig wlan0
2009/04/10 15:17:14 ::
2009/04/10 15:17:14 :: route del dev eth0
2009/04/10 15:17:14 :: Generating psk...
2009/04/10 15:17:14 :: ['/usr/sbin/wpa_passphrase', 'Arazmataz', 'key commented out here']
2009/04/10 15:17:14 :: Attempting to authenticate...
2009/04/10 15:17:14 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c',
'/var/lib/wicd/configurations/001b11ada667', '-D', 'wext']
2009/04/10 15:17:14 :: iwconfig wlan0
2009/04/10 15:17:14 :: Putting interface up...
2009/04/10 15:17:14 :: ifconfig wlan0 up
2009/04/10 15:17:18 :: iwconfig wlan0 mode managed
2009/04/10 15:17:18 :: ['iwconfig', 'wlan0', 'essid', 'Arazmataz', 'channel', '6', 'ap',
'00:1B:11:AD:A6:67']
2009/04/10 15:17:18 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:19 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:20 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:21 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:22 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:23 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:24 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:25 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:26 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:27 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:28 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:29 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:30 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:31 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:32 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:33 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:34 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:35 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:36 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:37 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:38 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:39 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:40 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:41 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:42 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:43 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:44 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:45 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:46 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:47 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:48 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:49 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:50 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:51 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:52 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:53 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:54 :: WPA_CLI RESULT IS SCANNING
2009/04/10 15:17:55 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:56 :: WPA_CLI RESULT IS ASSOCIATED
2009/04/10 15:17:57 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE
2009/04/10 15:17:58 :: wpa_supplicant authentication may have failed.
2009/04/10 15:17:58 :: exiting connection thread
I checked the password multiple times, and it is what it is supposed to be. Still no luck connecting.

Can't connect to work VPN

Hi,
I've read through some previous posts, but haven't had luck connecting to the corporate VPN at work. I can sucessfully connect using a mobile wireless dongle (that uses the mobile telephony network) connected to my computer. I tested this to make sure everything works. Unfortaunately i cannot conect to work VPN server via my wireless LAN at home.
I'm using WRT54G2 linksys wireless router and have turned on the VPN options.
I can ping the VPN server, but I can't connect. I think it fails to authenicate, keeps trying, and I just have to cancel it after a few minutes.
Any ideas? Is it the router or could it be my service provider (iinet) that block the VPN connection somehow?
Thanks
Tim
Solved!
Go to Solution.

I tried connecting (with an ethernet cable) directly to the modem and I have the same problem.
I can still ping the VPN server at work, and I can access the internet fine except the VPN connection. It fails to connect to the VPN server and eventually times out. I get an error "VPN server failed to respond". I'm using Nortel VPN Client to connect (everything was installed and configured by my work IT).
I've asked by ISP (iinet) to open port 500udp (which is what my work IT guys suggested). I haven't heard back from my ISP yet.
I'll let you know if it works after I hear back from my ISP. Fingers crossed...
Tim

Sender mail adapter - connecting to Lotus Domino

Hi all,
I'm currently trying to configure a communication channel to pick up from a Lotus Domino mail server using POP3 (I'd be willing to do IMAP4 as well). The Lotus team has told me that the POP and IMAP services have been activated but I'm not having any luck connecting to the server. The error message I get each time is exception caught during processing mail message; java.net.ConnectException: A remote host refused an attempted connect operation.
Any ideas? The configuration I'm using is:
URL: pop://mymailserver.com/mailin/xi_dev_users.nsf
Authentication Method: Plain
User: mmorris (my user has been given access to this mail file)
The rest of the config is default.
I've also tried specifying the port (110) even though that is the default - no luck.

Hi Mike,
pinging successfully does not guarantee you're gonna be able to exchange messages.
Try to connect through telnet through the port you mentioned.
Another possibility: did they set SSL on the POP3 communication?
If yes, you need "pops://" as the protocol in the URL (default port 995).
Best regards,
Henrique.

Connecting my Tungsten E2 to the internet

I cannot get a connection what is the easiest way of doing such?
Post relates to: Tungsten E2

The problem you're having dunaz is the lack of a driver for any LG phone.
Palm PDA's seem to have much better luck connecting to phones on GSM networks. Sprint unfortunately uses a CDMA network.
I don't know why there aren't any LG drivers, but even a third-party driver provider (NovaMedia) does not make one for that manufacturer.
WyreNut
Post relates to: Centro (AT&T)
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

Connecting Sony Handycam HDR-SR10 to Macbook (circa Jan 2007)

Hey Guys,
Sorry for my macbook noobness but I'm actually asking this question on behalf of my girlfriend.
She has a HDR-SR10 handycam as mentioned and needs to hook it up via USB. The install disk that came with it is windows (according to her, I havent verified if it has any Mac software on it), and if she plugs it in it doesnt auto-install.
I've heard these cameras work OK with the Intel Macbooks, however I think this macbook isnt an Intel model. It was bought around the start of 2007...
Has anybody had much luck connecting the HDR-SR10 to these vintage Macbooks and how did you go about it?
Much appreciated.

I don't know if this will work for you (tested with an HDR-SR8), but, you'll need an external firewire hard-disk, the steps:
1. Plug the camera to your Mac;
2. A folder named NO NAME will appear in your desktop (if you have set in Finder to show external HD's);
3. Copy all the folders inside NO NAME to the external hard-disk;
4. Eject both NO NAME and your external hard-disk;
5. Disconnect both the camera and the firewire cords;
6. Open iMovie and press command + I (Movie import window will open);
7. Plug your external hard-disk and a message telling you that a new camera was detected will appear;
8. All the movies inside the external firewire disk should appear, select the ones you want to import or all of them;
The first time i did this, nothing happened, disconnecting and connecting the cord did the trick for me, the second time this was not necessarily, just press command + I and the message should appear, also i have HD and SD footage on the camera and could only import SD footages directly from the camera, to import HD footages i have to do the firewire disk trick (maybe you don't need to copy all the folders, only the AVHCD folder).
It took me 1 week of trial-error until: success!!

Airport refuses to connect to wireless router... most of the time

I'm having a really odd problem with my MacBook Pro trying to connect to the internet via my wireless ZyXEL router. I've had the router for a while and use it to connect a Mac Pro and PC by LAN and a Wii and iPhone wirelessly and It's never given me a headache before.
Airport picks up the local WIFI networks, including mine, no problem. But when it tries to connect, after asking for the WEP Password, it just times out. I have tried creating the network connection manually within the "Network" area under "System Preferences" selecting various security methods (WEP Password, WEP 40/128-bit ASCII and None) but nothing works. And everytime I manually select the ZyXEL network it asks for the WEP password anyway. No matter how many times I put it in, it wont connect.
I also logged into the system preferences of the ZyXEL wireless router and input the MacBook Pro's MAC address and selected "allow access" but it still wont connect. Except just one time, when I simply turned Airport Off and On again it connected fine and didn't ask for the WEP Password?!? But then after I rebooted machine It won't connect again and turning Airport Off and On doesn't work anymore either.
Can anyone shed some light on the problem?
Thanks very much

You may have noticed that your issue is fairly common and no one single solution works. So all I can offer is a few things that I know have worked for me, my friends and colleagues, and my customers.
1) make sure your computer can connect wirelessly elsewhere. There's little worse than struggling with an issue at home only to discover it wasn't fixable.
2) make sure your base station's firmware is up to date
3) try turning off the security on your base temporarily and see if you can connect that way. If so, try a different security method.
4) try changing broadcast channels. You may have a neighbor on the same channel which blocks reception - I know, why this computer and not others? Voodoo
5) open your Network preference tab and select Airport. Delete any preferred networks you find and make sure that ask to join new networks is checked
6) create a new account and see if it has any better luck connecting. Last spring I struggled with a computer for several days and one of my IT students suggested this pointing out that I suggest it for many other troubleshooting issues. Darn smart aleck student! Obviously at some point the admin's network prefs got munged and everything I tried after that was for naught.
Good luck

Airport refuses to connect unless I restart

After installing Leopard, my Airport has been having issues with the wireless network at my workplace. Whereas with Tiger, it would connect to the network and everything would work fine, with Leopard, Airport connects, but has a "self-assigned IP address". Nothing short of restarting will get the computer to connect to the internet; after restart, Airport connects, gets an IP address and everything works fine. This issue was NOT fixed in 10.5.1. Any suggestions?
May I add, an "upgrade" that breaks such fundamental aspects of the system is unacceptable.

You may have noticed that your issue is fairly common and no one single solution works. So all I can offer is a few things that I know have worked for me, my friends and colleagues, and my customers.
1) make sure your computer can connect wirelessly elsewhere. There's little worse than struggling with an issue at home only to discover it wasn't fixable.
2) make sure your base station's firmware is up to date
3) try turning off the security on your base temporarily and see if you can connect that way. If so, try a different security method.
4) try changing broadcast channels. You may have a neighbor on the same channel which blocks reception - I know, why this computer and not others? Voodoo
5) open your Network preference tab and select Airport. Delete any preferred networks you find and make sure that ask to join new networks is checked
6) create a new account and see if it has any better luck connecting. Last spring I struggled with a computer for several days and one of my IT students suggested this pointing out that I suggest it for many other troubleshooting issues. Darn smart aleck student! Obviously at some point the admin's network prefs got munged and everything I tried after that was for naught.
Good luck

AD HOC connection EOS 6D to MacBook Pro

Though successfully made an AD HOC connection to my smartphone I've had no such luck connecting to my Mac. If it's possible on ios 7 it's gotta be possible on OS X Mavericks...
I get all the way to the "select camera" option from the WFT pairing icon at the top of my screen, which indicates that it sees my eos 6D. I select it, click connect, at which point it prompts me to complete the process on my camera's LCD.. and then something happens, the camera disapears from the WFT Pairing Software window. Once or twice I've gotten my camera to see "Nate's MacBook" too but still the EOS Utility doesn't recognize any connection.
Has anybody had any success connecting the 6D to a Mac wirelessly using an Ad hoc connection? It must be possible.. it should be trivial. But I've (unfruitfully) poured hours into this. Very frustrating.
Thanks in advance.

Speaking for my own experience, I do understand the difference between ad hoc and infrastructure. As I mentioned in my previous post, I have 6D WiFi working with my iPhone, iPad and Selphy printer. All of these are "ad hoc" and I've named the settings with "-CAP" to indicate Camera Access Point. I turn on the 6D WiFi, then I have to change or choose the other device settings to Join my 6D WiFi name.
For using the EOS Utility, I'm trying to use infrastructure. In this case I have the camera search for my home WiFi network, which it finds. Apparently the only option I have to connect to my AP is thru WPA2 so I enter the ascii password. This works. I then go thru the steps to initiate pairing, start the EOS Utility if its not already running. WFT Pairing appears in the menu bar, sends a notification that an EOS camera is connected, and shows the Select Camera dialog. I select it and Connect. At this point one of two things happens:
1) I get a popup from either EOS Utility or WFT Pairing telling me to complete the steps on the back of my camera. However, there are no steps there to complete. I can only Exit the connection, or Confirm the settings, which is display only. There is no way to exit this popup manually on the Mac.
2) A popup (might be the same as above) appears briefly, disappears, the EOS Utility main menu comes up, but everything but the last option (Monitor Folder, which is merely a preference setting) is greyed out.
In both cases the camera's Confirm Settings looks correct, except that sometimes the auto assign of an IP is all zeroes, sometimes it's a good IP address from my router. This doesn't seem to have any bearing on whether WFT Pairing will see the camera, however briefly.
Now here's the interesting thing. Yesterday I tried setting it up using my iPhone as a personal hotspot. Using that as my WiFi infrastructure access point, switching my computer over to it and creating new 6D settings for it, I was able to get it to work. That's good to have/know, but I would like to use this around the house when I am using my home studio without having to switch over to my cell phone.
I'm using an Apple Time Capsule as my router. Because of how Verizon hooked me up to their system, it's in its passthru mode. I don't know if that matters, but at any rate, I could not get it to work with the Verizon router directly either.
I also see that OS X Image Capture app (OS X default app for pulling pics off cameras and cards) does see the 6D when I make this WiFi connection.
I see this in the console log whenever this fails:
3/21/14 3:48:36.109 PM Image Capture Extension[544] [2] Failed to register for death of process with pid: 555
where the pid refers to the PTPCamera process. No useful messages from it, though.
Right now my guesses are that there is some sort of miscommunication between the camera and the Pairing utility, or something like Image Capture is interfering. Although the latter guess loses credence considering I got it to work with a personal hotspot.
I am using the latest Canon software available here, on OS X Mavericks. Camera firmware was just updated to 1.1.4 yesterday.

No Luck Connecting to Boombox

Similar Messages

Maybe you are looking for