[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 553
  • Last Modified:

Mac cannot ping another network segment

This machine was bound to AD domain. For no apparent reason, it can no longer ping other network segments. The DC and DNS servers are of course on a different segment. It can ping the gateway, but not any next hop. IP address comes from DHCP, which is located on its network segment. All other PCs and Macs on this segment can access all of the network resources. This machine was just rebuilt and is running Snow Leopard 10.6.3 with all of the most recent updates.
1 Solution
Before rebuilding it did you remove it from AD and then rebind?  If not, you might try unbinding it, rebooting and then rebinding it.  Also, check every setting in Network system preferences and security system preferences against another Mac that works OK.
I believe you have got a corrupted routing table or something (switch/firewall/router) is blocking your packets. I don't think that anything of AD except of Security settings could be in a charge here
ksepcitAuthor Commented:
I realized that I had configured two gateways - one on each NIC. I deleted the gateway on NIC 1, and everything works now. NIC 1 connects to a network which does not require a gateway.
Thanks for your responses,

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now