Carlson Software Knowledge Base

If there appears to be a significant delay in retrieving the feature information for the module you are working with, this may be a result of problems in name resolution. Name resolution is important for accessing the server holding the license files from the workstations. Please refer to instructions attached below.

Correcting Name Resolution Issues:

1. Assign the server a static IP address if it does not already have one.
2. Verify that the server and client have the same DNS servers specified and make sure these servers are actually available.
3. Make sure that forward and reverse name resolution queries produce the same result. To do that:
   1. Open the Start menu in Windows and select RUN from the menu.

      

   2. Type CMD in the “Open:” box then click OK to open the command prompt
   3. At the command Prompt - type ping servername (using the actual server name such as “ping stranger” as shown below) then hit enter.
   4. Write down the IP address the "ping" command returns.

      

   5. If the IP address is correct, type tracert IP address (using the IP address from the ping results in the previous step such as tracert 123.45.67.890) and verify that the correct server NAME is returned.

      

   6. If they are pointing to different names then there is a problem on the local DNS server.

NOTE: In extreme cases, when everything else seems to fail, you can add a server name/IP pair to your local hosts file for local name resolution of the server name.

• On Windows 2000, XP, and Vista the file is located: c:\windows\system32\drivers\etc\hosts
• On WIN9x machines the file is located: c:\windows\system\hosts

1. You will need to open the host file in Notepad and add this line to the bottom of the file, using the actual server IP address and name: 111.222.333.444 SERVERNAME
2. Save the file and reboot. Do this on BOTH the server and the client machines.
3. Re-run WLMADMIN to verify that the change was successful. You should be able to see the Subnet Server.