Updated 11/28/96 for ISP Independence!
This complaint is also frequently described as "my Java applet doesn't start", "can't play Java applet in Netscape Navigator 3".
Other indications: This fix applies when the applet starts right away **if and only if you're connected to your internet service provider**. When you're not connected, it takes 2 minutes to start or doesn't start. I've seen it happen with both Netscape Navigator 3 and JDK AppletViewer.
Test to make sure that the applet comes right up when you're hooked to your Internet Service Provider. If it does not, this solution probably won't help you. Also, I've tested this fix in Windows 95. It may be different or not relevant in other operating systems.
From Control Panel, doubleclick on Networks to bring up the Network Properties Dialog Box, as shown below:
Next, highlight TCP/IP as shown, then click the Properties button. You'll be brought to the TCP/IP Properties dialog box, as shown below.
Click the IP Address tab, and note that the "Obtain an IP address automatically" radio button is selected. This is the cause of your problem. Your Java Applet is waiting for your (disconnected) ISP to provide an IP address, and finally times out after 2 minutes.
Click the "Specify an address" radio button to enable you to input an IP address and subnet task. Set both to 184.108.40.206. My research indicates that these addresses mean nothing on a dialup connection, but their absense causes delays on disk based Java applets and other applications.
Click OK all the way out, and allow the computer to restart. Your Java applet should now fire up right away with or without your dial up connection to your ISP.
Be sure to test your applet, and your dial up connection (via browser, email, ftp, telnet, etc). I tested extensively and found no ill effects.
Please email me with any new information you find on this subject.
[ Home page | About Steve Litt | Email Steve Litt | Training ]
Copyright (C)1996 by Steve Litt. -- Legal