No Internet or network connection

I am having the same problem with no solution yet
No Internet or network connection
Toshiba Satellite running Vista
Cable modem
Linksys BEFW11S4 router

network computers working OK
This computer is only two weeks old and was working OK before. Can’t think of anything that I have done that would stop it from working. I have done all the things stated above except for registry edit. Can & have edited registry before but not comfortable with doing it plus the following diagnostics. Any additional help will be appreciated I have tried to break this down into different parts for easier reading


How to troubleshoot a Windows PC Network Interface Card.


· Check the cable connectors and cable. It should be 343 feet or less and contain a correct RJ45 (8 Pin) cable connector. (done)
· Check to ensure that you are plugged into the correct NIC jack. An RJ45 will not fit into an RJ11 but an RJ11 (6 pin) will fit into an RJ45 (8 pin) receptacle. It will be a loose fit. the RJ45 is for your network interface card. RJ11 is your modem (telephone). (done)
· Are the link lights on? (yes)
· Recycle the modem hub/router. If you are running a cable modem or aDSL then you will have a separate hub or router. Disconnect the power for at least 20 seconds and then restart. (done)
· Check the link lights on the router. Are they on? (yes)
· Check the cable types. A Crossover is for computer to computer and will NOT work with your cable modem. You cable must be a straight RJ45 type cable. It should state the cable type on the cable sleeve. Check for crimps in the cable and/or try a different cable. (done)
· Check for error messages => wrong username or password then contact your ISP for the correct account settings. Check to ensure that your ISP did not disconnect you for violations or failure to pay your bill. (no error messages)
· Check error messages in Event Viewer. Start / Settings / Control Panel / Administrative Tools / Computer Management (or Event Viewer) (done—not sure what to look for)
· PING 127.0.0.1 - this will test to ensure that your TCP/IP software is working correctly. If it is not then re-install the TCP/IP software. (done---see addendum #1)
· PING n.n.n.n - where n.n.n.n is taken from IPCONFIG (WINIPCFG on Windows 98 and Me). Windows assigns default IP addresses starting with 192.168.n.n (for private networks). This will test to ensure that your NIC card is working correctly. If it is not then reseat the NIC card. If problem persists and you cannot PING across the NIC card then the card is bad - send in for service. (done—see addendum #1)
· Perform an IPCONIG /RELEASE and then a IPCONFIG /RENEW in DOS to release the current IP settings and then re-assign the IP settings. (done see addendum #1)
· Perform a TRACERT to see if it will hop across the NIC. (done—see addendum #2)
· Perform a ROUTE PRINT and view the IP Settings. There should be 7 entries. (see addendum #3)
· Will your browser work with IP addresses but not with DNS names? If you cannot type in http://www.google.com and get it to work but you can type in a known IP address http://216.239.51.100 (the IP for Google.com). If the IP address works but the DNS does not work the re-install WinSocks (the DNS lookup software). (neither option works)
· Reset the BIOS (Re-boot and tap the F2 Key, Press F9 (Default Settings), Press F10 (Save and Exit) (done)

 

no internet & no network part-2

Ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data
General Failure
General Failure
General Failure
General Failure

Ping stats for 127.0.0.1
Packets sent=4 received=0 loss=100%

Ping 169.254.116.39 (from ipconfig IPv4 address data)

Pinging 169.254.116.39 with 32 bytes of data
General Failure
General Failure
General Failure
General Failure

Ping stats for 169.254.116.39
Packets sent=4 received=0 loss=100%

Ping 169.254.150.149 (from ipconfig IPv6 address data)

Pinging 169.254.150.149 with 32 bytes of data
General Failure
General Failure
General Failure
General Failure

Ping stats for 169.254.150.149
Packets sent=4 received=0 loss=100%

Ipconfig /release
The requested operation requires elevation (?????)

Ipconfig /renew

Windows IP Configuration

An error occurred while renewing interface Local Area Connection : unable to
Contact your DHCP server. Request has timed out
An error occurred while releasing interface loopback Pseudo-Interface 1 : The system cannot find the specified file.




C:\Users\user>

 

no internet & no network part-3

Tracert -j host-list
Unable to resolve target system name host-list

Tracert -4 169.254.116.39 (from ipconfig IPv4 address data)

Tracing route to 169.254.116.39 over 30 hops

1 general failure
Trace complete

C:\Users\user>ipconfig /release
The requested operation requires elevation.

C:\Users\user>ipconfig /renew

Windows IP Configuration

An error occurred while renewing interface Local Area Connection : unable to con
tact your DHCP server. Request has timed out.
An error occurred while releasing interface Loopback Pseudo-Interface 1 : The sy
stem cannot find the file specified.

C:\Users\user>tracert -j host-list
Unable to resolve target system name host-list.

C:\Users\user>tracert -4 169.254.116.39

Tracing route to 169.254.116.39 over a maximum of 30 hops

1 General failure.

Trace complete.

 

no internet & no network part-4

C:\Users\user>route print
================================================================
Interface List
11 ...00 1f e1 5a fe 1d ...... Atheros AR5007EG Wireless Network Adapter
10 ...00 1e 68 88 5a 9c ...... Marvell Yukon 88E8040T PCI-E Fast Ethernet Contr
oller
1 ........................... Software Loopback Interface 1
15 ...00 00 00 00 00 00 00 e0 isatap.{469824FF-22D4-4761-B815-54346C7C3DDE}
13 ...00 00 00 00 00 00 00 e0 6TO4 Adapter
14 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
12 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
================================================================

IPv4 Route Table
================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
169.254.0.0 255.255.0.0 On-link 169.254.158.149 276
169.254.158.149 255.255.255.255 On-link 169.254.158.149 276
169.254.255.255 255.255.255.255 On-link 169.254.158.149 276
192.168.0.0 255.255.255.0 On-link 192.168.0.1 286
192.168.0.1 255.255.255.255 On-link 192.168.0.1 286
192.168.0.255 255.255.255.255 On-link 192.168.0.1 286
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.0.1 286
224.0.0.0 240.0.0.0 On-link 169.254.158.149 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.0.1 286
255.255.255.255 255.255.255.255 On-link 169.254.158.149 276
================================================================
Persistent Routes:
None

IPv6 Route Table
================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
11 286 fe80::/64 On-link
10 276 fe80::/64 On-link
11 286 fe80::7d:a147:944c:7427/128 On-link
10 276 fe80::65e5:a89b:b647:9e95/128 On-link
1 306 ff00::/8 On-link
11 286 ff00::/8 On-link
10 276 ff00::/8 On-link
================================================================
Persistent Routes:
None

 

I've moved the four posts above from another thread as they deserve being reviewed separately.

 

That's all we need. Loop-back is failing. You've got a fundamental problem with TCP/IP Networking on the PC.

First thing to rule out is hardware. Reboot into Safemode with Network support. If you can now connect OK, we know it is not a hardware problem.

Next thing to check is firewalls. Try turning off you personal firewall and try again. Also check your anti-virus for settings that might block network ports.

The try reseting TCP/IP with:

netsh int ip reset c:\resetlog.txt - notes here.

 

Thanks Reggie,
Didn't work. Taked to my ISP Teach garu yesterday and he walked me through basically the same things I had done. The only thing different was he had me reset the winsocket. When that didn't work he surmised that it was a problem with the NIC card so I guess I'll have to take it in for repairs.
Thanks again,
Lou