workgroup is not accessible

gdemaria
gdemaria used Ask the Experts™
on
I am running windows XP Pro in my home office network.

When I click on View WorkGroup Computers, I get the following error message:

<workgroupname> workgroup is not accessible. you might not have permission to use this network

When I choose "My Network Places" the folder is completely empty except for "My Web Sites on MSN"

I've read a lot about this on the web, but haven't found a solution yet
Thanks for any help!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Britt ThompsonSr. Systems Engineer
Top Expert 2009

Commented:
Make sure file and printer sharing is enabled on the machines. Also, for testing purposes, disable all firewalls to eliminate that as the possibility.
Yes, I had tried those. Thanks.
Britt ThompsonSr. Systems Engineer
Top Expert 2009

Commented:
In the NIC properties under WINS enable NETBIOS over TCP/IP
11/26 Forrester Webinar: Savings for Enterprise

How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.

Check that the Computer Browser, DNS Client, DHCP Client, NetLogon and Network Connections services are set to Automatic and are started. Check this by going to Start, Run, type "services.msc" (no quotes) <hit enter>.
How does one get to WINS ?

.. this is Windows XP Pro
Britt ThompsonSr. Systems Engineer
Top Expert 2009

Commented:
Control Panel > Network Connections > Right Click on Local Area Network Connection (assuming your hardwired, choose your connected adapter) > Properties > Find TCP/IP > Properties > Advanced > WINS tab
@and,  I did this.  NetLogon was not started, when I started it, it stopped again and presented a message that some servers automatically stop when the have no work to do.  I believe that is used for a Domain, I am using a workgroup.

The others were up and running.

Thanks
@renazonse, thanks, I found that.  It was set to "default"  I changed it..
same error, but do you think I need to reboot?
Netlogon should not start and stop like that - even for a workgroup PC. Check the Event Viewer (Start, Run, type "eventvwr" <hit enter) for any errors that correspond to the service starting and stopping, and list them here.
 

Here are the warnings/errors from my Event Viewer:

------------------------------------------------------------------------------------
5:00 PM

This computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

------------------------------------------------------------------------------------
4:04 PM - Source: DCOM

The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

------------------------------------------------------------------------------------
3:47 PM  - Source is Service Control Manager

The MLPTDR_B service depends on the Parallel arbitrator group and no member of this group started.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

------------------------------------------------------------------------------------
Britt ThompsonSr. Systems Engineer
Top Expert 2009

Commented:
Control Panel > Network Connections > Right Click on Local Area Network Connection (assuming your hardwired, choose your connected adapter) > Properties > Verify there is a "Client for Microsoft Networks" client installed and checked
Did you create the same user list on all computers that you want to access in the workgroup? If it's a peer-to-peer network with Windows XP you must have the same user list on all computers in the workgroup and they must have the SAME username AND password on all the computers.
@premillard, that's a good tip, thank you.  I suspect that some users are not on all PCs.  I do know that at least my account is the same, however.

