hmm; The thread was originated by maXimus4444 and the HTTP interface
(ie the protocol for browsers) does not reference or depend upon the computer 'name'.

I doubt the relevance ...

The "Underscore" looks like a dash in the ipconfig file.
The network might have trouble with a bad name, but "KERRY-PC" looks like a legal name.

My point re names is that TCP doesn't care, port2 (25,110) email doesn't care and the port 80 HTTP doesn't care.

Only Microsoft port 138 lan name cares, so ping, email and browser will work regardless.

But would the router/modem care?
And, is it even possible to give the computer a bad name?

Since you can ping external IP addresses, your primary TCP/IP layers ARE working correctly but DNS (domain name services) needed to resolve websites by name (e.g. "www.techspot.com") isn't working. One possibility is your adapter isn't getting useable DNS IPs from router when adapter TCP/IP is set as a DHCP client- Solution: set valid DNS IPs (displayed in your router) manually in your adapter TCP/IP screen, then reboot. The other (do this FIRST) is really easy: Start> Run> cmd.exe, then in the CMD window: ipconfig /flushdns. That should flush stale DNS IPs from the adapter and force DNS IPs to refresh. Post back results.

Routes and modems pass tcp packets and know nothing of 'names'. They use IP addresses and 'MAC' addresses.

Already solved nslookup (ip vs name) IS working

yes very unusual. maybe this will remain a mystery. oh well... better luck next time