Reboot!

Sometimes, for whatever reason, the networking stack gets stuck on the Mac. Rebooting the computer usually helps with that. Rebooting your device also may help. It's easy to do and relatively quick, so give it a try first.

Bonjour

For Wi-Fi sync, we use Bonjour (Zero Configuration Networking), an Apple technology. It is possible that Bonjour is disabled on your network. There are many ways to find out if Bonjour is working on your network:

• Try to find out if other Mac applications using Bonjour also have problems on your network -- such as iTunes music sharing or chatting via Bonjour in iChat (use the menu Window > Bonjour).
• Try another iPhone application that uses Bonjour, such as Apple's Remote (free).
• Another way to test this is to download and install Bonjour Browser (free). Launch Bonjour Browser, and look for an entry "_budget-touch._tcp" like in this screenshot. If you don't see this entry in Bonjour Browser while Budget Touch is running on the iPhone and the iPhone is connected to the same Wi-Fi network as your Mac, then it's a network problem.

If your network doesn't support or is blocking Bonjour, there is nothing we can do, and you will need to contact your network administrator.

Little Snitch

Are you using an application like Little Snitch to block certain network traffic?

If you have Little Snitch installed, and it asks you to approve Budget Touch it may still not be allowing the network connection between your Mac and iPhone. You will need to ensure connections are allowed for All Applications > Bonjour and also for mDNSResponder specifically.

Firewalls

Are you using Mac OS X's firewall? You can check by going to System Preferences > Security > Firewall. A Firewall is set up if the second or third option is chosen.

The process mDNSResponder might be blocked. As a result, Bonjour won't be able to connect to the iPhone. Once you allow connections for mDNSResponder, Budget Touch should sync without issues.

To correct this, open System Preferences > Security > Firewall. Now, add mDNSResponder to the "Set access..." list as follows:

• mDNSResponder resides in a hidden directory. To view this directory, switch to the Finder. From the Go menu, select "Go to Folder..." (or use the keyboard shortcut shift-command-G). When the "Go to Folder" window appears, enter the following path: /usr/sbin
• In the Firewall settings select Set access for specific services and applications
• Click the + button. A sheet with a file choosing dialog appears.
• Drag the mDNSResponder file from finder onto the sheet. (It doesn't matter what's actually pre chosen in the dialog.) The selected folder automatically switches to the sbin folder with the mDNSResponder file selected.
• Click the Add button
• Switch back to Allow all incoming connections

If it still doesn't work (as reported by some users who have a 2wire router), you might have to make the following modifications to your router's settings:

• Set the firewall on the router to allow traffic from mDNSResponder. The port numbers are TCP 5354 and UDP 5353.
• It takes a while for these settings to activate.

Different subnets

Another problem might be that your iPhone/iPod and Mac are on different subnets of the same network. In that case, syncing will not work. This is rather unlikely in small private networks.

Router

Sometimes it helps to simply restart your router. Also, make sure your router has the latest firmware updates installed.

Some users were able to fix the sync issues by checking their router settings. One user reported: "The problem was the WLAN. Using a Zyxel Router we had to *disable* the standard setting under WLAN: Block network traffic between WLAN and WAN."

Other issues

Is there anything special about your network setup that might prevent Budget Touch from communicating through Bonjour? For example, using VPN?

Isolating the issue & workaround

Create a computer-to-computer ad hoc network to isolate the issue. If syncing works via computer-to-computer, it's likely something on your network. If it doesn't, it's likely a firewall/computer configuration issue.