Unresolved host name-Siebel dedicated client


While trying to open a dedicated client an error is shown.

“Requested Server could not be found”


“Your requested host ‘server name’ could not be resolved by DNS Server”

Proxy error details


Client CFG file has a parameter EnableFQDN set to TRUE by default. FQDN stands for Fully Qualified Domain Name.

You will be able to find this parameter under [Siebel] section.

If set to true your dedicated clients picks up your computer name and uses it as target address in your browser. For example

If your computer name is “comp67.yourcompany.com”, when you open your dedicated client you will see the following address in address bar.


Now, all the company network use proxy to open internet sites and when you open your dedicated client it uses your proxy settings and tries to find a site with comp67.yourcompany.com by contacting its DNS server. Since DNS server don’t have this address you see an error.


The simplest way to solve this problem is to set EnableFQDN parameter to FALSE which will result target address to be changed to http://localhost/start.swe as shown below

Internet explorer is usually configured to not use proxy for local address but just to be sure follow the below given steps to verify:

  • Open Internet Explorer
  • Click on Tools Menu -> Internet Options
  • Click on Connections Tab -> LAN Settings button
  • Set the option “Bypass proxy server for local addresses” to true as shown below

7 Responses to Unresolved host name-Siebel dedicated client

  1. OK. But this somehow, didn’t solve problem. Now it connects to “http://localhost:8080/start.swe”, how can I make it to connect to server database?

  2. Oh Ok. I got, it will connect to localhost anyway. So I have some problem. When I launch dedicated client I go error in Internet Explorer “HTTP 405 Method Not Allowed”. Do you have any clue?

  3. Related Problem:

    Error 404–Not Found
    From RFC 2068 Hypertext Transfer Protocol — HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.



    Change EnableFQDN to TRUE and comment FQDN with semicolon (;).

    EnableFQDN = TRUE
    ;FQDN = localhost

Leave a Reply