Troubleshooting iChain Proxy Server Issues

This section contains information on how to troubleshoot problems you might encounter with your iChain Proxy Server. The following topics are covered:

• Troubleshooting iChain Proxy Server Connectivity Issues
• Troubleshooting iChain Proxy Server Authentication Issues
• Troubleshooting iChain Proxy Server Authorization Issues

Troubleshooting iChain Proxy Server Connectivity Issues

This section contains information on how to troubleshoot connectivity problems you may encounter with your iChain Proxy Server. The following topics are covered:

• My proxy server isn't working
• I can't ping the proxy server from my client
• All the numbers are correct and it still won't ping
• My browser can't find the application
• Nothing ever comes up on my browser
• None of the changes I made in the browser application are taking effect

My proxy server isn't working

Most problems are caused by invalid IP address configurations. Four things are critical:

• A numeric IP address with a subnet mask
• A valid gateway address on the same subnet as the IP address
• A valid DNS server IP address
• A valid DNS domain name

I can't ping the proxy server from my client

The IP address for the client must be 10.1.1.2 (or any other valid 10.1.1 subnet address other than 10.1.1.1) and the subnet mask must be 255.255.255.0. Its gateway must be the address of the proxy server; in the original configuration that address is 10.1.1.1. DNS on the client must also be set to the IP address of the proxy server. If the ping fails with these addresses, dump the arp table on the browser (for example, using arp -a on Windows) and check that an entry exists for the proxy server IP address 10.1.1.1. If there is no entry, the problem is likely a hardware issue. Check the cables and confirm that there is a physical connection between both IP hosts.

All the numbers are correct and it still won't ping

• Some Ethernet cards under Windows NT* or Windows 95/98 do not allow a crossover cable. If that is the case, try connecting the two machines with a standard Ethernet cable running through a hub.
• Windows 2000 requires modification of its registry to work with a cross-over cable.

  To initialize an iChain Proxy Server from a Windows 2000 workstation, you must complete the instructions in "How to Disable Media Sense for TCP/IP in Windows 2000" on the Web.

My browser can't find the application

• The correct URL is http://10.1.1.1:1959/appliance/config.html.
• Make sure you specify http:// in the URL window. Typing the address of the application without http:// doesn't work.

Nothing ever comes up on my browser

• We recommend that you use Internet Explorer 5.5 (or higher) with the proxy server. Also, the product release notes might contain more information regarding browser compatibility.
• You must have a JVM (Java Virtual Machine) installed.
• Try exiting from your client OS and restarting.
• Try the SHUTDOWN command from a Telnet or command line session on the proxy server. Then turn the proxy server off and on again and wait for it to come up.
• If you just started the proxy server, you might be trying to start before the server is up. When the proxy server starts, you will hear the startup beep pattern (two longs and four shorts) repeated four times. When the beeping stops, the proxy server is ready.
• If the browser appears to have hung, check the URL to see if it is trying to go to a URL with port 2222 in it. If this is the case, then there is probably an issue with the default certificate used for authentication to the iChain GUI. Go to the iChain Proxy Server console and do the following:

1. Unlock the console.

2. At the iChain command line interface, enter an_kill. This will cause all iChain modules to be unloaded.

3. When you have control of the iChain Proxy Server console, enter the following:

   unload certappstart.ncf

4. After loading TCPCON at the iChain Proxy Server console, you should confirm that TCP port 2222 is listening on that server. You can do this by going to Protocol Information > TCP > TCP Connections, then confirming that an entry exists for TCP port 2222.

None of the changes I made in the browser application are taking effect

• After making the changes, you must click Apply to make the changes effective.

Troubleshooting iChain Proxy Server Authentication Issues

For information on troubleshooting iChain Proxy Server authentication issues, see the Novell Developer Web site.

Troubleshooting iChain Proxy Server Authorization Issues

For information on troubleshooting iChain Proxy Server authorization issues, see the Novell Developer Web site.