Help w/ multiple interfaces + AD DNS

[aristobrat]

If anyone has run into this before, I’d appreciate any advice/comments. 🙂

The issue that we’re having is that our Mac users can’t connect to each other.

The Macs are all Mac Pros running 10.5.5 + VMWare Fusion 2.0

VMWare Fusion adds two virtual interfaces [vmnet1, vmnet8] to each Mac. Each of these virtual interfaces has a non-routable IP address (172.16.x.x and 192.168.x.x).

When the Macs boot up, they’re registering en0 + the two vmnet interfaces with our Active Directory DNS.

So … when you try to resolve a Macs DNS name, you’re more likely to get a vmnet IP address back (that can’t be used to communicate between the Macs), not the en0 IP address that we need.

I’ve tried the suggestion listed in the ‘Mac OS X 10.5 Server: Preventing DDNS registration for multiple interfaces’ article (which is to modify /etc/smb.conf), but it’s not working. When I delete the Macs DNS entries from the DNS servers and reboot the Mac I’m testing with, all three interfaces get re-registered.

http://support.apple.com/kb/HT3169

I’m stumped. If anyone has any advice/suggestions, I’d really appreciate it!

Thanks!

Jason

[joshtidsbury]

I’d just like to bump this one as I’m in exactly the same predicament. I tried the smb.conf adjustments suggested in the KB article, but that didn’t solve the issue.

I’d be shocked if there wasn’t some plist/dameon running in the background to do the DDNS updates, but I’m stumped on where it might be located and how to prevent the additional interfaces from registering…

Thoughts?

Many thanks,
Josh

[rgrant]

We are having the same problem also, applying the Kb fix also didn’t have any effect/

Rich Grant
Colgate University

[rgrant]

Yes I’ve tried specifying the mask but still no luck

[Author]

Posts