Can't Connect To the Internet.

turkishmonkey · 08-10-2006, 11:51 PM

Ok, so basically i can't get online. I've tried IE and Firefox. Neither of them work. I've just re-installed my NIC and when i look at the properites it shows the the connection is working. It's not a problem with the internet it self I'm pretty sure because the internet works on my other computer. If anyone knows about any solutions then I'm all open for them.

**johnwill** · 08-11-2006, 02:50 PM

For 98 or ME, Start, Run, COMMAND to open a DOS window:
--- or ---
For 2K or XP, Start, Run, CMD to open a DOS window:

Type the following command:

IPCONFIG /ALL

Right click in the command window and choose Select All, then hit Enter.
Paste the results in a message here.

turkishmonkey · 08-11-2006, 05:20 PM

And remember this is not my main computer.

Windows IP Configuration

Host Name: STOLEN
Primary DNS Suffix:
Node Type: Broadcast
IP Routing Enabled: No
WINS Proxy Enabled: No

Ethernet adapter Local Area Connection:

Connection-Specific DNS Suffix:
Description: GVC-REALTEK Ethernet 10/100 PCI Adapter
Physical Adress: 00-C0-A8-80-F6-6C
Dhcp Enabled: Yes
Autoconfiguration Enabled: Yes
IP Adress: 0.0.0.0
Subnet Mask: 0.0.0.0
Default Gateway:
DHCP Server:0.0.0.0

**johnwill** · 08-12-2006, 10:24 AM

The IP address of 0.0.0.0 normally indicates either a corrupt Windows installation, a bad NIC, or a duplicate IP address on the network.

Try this Automated WINSOCK Fix for XP, reboot and test.

If that doesn't do the trick, try this stack reset procedure.

TCP/IP stack repair options for use with Windows XP with SP2.

For these commands, Start, Run, CMD to open a command prompt.

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log

rstainforth · 08-13-2006, 05:05 AM

your problem looks as though your pc isn't dhcp'ing properly, as you don't have an ip/subnet mask, or a default gateway. to check that your nic is working, you can try pinging the loopback address (run>cmd>ping 127.0.0.1) and see if you get a reply.

have you tried repairing your network connection? (either rclick on the network icon on your task bar, or find your network connection in "network connections", rclick and select repair).

try a power cycle on your router/modem (turn it off at the power, wait about five mins, then turn it all back on again), you might need to run a repair on your network connection again if you do that.

i would hazard a guess that either your nic isn't installed properly or your router/modem is having an elderly moment lol

oh, and have you checked that the cables are all connected properly between your machine and the router/modem, and that you have the right type of cable????

you could also try uninstalling your nic from my computer>hardware manager, and then rebooting, to see if it is a nic driver issue.

**johnwill** · 08-13-2006, 02:49 PM

I doubt he'll be able to ping localhost with an IP address of 0.0.0.0. Bad cables will result in 169.254.x.x adresses.

08-10-2006, 11:51 PM	#1 (permalink)
turkishmonkey Registered User Join Date: Aug 2006 Location: Tacoma, WA Posts: 7 OS: XP Professional	Can't Connect To the Internet. Ok, so basically i can't get online. I've tried IE and Firefox. Neither of them work. I've just re-installed my NIC and when i look at the properites it shows the the connection is working. It's not a problem with the internet it self I'm pretty sure because the internet works on my other computer. If anyone knows about any solutions then I'm all open for them. __________________ -Israel

08-11-2006, 02:50 PM	#2 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,740 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	For 98 or ME, Start, Run, COMMAND to open a DOS window: --- or --- For 2K or XP, Start, Run, CMD to open a DOS window: Type the following command: IPCONFIG /ALL Right click in the command window and choose Select All, then hit Enter. Paste the results in a message here. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

08-11-2006, 05:20 PM	#3 (permalink)
turkishmonkey Registered User Join Date: Aug 2006 Location: Tacoma, WA Posts: 7 OS: XP Professional	Results And remember this is not my main computer. Windows IP Configuration Host Name: STOLEN Primary DNS Suffix: Node Type: Broadcast IP Routing Enabled: No WINS Proxy Enabled: No Ethernet adapter Local Area Connection: Connection-Specific DNS Suffix: Description: GVC-REALTEK Ethernet 10/100 PCI Adapter Physical Adress: 00-C0-A8-80-F6-6C Dhcp Enabled: Yes Autoconfiguration Enabled: Yes IP Adress: 0.0.0.0 Subnet Mask: 0.0.0.0 Default Gateway: DHCP Server:0.0.0.0 __________________ -Israel

08-12-2006, 10:24 AM	#4 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,740 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	The IP address of 0.0.0.0 normally indicates either a corrupt Windows installation, a bad NIC, or a duplicate IP address on the network. Try this Automated WINSOCK Fix for XP, reboot and test. If that doesn't do the trick, try this stack reset procedure. TCP/IP stack repair options for use with Windows XP with SP2. For these commands, Start, Run, CMD to open a command prompt. Reset WINSOCK entries to installation defaults: netsh winsock reset catalog Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

08-13-2006, 02:49 PM	#6 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,740 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	I doubt he'll be able to ping localhost with an IP address of 0.0.0.0. Bad cables will result in 169.254.x.x adresses. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

08-13-2006, 05:05 AM	#5 (permalink)
rstainforth Registered User Join Date: Jul 2006 Location: York, UK Posts: 14 OS: XP	your problem looks as though your pc isn't dhcp'ing properly, as you don't have an ip/subnet mask, or a default gateway. to check that your nic is working, you can try pinging the loopback address (run>cmd>ping 127.0.0.1) and see if you get a reply. have you tried repairing your network connection? (either rclick on the network icon on your task bar, or find your network connection in "network connections", rclick and select repair). try a power cycle on your router/modem (turn it off at the power, wait about five mins, then turn it all back on again), you might need to run a repair on your network connection again if you do that. i would hazard a guess that either your nic isn't installed properly or your router/modem is having an elderly moment lol oh, and have you checked that the cables are all connected properly between your machine and the router/modem, and that you have the right type of cable???? you could also try uninstalling your nic from my computer>hardware manager, and then rebooting, to see if it is a nic driver issue.