Hello all,
Got a problem with tesco.com today. It won't log in -- at all. It will sit there for ages and then time out, or the remote host closes the connection. It works fine on JANet and the ADSL2 connection I have somewhere else. Strangely it will partially log in if I use the IP address rather than the host name, but then of course, the cookies don't work. I've tried it on multiple PCs on the IDNet line and even reset the router to no avail.
Having to use a ridiculous Xming/SSH link with X11 forwarding running firefox on a server in warwick to order shopping currently :)
Any ideas? Or is this some obscure tesco madness?
I've just logged in fine on my phone so my guess is it's either a issue at tesco now possibly resolved or a dns issue somewhere along the line.
I can't comment fully, Esh, as I don't have a membership to log in to, but no problems accessing tesco.com itself.
No problem logging in from here. :)
Tried it in three browsers and deleted all cookies to no avail. Total madness. Proxying through another interrnet line is just fine, so I guess it'll have to go like that. I can log in on other secure connections like Lloyds TSB etc.
I've been having problems with various sites in the last few days. Mainly ones with security on them. www.three.co.uk wouldn't load when logging into my account page (and when it did Firefox had a tantrum because of an expired certificate), and I've had the same with a few other sites this week while I've been off work. Things seem to be fine in the evenings though, so I have no idea what's going on there.
The three site might not be a good example though, as even Internet Explorer had issues with their site, as did logging in with my mobile.
That's interesting. I'll try again tonight as I still can't login. Does anyone know how long it would be if it was a DNS issue? The site resolves the same to me.
If it's DNS and it's resolving, then you'd need to ask support to take a look to see if there's anything wrong in the nameserver records.
I do have an account with Tesco, and can log in as normal.
The DNS resolves to the same IP for me on IDNet and elsewhere. I can't figure this one out at all. I can only assume they are doing something crazy with their server.
It's probablly some kind of intrustion detection system blocking you.
Check every machine on your network for virus infections. If that fails then unfortunately it probablly means that the intrusion detection system is badly configured and is blocking you along with other customers close to you in IP space.
Might be interesting to do a traceroute to see where the packets dissapear (note: firewalls mean that traces don't always reach thier destination even if the link is working)
No, I don't see how it could be something like that. The traceroutes also disappear at the same place in both the IDNet line and an external line. This has been working for months on end, if not years.
Sigh. Out of date security certificate on one of the routers. Sorry for the crazed rambling everyone.
How odd, thanks for letting us know. :thumb:
At least you've now worked out the problem!