Yes it still occurs when I use the port number and it occurs with the Netscape 4.6 browser.
<blockquote> Do you see this when you use nsvhr/nssock (and not nsvhr/nsunix?) </blockquote>
How do I switch from nssock to nsuinx and back?
-Bob