Full Qualified Domain Name (FQDN) doesn't work when try to login in portal

I Install a NetWeaver 7.0 with BI JAVA
SP15
I try to login in portal with 3 diferent ways:
1) - With IP I can login but I can't see any objects;
2) - With only hostname without domain I can login I see objects, every thing works fine.
3) - With FQDN I can't login. I don't get any error. It refreh again the login page, and ask again the user and pass.
I could always login with only the hostname, but the problem is that all links are generated with FQDN.
This is the error that is in Security.log:
#1.5 #0050568F3C72005B0000026A00000B000004555928D4E3E7#1219741332358#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#SAP_BASIS#5575##slmqlsbi1.lm.pt_BIP_3925050#Guest#abd12770734d11dd889a0050568f3c72#SAPEngine_Application_Thread[impl:3]_4##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###SAP_BASIS     | LOGIN.OK     | USER.R3_DATASOURCE.SAP_BASIS     |      | IP Address=[192.168.4.4]#
#1.5 #0050568F3C72005F000014BF00000B000004555928F31063#1219741334343#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5576##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C720075000005CA00000B00000455592934EDEE#1219741338656#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#SAP_BASIS#5577##slmqlsbi1.lm.pt_BIP_3925050#Guest#af8afb20734d11ddc4230050568f3c72#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SAP_BASIS
Authentication Stack: ticket
Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
Central Checks                                                                                true                  #
#1.5 #0050568F3C720075000005CB00000B00000455592934F1FE#1219741338656#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#SAP_BASIS#5577##slmqlsbi1.lm.pt_BIP_3925050#Guest#af8afb20734d11ddc4230050568f3c72#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###SAP_BASIS     | LOGIN.OK     | USER.R3_DATASOURCE.SAP_BASIS     |      | IP Address=[192.168.4.4]#
#1.5 #0050568F3C72005F000014C000000B0000045559298BC213#1219741344346#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5578##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72005F000014C100000B00000455592A2466F9#1219741354348#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#5579##n/a##28fb55a072da11dd9b760050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
Can you tell me why I can't login in portal with FQDN?
Best regards,
Filipe Sacadura Botte
Edited by: Filipe Sacadura Botte on Aug 26, 2008 11:03 AM

I have all that configured:
File host:
IP host FQDN
File Security.log
#1.5 #0050568F3C72006D000002C700000E580004556D63F80A15#1219828223462#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7764##slmqlsbi1_BIP_3925050#Guest#fae2cba0741711dd91c40050568f3c72#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN     | LOGIN.OK     | USER.R3_DATASOURCE.J2EE_ADMIN     |      | IP Address=[10.131.224.205]#
#1.5 #0050568F3C72006300001DB400000E580004556D64287F5C#1219828226635#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7765##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72006300001DB500000E580004556D64C1226C#1219828236635#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7766##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C720076000000E400000E580004556D64CDE4A3#1219828237479#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7767##slmqlsbi1_BIP_3925050#Guest#034bcf80741811dd8c500050568f3c72#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: J2EE_ADMIN
Authentication Stack: ticket
Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
Central Checks                                                                                true                  #
#1.5 #0050568F3C720076000000E500000E580004556D64CDE766#1219828237479#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7767##slmqlsbi1_BIP_3925050#Guest#034bcf80741811dd8c500050568f3c72#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN     | LOGIN.OK     | USER.R3_DATASOURCE.J2EE_ADMIN     |      | IP Address=[10.131.227.30]#
#1.5 #0050568F3C720078000000D100000E580004556D653EF26F#1219828244886#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7768##slmqlsbi1_BIP_3925050#Guest#07b14c80741811dd94540050568f3c72#SAPEngine_Application_Thread[impl:3]_18##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: J2EE_ADMIN
Authentication Stack: ticket
Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
Central Checks                                                                                true                  #
#1.5 #0050568F3C720078000000D200000E580004556D653EF5CD#1219828244886#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7768##slmqlsbi1_BIP_3925050#Guest#07b14c80741811dd94540050568f3c72#SAPEngine_Application_Thread[impl:3]_18##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN     | LOGIN.OK     | USER.R3_DATASOURCE.J2EE_ADMIN     |      | IP Address=[10.131.227.30]#
#1.5 #0050568F3C72006300001DB600000E580004556D6559DF5B#1219828246652#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7769##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72007A0000016C00000E580004556D659A15BF#1219828250856#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_ADMIN#7770##slmqlsbi1_BIP_3925050#Guest#0b36a2b0741811dd8eeb0050568f3c72#SAPEngine_Application_Thread[impl:3]_22##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: J2EE_ADMIN
Authentication Stack: ticket
Login Module                                                               Flag        Initialize  Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false                
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true                 
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true                 
Central Checks                                                                                true                  #
#1.5 #0050568F3C72007A0000016D00000E580004556D659A18AF#1219828250856#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#J2EE_ADMIN#7770##slmqlsbi1_BIP_3925050#Guest#0b36a2b0741811dd8eeb0050568f3c72#SAPEngine_Application_Thread[impl:3]_22##0#0#Info#1#com.sap.security.core.util.SecurityAudit#Plain###J2EE_ADMIN     | LOGIN.OK     | USER.R3_DATASOURCE.J2EE_ADMIN     |      | IP Address=[10.131.227.30]#
#1.5 #0050568F3C72006300001DB700000E580004556D65F28856#1219828256653#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7771##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72006300001DB800000E580004556D668B39B0#1219828266654#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7772##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72006300001DB900000E580004556D6723CECE#1219828276655#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7773##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72006300001DBA00000E580004556D67BC791B#1219828286656#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7774##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72006300001DBB00000E580004556D685513CD#1219828296657#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7775##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72006300001DBC00000E580004556D68EDBF58#1219828306673#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7776##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
#1.5 #0050568F3C72006300001DBD00000E580004556D69865801#1219828316674#/System/Security/Audit/J2EE#sap.com/irj#com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_GUEST#7777##n/a##e398c660736e11dda4c50050568f3c72#Thread[Thread-50,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.sap.engine.services.security.roles.SecurityRoleImpl#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.OK#SAP-J2EE-Engine#guests#
files std_server0.out and defaultTrace don't have any error.

