> I'm guessing the issue is tied to the internal IP that IIS is > configured for versus the external IP that IE6 sees.
That should make absolutely no difference at all. Cookies are associated with hosts and domains, not with IP addresses (assuming that you reached the server via a hostname and not an IP address typed into your browser's location bar). With this, as with so many other HTTP issues, being able to look at the raw HTTP requests and responses can be useful. You might try using a recording proxy or packet sniffer, or you might install something like ieHTTPHeaders: http://www.blunck.info/iehttpheaders.html Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:206224 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
