Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

My friend's laptop is able to connect to the WiFi router. Typing 192.168.1.1 in the browser shows the login page for the router. But he cannot connect to the Internet. This is true on both Windows and Linux (dual booting setup).

There are three other laptops connecting to the Internet via WiFi just fine and his was fine too until this happened all of a sudden. I tried doing a tracert from Windows to an external ip. The first hop to the modem is fine but then the packets seem to be getting dropped. I haven't asked a question here before but this is really weird. If anyone needs any more information I shall post it here.

EDIT : He can ping my PC wirelessly on the network and logon to the router login change settings on the router and all that stuff. Pinging any external IP fails. That's the crux of the problem.

If his WiFi adapter is damaged how is it connecting to the modem via WiFi?

Posting the contents of ipconfig /all.

Windows IP Configuration:

Host Name . . . . . . . . . . . . : praveen-laptop
Primary Dns Suffix  . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dslhome
                                    dslhome

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix  . : dslhome
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-21-5D-17-04-AC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, December 07, 2012 10:41:48 PM
Lease Expires . . . . . . . . . . : Saturday, December 08, 2012 10:41:48  PM

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix  . : dslhome
Description . . . . . . . . . . . : Marvell Yukon 88E8042 PCI-E Fast Ethernet Controller
Physical Address. . . . . . . . . : 00-22-64-54-9F-CB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, December 07, 2012 10:41:39 PM
Lease Expires . . . . . . . . . . : Saturday, December 08, 2012 10:41:39  PM

The problem is with the WiFi link.

share|improve this question
    
please post 'IPconfig /all' from the host. –  Frank Thomas Dec 7 '12 at 17:07
    
I'm assuming you have tried restarting the computer? –  Joshua Nurczyk Dec 7 '12 at 17:31
    
Well as you might have noted this occurs on both linux and windows. –  eddard stark Dec 7 '12 at 17:32
    
I'm not doing that great with reading comprehension I see... Sorry. –  Joshua Nurczyk Dec 7 '12 at 17:35
    
Can you connect with just LAN connection enabled (i.e. plug in ethernet, disable wifi)? And is your wifi router (192.168.1.1) really the DNS server? –  joel Dec 7 '12 at 18:46

5 Answers 5

Try manually setting up his DNS server. Go into the network and sharing center. Then open up the properties of his wireless router. Select IPv4 and type in your own DNS servers.

User Google's public DNS

8.8.8.8
8.8.4.4
share|improve this answer
    
I cant ping any external addresses. Only the modem –  eddard stark Dec 7 '12 at 17:25
    
Did you change the DNS server yet? –  JustinD Dec 7 '12 at 17:27
    
Yes I did.And I had tried pinging them even before you suggested changing it . –  eddard stark Dec 7 '12 at 17:28
    
Well I'm looking at your connections, and it looks to me like you're connecting through a server. Having your default gateway and DHCP server set to the router's IP is normal, but I'm not sure about the DNS, it's usually something else for what I've seen. That's why i made the recommendation. try using an nslookup command i.e. "nslookup www.microsoft.com" –  JustinD Dec 7 '12 at 17:31
1  
Name service doesn't relate to the OP's question so don't worry about the DNS. A lot of SOHO routers perform nslookup on device then pass the result to local nodes using NetBIOS over TCP/IP. That's what his router is doing. –  OCDtech Jan 14 '13 at 20:32

Try connecting your internet connection direct to your PC through ethernet. If that works, you are most likely looking at a router problem. I have had routers connect to the wireless and give IP addresses and all and still not deliver any internet.

share|improve this answer

If I understood correctly, the wired network works correctly on praveen-laptop but over Wifi, only local addresses can be reached ?

I would suggest:

  • Check with "route print" (windows) and "route -n" (linux) that you don't have some nasty manually set routes that send packets to a wrong default route. This easily happens with some VPNs.
  • Check that the IP address is not conflicting with another host on your network. praveen-laptop is in DHCP but another host could have been using .2 or .6 manually for some time and only causing trouble now.
  • It could be a limitation in the router. Some older crappy routers will only let you connect a handful of clients at once. Don't laugh, I've seen it more than once.
  • Did you try to restart the router ? Mine does weird things when it had too much torrent traffic.
  • In the router interface, you usually have a location that lists the active clients, their MAC and their IP. Anything weird ?

If all this fails and you're feeling adventurous, you can use wireshark (on Linux, it's easier) to "sniff" the traffic from a ping to an external IP. You should see where it's trying to go. If the packet leaves with 192.168.1.1 as destination, the problem is on the router's side. Otherwise, it's a clue.

share|improve this answer

I suggest you verify on your SOHO router's administration interface that there is no security rules forbidding external traffic on his Wireless NIC's IP or MAC.

You may also verify the router's internal routing table, it may have broken rules somehow.

share|improve this answer

If you are able to ping each other computer that means there is nothing wrong in wireless network however seems like your wireless router wan port is not plugged with ISP modem using a Ethernet cable or that cable needs a replace.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.