Solved

Mac Pro taking another name

Posted on 2011-03-24
9
503 Views
Last Modified: 2012-09-06
I have the following in my workplace:
Windows SBS 2008 server (SERVER)
Windows Server 2008 (used for backup - SERVER-BACKUP) - joined to SBS2008
Multiple Win 7 Prof Desktops & Laptops - connected to SBS2008 by share only
Mac Pro Desktop (OS 10.6.6) (MY NAME) -also running Parallels (Win 7 - joined to SBS2008)

Here is the issue:

For some reason, when looking at the System Logs, I found that the Mac Pro is taking the name SERVER-BACKUP and not MY NAME.  Most of the time this is not a problem, but sometimes Time Machine gets confused and the Mac requires a reboot.  The Mac Pro then sees itself as MY MACHINE for a while. The Mac is a brand new machine.  
The Apple people do not seem too concerned about this issue, but I am very curious about this and would like to know why it is doing this and how to correct the problem.
0
Comment
Question by:jonelr70115
  • 4
  • 3
  • 2
9 Comments
 
LVL 8

Expert Comment

by:Mac2010
ID: 35209753
It looks to me that -assuming the Mac Pro gets network settings using DHCP- the name is pre-defined on the DHCP server. I had something similar once, and the DHCP caused it, as it appeared.
0
 

Author Comment

by:jonelr70115
ID: 35235095
What should be done about it?
0
 
LVL 8

Expert Comment

by:Mac2010
ID: 35238599
Depends on the cause. I suggest you look for a 'computer record' on the DHCP server, if such a record is available and delete or change it. But verify it first. If the Windows server is DHCP server, I can't help you since I rarely work with Windows SBS server.

You can also change the TCP/IP settings from DHCP to manual on the Mac Pro. I'm assuming here that DHCP settings caused the name change. When you change IP settings, also check the computer name in the 'Sharing' section in System Prefrences.
0
 
LVL 3

Expert Comment

by:ilarge
ID: 35261052
This is caused by your Mac talking to the Microsoft DHCP server and is a common problem. The DHCP server will not be scavenging out dead records and so you take an address previously used by a different machine and get its host name.

To fix it on your Mac you can hard code your hostname by opening a terminal window and typing the following command:

sudo scutil --set HostName yourhostname


Reboot and you should be set!

Hope this helps.

Ian
0
Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

 

Author Comment

by:jonelr70115
ID: 35261327
Thanks.  Is the HostName the name of the SBS2008 server (SERVER) and yourHostName the name of the MAC Pro (MYName) or is this saying that the HostName shoud be = to MYName?  Sorry for the seemingly dumb question, but I have never had this occur before.  Thanks for your assistance.
0
 
LVL 3

Accepted Solution

by:
ilarge earned 500 total points
ID: 35266423
Not dumb at all. I should've been clearer. Sorry!

To clarify, the command sets the system setting called "HostName" to yourhostname. The only thing you should change for your computer is what you want to set your computer to be called; MYName in your example. This is purely for your computer and has nothing to do with the SBS machine - other than instead of your Mac taking whatever name the server gives it, it'll say "gimme an address and by the way, my name is MYName". Or computer speak to that effect.  :-)

It'll ask for a password by the way, just in case you've not come across sudo before. That is the password you use to login to your Mac, to confirm you want to run the command as a super user.

Good luck!

Ian
0
 

Author Comment

by:jonelr70115
ID: 35282028
Thanks, I'll try it and let you know what happens
0
 

Author Closing Comment

by:jonelr70115
ID: 35298046
Worked like a charm. Thank you so much for your help in fixing the problem.
0
 
LVL 3

Expert Comment

by:ilarge
ID: 35325596
Excellent news!

I do it as a matter of course with all of our new/rebuilt Macs because we use an AD backend for shared data and login authentication so it is necessary. I've never actually tried using a purely OS X server backend to see if it is a Windows specific issue or just a DNS/DHCP issue; we run a Mac Mini server and I've extended the AD schema to include the Apple systems management extras so both our Macs and the odd Windows clients are all capable of central control.
0

Featured Post

How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

Join & Write a Comment

I work for a company that primarily works with small businesses as their outsourced IT vendor. As such the majority of these customers utilize some version of Small Business Server. Due to the economics of running a small business, many of these cus…
Set up iPhone and iPad email signatures to always send in high-quality HTML with this step-by step guide.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now