Dynamic Host Configuration Protocol (DHCP) is a standard protocol that is defined by RFC 1541 (which is superseded by RFC 2131) and enables a server to dynamically distribute IP addressing and configuration information to clients. Normally the DHCP server provides the client with at least the following basic information:

• IP Address
• Subnet Mask
• Default Gateway

Additional information might be provided, including Domain Name Service (DNS) server addresses and Windows Internet Name Service (WINS) server addresses.

If you are using SAS 9.2 with Dynamic Host Configuration Protocol (DHCP) in a Windows operating environment, you might need to take the following steps in order for SAS 9.2 to work correctly:

1. Ensure that you do not have both Internet Protocol Version 6 and Version 4 selected. Examine the Local Area Connection Properties dialog box (shown below) to verify whether Internet Protocol Version 6 (TCP/IPv6) is selected. If it is, clear the check box.

   

2. Ensure that the hosts file contains the following two entries:

   127.0.0.1 localhost
   ::1 localhost 

   The hosts file is located in one of the following locations:
   
   

   C:\WINNT\system32\drivers\etc
   C:\Windows\system32\drivers\etc
   
   
   
3. Ask the system administrator to set the IP properties as a DHCP connection. (The system administrator configures the DHCP server with the options that are parsed out to the client.)
   
   
4. Select Start ► Run and type cmd. At the DOS prompt, type ipconfig in order to display the ipaddress.
   
   
5. Copy the address.
   
   
6. Go to the Internet Protocols (TCP/IP) Properties dialog box, select Use the following IP address, and paste in the address that you copied in step 5 when you entered the ipconfig command.
   
   
7. Restart the computer.

If you are having specific issues with the SAS Remote Services application, do the following:

1. Turn on the DEBUG option in the wrapper.conf file that is located in this directory:
   
   sas-configuration-directory/lev1/web/applications/remoteservices.

   For example, the directory path for your configuration file might be similar to the following:

   C:\SAS\config\Lev1\web\applications\remoteservices\

   Make a backup copy, and then edit the wrapper.conf file, changing WARN to DEBUG:

   wrapper.logfile.loglevel=WARN wrapper.console.loglevel=WARN
2. In the same directory, make a backup copy and then edit the file log4j.properties, changing all log levels to DEBUG.

   For additional information about the log4j.properties file, see the SAS 9.2^® Intelligence Platform Web Application Administration Guide.
   
   

3. In the same directory, edit the wrapper.conf file and make sure that the settings for IPv6 and IPV4 have the same values as the following code:
   -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false

   If the entry in your configuration file is different, update the code so that it matches what is shown above.

   If you need additional information about IPv, see the SAS 9.2 Intelligence Platform Web Application Administration Guide.

4. Verify that the environment.properties file is in same directory as the wrapper.conf file, and make sure that the following IPv4 multicast address is listed in the file:
   (239.192.0.1)
5. Select Control Panel ► Services to restart the remote services. Note that in some Windows operating environments Services is located under Administrative Tools. Verify that start-up is successful.
   
   
6. Make a backup copy of the file, and then make the same change to the IP stack in Jboss-4.2.0GA/bin/SASServer1.bat for Jboss.
   -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false
7. Navigate to Services and start JBoss by entering http://127.0.0.1:8080 in your browser:

   Verify that the start-up is successful.

8. Log on to SAS^® Information Delivery Portal with sastrust by entering the following URL in your browser: http://127.0.0.1:8080/SASPortal

   Verify that the start-up is successful.

These steps are necessary when you have both IPv4 and IPv6 network interfaces running on the same machine. The default DHCP setup appears to select both network interfaces.

You can find additional information about DHCP in the following Microsoft articles:

• "DHCP (Dynamic Host Configuration Protocol) Basics"
• "DHCP (Dynamic Host Configuration Protocol)"

Operating System and Release Information