🛜 What to Do When MetaGrid Pro Can’t Find Your Mac (WiFi)

WiFi connectivity can be tricky. While MetaGrid Pro is designed to seamlessly connect to your Mac via MetaServer, there can be times when your iPad and Mac don’t want to play nicely. Connectivity issues can arise due to various reasons—network configurations, interference, software settings, or simply the quirks of WiFi networks themselves.

We understand how frustrating this can be, especially when you’re in the middle of a project. That’s why this post is here: to collect tried-and-tested solutions from real users, along with practical steps to troubleshoot and resolve connection problems.

Below, you’ll find a curated list of solutions that have worked for others in the MetaGrid Pro community. These include tips for configuring your network, tweaking settings, and overcoming common connectivity hurdles. If you’ve faced a similar issue and have a solution to share, we’d love to hear from you—feel free to contribute your insights!

Let’s make this a go-to resource for keeping your MetaGrid Pro and Mac in sync. After all, a connected workflow is a productive workflow! :control_knobs::sparkles:

Check Local Network Settings

One of the first things to check if MetaGrid Pro can’t connect to your Mac is the Local Network settings.

Go to System Settings > Privacy & Security > Local Network and ensure that MetaServer is listed and enabled.

Typically, macOS will prompt you to enable network access for MetaServer the first time you run it. However, it’s not uncommon for this setting to get disabled—especially after a MetaServer or macOS update. If MetaServer isn’t enabled here, MetaGrid Pro won’t be able to communicate with your Mac.

Double-check this setting, toggle it on if needed, and give it another go. Often, this simple fix can restore the connection!

Test Network Connectivity Options

MetaServer offers flexible network settings to help ensure smooth communication with MetaGrid Pro over WiFi. If you’re having trouble connecting, adjusting these settings could make a difference. Here’s how:

  1. Open MetaServer > Setup… > Network on your Mac.

  2. You’ll see two key options:

• Enable IPv6: This allows MetaServer to use IPv6, the modern version of the internet protocol. IPv6 can sometimes resolve issues on networks that prioritize or require it for communication.

• Enable TCP: By default, MetaServer uses UDP, a faster but less reliable method for sending data. Enabling TCP switches to a more reliable connection type, ensuring all data packets are delivered correctly—though it may be slightly slower.

What’s the difference between TCP and UDP?

• UDP (default): Think of it as sending postcards. It’s fast and efficient but doesn’t confirm delivery. Perfect when speed matters, but occasionally some data might not arrive.

• TCP: Think of it as sending registered mail. Each piece of data is tracked to ensure it reaches its destination, making it more reliable but a little slower.

What to Do:

  1. Try toggling Enable IPv6 on or off.

  2. Switch between TCP and UDP.

  3. After making changes, relaunch MetaServer and try connecting MetaGrid Pro again.

By experimenting with these settings, you can often find the configuration that works best for your network.

Check if MetaServer is Blocked by Antivirus or Anti-Malware Software

Sometimes MetaServer may be blocked by antivirus, anti-malware software, or even macOS’s built-in firewall, preventing it from connecting to MetaGrid Pro. Here’s how to identify and resolve this issue:

Why MetaServer Might Be Blocked

Security software monitors your system to prevent unauthorized network access. MetaServer communicates over your local network, and this can sometimes trigger a false alarm, especially after updates to MetaServer, macOS, or your security software.

Steps to Check and Resolve the Issue

  1. For macOS Firewall:

• Go to System Settings > Privacy & Security > Firewall.

• Ensure the firewall is turned on.

• Click Options or Firewall Options (depending on your macOS version).

• Look for MetaServer in the list of apps. If it’s listed, ensure that it’s set to Allow Incoming Connections.

• If MetaServer isn’t listed, click the + button, find MetaServer in your Applications folder, and add it to the list with incoming connections allowed.

  1. For Antivirus or Anti-Malware Software:

• Open the settings of your antivirus or anti-malware application.

• Check sections like Blocked Apps, Firewall, or Quarantine.

• Search for MetaServer and, if blocked, add it to the trusted or allowed list (also called “whitelisting”).

• Make sure that both incoming and outgoing network connections for MetaServer are permitted.

  1. Restart and Test:

• After making changes, restart MetaServer, MetaGrid Pro, and, if necessary, your Mac.

• Try reconnecting MetaGrid Pro to your Mac.

  1. Temporarily Disable Security Software for Testing (Optional):

• Temporarily turn off your antivirus or firewall to see if the issue persists. If MetaGrid Pro connects successfully, you’ll know the software is the source of the block.

By ensuring that MetaServer is allowed through your security settings, you can restore connectivity and keep your workflow uninterrupted.