Member Avatar for jmflint

I'm at a loss. I have a Windows network (4 PC's plus 3 Macs). My Windows PCs all see each other and the Macs and successfully connect. One of my MBP (13") sees all Windows PCs and Macs. The other MBP (17") sees all but ONE of the Windows PCs (and the one it won't connect to is the only one that is critical -- of course).

I get the error "Connection Failed: The server "name" may not exist or it is unavailable..." I have tried everything I've found on the 'net as far as troubleshooting. All the settings on the Windows PC are good (no Firewall) and, as I said, everything else on the network can connect to it. I've tried deleting all the plist files related to the Airport, nothing. I even tried directly connecting via Ethernet (that made things worse -- I couldn't connect with ANY of the computers).

I am resorting to sneakernet to copy files between these two computers and I'm losing it.

Any help?

TIA.
JMFlint

  • 3 Contributors
  • 4 Replies
  • 214 Views
  • 4 Weeks Discussion Span
  • Latest Post Latest Post by tje210

Dani AI

Generated

Quick diagnosis and a focused set of steps to try (built on 's ping suggestion and noting that already removed AirPort plists and briefly tried Ethernet):

Start with basic reachability from the problematic MBP. In Terminal run:

ping -c 4 192.168.x.y
traceroute 192.168.x.y
arp -a | grep 192.168.x.y
ifconfig

Confirm the MBP actually has an IP on the same subnet as the Windows PC and that ping/ARP show the Windows machine. If ping succeeds but Finder still gives the “server may not exist” error, the problem is name resolution or SMB auth; if ping fails, the problem is lower-level networking (IP, routes, duplicate IPs, VLANs, VPNs or a blocking appliance).

If reachability is OK, connect explicitly by IP from Finder: Cmd+K -> smb://192.168.x.y/ShareName (or smb://username@192.168.x.y/ShareName). Clear any stored credentials in Keychain Access (search for the server name) and flush the Mac DNS cache:

sudo dscacheutil -flushcache
# on very old Mac OS X try: sudo lookupd -flushcache

On the Mac: create a new Network Location (System Preferences > Network > Location > Edit Locations > +) and disable any VPNs or third‑party firewalls (Little Snitch, etc.). Check Network > Advanced > WINS to make sure the Workgroup matches the Windows machine.

On the Windows side confirm Network Discovery and File and Printer Sharing are enabled, the network is set to Home/Private (not Public), the Server service and TCP/IP NetBIOS Helper are running, and no security product is blocking SMB. Verify share permissions and NTFS permissions include the account being used.

If nothing else works, try a safe reset of Mac network preferences (backup first):

sudo cp -a /Library/Preferences/SystemConfiguration /tmp/SysConfigBackup
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist \
        /Library/Preferences/SystemConfiguration/preferences.plist
(reboot)

Also test from a new macOS user account on the same machine to rule out user‑level Keychain/profile corruption. If those steps still fail while other machines can connect to that Windows PC, the issue is almost certainly a local configuration on the problematic MBP (network profile, credentials, or a blocking app).

Recommended Answers

All 4 Replies

Member Avatar for freshfitz

Are you using the ip address or dns name? Can you ping it

Member Avatar for jmflint

I've tried both IP Address and DNS. I don't know how to ping it -- can you assist? Thanks!

Member Avatar for freshfitz

Open terminal type ping and the ip address of the machine you want to connect to

Member Avatar for tje210

have you got this resolved yet? if not, pm me...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.