Similar Messages

  • Fully Qualified Domain Names (FQDN) error - How to get domain and extension

    I have created a Web Dynpro ABAP application. On executing it, I get Fully Qualified Domain Names (FQDN) error. I have host name of my server.
    I do not know domain name and extension name of my server. How can I detect it?
    I want to know in  Windows XP and Windows 7.
    Please help me asap.

    Hello,
    Right click on the my computer and click properties and then go to the tab computer name .
    there you will have full computer name and this should have your host name as well as the domain name.
    to check the domain name click on change a new popup will open ther domain will be metntioned.
    IF nothing is ther in the domain then add just .(dot) at the end of the computer name .
    and save it and then put the same name in the  ICM/host_name_full parameter in rz11 and try .
    thanks
    sarbjeet
    Edited by: sarbjeet  singh on Jan 23, 2011 10:26 AM

  • Web Dynpro ABAP application  - Fully Qualified Domain Names (FQDN) error

    I have created a Web Dynpro ABAP application. On executing it, I get Fully Qualified Domain Names (FQDN) error. I have host name of my server.
    I do not know domain name of my server. How can I detect it?
    I want to know in  Windows XP and Windows 7.
    Please help me asap.

    Hi,
    On your server run command ipconfig /all
    FQDN = Hostname + Primary DNS Suffix
    The make sure the profile parameters SAPLOCALHOSTFULL and icm/host_name_full reflect the same.
    Regards,
    Srikishan

  • Launch JNLP file which required full-qualified domain name

    Hi all,
    My suitation is like this:
    I need to launch an JNLP file which I need a domain name in order to access it: (using JDK 1.5.0_11)
    e.g. http://hostname.domain.domain/xxx/yyy/zzz.jnlp
    But when it try to access one of the jar file, it will refer to http://hostname/aaa.jar that lead to UnknownHostException.
    Note: (I already use the full domain name to launch the JNLP file..)
    Any one have idea on what to do? And I have no option to change the network setting to support solely "hostname" without domain.
    Here's the "little modified" Launch file in the error dialog (as some details can't be disclosed)
    [Launch path]:
    http://hostname.domain.com:12718/CMTE-3rdParty/tibco/7.5.2/tibco.jnlp
    [Error message]:
    Unable to load resource: http://hostname:12718/CMTE-3rdParty/tibco/7.1.2/tibco.jnlp
    [Launch File shown in error dialog]:
    <?xml version="1.0" encoding="UTF-8"?>
    <jnlp codebase="http://hostname:12718/CMTE-3rdParty" href="tibco/7.1.2/tibco.jnlp">
    <information>
    <title>Tibco</title>
    <vendor>Multicast messaging library</vendor>
    </information>
    <security>
    <all-permissions/>
    </security>
    <resources>
    <jar href="tibco.jar" version="7.5.2"/>
    </resources>
    <resources os="Windows" arch="x86">
    <nativelib href="tibco-libs.jar" version="7.5.2"/>
    </resources>
    <component-desc/>
    </jnlp>
    Thank you very much.

    You should change the codebase (declared in the jnlp tag) to http://hostname.domain.com:12718/CMTE-3rdParty
    That's how jnlp works, URL are made up as codebase+href.
    You'd better use absolute URL for the jnlp href (not for resources).
    And, last but not least, as Andrew would say: use JaNeLa (look for a link almost anywhere in the forum).
    Bye.

  • BI 7.0 Java Add-in without fully qualified domain name

    Hi
    I have just installed the Java Add-in for BI 7.0, and now I am trying to set up BEx to work. I have run the template installer, but there seems to be an issue with server names vs. fully qualified domain names. The server name is currently in the format "server.domain", but I suspect that it should/must be "server.domain.com".
    Is it possible to get full functionality without using fully qualified domain names (FQDN)? Is so, how can I acheive this?
    Regards,
    Thomas
    Edited by: Thomas Kjelsrud on Apr 23, 2008 8:39 PM

    This issue is no longer relevant for me. I still wish to find the solution tough, for future reference.
    Tegards,
    Thomas

  • Fully qualified domain name in EP 6.4 configuration

    Hi guys,
    I've got some problems with using fully qualified domain names (FQDN) while getting to Portal.
    Having EP installed and running properly, I've installed, on my MS Windows 2003 Server (on which my EP is running), DNS to provide FQDN.
    Until this my EP worked properly (I get to my portal main page using host name without FQDN - http://<host>:<port>/irj).
    After installing DNS and configuring new domain my EP runs properly when I get via simple hostname, but I've noticed, that it isn't working properly, when I try to get via url with FQDN.
    The FQDN is correctly recognized on sysop level (ping...) - the problem is surely in EP configuration.
    The most common symptom is an empty HTTP page or a portal page containing some interface elements, but without content.
    Who knows what I have to change in my EP configuration?
    I will be thanful for any help.
    Best regards,
    Marcin

    Hi Chung,
    Thanks for advice.
    Actually, in my case, problem was in IE internet settings.
    The solution was adding host name to the host list in in "local intranet" setting (tabpage Security).
    Regards,
    marcin

  • /etc/hosts Private Host Name Fully Qualified Domain Name does it matter?

    During installation of 11gR1 on Windows 2003 the examples in the installation guide show adding the Private IP and host name to /etc/hosts
    However they only add the short name, racnode1, not Fully qualified Domain Name (FQDN), racnode1.mycompany.com
    e.g.
    10.0.0.1 racnode1
    10.0.0.2 racnode2
    Later when installing the Clusterware it then expects to see the FQDN, racnode1.mycompany.com, of course you can modify this and remove the domain name and continue. OR go back and add the FQDN in /etc/hosts
    e.g.
    10.0.0.1 racnode1 racnode1.mycompany.com
    10.0.0.2 racnode2 racnode2.mycompany.com
    What is the best practice? Currently my company is just dropping the FQDN from the name during the install, my instinct is instead to add the FQDN to the /etc/host in the first place.
    Does anyone have a recommendation or experience with either situation?
    Will (using/ or not using) the FQDN cause me issues in the future?

    If it's a problem, the assistent will tell you :-)
    I don't think it's a problem.
    Please mind that the first entry will be the name of the ip address, if it's not in DNS and a utility tries to get the name. (that's the reason 127.0.0.1 resolves to localhost.localdomain, it's the first entry in /etc/hosts)

  • Exchange 2013 wildcard certificate - problem IMAP POP Because the matter is not a fully qualified domain name

    Hi all, I have an Exchange 2013 SP1, I have installed a third-party SSL certificate and correctly on the server, but when I assign the POP and IMAP services, I see this error
    The certificate with thumbprint XXXXXXXXX and subject '*. Xxxx.yyy' can not be used for POP SSL / TLS connections because the matter is not a fully qualified domain name (FQDN). Use the Set-POPSettings X509CertificateName command to set the FQDN of the service.
    I tried to run this command and restart the POP and IMAP services
    ImapSettings set-ca-server-1-X509CertificateName mail.xxxxx.yyy
    POPSettings set-ca-server-1-X509CertificateName mail.xxxxx.yyy
    But the POP and IMAP services, the certificate is not assigned.
    You know as you can solve
    regards
    Microsoft Certified IT Professional Server Administrator

    Hi,
    Before we go further, I’d like to confirm if you can use POP and IMAP properly.
    If everything goes well, we can safely ignore it:
    http://www.hsuconsulting.com/wildcard-ssl-certificate-exchange-2013-imap-and-pop-error/
    If not, we can try the following commands :
    Set-POPSettings -ExternalConnectionSetting {mail.domain.com:995:SSL}
    Set-ImapSettings -ExternalConnectionSetting {mail.domain.com:993:SSL}
    http://careexchange.in/how-to-enable-and-configure-pop-imap-in-exchange-2013/
    Note: Microsoft is providing the above information as convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information
    found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Fully Qualified Domain Name for JES on win2k

    I'm trying to install the Java Enterprise System (java_es_05Q1-windows-x86) to a Win 2k workstation.
    I get the following error msg:
    "system doesn't have Fully Qualified Domain Name. Setup Fully Qualified Domain Name and then continue installation"
    I included hostname in c:/Winnt/system32/drivers/etc/hosts
    Regards,
    Suri.

    Hello
    I have the same problem?
    I am trying to install java_es_05Q1_appserver-windows-x86 on Windows 2K Advance Server
    My machine is Domain Controller already and working with Microsoft Active Directory.
    But when I am trying to install java_es_05Q1_appserver-windows-x86 on Same machine it give me error
    System Doesn't Have Fully Qualified Domain Name
    Configure and then try
    I have updated C:\WINNT\SYSTEM32\DRIVERS\ETC\HOST with domain names
    But still it is causing the same problem again?
    Please Reply
    Yogesh Gurav

  • Error in Installing- System dosen't have fully qualified domain name.

    When I try to install Java Enterprise System in my PC, I get the following error message and cannot proceed further:
    System dosen't have fully qualified domain name.
    Setup fully qualified domain name and then continue instalation.
    Please help me to solve this problem.
    About my PC:
    Windows XP Home edition
    1 GB memory
    Thanks.

    Do you have DNS running on the net and configured right? Run "ipconfig" in a Windows XP command line to see if the DNS suffix is set. Another trick is to run "nslookup" in the command line and look up your system's IP address (wehich ipconfig will tell you.) If that doesn't get you a DNS name for the system, you need to fix that in the network connections dialogs.

  • Httpd: Could not determine the server's fully qualified domain name, using

    Hello, I am checking why the response time of the display of the pages of the sites are slow, then I checked the error_log file in /var/log/httpd and I got this texts: (I am hosting 3 sites in the server)
    [Mon May 14 21:21:37 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    Processing config directory: /etc/httpd/sites/*.conf
    Processing config file: /etc/httpd/sites/000010.129.0.37_80avepublishing.com.conf
    Processing config file: /etc/httpd/sites/000110.129.0.37_80escuelamovil.com.conf
    Processing config file: /etc/httpd/sites/000210.129.0.37_80sabiduria.com.mx.conf
    Processing config file: /etc/httpd/sites/0003any_80default.conf
    Processing config file: /etc/httpd/sites/virtualhostglobal.conf
    [Mon May 14 21:21:37 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Mon May 14 21:21:38 2007] [notice] Apache/1.3.33 (Darwin) mod_jk/1.2.6 DAV/1.0.3 mod_ssl/2.8.24 OpenSSL/0.9.7l PHP/4.4.4 configured -- resuming normal operations
    [Mon May 14 21:21:38 2007] [notice] Accept mutex: flock (Default: flock)
    [Mon May 14 22:12:18 2007] [error] [client 10.129.0.37] File does not exist: /Library/WebServer/Documentsescuelamovil/robots.txt
    [Mon May 14 22:12:18 2007] [error] [client 10.129.0.37] File does not exist: /Library/WebServer/Documentsescuelamovil/error.html
    with the alert:
    [Mon May 14 21:21:37 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    the virtual host file (virtualhostglobal.conf) is:
    # This file is auto-generated by the Server Admin Web
    # backend plugin whenever settings are saved.
    # The Listen and NameVirtualHost directives are generated
    # based on the VirtualHost directive inside
    # each site configuration file found in this directory.
    # Please add appropriate Listen and NameVirtualHost directives
    # if a site is manually edited
    # i.e. the site is moved from sites to sites_disabled (or vice versa)
    # or the site's Virtual Host ip address and/or port is modified
    # Last updated at 2007-05-07 14:22:34 -0500
    Listen 10.129.0.37:16080
    NameVirtualHost 10.129.0.37:16080
    Listen *:16080
    NameVirtualHost *:16080
    how can I correct this alert?
    thanks
    Dual 2 GHz PowerPC G5   Mac OS X (10.4.9)   4GB DDR SDRAM, MAC OS X Server
    Dual 2 GHz PowerPC G5   Mac OS X (10.4.9)   4GB DDR SDRAM, MAC OS X Server

    >how can I correct this alert?
    Fix your DNS.
    This non-fatal error is Apache's way of telling you that it can't work out the hostname of the machine it's running on.
    It uses reverse DNS to determine this information. If you don't have a reverse DNS entry for your server's IP address, this is what you get.
    Fix your DNS and the alert will go away, or just ignore it.

  • Ip address to fully qualified domain name

    Dear friends, I am unable to get the correct fully qualified domain name from IP address. Please help. I have already spent more than a day searching for the solution on these forums and on google. So now only option remaining is help from you friends.
    I think I need to explain my set up first.
    The machine runs on Solaris8 & is part of corporate intranet. Java version 1.4.2. I am just a developer (cannot touch networking) and here is what I know about its network set up.
    The machine has a network alias ("bluesky"). So when I access it thru telnet using VPN, the command line shows "bluesky" at the prompt. There are at least two domain names that lead to this machine. One is bluesky.XXX.com and another is somesubdomain.yyy.com.
    I have a piece of existing Java code that produces the IP number of this
    machine. I want to convert it to its domain name (either bluesky.xxx.com or the other one).
    When I connect by VPN to the network and use nslookup against the IP on my XP laptop, it displays the full domain (somesubdomain.yyy.com). When I do the same thing after I join the intranet directly (not thru VPN), it again shows the full domain, but the different one bluesky.xxx.com.
    Some of the code I tried:
    Try 1:
    String ip = "";//valid IP here
    InetAddress ia = InetAddress.getByName(ip);
    String hostname1 = ia.getCanonicalHostName();
    String hostname2 = ia.getHostName();When I connect to intranet (without VPN) and run the above code on my laptop, hostname1 and hostname2 both generate "bluesky.xxx.com". This is what I want.
    But when I run the code on the remote machine, both strings are only
    "bluesky". When I run the code on my laptop after logging into the network using VPN, both produce the second fully qualified domain name. That would also be OK for me if I can get it on remote machine.
    Try 2:
    I added the following line before the above code (based on forum search).
    System.setProperty("sun.net.spi.nameservice.provider.1", "dns,sun");The result was same as Try1.
    Try 3:
    InetAddress[] iaa = InetAddress.getAllByName(ip);
    for(int i=0;i<iaa.length;i++){
         System.out.println(iaa.getCanonicalHostName());
         System.out.println(iaa[i].getHostName());
    When ran on laptop, it iterates only once (I expected it to iterate twice) and produces bluesky.xxx.com for both println statements.
    On remote machine, it again produces only "bluesky".
    It's getting frustating. Please help. Thanks.

    Following could be the reason
    When you are running the InetAddress api's to get the domain name on your laptop (windows machine), It is not hitting the DNS server. It is just returning the domian name what is mention in the Laptop configuration. If you are making a security check based on that, then anyone can spoof up his domain name locally and get the desired domain.
    When you run the application at some remote machine, it actually resolves the ip address with DNS server.
    You may want to use the following code to hit DNS server all the time. But with this I have a issue. I am not able to get the domain when I am on VPN. I have to find the exact reason for this issue.
    private static String domainFmReverseDNS(String hostIp) throws IOException
    //Record opt = null;
    Resolver res = new ExtendedResolver();
    Name name = new Name(getReversedIP(hostIp)+ ".in-addr.arpa");
    short type = Type.PTR;
    short dclass = DClass.IN;
    Record rec = Record.newRecord(name, type, dclass);
    Message query = Message.newQuery(rec);
    Message response = res.send(query);
    Record[] answers = response.getSectionArray(Section.ANSWER);
    if (answers.length == 0)
    System.out.println("reverseDns did not find anything");
    return ("NotFound");
    else
    System.out.println("reverseDns found the value :-)");
    return answers[0].rdataToString();
    private static String getReversedIP(String ip)
    StringTokenizer st = new java.util.StringTokenizer(ip, ".");
    String reversedIp=st.nextToken();
    while ( st.hasMoreTokens())
    reversedIp = st.nextToken()+"."+reversedIp;
    return reversedIp;
    }

  • Modifying Portal URL to use Fully Qualified Domain Name

    Hi,
    We have a portal that I can access now by using the URL 'invsrvr001:50000/irj/portal'. We would need the URL to use the fully qualified domain name such as 'invsrvr001.company.com:50000/irj/portal'. Towards that end we added the profile paramter 'icm/host_name_full' with parameter value 'invsrvr001.company.com' and restarted the server. After the we tried to login to the portal using 'invsrvr001.company.com:50000/irj/portal' but the system displayed 'The page cannot be displayed' error.
    What else needs to be done so as to use the fully quailified domain name?
    Do I name to change the computer name from 'INVSRVR001' to 'INVSRVR001.COMPANY.COM'?
    Regards
    ND

    Ok, if you want to use FQDN including your domain extention (host.domain.com) you need to include your host into the domain.
    Also your PDC should be doing the time of DNS server so check that.    
    This should solve your issue, please close the thread.
    Regards
    Juan

  • Problem connecting through RFC with fully qualified domain name

    I am using the .NET Connector and RFC to call a BAPI
    I use a fully qualified domain name in the form <DOMAIN>\<HOST>
    The RFC seems to have problems with this form of address. It produces the following execption in my .NET code.
    SAP.Connector.RfcCommunicationException: Connect to SAP gateway failed
    LOCATION    CPIC (TCP/IP) on local host
    ERROR       hostname 'DOCUNET_AG\DWSAP' unknown
    TIME        Mon Feb 05 11:57:20 2007
    RELEASE     640
    COMPONENT   NI (network interface)
    VERSION     37
    RC          -2
    MODULE      ninti.c
    LINE        329
    DETAIL      NiPGetHostByName2: hostname 'DOCUNET_AG\DWSAP' not found
    SYSTEM CALL gethostbyname_r
    ERRNO       11004
    ERRNO TEXT  WSANO_DATA: Valid name,
       at SAP.Connector.SAPConnection.ThrowRfcException(RFC_ERROR_INFO_EX rfcerrInfo
    , Encoding encoding, String languangeCode)
       at SAP.Connector.SAPConnection.Open()
    What can I do that I am able to use a fully qualifies domain name in this way?
    Thank you very much for your answers.
    Mirco

    Hi Mirco,
    additional to my first reply, open a shell window and type
    <b>
    ping <computername>
    </b>
    or
    <b>
    ping -a <ipaddress>
    </b>
    so you should get the full qualified name for the host.
    Regards
    Holger

  • How to set-up Fully Qualified Domain Name in WIN2k3?

    Dear Experts,
    Admin, please rederict if this is the wrong forum.
    I need to set up a FQDN for our one host demo system running on Windows Server 2k3. How do I set it up (without compromizing our system)? On this host we have ECC 6.0 and GRC running.
    We don't have a registred domain.
    Kind Regards,
    Vit Vesely

    Hi,
    Set your domain name as FQDN (fully qualified domain name.)
    1) start the transaction RZ10.
    2) select INSTANCE Profile name where your server name is given.
    3) Select Extended Maintenance.
    4) Click on change button.
    5) Change parameter icm/host_name_full to FQDN
    6) Copy your settings with new version number.
    7) Activate that version.
    8) Restart your WAS (Transaction code SMICM -> Administration Menu).
    Check that the following services are active in your ICF setting (transaction code SICF)
    /default_host/sap/bc/bsp/sap
    /default_host/sap/bc/bsp/sap/system
    /default_host/sap/bc/bsp/sap/public/bc
    /def ault_host/sap/public/bc
    /default_host/sap/public/bc/ur
    /default_host/sap/public/bsp/sap/public
    /default_host/sap/public/bsp/sap/public/bc
    /defaul t_host/sap/public/bsp/sap/system
    /default_host/sap/public/bsp/sap/htmlb
    Set Request Hanlder Class, add Standard Class provided by SAP to default\sap\bc\bsp\sap service. Right click on default\sap\bc\bsp\sap service service.
    Now select display service, go to Handler Tag, and add the class CL_HTTP_EXT_BSP, which is a default HTTP request handler class.
    Specifically for fully qualified domain names problems,
    see:
    434918 Configuration for fully qualified host names for BSP
    654326 Domain restrictions in a portal environment         
    654982 URL requirements due to Internet standards          
    677118 SP31  >: Fully Qualified Domain Names Check         
    763427 Error message for domain name with underscore  
    Regards
    Krishna

Maybe you are looking for