From roots-in@roots-l.rootsweb.com Tue Sep 12 12:25:11 2006 Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34]) by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k8CIPBjb019229; Tue, 12 Sep 2006 12:25:11 -0600 Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k8CIPB27018517 for ; Tue, 12 Sep 2006 12:25:11 -0600 Received: from roots-l.rootsweb.com (roots-l [127.0.0.1]) by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k8CFhqFI020329 for ; Tue, 12 Sep 2006 11:43:52 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k8CFhqfo020328 for roots-approved@rootsweb.com; Tue, 12 Sep 2006 11:43:52 -0400 Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41]) by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k8CElnFI020184 for ; Tue, 12 Sep 2006 10:47:49 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k8CHSu0h007887 for roots-in@roots-l.rootsweb.com; Tue, 12 Sep 2006 11:28:56 -0600 X-Envelope-From: justrootin@gmail.com Tue Sep 12 11:28:56 2006 Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34]) by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k8CHSujb007875 for ; Tue, 12 Sep 2006 11:28:56 -0600 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.224]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k8CHStft001168 for ; Tue, 12 Sep 2006 11:28:56 -0600 Received: by wx-out-0506.google.com with SMTP id t4so2387657wxc for ; Tue, 12 Sep 2006 10:28:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:to:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:from:sender; b=jd7W7uI1gqwA6yYuDUmDusz+R9MFnkKiOwfLgc5+aAALIA2ZXuGVJr1ErB6t1gTAn/CuqlBlOsiCv4KoiG3T0ycHlFGC8dVms3AFdJDklsvP/i9aP5cNr2G1JcA6wLfuafsQfRJn7SXUriuyv340+tFSDFB086B1TUfA4mSW77k= Received: by 10.70.29.7 with SMTP id c7mr8714125wxc; Tue, 12 Sep 2006 10:21:53 -0700 (PDT) Received: from SUZY ( [66.61.157.193]) by mx.gmail.com with ESMTP id i15sm2651841wxd.2006.09.12.10.21.50; Tue, 12 Sep 2006 10:21:52 -0700 (PDT) Message-ID: <016c01c6d68f$e570f350$c19d3d42@SUZY> To: "Peggy Kopp" , References: <4506E206.2040104@epix.net> Subject: Re: [ROOTS-L] Heritage Quest Remote Access Date: Tue, 12 Sep 2006 13:21:29 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 From: Suzy McGrew Krol Sender: roots-in@roots-l.rootsweb.com X-Spam-Score: 1.293 (*) BAYES_00,RCVD_BY_IP,RCVD_IN_BL_SPAMCOP_NET X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 Hi Peggy, I don't have a solution to your problem, but I did experience the same thing here in Florida several months ago. The library also told me everything was fine. When I followed up with the library one librarian told me that everyone else was complaining about the same thing; she used to do genealogy and was no longer able to access it herself. I think what the actual problem was my library's subscription had run out for at-home access. My cousin gave me her library card # and password, so now I access it through another state. (shhh)! Sorry I couldn't offer you a solution. Suzy Hugs & Smiles are great gifts: One size fits all & nobody cares if you exchange them! ----- Original Message ----- From: "Peggy Kopp" To: Sent: Tuesday, September 12, 2006 12:36 PM Subject: [ROOTS-L] Heritage Quest Remote Access > As of last week authentication fails when I try to log on to Heritage > Qyest Remote At-home Access through the New Cumberland, PA library. > Previously I've been able to log on with no problem. > > Does anyone have experience solving with this problem? The library tells > me that 'everything is fine'. I've looked at the Database Problems > information on the library web site and it seems that my computer complies > in all respects. So far I've not been able to find a users' forum where I > can go to see how others handle authentication failure. > > Any help is appreciated. > > Peggy >