Cannot Connect Laptop To Wireless Network (resolved)

I have a Linksys WRT150N Wireless Router installed with a DSL Modem on a Dell Dimension 4700 PC running WIN XP SP2. I've run the Linksys Setup Wizard from the CD they include with the router and have no problem connecting to the web from the PC.

I can't seem to get my laptop (also WIN XP SP2) to connect however. When I list the available networks, the network I built with the wizard shows up but when I select it and try to connect, it fails.

Any idea what I'm doing wrong?

 

Don't bother posting answers to this thread - turns out I can't get a wired connection on the laptop either.

More later.

 

Just had an idea............Noahdfear and I did a lot of work repairing WMI on my other machine. I don't remember doing so, but I may have mistakenly made changes to my laptop's WMI. I've run the WMIDiag tool on the laptop and Noahdfear has agreed to take a look at the results - see below:
-----------------------------------------------

16550 13:43:26 (0) ** WMIDiag v2.0 started on Sunday, August 19, 2007 at 13:39.
16551 13:43:26 (0) **
16552 13:43:26 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
16553 13:43:26 (0) **
16554 13:43:26 (0) ** This script is not supported under any Microsoft standard support program or service.
16555 13:43:26 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
16556 13:43:26 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
16557 13:43:26 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
16558 13:43:26 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
16559 13:43:26 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
16560 13:43:26 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
16561 13:43:26 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
16562 13:43:26 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
16563 13:43:26 (0) ** of the possibility of such damages.
16564 13:43:26 (0) **
16565 13:43:26 (0) **
16566 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16567 13:43:26 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
16568 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16569 13:43:26 (0) **
16570 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16571 13:43:26 (0) ** Windows XP - Service pack 2 - 32-bit (2600) - User 'COMPUTER2\OWNER' on computer 'COMPUTER2'.
16572 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16573 13:43:26 (0) ** Environment: ........................................................................................................ OK..
16574 13:43:26 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
16575 13:43:26 (0) ** Drive type: ......................................................................................................... IDE (IC25N060ATMR04-0).
16576 13:43:26 (0) ** There are no missing WMI system files: .............................................................................. OK.
16577 13:43:26 (0) ** There are no missing WMI repository files: .......................................................................... OK.
16578 13:43:26 (0) ** WMI repository state: ............................................................................................... NOT TESTED.
16579 13:43:26 (0) ** BEFORE running WMIDiag:
16580 13:43:26 (0) ** The WMI repository has a size of: ................................................................................... 12 MB.
16581 13:43:26 (0) ** - Disk free space on 'C:': .......................................................................................... 39963 MB.
16582 13:43:26 (0) ** - INDEX.BTR, 1949696 bytes, 8/19/2007 12:10:51 PM
16583 13:43:26 (0) ** - INDEX.MAP, 984 bytes, 8/19/2007 12:32:55 PM
16584 13:43:26 (0) ** - MAPPING.VER, 4 bytes, 8/19/2007 12:32:56 PM
16585 13:43:26 (0) ** - MAPPING1.MAP, 6156 bytes, 8/19/2007 12:32:56 PM
16586 13:43:26 (0) ** - MAPPING2.MAP, 6156 bytes, 8/19/2007 12:30:10 PM
16587 13:43:26 (0) ** - OBJECTS.DATA, 10493952 bytes, 8/19/2007 12:10:51 PM
16588 13:43:26 (0) ** - OBJECTS.MAP, 5172 bytes, 8/19/2007 12:32:55 PM
16589 13:43:26 (0) ** AFTER running WMIDiag:
16590 13:43:26 (0) ** The WMI repository has a size of: ................................................................................... 12 MB.
16591 13:43:26 (0) ** - Disk free space on 'C:': .......................................................................................... 39957 MB.
16592 13:43:26 (0) ** - INDEX.BTR, 1949696 bytes, 8/19/2007 12:10:51 PM
16593 13:43:26 (0) ** - INDEX.MAP, 984 bytes, 8/19/2007 12:32:55 PM
16594 13:43:26 (0) ** - MAPPING.VER, 4 bytes, 8/19/2007 12:32:56 PM
16595 13:43:26 (0) ** - MAPPING1.MAP, 6156 bytes, 8/19/2007 12:32:56 PM
16596 13:43:26 (0) ** - MAPPING2.MAP, 6156 bytes, 8/19/2007 12:30:10 PM
16597 13:43:26 (0) ** - OBJECTS.DATA, 10493952 bytes, 8/19/2007 12:10:51 PM
16598 13:43:26 (0) ** - OBJECTS.MAP, 5172 bytes, 8/19/2007 12:32:55 PM
16599 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16600 13:43:26 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
16601 13:43:26 (0) ** Windows Firewall Profile: ........................................................................................... STANDARD.
16602 13:43:26 (0) ** Windows Firewall 'RemoteAdmin' status: .............................................................................. DISABLED.
16603 13:43:26 (0) ** => This will prevent any WMI remote connectivity to this machine.
16604 13:43:26 (0) ** - You can adjust the configuration by executing the following command:
16605 13:43:26 (0) ** i.e. 'NETSH.EXE FIREWALL SET SERVICE REMOTEADMIN ENABLE SUBNET'
16606 13:43:26 (0) **
16607 13:43:26 (0) ** Windows Firewall application exception for 'UNSECAPP.EXE': .......................................................... MISSING.
16608 13:43:26 (0) ** => This will prevent any script and MMC application asynchronous callbacks to this machine.
16609 13:43:26 (0) ** - You can adjust the configuration by executing the following command:
16610 13:43:26 (0) ** i.e. 'NETSH.EXE FIREWALL SET ALLOWEDPROGRAM C:\WINNT\SYSTEM32\WBEM\UNSECAPP.EXE WMICALLBACKS ENABLE'
16611 13:43:26 (0) **
16612 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16613 13:43:26 (0) ** DCOM Status: ........................................................................................................ OK.
16614 13:43:26 (0) ** WMI registry setup: ................................................................................................. OK.
16615 13:43:26 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
16616 13:43:26 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
16617 13:43:26 (0) ** - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Automatic')
16618 13:43:26 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
16619 13:43:26 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
16620 13:43:26 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
16621 13:43:26 (0) ** this can prevent the service/application to work as expected.
16622 13:43:26 (0) **
16623 13:43:26 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
16624 13:43:26 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
16625 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16626 13:43:26 (0) ** WMI service DCOM setup: ............................................................................................. OK.
16627 13:43:26 (0) ** WMI components DCOM registrations: .................................................................................. OK.
16628 13:43:26 (0) ** WMI ProgID registrations: ........................................................................................... OK.
16629 13:43:26 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
16630 13:43:26 (2) !! WARNING: WMI provider CIM registrations missing for the following provider(s): ...................................... 3 WARNING(S)!
16631 13:43:26 (0) ** - ROOT/INTELNCS, NcsEvent (i.e. WMI Class 'IANet_802dot3VlanEvent')
16632 13:43:26 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
16633 13:43:26 (0) ** - ROOT/INTELNCS, NcsEvent (i.e. WMI Class 'IANet_802dot3TeamEvent')
16634 13:43:26 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
16635 13:43:26 (0) ** - ROOT/INTELNCS, NcsEvent (i.e. WMI Class 'IANet_802dot3AdapterEvent')
16636 13:43:26 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
16637 13:43:26 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
16638 13:43:26 (0) ** while the CIM registration is wrong or missing. This can be due to:
16639 13:43:26 (0) ** - a de-installation of the software.
16640 13:43:26 (0) ** - a deletion of some CIM registration information.
16641 13:43:26 (0) ** => You can correct the CIM configuration by:
16642 13:43:26 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
16643 13:43:26 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
16644 13:43:26 (0) ** (This list can be built on a similar and working WMI Windows installation)
16645 13:43:26 (0) ** The following command line must be used:
16646 13:43:26 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
16647 13:43:26 (0) ** - Re-installing the software.
16648 13:43:26 (0) ** => If the software has been de-installed intentionally, then this information must be
16649 13:43:26 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove the provider
16650 13:43:26 (0) ** registration data and its set of associated classes.
16651 13:43:26 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\INTELNCS path __Win32Provider Where Name='NcsEvent' DELETE'
16652 13:43:26 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\INTELNCS Class IANet_802dot3AdapterEvent DELETE'
16653 13:43:26 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,
16654 13:43:26 (0) ** the namespace and ALL its content can be ENTIRELY deleted.
16655 13:43:26 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='INTELNCS' DELETE'
16656 13:43:26 (0) **
16657 13:43:26 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
16658 13:43:26 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
16659 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16660 13:43:26 (0) ** Overall DCOM security status: ....................................................................................... OK.
16661 13:43:26 (0) ** Overall WMI security status: ........................................................................................ OK.
16662 13:43:26 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
16663 13:43:26 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
16664 13:43:26 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name= "Microsoft WMI Updating Consumer Scenario Control ".
16665 13:43:26 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
16666 13:43:26 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name= "SCM Event Log Consumer ".
16667 13:43:26 (0) ** 'select * from MSFT_SCMEventLogEvent'
16668 13:43:26 (0) **
16669 13:43:26 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
16670 13:43:26 (0) ** WMI ADAP status: .................................................................................................... OK.
16671 13:43:26 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
16672 13:43:26 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
16673 13:43:26 (0) ** WMI GET operations: ................................................................................................. OK.
16674 13:43:26 (0) ** WMI MOF representations: ............................................................................................ OK.
16675 13:43:26 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
16676 13:43:26 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
16677 13:43:26 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
16678 13:43:26 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
16679 13:43:26 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
16680 13:43:26 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
16681 13:43:26 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
16682 13:43:26 (0) ** WMI static instances retrieved: ..................................................................................... 658.
16683 13:43:26 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
16684 13:43:26 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
16685 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16686 13:43:26 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
16687 13:43:26 (0) ** DCOM: ............................................................................................................. 0.
16688 13:43:26 (0) ** WINMGMT: .......................................................................................................... 6.
16689 13:43:26 (0) ** WMIADAPTER: ....................................................................................................... 0.
16690 13:43:26 (0) ** => Verify the WMIDiag LOG at line #16283 for more details.
16691 13:43:26 (0) **
16692 13:43:26 (0) ** # of additional Event Log events AFTER WMIDiag execution:
16693 13:43:26 (0) ** DCOM: ............................................................................................................. 0.
16694 13:43:26 (0) ** WINMGMT: .......................................................................................................... 0.
16695 13:43:26 (0) ** WMIADAPTER: ....................................................................................................... 0.
16696 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16697 13:43:26 (0) ** WMI Registry key setup: ............................................................................................. OK.
16698 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16699 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16700 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16701 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16702 13:43:26 (0) **
16703 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16704 13:43:26 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
16705 13:43:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16706 13:43:26 (0) **
16707 13:43:26 (0) ** WARNING: WMIDiag determined that WMI works CORRECTLY. HOWEVER, some issues were detected. Check 'C:\DOCUMENTS AND SETTINGS\OWNER\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.SP2.32_COMPUTER2_2007.08.19_13.39.03.LOG' for details.
16708 13:43:26 (0) **
16709 13:43:26 (0) ** WMIDiag v2.0 ended on Sunday, August 19, 2007 at 13:43 (W:80 E:5 S:2).

 

