Computer name being show as "localhost" when trying to bind to directory

Question

Computer name being show as "localhost" when trying to bind to directory

I am trying to bind my computer (OS 10.4.11) to my server (10.4.11) but each time I go to bind it the computer name is shown as "localhost" rather than the computer's real name. The computer's name is shown as r2.local in the Sharing pane of System Prefs, also confirmed by the output of hostname. I am also getting this in my system log during bootup:

May 5 12:33:52 localhost usbmuxd[66]: usbmuxd-176 built for iTunesNineDot on Sep 24 2009 at 16:11:04, running 32 bit
*May 5 12:33:53 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-000000000000” instead*
*May 5 12:33:53 localhost mDNSResponder: Couldn't read user-specified local hostname; using default “Macintosh-000000000000.local” instead*
May 5 12:33:54 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:64:5e:36
May 5 12:33:54 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:64:5e:37
May 5 12:33:54 localhost mDNSResponder: Adding browse domain local.
May 5 12:33:56 localhost kernel[0]: NVDA,Display-A: vram [90020000:10000000]
May 5 12:33:56 localhost kernel[0]: NVDA,Display-B: vram [00000000:01000000]
May 5 12:34:00 localhost launchd: com.logmein.logmeinserver: exited abnormally: Bus error
May 5 12:34:00 localhost launchd: com.logmein.logmeinserver: 9 more failures without living at least 60 seconds will cause job removal
May 5 12:34:00 localhost launchd: com.logmein.logmeinserver: exited abnormally: Bus error
May 5 12:34:00 localhost launchd: com.logmein.logmeinserver: respawning too quickly! throttling
May 5 12:34:00 localhost launchd: com.logmein.logmeinserver: 8 more failures without living at least 60 seconds will cause job removal
May 5 12:34:00 localhost launchd: com.logmein.logmeinserver: will restart in 10 seconds
May 5 12:34:03 localhost lookupd[97]: lookupd (version 369.8) starting - Wed May 5 12:34:03 2010
May 5 12:34:05 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
*May 5 12:34:05 r2 configd[68]: setting hostname to "r2.local"*
May 5 12:34:07 r2 loginwindow[99]: Login Window Started Security Agent
May 5 12:34:08 r2 kernel[0]: AppleBCM5701Ethernet - en0 link active, 1000-Mbit, full duplex, flow control disabled
May 5 12:34:08 r2 configd[68]: AppleTalk startup
May 5 12:34:10 r2 configd[68]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
May 5 12:34:10 r2 configd[68]: posting notification com.apple.system.config.network_change
May 5 12:34:10 r2 lookupd[110]: lookupd (version 369.8) starting - Wed May 5 12:34:10 2010
May 5 12:34:15 r2 configd[68]: target=enable-network: disabled
*May 5 12:34:16 r2 mDNSResponder: HostnameCallback: Error -65557 for registration of r2. IP 192.168.1.122*
May 5 12:34:16 r2 configd[68]: AppleTalk startup complete

Thoughts?

Mac Pro 8 Core 2.8 GHz, Mac OS X (10.5.6), 6GB RAM - (2x) 500GBx2 Software RAID 0, FCP 5.1.4

Posted on May 5, 2010 10:43 AM

Reply

Answer 1

BDAqua

Level 10

245,633 points

May 5, 2010 11:40 AM in response to Brent Hilgenkamp

Hmmm, not dertain, but might see the last post here for clues...

http://forums.macosxhints.com/archive/index.php/t-34728.html

Reply

Answer 2

May 5, 2010 12:33 PM in response to BDAqua

Not sure if this will apply to me or not. Doing an "echo $HOSTNAME" in terminal responds with the proper computer name. I have never had this problem before but I'm trying to bind 2 computers and they are both having the same problem.

Reply

Answer 3

BDAqua

Level 10

245,633 points

May 5, 2010 12:45 PM in response to Brent Hilgenkamp

