Sign in with
Sign up | Sign in
Your question

Wireless connected but no internet access

Last response: in Wireless Networking
Share
October 11, 2010 10:32:02 PM

Hello,
I have been unable to connect to the internet for 3 days. The settings for the network have worked for 6 months and just stopped suddenly. The computer says that I am connected with excellent signal quality. I ran a dignostic and here are the results:

Internet Service
+ Default Outlook Express Mail
mail / mail
FAILED

+ Default Outlook Express News
news
FAILED

  Internet Explorer Web Proxy
Not Configured

Computer Information
+ Computer System
JP


+ Operating System
Microsoft Windows XP Professional


+ Version
5.1.2600


Modems and Network Adapters
+ Modems
Standard Modem


- Network Adapters

FAILED
+ [00000008] Intel(R) PRO/1000 MT Network Connection
- [00000020] Linksys Wireless-G PCI Adapter (FAILED)
  Caption = [00000020] Linksys Wireless-G PCI Adapter
  DatabasePath = %SystemRoot%\System32\drivers\etc
+ DefaultIPGateway = 192.168.1.1(Same Subnet) (PASSED)
  Description = Linksys Wireless-G PCI Adapter - Packet Scheduler Miniport
  DHCPEnabled = TRUE
  DHCPLeaseExpires = 10:49:29 PM 10/11/2010
  DHCPLeaseObtained = 10:49:29 PM 10/10/2010
+ DHCPServer = 192.168.1.1 (PASSED)
  DNSDomain = home
  DNSEnabledForWINSResolution = FALSE
  DNSHostName = JP
- DNSServerSearchOrder (FAILED)
+ 192.168.1.1 (PASSED)
+ 71.252.0.12 (FAILED)
  DomainDNSRegistrationEnabled = FALSE
  FullDNSRegistrationEnabled = TRUE
  GatewayCostMetric = 25
  Index = 20
+ IPAddress = 192.168.1.7 (PASSED)
  IPConnectionMetric = 25
  IPEnabled = TRUE
  IPFilterSecurityEnabled = FALSE
  IPSecPermitIPProtocols = 0
  IPSecPermitTCPPorts = 0
  IPSecPermitUDPPorts = 0
  IPSubnet = 255.255.255.0
  IPXEnabled = FALSE
  MACAddress = 00:14:BF:77:EF:9D
  ServiceName = RT2500
  SettingID = {516B0F06-7770-4E02-881E-7F40E525D21E}
  TcpipNetbiosOptions = 0
  WINSEnableLMHostsLookup = TRUE
Anonymous
a b F Wireless
October 12, 2010 5:21:01 AM

If you are using wireless, try connecting computer to router by ethernet cable instead and see if that cures it -- may suggest where the problem lies.
m
0
l
Related resources
!