The curious thing here is that the network area is empty, it does not even list the workgroup name.   I only get the error, so I am thinking I am not getting far enough to even see if the user account matches.  
The error you reported: "The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout." may be significant.
This CLSID referes to WMI. Check the WMI Repository for errors: http://windowsxp.mvps.org/repairwmi.htm
(WMI Diagnosis Utility) http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en

 
Ok, here are the results of the RepairWMI...  Overall it said setup was OK but there were some errors...
20332 17:44:25 (0) ** WMIDiag v2.0 started on Monday, July 20, 2009 at 17:40.
20333 17:44:25 (0) ** 
20334 17:44:25 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
20335 17:44:25 (0) ** 
20336 17:44:25 (0) ** This script is not supported under any Microsoft standard support program or service.
20337 17:44:25 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
20338 17:44:25 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
20339 17:44:25 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
20340 17:44:25 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
20341 17:44:25 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
20342 17:44:25 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
20343 17:44:25 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
20344 17:44:25 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
20345 17:44:25 (0) ** of the possibility of such damages.
20346 17:44:25 (0) ** 
20347 17:44:25 (0) ** 
20348 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20349 17:44:25 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
20350 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20351 17:44:25 (0) ** 
20352 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20353 17:44:25 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'OFFICE\GEORGE' on computer 'OFFICE'.
20354 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20355 17:44:25 (2) !! WARNING: => The PATH is longer than the supported PATH length:
20356 17:44:25 (0) **           The maximum PATH length must be made of 512 positions.
20357 17:44:25 (0) **           However, the current PATH length is be made of 549 positions.
20358 17:44:25 (0) **           - C:\WINDOWS\SYSTEM32;C:\WINDOWS;C:\WINDOWS\SYSTEM32\WBEM;C:\PROGRAM FILES\ATI TECHNOLOGIES\ATI.ACE\;C:\PROGRAM FILES\COMMON FILES\ROXIO SHARED\DLLSHARED\;C:\PROGRAM FILES\COMMON FILES\ROXIO SHARED\9.0\DLLSHARED\;C:\PROGRA~1\ABSOLU~1;C:\PROGRAM FILES\MICROSOFT SQL SERVER\80\TOOLS\BINN\;C:\PROGRAM FILES\MICROSOFT SQL SERVER\90\TOOLS\BINN\;C:\PROGRAM FILES\MICROSOFT SQL SERVER\90\DTS\BINN\;C:\PROGRAM FILES\MICROSOFT SQL SERVER\90\TOOLS\BINN\VSSHELL\COMMON7\IDE\;C:\PROGRAM FILES\PINNACLE\SHARED FILES\;C:\PROGRAM FILES\PINNACLE\SHARED FILES\FILTER\\
20359 17:44:25 (0) **           When the PATH environment variable is too long the bottom part of the path is ignored, which
20360 17:44:25 (0) **           could prevent the system to work properly.
20361 17:44:25 (0) ** INFO: => 4 incorrect shutdown(s) detected on:
20362 17:44:25 (0) **          - Shutdown on 21 June 2009 03:08:49 (GMT+4).
20363 17:44:25 (0) **          - Shutdown on 21 June 2009 09:21:35 (GMT+4).
20364 17:44:25 (0) **          - Shutdown on 21 June 2009 20:17:09 (GMT+4).
20365 17:44:25 (0) **          - Shutdown on 26 June 2009 09:41:46 (GMT+4).
20366 17:44:25 (0) ** 
20367 17:44:25 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
20368 17:44:25 (0) ** Drive type: ......................................................................................................... IDE (WDC WD3200AAKS-75L9A0).
20369 17:44:25 (0) ** There are no missing WMI system files: .............................................................................. OK.
20370 17:44:25 (0) ** There are no missing WMI repository files: .......................................................................... OK.
20371 17:44:25 (0) ** WMI repository state: ............................................................................................... N/A.
20372 17:44:25 (0) ** BEFORE running WMIDiag:
20373 17:44:25 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
20374 17:44:25 (0) ** - Disk free space on 'C:': .......................................................................................... 75959 MB.
20375 17:44:25 (0) **   - INDEX.BTR,                     1163264 bytes,      7/20/2009 5:05:41 PM
20376 17:44:25 (0) **   - INDEX.MAP,                     624 bytes,          7/20/2009 5:05:41 PM
20377 17:44:25 (0) **   - OBJECTS.DATA,                  6283264 bytes,      7/20/2009 5:05:41 PM
20378 17:44:25 (0) **   - OBJECTS.MAP,                   3116 bytes,         7/20/2009 5:05:41 PM
20379 17:44:25 (0) ** AFTER running WMIDiag:
20380 17:44:25 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
20381 17:44:25 (0) ** - Disk free space on 'C:': .......................................................................................... 75957 MB.
20382 17:44:25 (0) **   - INDEX.BTR,                     1163264 bytes,      7/20/2009 5:41:41 PM
20383 17:44:25 (0) **   - INDEX.MAP,                     624 bytes,          7/20/2009 5:41:41 PM
20384 17:44:25 (0) **   - OBJECTS.DATA,                  6283264 bytes,      7/20/2009 5:41:41 PM
20385 17:44:25 (0) **   - OBJECTS.MAP,                   3116 bytes,         7/20/2009 5:41:41 PM
20386 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20387 17:44:25 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
20388 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20389 17:44:25 (0) ** DCOM Status: ........................................................................................................ OK.
20390 17:44:25 (0) ** WMI registry setup: ................................................................................................. OK.
20391 17:44:25 (0) ** WMI Service has no dependents: ...................................................................................... OK.
20392 17:44:25 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
20393 17:44:25 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
20394 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20395 17:44:25 (0) ** WMI service DCOM setup: ............................................................................................. OK.
20396 17:44:25 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
20397 17:44:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
20398 17:44:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
20399 17:44:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
20400 17:44:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
20401 17:44:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
20402 17:44:25 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
20403 17:44:25 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
20404 17:44:25 (0) **    fail depending on the operation requested.
20405 17:44:25 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
20406 17:44:25 (0) ** 
20407 17:44:25 (0) ** WMI ProgID registrations: ........................................................................................... OK.
20408 17:44:25 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
20409 17:44:25 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
20410 17:44:25 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
20411 17:44:25 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
20412 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20413 17:44:25 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20414 17:44:25 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
20415 17:44:25 (0) **        - ACTUAL ACE:
20416 17:44:25 (0) **          ACEType:  &h0
20417 17:44:25 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20418 17:44:25 (0) **          ACEFlags: &h2
20419 17:44:25 (0) **                    CONTAINER_INHERIT_ACE
20420 17:44:25 (0) **          ACEMask:  &h1
20421 17:44:25 (0) **                    WBEM_ENABLE
20422 17:44:25 (0) **        - EXPECTED ACE:
20423 17:44:25 (0) **          ACEType:  &h0
20424 17:44:25 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20425 17:44:25 (0) **          ACEFlags: &h12
20426 17:44:25 (0) **                    CONTAINER_INHERIT_ACE
20427 17:44:25 (0) **                    INHERITED_ACE
20428 17:44:25 (0) **          ACEMask:  &h13
20429 17:44:25 (0) **                    WBEM_ENABLE
20430 17:44:25 (0) **                    WBEM_METHOD_EXECUTE
20431 17:44:25 (0) **                    WBEM_WRITE_PROVIDER
20432 17:44:25 (0) ** 
20433 17:44:25 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
20434 17:44:25 (0) **    This will cause some operations to fail!
20435 17:44:25 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
20436 17:44:25 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20437 17:44:25 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20438 17:44:25 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
20439 17:44:25 (0) **       A specific WMI application can always require a security setup different
20440 17:44:25 (0) **       than the WMI security defaults.
20441 17:44:25 (0) ** 
20442 17:44:25 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20443 17:44:25 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
20444 17:44:25 (0) **        - ACTUAL ACE:
20445 17:44:25 (0) **          ACEType:  &h0
20446 17:44:25 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20447 17:44:25 (0) **          ACEFlags: &h2
20448 17:44:25 (0) **                    CONTAINER_INHERIT_ACE
20449 17:44:25 (0) **          ACEMask:  &h1
20450 17:44:25 (0) **                    WBEM_ENABLE
20451 17:44:25 (0) **        - EXPECTED ACE:
20452 17:44:25 (0) **          ACEType:  &h0
20453 17:44:25 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20454 17:44:25 (0) **          ACEFlags: &h12
20455 17:44:25 (0) **                    CONTAINER_INHERIT_ACE
20456 17:44:25 (0) **                    INHERITED_ACE
20457 17:44:25 (0) **          ACEMask:  &h13
20458 17:44:25 (0) **                    WBEM_ENABLE
20459 17:44:25 (0) **                    WBEM_METHOD_EXECUTE
20460 17:44:25 (0) **                    WBEM_WRITE_PROVIDER
20461 17:44:25 (0) ** 
20462 17:44:25 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
20463 17:44:25 (0) **    This will cause some operations to fail!
20464 17:44:25 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
20465 17:44:25 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20466 17:44:25 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20467 17:44:25 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
20468 17:44:25 (0) **       A specific WMI application can always require a security setup different
20469 17:44:25 (0) **       than the WMI security defaults.
20470 17:44:25 (0) ** 
20471 17:44:25 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
20472 17:44:25 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
20473 17:44:25 (0) **        - REMOVED ACE:
20474 17:44:25 (0) **          ACEType:  &h0
20475 17:44:25 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20476 17:44:25 (0) **          ACEFlags: &h12
20477 17:44:25 (0) **                    CONTAINER_INHERIT_ACE
20478 17:44:25 (0) **                    INHERITED_ACE
20479 17:44:25 (0) **          ACEMask:  &h13
20480 17:44:25 (0) **                    WBEM_ENABLE
20481 17:44:25 (0) **                    WBEM_METHOD_EXECUTE
20482 17:44:25 (0) **                    WBEM_WRITE_PROVIDER
20483 17:44:25 (0) ** 
20484 17:44:25 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20485 17:44:25 (0) **    Removing default security will cause some operations to fail!
20486 17:44:25 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
20487 17:44:25 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
20488 17:44:25 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
20489 17:44:25 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
20490 17:44:25 (0) **       A specific WMI application can always require a security setup different
20491 17:44:25 (0) **       than the WMI security defaults.
20492 17:44:25 (0) ** 
20493 17:44:25 (0) ** 
20494 17:44:25 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
20495 17:44:25 (0) ** DCOM security error(s) detected: .................................................................................... 0.
20496 17:44:25 (0) ** WMI security warning(s) detected: ................................................................................... 0.
20497 17:44:25 (0) ** WMI security error(s) detected: ..................................................................................... 3.
20498 17:44:25 (0) ** 
20499 17:44:25 (0) ** Overall DCOM security status: ....................................................................................... OK.
20500 17:44:25 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
20501 17:44:25 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
20502 17:44:25 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
20503 17:44:25 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
20504 17:44:25 (0) **   'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
20505 17:44:25 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
20506 17:44:25 (0) **   'select * from MSFT_SCMEventLogEvent'
20507 17:44:25 (0) ** 
20508 17:44:25 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
20509 17:44:25 (0) ** WMI ADAP status: .................................................................................................... OK.
20510 17:44:25 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
20511 17:44:25 (0) ** - ROOT/SERVICEMODEL.
20512 17:44:25 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
20513 17:44:25 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
20514 17:44:25 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
20515 17:44:25 (0) **    i.e. 'WMIC.EXE /NODE:"OFFICE" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
20516 17:44:25 (0) ** 
20517 17:44:25 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
20518 17:44:25 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
20519 17:44:25 (0) ** WMI GET operations: ................................................................................................. OK.
20520 17:44:25 (0) ** WMI MOF representations: ............................................................................................ OK.
20521 17:44:25 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
20522 17:44:25 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
20523 17:44:25 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
20524 17:44:25 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
20525 17:44:25 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
20526 17:44:25 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
20527 17:44:25 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
20528 17:44:25 (0) ** WMI static instances retrieved: ..................................................................................... 675.
20529 17:44:25 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
20530 17:44:25 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
20531 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20532 17:44:25 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
20533 17:44:25 (0) **   DCOM: ............................................................................................................. 31.
20534 17:44:25 (0) **   WINMGMT: .......................................................................................................... 2.
20535 17:44:25 (0) **   WMIADAPTER: ....................................................................................................... 0.
20536 17:44:25 (0) ** => Verify the WMIDiag LOG at line #19926 for more details.
20537 17:44:25 (0) ** 
20538 17:44:25 (0) ** # of additional Event Log events AFTER WMIDiag execution:
20539 17:44:25 (0) **   DCOM: ............................................................................................................. 0.
20540 17:44:25 (0) **   WINMGMT: .......................................................................................................... 0.
20541 17:44:25 (0) **   WMIADAPTER: ....................................................................................................... 0.
20542 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20543 17:44:25 (0) ** WMI Registry key setup: ............................................................................................. OK.
20544 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20545 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20546 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20547 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20548 17:44:25 (0) ** 
20549 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20550 17:44:25 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
20551 17:44:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20552 17:44:25 (0) ** 
20553 17:44:25 (0) ** WARNING: WMIDiag determined that WMI works CORRECTLY.  HOWEVER, some issues were detected.  Check 'C:\DOCUMENTS AND SETTINGS\GEORGE\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_OFFICE_2009.07.20_17.40.14.LOG' for details.
20554 17:44:25 (0) ** 
20555 17:44:25 (0) ** WMIDiag v2.0 ended on Monday, July 20, 2009 at 17:44 (W:61 E:18 S:2).

