Wifi Is Connected But Still Can Not Surf The Net

[DJboutit2]

Wifi is connected with a strong signal but I still can not surf the net I do not know what is up. I had to reinstall windows a few days ago router is a Dlink DIR-815 using a Amped UA600 usb apater to connected to wifi. I hooked up this usb adapter to another computer it can connect just I tryed a latop with wifi it connects to just I have no idea what is up anybody have any idea what is up??

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : phatbeat-t2hrl4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/1000 CT Network Connection
Physical Address. . . . . . . . . : 00-13-20-4B-98-68
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, June 03, 2011 1:19:33 AM
Lease Expires . . . . . . . . . . : Friday, June 10, 2011 1:19:33 AM

 

[johnb35]

Connection-specific DNS Suffix . :
DNS Servers . . . . . . . . . . . : 192.168.0.1

Unless this was a type, dns server is your router and that is why you can't get online. And also the connection specific dns suffix will tell you when you are actually connected as this will list your isp name.

How did you set up this router? The best way is to set IP and dns servers to automatic not to manual.

 

[Quiltface]

Well sometimes the routers will setup DNS server as the router and it will just forward dns requests to the public DNS servers.

try pinging 74.125.225.83

if that doesnt work then DNS isnt the issue here its a routing issue or the way your router is hooked up. or your internet is down.

if you can ping that then try pinging google.com

if the ip works and the FQDN does not then it is most likely a DNS issue, see if your router has public DNS servers entered in there... or you can try what john said and put your ISP's DNS servers in your DHCP scope or if you dont know what those are you can use googles 8.8.8.8 and 8.8.4.4