Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to get Macsd to register on DNS 3

Status
Not open for further replies.

sebjenkins

Technical User
Jan 8, 2003
164
GB
Hi,

We have a mixed network or Windows 2000 PCs and Macs running OSX 10.3 and OSX 10.4

Apparently at the moment, the Macs on our network do not register on the DNS server.

I read that this may be because the Sharing PrefPane should be the same as the DHCP client field. The DHCP client field was empty so I filled it in the same as the Sharing one but no joy.
Whats more is that I can't seem to ping any Mac by its sharing name or even with the DNS suffix that the PCs seem to use either.
Whats more the Sharing name is different to the one displayed in 'Terminal'.
Also when looking at computer lists in Apple Remote Desktop 3, the DNS names next to each machine do not even tally up with the Sharing name.

Can anyone advise on getting these Macs registered on the DNS server and pinging them by name. They do of course ping by IP address.

I'm hoping that someone is not goin to tell me the only way to achieve this is by binding them to the AD ??!!

Many thanks in advance.
 
Well, the MAC can't be a memeber of the domain so you don't have to worry about someone telling you that.

If the Mac's are DHCP clients and you are using MS DHCP server, there is an option to "Dynamically update DNS A and PTR records for DHCP clients that do not request updates(for example, clients running Windows NT 4.0)."
That would be the first thing I would check. Confirm the option is enabled.
The option is located on the properties of the DHCP server within the DHCP mmc. Look under the DNS tab of the properties page.
 
WhoKilledKenny, thanks so much for your suggestion, I can confirm that turning this option on, now allows us to ping our Macs by their hostnames.
Along with filling in the Macs DHCP client id field in both the DHCP and DNS servers are happy.
Hoorah!!

Thanks again for this valuable advice.
 
Well, the MAC can't be a memeber of the domain so you don't have to worry about someone telling you that."

Macs CAN be a member of the domain. Our people are using their AD credentials to login to their macs.
 
Indeed, as can Linux machines. Times change.

Carlsberg don't run I.T departments, but if they did they'd probably be more fun.
 
Macs CAN be a member of the domain. Our people are using their AD credentials to login to their macs.

Guys,
You can use your AD credentials on Win9x as well; still the Win9x, MAC, and Linux machines can not be members of an AD Domain. Meaning, they don't have computer accounts in AD.
 
WhoKilledKenny:

Actually, the computers to have machine accounts in the ADUC.

When binding Mac OSX to the Domain to allow for unified login a machine account is indeed created. In the ADUC under computers, I can select a mac it is listed as Role: Workstation, under the OS tab, I can see what version and build the computer was at the time of binding. Has a canonical name and everything.




Robert Liebsch
Systems Psychologist,
Network Sociologist,
Security Pathologist,
User Therapist.
 
The only thing I have problems with is that after changing the AD password (also on the mac!), the login keychain isnt updated.
 
New bug we've noticed here.

THe keychain has to be reset each time they reset their password.



Robert Liebsch
Systems Psychologist,
Network Sociologist,
Security Pathologist,
User Therapist.
 
PS, star for Kenny. DNS issues cleared up allowing Mac to register DNS.

management just got a little easier!


Robert Liebsch
Systems Psychologist,
Network Sociologist,
Security Pathologist,
User Therapist.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top