Cannot connect

[Bobcoop103]

A friend asked me to check her computer to see why she could not access the internet, whenever she tried she got the message : CANNOT DISPLAY THIS WEB PAGE. It's a fairly new HP with VISTA, she is connected with a MODEM/ROUTER via cable. Nothing had changed during the time the problem occurred. I received the same message when I connected to my DSL I also received a message saying that there were 2 Internet connections and I should disconnect one, there was only one.
I restored her system to an earlier restore point and it solved the problem for a while then it happened again. Any ideas anyone?
Follow up to above.
I went to NETWORK PROPERTIES & MANAGE INTERNET CONNECTIONS, DIAGNOSE which reported that the internet connection was working properly.
While working with the system I received an IM which told me that the connection was OK I also used a disk that I had downloaded MSIE 8 onto and was able to upgrade to that version, the updates were downloaded and installed. But the main problem remains, I cannot get on the internet through MSIE. I would appreciate any help with this.

 

[bitznpcz]

it's probably a winsock error. try the following:

1.Click on the Start button.
2.Type Cmd in the Start Search text box.
3.Type netsh winsock reset in the Command Prompt shell, and then press the Enter key.
5.Restart the computer.

 

[LunchBox]

One this that I always do now is carry a copy of FireFox portable or you can install it to see if you are able to surf the net.

Can yo ping any site like google.com or their ip of 209.85.171.100 (cant remember the other one).

as bitznpcz stated resetting the winsock should fix it.

 

[tartis]

Spyware that is changing the DNS scewing up the Winsock.

 

[TimeCode]

Bobcoop103,

I want you to understand that this is a forum for computer professionals or those who are starting computer businesses.

What is Technibble? Technibble is a resource for computer technicians who are looking to start their own computer business or improve their existing one. Technibble also provides an amazing place for technicians to help other technicians via our forums.

As clearly stated in the above paragraph which can be found here, it is a place for technicians. If you are a tech, we welcome you with open arms and apologize for any perceived rudeness. If you are an end user looking for help, please look here, here or here.

Please understand that you are not being attacked so much as we are just trying to keep our beloved forums free from tech-support seekers.

 

[ChrisQC]

What ip address is being assigned to the computer. Check and post it on here.

 

[Nayth]

Lately ,Me and my boss chris been having alot of Pc's/Laptops's, with the Ip adress off 169.***.***.. Just Basic format should do the job ..
Nath

 

[purple_minion]

Lately ,Me and my boss chris been having alot of Pc's/Laptops's, with the Ip adress off 169.***.***.. Just Basic format should do the job ..
Nath

wtf?

(PADDING)

 

[Methical]

One this that I always do now is carry a copy of FireFox portable or you can install it to see if you are able to surf the net.

Can yo ping any site like google.com or their ip of 209.85.171.100 (cant remember the other one).

as bitznpcz stated resetting the winsock should fix it.

127.0.0.1.
Is that what u were missing LunchBox?

 

[Methical]

wtf?

(PADDING)

LOL
F**cken aye, report him! lol

Doesnt 169.*.*.* have sumthin to do with APIPA?

 

[Galdorf]

I have seen another problem like this it has to do with corruption in IE itself if your settings corrupts it stays off you have to get rid of IE totally and reinstall this includes all registry settings.

If you can ping ect from command line and not surf this is most likely the cause.

 

[TimeCode]

Lately ,Me and my boss chris been having alot of Pc's/Laptops's, with the Ip adress off 169.***.***.. Just Basic format should do the job ..

You're not getting DHCP so if there are 2 PCs not with the same problem, the problem is almost definitely NOT the PCs. Probably the router. Restart it.

And if you reformat over a 169.x.x.x IP Address, you've got much bigger problems than not getting a proper address via DHCP.

Doesnt 169.*.*.* have sumthin to do with APIPA?

Any IP Address that starts with 169 is a sign that you have no IP address assigned. You're not receiving DHCP.

 

[iptech]

Any IP address beginning with 169.254.x.x will be one assigned by Windows Automatic Private IP Addressing (APIPA) as TimeCode says this is most commonly cased by a non-functioning DHCP server (typically the router on small SoHo networks). IP addresses in the 169.154.x.x range are local addresses only and cannot be routed so if say you had two computers on a LAN with IP addresses of 169.254.55.22 and 169.254.55.23 they should be able to see one another but nothing that exists via a router or gateway, or has a static IP address outside of this range. APIPA is a switchable function of the operating system IP stack that provides an address that is guaranteed not to conflict with routable addresses.

Sometimes a simple router reboot can resolve this issue, although it can be caused by cabling issues, incorrectly installed or damaged NICs or incorrectly configured or damaged TCP/IP protocol stacks on the host PC. If it's only a single PC that's affected only then should you need to mess with the Windows network settings, if it's happening on more than one computer on a LAN segment but others on the same network are working OK then it's likely to be a broken cable or network switch, if all computers are affected then you should begin diagnosis with the DHCP server.

 

[iptech]

I have seen another problem like this it has to do with corruption in IE itself if your settings corrupts it stays off you have to get rid of IE totally and reinstall this includes all registry settings.

If you can ping ect from command line and not surf this is most likely the cause.

It's not likely to be in IE itself as it's only a browser client, the problem's more likely to be in the IP stack. Easy to diagnose by using Firefox portable, if that works OK then it's IE that's at fault and not the IP stack.

 

[SOHO-NZ]

LOL

Doesnt 169.*.*.* have sumthin to do with APIPA?

It's the address you get when the DHCP process fails.
In XP, see TCP/IP properties, Alternate Configuration "Automatic private IP address"