Previously: >> A third checker option to check for a string provided by the >> Ringmaster would let me check for 'BlacksmithsRingID' (or any >> other line in the Javascript) and the checker would work for my >> rings and others that are using my jsNAVBAR. >I see your point, but I'm not ready to give it very high priority for >the time being. I may run a few more tests of the new system but without this option the checker does me no good at all. The access problems may not be related to how a browser accesses a page but the way a spider accesses a page. The rules and system responses may be different. I know there are rules for spiders such as checking and abiding by the ROBOTS.TXT file. I understand that you are not "spidering" sites in the technical sense since all you are checking is the one page per site, however you ARE spidering that page. . . In any case, I don't know much about these systems except that what you are doing is more like a spider or robot than a browser. In THAT line of thought I wonder if the server sensing a spider or robot is responding differently than it does to a browser. The server knows the type of browser AND spiders. . . Maybe your "signature" (or lack of one) sent to the other server is producing an undesired response. Jock Dempsey http://rings.anvilfire.com/