ok what's occurin here then?

[Kayless]

Through my wireless connection over the last couple of days I cannot access ebay at all, it simply the standard "no response" message. However through my ebay app on blackberry, I can and also I can through my dongle. I can access everything else via my standard home wireless connection. Anyone any idea what the problem is? the message says: "The server at www.ebay.co.uk is taking too long to respond.", thanks

[ChuckFickens]

If the dongle is being used on the same computer then it points to an ISP problem (which one is it?)

It would be worth checking your ISPs forums to see if anyone else is reporting the same problem.

[Kayless]

it's btinternet chuck, there do seem to be some issues out there but nothing specific.

[ChuckFickens]

Have you tried resetting your router (just switch it off for 2 minutes)

It's always a good starting place for obscure problems like this.

[Kayless]

yes, well I turn it off when I'm not sing it anyway so it's been on and off several times. This started happening yesterday. some forums do seem to point to a firmware upgrade needed but that seems illusive.

[ChuckFickens]

I'd be surprised if a firmware update would resolve a problem where you can't access one site.

If you try and ping www.ebay.co.uk does it resolve to an IP address OK (if so what address) and do you get a response?

[Kayless]

how do i do that chuck?

[ChuckFickens]

Start > run, type cmd into the run box and press enter, then in the command prompt type ping www.ebay.co.uk

It should then return something like pinging www.intl.ebay.co.uk (66.211.181.182) with 32 bytes of data.

The ping will time out as it looks like ebay doesn't answer pings, but if the IP address it resolves to is a correct one for ebay it rules out a DNS problem.

You can also try putting the IP address straight into the address bar of a browser to see if that takes you to an ebay page (it will be an error page but good enough to see if you can get a route to ebay)

[Kayless]

the ping comes back with 66.135.200.182 it came back with "request timed out"