Well, from the log, it looks like logmeinserver is failing because it's trying before enable-network is even happening.

Have you tried logging out & back in?

Reply

Answer 4

May 5, 2010 12:47 PM in response to BDAqua

Do you think logmein might be causing any issues?

Yup, multiple login/logouts, restarts, and repair perms.

Reply

Answer 5

BDAqua

Level 10

245,633 points

May 5, 2010 12:50 PM in response to Brent Hilgenkamp

I think there's a good chance, is logmein showing repeated attempts in the Console while booted?

Reply

Answer 6

May 5, 2010 2:18 PM in response to BDAqua

Yeah there are quite a few entries from logmein during bootup. But:

When I unplugged the ethernet from a machine the "mDNSResponder: HostnameCallback: Error -65557 for registration of r2. IP 192.168.1.122" wasn't there. Instead I got this:

May 5 15:59:26 localhost mDNSResponder: Adding browse domain local.
May 5 15:59:28 r2 configd[39]: setting hostname to "r2.local"

With no errors after that. Could there be something on my network causing problems? I do have a Windows server on the network for the PCs here.

Reply

Answer 7

BDAqua

Level 10

245,633 points

May 5, 2010 2:59 PM in response to Brent Hilgenkamp

Hmmm, Bind, did you try using Directory Access in Utilities?

I don't know which versio of the OS has "Directory Utilty", but some clues here maybe...

http://www.makemacwork.com/bind-to-active-directory.htm

Although it's talking about Windows, I thought this at least might help resolve it...

To begin, check the “Network” pane in System Preferences, and be sure that your Windows domain is listed in the “Search Domains” for each interface.

Reply

Answer 8

May 5, 2010 3:26 PM in response to BDAqua

I think Directory Utility is in 10.5+, it's called Directory Access in previous versions (at least in 10.4). I have an OD running on the Mac server that I am trying to bind to, the AD/windows server is just for the PCs.

I did find this though about the mDNSresponder error I'm getting:
(from http://lists.apple.com/archives/bonjour-dev/2005/Aug/msg00020.html)
-65557 means NAT Traversal error. You need to be using a router that
supports NAT-PMP or UPnP if you want to register your hostname
successfully using DNS Update.

I enabled UPnP on my router/firewall but it did not help.

Reply

Answer 9

May 5, 2010 3:40 PM in response to Brent Hilgenkamp

I recently started using the DNS server on the Windows machine instead of the DNS server built into the OS X server. I wonder if that could be part of the problem?

Reply

Answer 10

May 6, 2010 12:15 PM in response to Brent Hilgenkamp

I'm thinking this may be due to the Windows machines having a .local address due to being bound to the Windows domain. Gonna try to see if I can change the domain suffix on the Windows computers to see if this clears up the problems on the Macs.

I also use Qmaster on the computers and the cluster controller normally shares out its storage with an address like nfs://server.local/...... but now that too is using localhost instead of the computer name. Seems it's all got something to do with Bonjour messing up somehow. Will post my results.

Reply

Answer 11

BDAqua

Level 10

245,633 points

May 6, 2010 12:23 PM in response to Brent Hilgenkamp

Did you try adding a local IP or Windows server IP to your DNS lookup?

Reply

Answer 12

May 6, 2010 12:31 PM in response to BDAqua

Yes, the Windows server provides DNS resolution to all the computers on the network here.

Reply

Answer 13

BDAqua

Level 10

245,633 points

May 6, 2010 2:04 PM in response to Brent Hilgenkamp

Try putting those numbers in the Macs... Network>TCP/IP>DNS Servers, for the Interfaces you connect with.

Reply

Answer 14

May 6, 2010 2:06 PM in response to BDAqua

Already did that. The DHCP server hands out the proper DNS server IP for any DHCP connections, but for the Macs I've statically entered the IP information, including the Windows DNS server address.

Reply