"Page not found" errors on Ancestry this weekend ?

[O1dgobbo]

Google results suggest that the 400 error arises when your computer sends an unrecognized code to the receiving computer.  I wonder whether it is a contention problem.  The code that your computer sends to Ancestry may actually travel as several packets and if your contenders are keeping the line busy by downloading video then the packets you send may get dispersed with the later ones much delayed. The Ancestry receiver may then give up waiting for the termination packet and just say that there is a 400 error in your information.

All the best

Gobbo

PS Does this man understand what he is talking about?  Probably not!

[Gadget]

Hi Nick

I put a random name into the trees search and then it took me ages to find a person who had any historical records in their profile  - most of the people that I clicked on said 'No Historical Records'. 

When I got one, I clicked on a random census record that was listed in the Historical records section and it came up, no problems at all.


Gadget

[jc26red]

another thought for the time out...

are you trying to search on a person from London by any chance? It could be that Ancestry hasn't perfected the search through the LMA records yet from the people listed in trees or someone has added the pre 1812 records and of course they are not.

just a thought

Jenny

[Nick29]

Could someone do me a favour and put in search.ancestry.co.uk into the URL, and see what comes up ?

I don't seem to be able to resolve it at all !  Even the Search box doesn't work now !

(P.S.  I've looked at the MTU setting, and it's just fine)

[Gadget]

The Ancestry Search Page !

[Necromancer]

You've got a DNS problem.

[Alan b]

You've got a DNS problem.

I am on Sky like Nick and still don't have those problems. I don't use Sky's DNS servers though as I use OpenDNS if that makes a difference.

[Nick29]

I recently changed routers, so I'm sure you're right.  I have to go out in a while, but I will take a look at it later.  Thanks for the suggestions 

[Nick29]

An update - I found that the problem only occurred on this computer, and I used the Windows XP diagnostic tool, which dropped the computer's network IP connection and re-established it.  After that it was OK (or at least as OK as Ancestry ever is !) 

Thanks to everyone for their suggestions 

Later note: After all that, I was still getting "Error 400"'s when using Ancestry search.  It was happening when I was searching on a person within the tree - the initial search was OK, but refining the search by asking only for (say) Census Entries caused an Error 400.  In the end, going into the IE settings and deleting all the cookie and cached pages got rid of the problem.  I was loathed to do that, because I would lose my browser history and would lose auto-login to many of the sites I visit, but it was inevitable in the end.