Roommate can't connect

[TheBiggmann]

I just set up a wireless router at our house and 5 of us have no issues, but one roommate can't connect to the internet. He can connect to the network but it will say local only when you mouse over the icon in the notification area and when you try and go to a website it says "The server can't be found because the DNS lookup failed." and in the bottom left of the screen it says "error 105 (net: ERR_NAME_NOT_RESOLVED) Unable to resolve the server's DNS address." Any ideas?

 

[MtnMan]

Is the IP address it picks up valid, or does it have a 169.254.xxx.xxx address. Is it configured to obtain an IP address automatically vs. a static?

Can he ping the router, typically 192.168.1.1.

 

[JackMDS]

From an Admin command prompt type ipconfig /all >Desktop\Ipconfig.txt and press Enter.

Open the Ipconfig.txt file with notepad copy and paste its content onto a post.

 

[TheBiggmann]

I dont recall what the IP adress was for him, but its set to obtain it automatically. I also set up a static IP and it didnt change anything. When I'm in the router settings it shows it as connected when you look at the devices connected. I'll post the ipconfig text tomorrow when I can get back on his computer.

 

[TheBiggmann]

Windows IP Configuration

Host Name . . . . . . . . . . . . : Jay-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Atheros AR5007 802.11b/g WiFi Adapter
Physical Address. . . . . . . . . : 00-1F-3A-5B-1F-18
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::21fe:d008:1d8d:ed6e%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, September 02, 2011 12:32:21 PM
Lease Expires . . . . . . . . . . : Saturday, September 03, 2011 12:35:12 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 335552314
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-73-48-18-00-1E-68-2D-E9-8C

DNS Servers . . . . . . . . . . . : fe80::2dbf:c6ce:9843:a565%11
192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
mshome.net

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-1E-68-2D-E9-8C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

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

Tunnel adapter Local Area Connection* 7:

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

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{582F547D-FCA4-4631-A8E4-95D50A44C
30D}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

 

[Gryz]

The first thing I would do is disable IPv6. It seems DHCP gave you 2 DNS-servers. One IPv6 and one IPv4 ip-address to reach a DNS server. Now I don't know if order is significant, but I find it suspicious that the IPv6 address is listed before the IPv4 address. With a little bad luck, the PC will try to resolve all DNS requests via IPv6. If you don't really have IPv6 connectivity to the outside world, then DNS requests will fall on the floor. Whether your PC (or your router) will try again (over IPv4) is a matter of implementation, and might trigger a bug or incompatibility.

(Note, I have zero experience with IPv6 on Windows, so this might not be the issues. But I think it's worth trying to simply disable IPv6. I'd disable it anyway, it's useless (this decade at least)).

 

[TheBiggmann]

I disabled IPV6, no luck :/

 

[mammador]

I don't think IPv6 is the issue, since IPv6 cannot operate directly on IPv4 networks. This is why dual stack and tunneling are common. it's just a proactive measure that MS put in Windows 7.

It may just be has your friend's wi-fi NIC is faulty.

 

[TheBiggmann]

If it was faulty wouldnt it not work anywhere though? It works everywhere he's tried except at our house, and he's the only person out of 6 roommates that it doesnt work for.

 

[JackMDS]

The IP and connection to the Router looks OK.

1. Make sure that there is No security configuration on the Router that reject the computer's Wireless (like MAC Filter).

2. On the computer make sure that the Firewall is Not blocking the Browser for your IP subnet.

 

[TheBiggmann]

Not sure how to check on the MAC filter, aka where to find it in the firmware. Looked around and all I found about MAC was a section titled Router MAC Address, with the options, use default MAC address, use computer MAC address, or use this MAC address where there was one listed after it. It's set to default.

 

[Gryz]

The normal way to troubleshoot a problem like this is to test everything step by step. So you know exactly what goes wrong, and what works. This is a process that is pretty hard (or bothersome) to do via a forum. You need to improvise a bit.

The error message says it's a DNS error. I suspect that is simply because DNS-requests are the first thing a PC tries to do (when surfing). But maybe it is indeed a DNS problem. So you should test to see if regular IP connectivity works.

Ping the router. Ping 192.168.1.1. Does that work ?
Ping something on the Internet. Ping a root nameserver. These ones answered me: 192.5.5.241, 198.41.0.4, 192.36.148.17. So try to ping those. If you can't ping those, do a "traceroute -n <ipaddr>" to see how far you are getting out. (Maybe do the same tests on a working PC, so you can compare).

If you can't find the configuration page on your router to block MAC-addresses, then your router might not have that feature (mine doesn't).

 

[zCypher]

Is it a laptop or desktop? What's the OS? Was that computer ever able to connect to that wifi network? Is the IP address set to automatic or was it specifically set in the TCP/IP (v4) properties? Definitely make sure IP/DNS set to automatic for the wireless network connection. Disconnect from the network, remove any existing wifi profile, disable/re-enable and then reconnect to wifi again and see if it works.

Good luck!