System name changing seemingly on it's own

I have a peculiar problem. My Macbook Air's name seems to be changing on it's own. The name doesn't change in any configuration prompt, but when I open the terminal it ALWAYS takes on the name of another computer on the LAN, regardless of what LAN I join. To clarify, if I go to system preferences, my computer's name is exactly what I named it. If I open a terminal, I get this:
anothercomputersname:~ myname$
I would rate my computer literacy as extremely high - I'm a CentOS geek, I program, I've been in the IT industry for a decade - but I'm at a loss for words on how this could happen or why this would happen. This is my first Apple product.
Possibly useful information:
1) I don't remember this happening before my first experience with LAN filesharing on a Mac. Maybe I messed up a setting there?
2) I can reset the name via the terminal with the following command, if and only if I am not on a network: "sudo scutil --set ComputerName JanetReno" (would change it to JanetReno)
3) This happens regardless of my LAN.
4) I use a very secure password and remote SSH access to my machine is disabled. In other words, I don't think my system is comprimised, but I suppose it's always possible that someone outsmarted me.
5) Using OS X 10.5.6
And finally, I tried googling this but unfortunately all of the relevant search terms are commonly Googled together and don't help my me find my answer.

Try this. Go to the Sharing preference panel. Click the "Edit" button. Deselect the "Use Dynamic Global Hostname" checkbox. Or if it is not select, enable it. That may fix it.

Similar Messages

Logical system name change

Hi all,
Now my BI development is pointing to R/3 development. R/3 logical sytem name is bbbclnt100. Now all my datasources are pointing to this logical system. Our basis people are going to change the logical system of R/3. Please tell me the repercussions? what will happen to my datasources?
Thanks in advance

