Troubleshooting iChain Proxy Server Problems
This section contains information on how to troubleshoot problems you may encounter with your proxy server. The following topics are covered:
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.
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 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
- You must be using Netscape* Navigator* 4.07 (or higher), Netscape Communicator* 4.5 (or higher), or Internet Explorer 4.01 (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. It comes with Netscape but might not be installed.
- Check to see if there is a copy of Netscape still in memory. (Open the task list by pressing Ctrl+Alt+Del.) Sometimes Netscape does not exit correctly from a previous session.
- 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.
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.
