Doesn't sound like a cookie problem to me.

One thing you might want to check under Netscape is whether or not you are loading from cache or from the web. The easiest way is to click on "Reload" (from Netscape or "Refresh" in Internet Explorer). A more "determined" way to reload is to flush the cache and reload using <Ctl>-Reload (Hold down control key and press reload at the same time).

You might also want to check the cache control on your browser. In Netscape, click on "Edit" -> "Preferences". Click on the "+" sign in front of "Advanced" and then highlight "Cache". Look at the bottom of the box on the right side. Where it says "Document in cache is compared to document on network". It should give three options. The first option (Once per session) means that unless there is a refresh command issued (either from the host computer on-line or from clicking on the reload button), you get the same page back. The second option (Every time) means that you load the page from the network every time. The third option (Never) means that you load from your internal cache on your computer at your fingertips and never ask for the new pages on-line. This last option should not be used when doing much stuff on-line at sites like FT.

The only fly-in-the-ointment is that some firewalls/proxy servers will have a network cache which doesn't reload new pages all the time. If you are behind such a firewall, you have to use the option of getting a page "Every Time," and even then, it might not work properly without proper configuration of the proxy server information.