Anni,
Change logical system name and run BDLS job to adjust. Do not change souce system. If you change source system all transfer rules will get deactivated.
Check: [Conversion of Logical Systems|http://help.sap.com/saphelp_nw70/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm]
Search forum for more links.
Srini

Logical system name changes

All,
Has anyone faced a scenario where you need to change the logical name for any SAP system?
For instance:
System      Logical Name                                                    System      Logical name B
BW                      A                     system is pointing to            ECC                  B
ECC will be upgraded and system name will changed to C
Is that possible? If so do you forsee any issues? Can we switch ECC B to ECC C with no issues?
I appreciate any help.
Regards

Hello Mike,
please elaborate a little more your inquiry. Are you talking about the ALE logical name changing? For this, please check the following notes:
#544509 ALE: Converting the name of the "logical system"
#121163 UTI: Logical System names
If you're referring to a domain name changing (like a Windows domain name change) or a hostname change, please refer to the following notes:
#96317:   Host names during R/3 upgrade, tips & tricks
#1275273: Hostname change on 7.10/7.11 java stacks
#757692: Changing the hostname for J2EE Engine 6.40/7.0 installation
#8307:    Changing host name on R/3 host: What do you do?
#1070561: SMD: Best practice for planned domain name changes
and on the following SDN threads:
/message/9196590#9196590 [original link is broken]
Re: Domain name change
Re: Change the Domain Controller
How to change hostname
Change Domain Controller
Or, lastly, you're talking about a SID change? On this case, you must perform a system copy to change de SID, please refer to the following note:
#11692: Renaming the system ID
(Sorry for the long and generic answer)
I hope this information helps.
Best regards,
Tomas Black

Logical System Name changing

Dear Team,
We had upgraded BI system from 3.0B to BI 7.0. At the time of upgrade dev
copy(shadow system) logical system was not changed because most of the data is coming from ETL. Now we want to test the extraction from R/3 Dev.
R/3 Dev is already connectwed to BW dev 3.0B, Now we need to test
extraction from R/3 Dev to BW dev copy server( NW2004SR1 ).
Here we are facing a problem with Logical system. While upgrading the
same logical sys was copied to BW dev copy.
What is the procedure to change the existing logical system name in BW
dev copy and establish connectivity with R/3 dev?
what is the impact if we run BDLS transaction.
Thanks& Regards,
Satish.K.Neni

Hi Satish,
Go to transaction SALE -> Basic settings -> Logical systems -> execute "Define logical system" to create a new logical system -> then execute "Assign Logical System to Client"
That should solve your problem
Regards
Juan
Please reward with points if helpful

Logical system Name Change Via Transport

Hi All,
Recently we made changes in parallel processing profile customizing table (/SAPAPO/SDP_PAR) and created entries for Macro Jobs and CIF.
For Application "CIF Delta Report", Logical system is mandatory and in Dev we gave the APO Dev Logical System Name (AD1XXX). Now when we moved the changes to Quality, expectation was that Logical system name for CIF Entry in the table would change to AQ1XXX - However, it still shows as AD1XXX there. Moreover AD1XXX entry is not a valid entry in Quality System and even when we see Drop Down values for that column (Press F4) - Only APO and ECC Quality systems names are appearing.
Please suggest how can this logical system name be corrected. One option is running BDLS, but when this TR moves to Production there also we might end up in same scenario (Logical system as AD1XXX instead of AP1XXX) and running BDLS in Production wont be approved.
Please suggest if there is any other option to handle this.
Regards,
Alok

Hi Alok,
we describe a solution in our
SAP Rapid Deployment Solutions (RDS)
Quick Link
                Access SAP Rapid Deployment Solutions (RDS) directly via
                  http://service.sap.com/rds
SAP Demand and Supply Network Planning rapid-deployment solution
Quick Link
    Access this area directly via
http://service.sap.com
/rds-dpa
In confgiguration guide
Central Master Data Replication (SCO)
you can read how it is done with
Create Entries in Table
TVARVC for Logical System Variable in Variants
Frank

SLD Logical System Name Changes not taking effect in IDOC

All -
I've had to change a logical system name in the SLD, everything appears to be okay but new Idocs are still posting with the old LS name - any suggestions as to where to look for the old name would be most appreciated.
Thanks!

Hi Dennis,
After changing the logical system name in SLD have you done "Compare with SLD" from Service --> "Adapter-Specific Identifiers" for Business system in Integration Directory?
- Pinkle

Mac's name changed to "machinename" on its own

Hi all,
Ever since I got my Mac Pro at work it's been called njintelmacpro. The other day, out of the blue, it's called machinename. In the sharing system preference I get this:
Other Macintosh users can access your computer at afp://10.32.53.127/
and then a second later it changes to:
Other Macintosh users can access your computer at afp://machinename/
The name in the Sharing System Preference is njintelmacpro!!
From the same dialog:
Other computers on your local subnet can access your computer at njintelmacpro.local
When I do a "set" in Terminal I get this:
HOSTNAME=machinename
Now, how is it that the Sharing System Preference says njintelmacpro but the name of the machine is "machinename"? It's driving me nuts.
Is it getting the name from somewhere else? Thanks.

Not sure of this of course, but I think something is kicking out a process, then it come back with the default when it can't read/do whatever it is... logs may show something.
Might try logging out and back in to see if it changes... or create a new user for a test.
At this point I think you should get Applejack...
http://www.versiontracker.com/dyn/moreinfo/macosx/19596
After installing, reboot holding down CMD+s, then when the prompt shows, type in...
applejack AUTO
Then let it do all 5 of it's things.
At least it'll eliminate some questions if it doesn't fix it.

System name change

I recently purchased an 'ex-demo' iMac, and I can't change the name of who it belongs to in the 'system profiler' etc. I need to change it because I think it's screwing with my 'AppleCare' registration! Besides that I'm starting to find it rather annoying.
Do I need to reformat the machine and start all over again, or is there a simpler way?

just in case you mean the +short username+ (home folder name), click here for information.
JGG

Changing logical system name on ECC

Hi,
We have made copy of production to our test environment. Next, we created a number of copies of the test environment. We now want to hook the copies up to BI, XI etc. where we don't have multiple test environments, which means that a single BI test instance will support several ECC test instances as an example. This means that our ECC instances will have to have their logical system name changes changed in addition to the obvious SID change. We have a fairly comprehensive landscape with GRC, XRPM, BI, SolMan, CRM connected to our ECC instance. What areas of concern would you consider important to test once the logical system name changes are done? We are looking at the ALE, RFC connections, BI connections. We included the [help.sap.com information |http://help.sap.com/saphelp_nw04/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/content.htm] in our thinking, but since that did not really explore landscape wide issues....
Thank you,
Mike

Hi
As prelim checks:
Check if these changes are maintained in SCC4 client details as well, and check if all the RFCs are working fine.
Regards
Rahul

Conversion of source system names

Hello Experts,
After having some transport problem (transporting infopackages), I notice that the source system mapping is not the same in DEV compared to PRD.
Other than change log which was not turned on, is there any other way I can find out who or when was the last change to this mapping table?
Am I right to say the mapping entries should exist in all systems? My DEV currently only has 1 entry compared to 6 entries in QAS and PRD.
The source system underwhich the infopackage resides is not shown in the DEV source system mapping table.
Is this the cause of my transport problem?
Regards,
Mirella Russo

Dear Experts,
Thanks for the useful information. Points awarded.
Am I right to say that mapping in target system cannot be transported and is set directly in target system QAS, PRD via RSA1 and no mapping is required even if there are other source systems, like flat file source systems, when the source system name is to be the same in all systems? In this case, my source system is a flatfile. Does this mean I need not maintain it? The 'no mapping' warning received in transport log shows that the flatfile source system concerned exists in the target system but no mapping. As I do not need source system name change, can I say I need not maintain in the mapping table? I still cannot understand why the error come about.
Many thank you in advance.
Regards,
Mirella Russo

Changing Logical System Names

Currently, each instance(SID) in an entire landscape all have the same logical system name and the RFC name that corresponds is all the same. You really don't know what system the RFC is pointing to until you open it up and see which server, etc. is listed in the RFC. So, we are working on a project so that each instance has it's own unique logical system name. The biggest problem we are concerned about is making sure that we change all the places where these definitions exist. I have a small list of transactions that need these items changed (SM59, SALE, SCC4, RSA1, SMQR, SMQS, SBIW, SPRO (this is a tough one)). We realize we will depend on our application teams heavily to know where they changed any configuration to use logical systems. My question is to see if anybody has done this type of change, if they have any tips/guidance, to see if anybody can give some good direction on where to find all the places these LS names are used, and if anybody else can throw out any other transaction suggestions that we should check. Thanks in advance.
-Marsha

Marsha,
I think you should examine the reasons why it would not work before asking if you can do it. One reason for us was archiving. We regularly archive off data only keeping the last 3-7 years of data in the system for some tables. Changing the logical system ID for us would mean it would be impossible to reload some of that archived data, without customizing or a new development effort.
So if your questions is can you do it? Yes, you can do it.
If the question is should you do it? .....Well, then you need to examine why or why not in your own environment. There are likely to be pitfalls especially if its usage is widespread at your company as you indicate.
-jwise

"Macintosh HD" name changed on its own, is this a virus?

Hey everybody,
for some unknown reason my Macintosh HD in the finder and on my desktop changed names from "Macintosh HD" to "are you gone now". There is no possible way I did this, and no one else had used my computer. Everything else seems normal, but I was concerned that this could be a virus or something. I have not heard of any serious Mac OSX viruses before, so I am hoping this is some random thing. I am running latest version of Leopard, and the name change occurred on May 13. Has anyone else experienced this?
Thanks for the help

It sounds as if the MBA user has been using his Mac foolishly, by downloading applications from a p2p service. That is a very high risk activity that will compromise any computer's security. I don't know if your Mac could have become infected through the MBA. It seems unlikely, but I can think of no other explanation.
Back up all your user files. Time machine should be fine for this, but a simple drag & drop of all your documents to a burned DVD or external drive would be easy too.
Then completely reformat and reinstall everything from scratch on both computers. Reinstall your third party apps from the original CDs or fresh downloads only. DO NOT restore any applications or system components from your backups, unless you are 100% sure you are retrieving them from a backup made before the intrusion began. Only recover your personal data from backups.
Change all your passwords. Don't use the admin account for anything except tasks that really need it (of which there are very, very few.)
Make sure the MBA user gets a lesson in safe computing. NEVER download any software from a p2p service.
Are you absoutely certain that the MBA user is not playing a practical joke on you?

JDBC to Idoc scenario - change of logical system name

Hi,
I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
Did i miss something resp. how can i load the current configuration from SLD?
Thanks in advance
Michael

Hi Michael,
Again Import the changed logical system in the Integration directory of you PI system.
And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
If they are showing old system then you have to replace the business system in all the scenario.
Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

Logical system name has been changed for this system

Hi gurus,
I am fasing problem in BI7 system. we created a new client in the system & want to set it for BI development.
System Response
The transaction is canceled.
Procedure
Change the name of the logical system (table T000) for client back to BID500. This enables you to continue working with the system.
If you really want to change the logical name, than you can, if and when you:
change the system name back to BID500,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow.
Regards,
Darshan..

Sorry, BI is a one client system. You cannot have a prod client and a dev client within one SAP system.
But...
...NO, you can't!
Best regards
Michael
EDIT: just to add, there is an exception if you have a SCM/APO type system [522569 - BW: Working in several clients (especially APO 4.x/SCM 4.x)|https://service.sap.com/sap/bc/bsp/spn/sapnotes/index2.htm?numm=522569]

How to change or rename the logical system name T90CLNT090 IN BI 7

HI Expert's,
i am really digging for the solution of changing or renaming the logical system name technical name T90CLNT090.
in our company we are using ecc5.0 with bi 3.5 and ecc6 with bi 7. In BW 3.5 having a connection with R/3 and the technical name of the myself bw source system(logical system) is T90CLNT090.
In bi 7 also the logical system name is same as T90CLNT090. Because of the same system name(Logical name) it is not active in BI7 and also it's giving error when i am activating the DSO Object as Transfer structure prefix for source system T90CLNT090 is not defined.
because of this i am not able to create the source system between r/3 also.
so how to change this source system name for T90CLNT090.
regards
harikrishna N

Hi,
Pls follow this OSS note : 325525.
Note 325525 - Copying and renaming systems in a BW environment
Summary
Symptom WARNING: THIS NOTE HAS BEEN REPLACED. FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
Other terms BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
Solution Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
           Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
           Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
           Reactivate all partner agreements that carry the new logical system name after renaming.
Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
           Solution scenario 2):
If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                    Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                    Reactivate all partner agreements that carry the new logical system name after renaming.
Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
Scenario 3) You want to copy a single BW system of the group by database copy.
Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                     Solution scenario 3)b): See Note 184754.
Scenario 4) You want to copy a single source system of the group by database copy.
Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                     Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
           Solution scenario 4)b): See Note 184322.
Scenario 5) You want to import a client copy in a source system.
           Solution scenario 5): See Note 325470.
Thanks & Regards,
Suchitra.V

System name changing seemingly on it's own

Similar Messages

Maybe you are looking for