Solved

The hostname of our Mac OSX server may have spontaneously changed.

Posted on 2015-02-17
5
64 Views
Last Modified: 2016-06-12
After a recent round up of updates to our Mac OSX 10.9 server operating system,  we are finding that the server is acting strangely.  It seems as if the name of the server has changed. During the update,  a dialog box appeared and then disappeared so fast that it was difficult to tell what it was.  We think it gave us a choice of using an existing machine name or using an outside domain.  It flashed by so fast that we didn't have a chance to really examine it.

Now when we examine the local host name, the local host name is now server.local whereas prior to the update it was ourserver.ourdomain.com.  When we open the advanced user settings for a user that was created before the update the home directory is specified as /Network/Servers/ourdomain.ourserver.com/Volumes/PROMISE PEGASUS/Network Home Folders/username.  For users created since the update the home directory is specified as /users/username.

Can anyone explain what may have happened and provide some guidance on what the next steps should be.

Thanks.
0
Comment
Question by:sswmoore
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 30

Accepted Solution

by:
serialband earned 500 total points
ID: 40616801
What is your hostname as shown in Preferences --> Sharing?

What is your hostname when you type hostname in Terminal.app?

What do you get with the following? Do they match?
sudo scutil --get ComputerName
sudo scutil --get LocalHostName
sudo scutil --get HostName

Open in new window


If they don't match, you can set them.
sudo scutil --set ComputerName "newname"
sudo scutil --set LocalHostName "newname"
sudo scutil --set HostName "newname"

Open in new window

0
 

Author Comment

by:sswmoore
ID: 40655137
Thank You Serialbrand for your respone.  Sorry it took me so long to get back to you.

The computer name in sharing  -- prefrences is BLC Server.  The computer name when we use the --get ComputerName command is also BLC Server.

When we use the --get LocalHostName command we get
 
server


And when we use the  --get  HostName command we get

server.local


When we select a user account in the Server app and choose advanced options we see that the home directory is /Network/Server/blcserver.ourdomain.com/Volumes……….

If I go to a Mac workstation I see under Users & Groups---Login--Options that the Network Account Server reads blcserver.ourdomain.com

I suspect that before the OSX Server upgrade routine ran, the the computer and local host names were blcserver, and the host name was blcserver.ourdomain.com

Currently the office is functional and users are able to connect to the server for the most part but there are a number of idiosyncrasies.

I would like to try the method you described to change the names back.  Do you think it is safe?  Might there be any unintended consequences in changing the names back to what they were?  Thanks
0
 
LVL 30

Expert Comment

by:serialband
ID: 40655219
Those are safe to change.  If you're worried, note the names in each entry and you can change it back.
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Connectivity using SMB Symptoms When connecting to Windows Server shares from a Mac you receive an error similar to "Connection failed because the original item could not be found"Authentication persistently fails to a Windows Server from a Mac wi…
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

622 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