I'm still unable to access this website (
www.amiga.org) and certain others from my Amiga setup. I've tried a number of TCP/IP stacks, and innumerable combinations of configuration settings, for DNS, DHCP, and so forth. The Miami Deluxe stack is the one I finally settled on, but its not fully enabled. (Is it still possible to register this software? The unregistered version of it has some features disabled, such as event triggering, which is needed for running SAMBA, and a few others, which may be contributing to my browsing problems. If anyone knows the answer to this question, please PM me).
In the mean time, another fact, which may also be contributing to the situation, is my own set up. When configuring the Miami stack, it became apparent to me that my particular network set up, although pretty commonplace today, is not really covered as an option in the MiamiInit application. It assumes you’re either directly connected to a broadband source, or dialing in, using a proxy, or not connecting to the Internet at all. That sort of leaves me out. Basically, I have a small network twelve machines, running off a Xincom dual-LAN router, two DSL accounts, and an array of three switches. I currently have a mix of W2K, WXP, Mandrake, W98, and NT4 machines, with a wireless node for my two Pocket PCs. Each and every one of these machines is visible and accessible to other machines on the network, as well as the Internet either through the MS-TCP/IP stack, and SMB, or, in the case of the Linux machines, SAMBA. But, the MiamiInt options don't really cover a network that accesses a broadband account by way of a router. That combined with other factors (such as the crippled version of Miami Deluxe I’m using) results in the current situation, where I can access some websites, but not others. With SAMBA installed on the Amiga, I can actually access shares on all the other machines, from the Amiga, but the other machines can't see it (the Amiga) by name. However, they can ping its internal IP address. My theory of differing communication protocols of the older browsers didn’t really pan out – I now have the Amiga running in a DMZ with my game server, and it still cannot go to this site, and certain others.
So, for now, instead of spending all of my time trying to resolve the DNS situation, I'm going to move ahead with setting up an email client (Yam), and something else I really need, an application that will allow the OS to handle long file names from a Windows machine.
:-?