Open in new window

can any of the other computers see each other or the workgroup? I'm trying to get a better understanding of the issue. Is it just an issue with the one computer or a workgroup problem or possibly a combination of the two.
Just tried it on another computer... I am getting the same error on that PC as well.   I had not gotten that before (but I haven't checked for a long while), so I thought it was just this computer.  So, both computers are giving this error...
my previous post doesn't seem to have gone through so my appologies if this posts twice. can any of the other computers see each other or the workgroup? I'm trying to understand if it's just an issue with this one computer, the workgroup or possibly a combination of the two.
@premillard, got your post, see answer above..  multiple computers give the same error, unable to access work group.  Thanks!

Commented:
Just want to find out, can the workstations ping each other? Can you access the other workstations by running "\\computername" ?
1. Could you send a quick network diagram? Rough sketch is fine.
2. Sorry for the obvious but I have to ask. The name of the workgroup on all the computers is exactly the same right? ie. "WORKGROUP"
3. Do you have another computer that you could swap one out with or is it possible to do a factory restore on one of the computers?
4. Are all of your Windows updates up to date and what about antivirus updates are they all up to date as well? Does your computer allow you to get the lastest updates? If everything is connected up properly I'd almost start wondering if you don't have some sort of malware. Try running all of your updates.

The diagram if fairly simple.  I have 4 computers, two of them go into a switch and then into a wall jack.  The other two go directly into wall jacks.  All wall jacks end up going into the same firewall/routers (Verizon FIOS).   All computers have the same workgroup name.

I will be rebuilding one of the PCs at some point, perhaps I can do that sooner than later but it may take me several days before I can clear it out.   The computer I am working on is only a few months old with a clean install from Dell of windows XP Pro.  

I have Macafee (full suite) and Spyware doctor both running and scanned with no issues found.  I have auto updates set so I assume I am up-to-date.

I am unable to ping at least two of my other computers, I can ping one, the other is not on.

Amazingly, I have found this issue on the web many, many times.  Each time with a different resolution.  It's baffling.  Here are some of the things that people said worked.  
 
> I had this problem and the only way I found to resolve it was to put all the comps on a totally new workgroup and redo my DNS server. When they came back on I could browse the entire group.  
http://www.experts-exchange.com/Networking/Microsoft_Network/Q_20965078.html
 
> it is the problem with name resolution, configure HOSTS or LMHOSTS file.  Add other computers to the host file.
 
> control panel, local settings, access this computer from the network"
double click the above and "add use or group".
add "everyone"
http://answers.yahoo.com/question/index?qid=20090524212221AA1S5qi
 
 
> Either you have a firewall up (router or somewhere), someone turned on client isolation (see google) or it's the same old account issue
 
 
> 1. Open Network Connections.
2. In Local Area Network, Right click on top of your connection and select Properties, click Install.
3. In Select Network Component Type, click Protocol, and then click Add.
4. Click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, click OK, and then click Close.
5. In Network Connections, on the Advanced menu (on top menu bar), click Advanced Settings.
6. On the Adapters and Bindings tab, under Connections, click the local area connection on which you are enabling IPX/SPX file and print sharing.
Under Bindings for Local Area Connection, under File and Printer Sharing for Microsoft Networks, clear the Internet Protocol (TCP/IP) check box, and then click OK."
 
http://forums.cnet.com/5208-7589_102-0.html?threadID=344743&start=15&tag=forum-w;forums06

Open in new window

Are the 2 workstations that can ping each other the ones plugged into the switch?
actually, they're not..
The last item I tried (the 6 step at the end of my previous post) actually did a little something.  Now when I go into network places, I can at least see my own PC.  Before, I saw nothing.    Does that solution make any sense to you?   I'm not sure what it was that I did :)
Here is what I would do before you restore any of the computers.
1. Plug all the computers into the same switch and fire them up
2. Make sure they all have the same user list if you haven't done that yet
3. Check the IP addresses of each of the computers including the subnet mask and the
default gateway and make sure they are all correct
4. See which computers can ping each other and which ones can't
5. Check if the ones that can ping each other can browes the workgroup
Start with that and please post the results
Number 6 of your post?
If so that was going to be the next step I was going to have you do after posting these results.
Did you add all of the computers to the host file? IP's and corresponding computer name?
I was referring to these steps (below)...

I followed these steps and can now see my own computer on the network places, but no other computers.  

I did not try the suggestion of adding to the host, it didn't sound like something that would make a difference since I cannot access the other computers by IP either, so adding to host probably wouldn't do anything.


I will try your 5 step suggestion above.  Thanks for sticking with me.
> 1. Open Network Connections.
2. In Local Area Network, Right click on top of your connection and select Properties, click Install.
3. In Select Network Component Type, click Protocol, and then click Add.
4. Click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, click OK, and then click Close.
5. In Network Connections, on the Advanced menu (on top menu bar), click Advanced Settings.
6. On the Adapters and Bindings tab, under Connections, click the local area connection on which you are enabling IPX/SPX file and print sharing.
Under Bindings for Local Area Connection, under File and Printer Sharing for Microsoft Networks, clear the Internet Protocol (TCP/IP) check box, and then click OK."
 
http://forums.cnet.com/5208-7589_102-0.html?threadID=344743&start=15&tag=forum-w;forums06

Open in new window

Oh, I'm afraid this will take you down the wrong path. You are going to need TCP/IP enabled.
This isn't/shouldn't be that difficult of a task, there's something really easy that's being missed.
To put you at ease I'm a network engineer and I build/Maintain very complex WAN's.
Post the results from my steps and I should be able to help you get this thing up.
How's it going? Any luck?
I'm sorry to disappear, I still really need this to get fixed, but big work problems got in the way !   I will return asap..

I appreciate your help very very much!
No problem, I'll just wait to hear back.
I spent much of today reworking my network.  I took out all wires and cleaned-up, moved the switch I was using, changed my workgroup name to the default "workgroup,"  undid the network change I made above, clicked "repair" on the network connections and when I tested, things were working !

Thanks so much for your help !

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial