Apple Event: May 7th at 7 am PT

How to fix network connectivity issues on iMac

None of my devices connected to my network are seeing any of the other devices.

File sharing is on.


[Re-Titled by Moderator]

Posted on Apr 21, 2024 10:02 AM

Reply
25 replies

Apr 23, 2024 4:26 PM in response to dstar

From the MacBook, enter the following command in the Terminal app: nc -z <IP address of iMacE> 1-1024


The result should like something like the following:



Now enter the same command with iMacW.


For File Sharing, the last two items will be critical. Please post back your results.


You also mentioned that iMacW was connecting to a repeater. You really need to provide us with the exact configuration of your local network, including all of the networking hardware that is being used (that is in addition to the TP-Link.)

Apr 23, 2024 9:09 AM in response to Tesserax

OK, I'm not sure what exactly fixed it. I did a power cycle of the router, but I also noticed that iMacW was connecting to the repeater, and had a weak signal. At any rate the network seems to be all connected again. The only odd thing is that iMacW, MacBook both show the iMacE with a (?) instead of the iMac icon.

Apr 24, 2024 10:41 AM in response to dstar

Ok, the "missing" port that needs to be open is port 139. That port lets two computers establish a connection that is required for Finder to "see" that the iMacE has file sharing enabled.


This may be because, your network is not properly configured to allow for, as a minimum, the IPv6 "link-local" only protocol being enabled ... or it is being blocked.

Apr 22, 2024 11:55 AM in response to dstar

Ok, since you have already renamed your two iMacs, let's concentrate on the network settings on both.


For clarity, I will name the Ethernet-connected iMac, as iMacE, and the wireless-connected one: iMacW.


Let's start with iMacE.

  1. Go to System Settings > Network > Ethernet > Details ... > TCP/IP
  2. Select Renew DHCP Lease.
  3. Give it a few seconds, then check the following settings: Configure IPv4 = Using DHCP. Note the values for IP Address, and Router Address. These addresses should start with one of the following: 192,172, or 10. If, instead, it starts with 169, this Mac is not "seeing" the DHCP server in your TP-Link router.


Next, let's work with iMacW. The steps will be similar to what we did for iMacE:

  1. Go to System Settings > Wi-Fi > Select your Wi-Fi network > Details ... > TCP/IP
  2. Select Renew DHCP Lease.
  3. Give it a few seconds, then check the following settings: Configure IPv4 = Using DHCP. Note the values for IP Address, and Router Address. These addresses should start with one of the following: 192,172, or 10. If, instead, it starts with 169, this Mac is not "seeing" the DHCP server in your TP-Link router.


For both iMacs, the IP Address of each should be in the same IP range. For example, if your TP-Link's DHCP server is serving IP address in the 192.168.0.x range, each Mac should be in the same range, but with a different last octet. The Router Address should be the same for both ... and pointing back to the LAN-side address of the TP-Link.


If all of this is good, I would like for you to use the Ping command in the Terminal to "ping" between these two iMacs to see if there are any issues with them communicating with each other. I would like for you to ping them from both directions. That is, from iMacE to iMacW, and then, from iMacW to iMacE.


To do so, starting with either iMac, run the Terminal app which is located in the /Applications/Utilities folder. At the Terminal's command prompt, enter: ping -c3 <enter the IP address of the other iMac>, and then press return.


A successful ping would have 3 transmitted & 3 pings received with 0% packet loss. Anything else would indicate an issue with your network. Please repeat this from the other iMac.


It should look something like the following:



Please post back your results.

Apr 24, 2024 7:59 AM in response to dstar

Incorrectly-configured subnets when multiple paths (Wi-Fi with intervening routers with mixes of wireless and wired) can cause connectivity issues, and buggy or failing routers (check for router firmware updates) can also cause issues. If there’s more than one Wi-Fi router present (and configured as a router, not as an access point), that can play havoc with connectivity when subnets are not configured. For many such configurations, switching routers over to APs can help. (Some routers can handle Wi-Fi and wired well, others not so much.)


How many IP network routers are present? Just that one TP-Link Archer AC1900?


Or is there another Wi-Fi router, or maybe an ISP IP router/firewall/gateway box involved?


Current firmware for that TP-Link Archer AC1900 is Archer AC1900(USW)_V1.6_1.13.2 Build 230824 from November 2023. (Details). If you’re not running that, update.


Wi-Fi interference can also be a potential issue. The built-in Wi-Fi troubleshooting tools are adequate and have the benefit of being trivial, while tools such as WiFi Explorer app can make troubleshooting shooting easier.


To view the basic Wi-Fi environment characteristics, Option-Click on the Wi-Fi logo 🛜 in the menu bar, and capture some Wi-Fi network data. Post the items shown in the following image including the Security mode and from Channel to NSS inclusive (Security, Channel, Country, RSSI, Noise, Tx Rate, PHY mode, MCS, NSS, green highlight) (without posting the Wi-Fi address, any local HotSpots that might be present, the network name, or the BSSID, all of which are expurgated from the image shown below, red highlight), and we can take a look at the basic network environment.


Apr 21, 2024 1:02 PM in response to dstar

Was this always an issue or just started happening recently?


Regardless, what have you tried, so far yourself, to resolve this so that we don't offer potential solutions that may not have already worked for you?


It would also help if you can provide us with some details about the network that you have all of these devices connected to? Like the make & model of the wireless router or gateway, and how each of these devices are connected to it ... by Ethernet, or wireless, or both.

Apr 21, 2024 1:51 PM in response to Tesserax

I actually used it once today, before it stopped working. I think the problem has something to do with computer names. We just got a new iMac, and both iMacs were named xxx's iMac. However, I have renamed both iMacs to no avail. The MacBook can see both iMacs, but the iMacs don't see anything, unless I connect with the MacBook.

Apr 23, 2024 8:19 AM in response to Tesserax

Yeah, they're not seeing each other.


192.168.0.165 ping statistics ---

3 packets transmitted, 0 packets received, 100.0% packet loss


192.168.0.15 ping statistics ---

3 packets transmitted, 0 packets received, 100.0% packet loss


Strangely the iMacE does see the MacBook, but the MacBook doesn't see the iMacE.

However, the two will connect through the network, but the MacBook shows the iMacE with a giant ?



Apr 23, 2024 8:44 AM in response to dstar

OK, update:

I was entering an incorrect IP. The iMacE and the MacBook can see each other fine, and in the finder do show up under Network. However the MacBook does still show the iMacE with a (?). I have no idea what that means.

The iMacW is not seeing, or being seen. That's not a problem really, since I will be disposing of that machine.

Apr 24, 2024 12:01 PM in response to dstar

IPv6 "Link-local" only would be the minimum setting for all of your network devices, including your router. If they are already configured for IPv6 "Automatically" that will be fine.


... and, if that is the case, I'm not sure what is blocking communications on port 139 on your network. This is why I had asked if any of your Macs have an active software firewall running on them.


... and, if they are all already disabled, I'm not sure what the issue, or solution to offer you without much more extensive network troubleshooting.

How to fix network connectivity issues on iMac

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.