Windows 7: LAN/Wired Local Area Connection - Unidentified Network; No Internet

Hi Guys, I have been experiencing this issue since 3 days ago. (1 year on and was having no problems)

I am currently using a Dell Studio XPS 16, Windows 7 64-bit

I am able to connect to the internet via wifi, however to no avail with my LAN connection. I have tried the basic stuff like changing LAN cables, testing connection with other Windows 7/Vista/XP laptops and they worked except for mine.

I have tried methods posted online such as the netsh winsock reset, disabling IPv6, setting static IP for IPv4 etc. However, none has worked for me.

Below is my ipconfig/all :
137.132.5.199Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Christopher Koh>ipconfig/all



Windows IP Configuration

Host Name . . . . . . . . . . . . : ChristopherKoh
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : nus.edu.sg
mshome.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : nus.edu.sg
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 00-22-19-F8-C1-77
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ed35:5ea:c983:4061%12(Preferred)
IPv4 Address. . . . . . . . . . . : 172.19.109.229(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Lease Obtained. . . . . . . . . . : Friday, 24 September, 2010 12:41:43 AM
Lease Expires . . . . . . . . . . : Friday, 24 September, 2010 1:11:42 AM
Default Gateway . . . . . . . . . : fe80::50d8:626c:9cf2:f16d%12
fe80::b5c8:b699:165e:bf69%12
fe80::4475:3e89:d454:4aa2%12
172.19.96.1
DHCP Server . . . . . . . . . . . : 137.132.5.246
DHCPv6 IAID . . . . . . . . . . . : 268444185
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-A9-1F-2E-00-22-19-F8-C1-77

DNS Servers . . . . . . . . . . . : 137.132.0.252
137.132.0.254
Primary WINS Server . . . . . . . : 137.132.4.5
Secondary WINS Server . . . . . . : 137.132.4.25
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : nus.edu.sg
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-22-FB-9B-83-C0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a9b7:be29:49f2:a1e8%11(Preferred)
IPv4 Address. . . . . . . . . . . : 172.17.186.97(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.224.0
Lease Obtained. . . . . . . . . . : Friday, 24 September, 2010 12:27:44 AM
Lease Expires . . . . . . . . . . : Friday, 24 September, 2010 2:04:35 AM
Default Gateway . . . . . . . . . : fe80::e4af:bf2a:4a22:8847%11
fe80::10d8:a2c6:8702:eafd%11
fe80::b5a0:17c:8b35:1db9%11
fe80::a54d:895d:d276:b961%11
fe80::d1ef:27ef:38da:1c49%11
172.17.160.1
DHCP Server . . . . . . . . . . . : 137.132.5.199
DHCPv6 IAID . . . . . . . . . . . : 184558331
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-A9-1F-2E-00-22-19-F8-C1-77

DNS Servers . . . . . . . . . . . : fe80::85a6:37c4:4cfe:40a0%11
137.132.0.254
137.132.0.252
Primary WINS Server . . . . . . . : 137.132.4.5
Secondary WINS Server . . . . . . : 137.132.4.25
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
mshome.net

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3444:f62a:767b:1bfa(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::3444:f62a:767b:1bfa%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.nus.edu.sg:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : nus.edu.sg
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Can anyone help me??????

You should automatically obtain your ip address, dns, and gateway, unless directed otherwise by your isp.
Did you "power down/power up" your cable modem and wireless router?
Check to make sure you have the latest driver for your network card.
Can you ping an ip address? Can you ping the router? Can you connect to the router?
Do you have to contend with a firewall from the National University of Singapore?
Researching more. Let me know about this...

http://www.nus.edu.sg/comcen/gethelp...%20Changes.pdf

Did you "power down/power up" your cable modem and wireless router?
What do you mean here? Anyways, I can't power down or up the school's modem.
Check to make sure you have the latest driver for your network card.
I have the latest driver.

Can you ping an ip address?
Can you ping the router?
Can you connect to the router?
For the 3 questions above, I suppose I have to switch off my WIFI connection before executing?

Do you have to contend with a firewall from the National University of Singapore?
This should not post as a possibility as I have been well on the connection for the past 1 year with the same laptop on Windows 7.

Default Gateway . . . . . . . . . : fe80::e4af:bf2a:4a22:8847%11
fe80::10d8:a2c6:8702:eafd%11
fe80::b5a0:17c:8b35:1db9%11
fe80::a54d:895d:d276:b961%11
fe80::d1ef:27ef:38da:1c49%11
172.17.160.1 < most likely the correct default gateway for this network.

The ipconfig read out from this network is pretty messed up so it's hard to say what the problem is.

Default Gateway . . . . . . . . . : fe80::50d8:626c:9cf2:f16d%12
fe80::b5c8:b699:165e:bf69%12
fe80::4475:3e89:d454:4aa2%12
172.19.96.1 < other possible default gateway

You might also try ipconfig /release command then ipconfig /renew typed into your command prompt.


Everything in bold red isn't supposed to be there. You might try going into your ipv4 properties and enter the correct default gateway manually. Enter 172.17.160.1 or 172.19.96.1 for your default gateway like in the picture below.

I think he hardcoded things which is probably not good. Nothing should be changed in ipv6. In ipv4, use defaults unless directed by the network admin.
c:ipconfig /release
c:ipconfig /renew
c: ping 128.163.16.242
If good, then
c: ping University of Kentucky - Welcome to the University of Kentucky
If successful let us know.

chev65, that garbage you notice is link local ipv6 address.

With due respect I know exactly what they are and the ipv6 address info is absolutely not supposed to be under the default gateway. I have seen this stange IPv6 address problem create problems in the past, in fact I helped someone with a similar problem just the other day and simply typing in the correct default gateway into the IPv4 properties fixed it. This is standard procedure for this unidentified network problem. It usually is caused by an out of date router firmware or using an improper driver.

And I agree that this should be done using DHCP, this is one messed up ipconfig in my book.

And why did you repeat what I just said about releasing and renewing the ip, maybe I added that after you did LOL? You do not need to put a C in front of those ipconfig commands.

With respect as well, I assumed you knew this. If I repeated, it's b/c I'm multi-tasking at work.
The C: was b/c I thought when using a command prompt, he would see something like:
C:\Users\Epilogue10
I didn't know what his level of expertise was.
Also, he didn't say he was at a university, so I thought it could be a router issue. Then I rechecked his dns and saw he was at National University of Singapore.

Meanwhile, I don't see the OP responding.

I figured so on the multi tasking LOL.

The problem with these university's is that if you have a router problem you can't just reset the router so going into the IPv4 properties is one way around that. I'm thinking router also by the way but it sucks when you can't actually access the router in these situations.

It's a top - down hierarchy with IT. If you don't control your hardware firewalls (Cisco pix for me), your routers, etc., then it's a major headache. Especially telling that he can get an ip from the wireless nic.