"Steve Olive" wrote in message
...
Thanks everyone.

DNS was manually set to the wrong address. Bloody second hand computers.

Ah! I nearly suggested that but discounted the "forced wrong address" error
as being too improbable. Mind you, my ipconfig test would have showed it up.

Thanks everyone.
DNS was manually set to the wrong address. Bloody second hand computers.

Yay, but look how much you learned in the process :-}

Mortimer wrote:
"Steve Olive" wrote in message
...

Thanks everyone.

DNS was manually set to the wrong address. Bloody second hand computers.


Ah! I nearly suggested that but discounted the "forced wrong address" error
as being too improbable. Mind you, my ipconfig test would have showed it up.



It did. Thanks.

Colin Wilson wrote:
Thanks everyone.
DNS was manually set to the wrong address. Bloody second hand computers.


Yay, but look how much you learned in the process :-}

Oh I agree. I learned a lot but:

A - It shouldn't be so difficult
B - It'll be something different next time.

Ah well.

DNS was manually set to the wrong address. Bloody second hand computers.

If we had known it was a second hand computer we probably would
have twigged that it was set up to talk to a different ISP.
This is also one of the perils of ISP supplied setup/signup disks,
they can really screw up a PC, making it a right pain in the arse
to set it up for a different ISP.
Decent ISP's give you the information you need to set things
up manually, and, "Let Windows manage this connection" can
be another example of the "Plug and Pray" philosophy,
fine if it works.

"Steve Olive" wrote in message
...


Colin Wilson wrote:
Thanks everyone.
DNS was manually set to the wrong address. Bloody second hand computers.


Yay, but look how much you learned in the process :-}

Oh I agree. I learned a lot but:

A - It shouldn't be so difficult
B - It'll be something different next time.

Ultimately, it's nothing that wiping the computer clean and starting again
won't cure!! (Probably!)

--
Graham J

Oh I agree. I learned a lot but:
A - It shouldn't be so difficult
B - It'll be something different next time.
Ah well.

Ah well indeed - that's where your friendly neighbourhood live linux
CD comes in handy :-)

Steve Olive wrote:
Right, an update.

She can iew web pages with http://212.58.226.20 etc.....
But not by typing the web address.

Then DNS is fscked.

check DNS servers settings.

I'm sure Google will come up trumps now.

Thanks all.

"The Natural Philosopher" wrote in message
...
Steve Olive wrote:
Right, an update.

She can iew web pages with http://212.58.226.20 etc.....
But not by typing the web address.

Then DNS is fscked.

check DNS servers settings.

You're a bit behind the times. The OP has already posted to say that
ipconfig showed a silly DNS server entry that had been set statically. He
either set it statically to the router's address or else set TCP to get DNS
address via DHCP, and everything works fine now.

On Tue, 01 Jul 2008 22:27:35 +0100, Colin Wilson passed an empty day by
writing:

Oh I agree. I learned a lot but:
A - It shouldn't be so difficult
B - It'll be something different next time. Ah well.

Ah well indeed - that's where your friendly neighbourhood live linux CD
comes in handy :-)

A live linux CD would have made what difference exactly? The tools to
diagnose the problem were right there in windows - it was a simple enough
misconfiguration.

My concern would have been which DNS server(s) the machine was pointing
at, why they would not resolve names and if they were poisoned in any way.

--
begin oefixed_in_2005.exe