Pinging 127.0.0.1 wouldn't do any good. Thats your computer! You're probably trying to connect using a WLAN IPaddress that's already assigned, or your router that thinks assigned. Im not a windows person so don't really know.

Get a Mac?

Ha!

Get a life!

Open a command prompt and enter the following one by one:


ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int reset all
netsh int ip reset
netsh winsock reset


Reboot.

Edited by Deadbeat (Mon 29-Jun-09 23:31:18)

I know this is fairly basic stuff but have you followed Microsoft's Advice to "Open Network Diagnostics by right-clicking the network icon in the notification area, and then clicking Diagnose and repair"?

I expect that you have already done this but if not give it a go. Also have a look at the section "I can't connect to my home network" in the link. Sorry if I'm stating the obvious.

Yup, tried em all several times. Thanks for ideas though.

Posting back soon about Deadbeat's suggestion.

(Another obvious one, but - hey.) Does the light on the router light up on the port that you have the PC plugged in to? And does it flicker when you try to ping the router?

Here's the command-by-command CLI text, followed by an ipconfig/all on restart:

ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int reset all
netsh int ip reset
netsh winsock reset

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Windows\system32>nbtstat -R
Successful purge and preload of the NBT Remote Cache Name Table.

C:\Windows\system32>nbtstat -RR
The NetBIOS names registered by this computer have been refreshed.


C:\Windows\system32>netsh int reset all


C:\Windows\system32>netsh int ip reset
Reseting Echo Request, failed.
Access is denied.

Reseting Global, OK!
Reseting Interface, OK!
Reseting Unicast Address, OK!
Reseting Route, OK!
A reboot is required to complete this action.


C:\Windows\system32>netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.


C:\Windows\system32>


-----


Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : XXXXXXXXXXXXXXXXXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
it Ethernet NIC (NDIS 6.0) #2
Physical Address. . . . . . . . . : 00-1F-D0-81-04-D5
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::adf5:282f:5121:4e9b%14(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.78.155(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 268443600
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-59-D9-1A-00-1F-D0-9B-55-FE

DNS Servers . . . . . . . . . . . : 212.159.13.49
212.159.13.50
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
it Ethernet NIC (NDIS 6.0)
Physical Address. . . . . . . . . : 00-1F-D0-9B-55-FE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{735E3CE7-C0FE-476D-8117-774434F33
5FA}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{D8E151C1-C0E1-49CE-9625-2B8C62F91
278}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Windows\system32>

Router port(s) have been checked. Cable has been tested with other node. NIC lights flash like the dickens...best guess is they are 'training' or at least attempting to get an 'ack' of some sort. Solid green light and occasional flashing orange. Router is working fine (laptop is connected as I type on it).

It 'seems' to be a logical problem. As I said before, I setup the IP on the PC as a standard private IP, but when I tell it to ping the router's IP, the (unsuccessful) replies are from the same IP number that the PC is set to. If I ping loopback, it's fine and if I ping the PC's private IP, it's fine. No other networking ports seem to be working (updates, tracert, telnet, http), so it's global in that sense.

In my BIOS, the LAN port 1 is disabled (no need to run two at present). The 'Green LAN' setting is disabled (auto detector for network cable presence). The setting for LAN Boot ROM is disabled (default).

I'm pretty damn sure it's the Vista ipv4 autoconfig that's snarling it all up.

Edited by camieabz (Tue 30-Jun-09 11:17:01)

when I tell it to ping the router's IP, the (unsuccessful) replies are from the same IP number that the PC is set to.

That's as should be. If I try and ping a non-existant address on my (working) connection I get:

Pinging 192.168.1.123 with 32 bytes of data:
Reply from 192.168.1.12: Destination host unreachable.
Reply from 192.168.1.12: Destination host unreachable.
Reply from 192.168.1.12: Destination host unreachable.
Reply from 192.168.1.12: Destination host unreachable.

192.168.1.123 doesn't exist, 192.168.1.12 is the PC.

I would be inclined to try enabling the other LAN port and see if that one works. To me it sounds like a hardware or driver problem.

Well for what it's worth, I deleted and let windows detect and reinstall the LAN connection. No probs.