Hi Dave,

Search your harddrive for the following files. Make sure to search hidden and system files and folders.

NcsIa.mof
NcsCm.mof
NcsCo.mof

If you find them, any of them, run the mofcomp command using the full path.

Let me know!

 

Hi again Dave:

Sorry, I searched both the laptop and the PC but came up empty.

 

Can you post the Make and Model of the laptop, and/or the specs on the network connections devices (wired and wireless).

I may have located the required mof files, but now I need to find out where they should be located on your comp

 

The laptop is a Gateway Model M350X-C. I was also having trouble with the
CD/DVD drive so I brought it to a local PC repair outfit. When the've solved the drive issue, I've asked them to look into the connection problem as well.

I'll post a summary of the findings when I hear back from them.

 

I got the laptop back today and I can now access the web wirelessly via my Linksys router. The person who got it running said my connection problem was caused by a fouled up TCP/IP stack and he fixed the problem by running a utility called WinsockxpFix.exe.

To Noahdfear - I've checked Device Manager. Under Network Adapters it lists:

1394 NetAdapter
Broadcom 802.11 Network Adapter
Intel PRO/100 VE Network Connection

I searched again for the three mof files and still came up dry. I did find three other files with similar names however (NcsCmLn.mof, NcsCoD.mof, and NcsCoLn.mof). All three are in C:\Program Files\Intel\NCS\WMIProv.

It appears the missing files aren't necessary though since as mentioned above, I no longer have a connection problem.

 

Glad to hear things are working again. I wouldn't bother chasing after those mof files anymore at this point.

 

I would bet that it is a result of interference from a neighbors router signal drifting in
change the channel from the default 6
1 and 11 are the next best picks
Change the ssid as well
Ensure that the router is high and uncluttered
As well sometimes just moving the router a foot or two over can help

 

resolved