Resolved Single XP PC will not see others on mixed OS network.

Hey howdy ho everybody. In my quest to get this working, I came across your site. I couldn't find a resolution to my problem and you guys seemed to be the most knowledgeable so I registered.

Anywho, I have a Vista Home x64 machine (RUTTEGER) and two XP Home x86 machines (robert and MARTY). They are all on the workgroup HOGANS_HEROES. Rutteger can't see Robert because I didn't install the LLTD on Robert, but I can go into shared folders just fine. They are playing nice. Marty, however, can not see the others. I installed the LLTD on Marty so that Rutteger can see it. Robert can see Marty as well. When I try to access Marty either by double clicking or by \\MARTY, I get the error message "Network path not found 0x80070035." It happens when I try to access Marty from either Rutteger or Robert. Both pc's give the same error message.

All the pc's can ping each other. NetBIOS is enabled. ESET is configured to allow all connections from the same subnet. Windows firewall is off. Have also tried turning off ESET. Have run the network setup wizard. Have tried renaming the workgroup. Vista has file and printer sharing on with no password necessary. Rutteger and Marty have one user with no password. Robert has one user with a password. Dunno if that's relevant.

I don't know what the problem is. I had the network up awhile ago. I don't know what I changed and I don't know when it stopped working.

Thanks for the upcoming help.

Andrew

 

Yes, Layer Link Topology Discovery. This is where I got the info about it and where I downloaded it.

 

So I found this. I went into the registry and I had the DhcpNodeType entry but not the Nodetype entry. I deleted the DhcpNodeType entry and rebooted. No difference. I did notice that I can access Rutteger from Marty with \\RUTTEGER. I can't remember if I could do that before.

So now I'm thinking it might have something to do wit McAfee. I previously had McAfee installed but switched to ESET. Before installing ESET, I uninstalled McAfee but I think I did it wrong. I downloaded the McAfee removal tool which you are supposed to run after you uninstall McAfee through Add/Remove Programs. For some dumb reason, I ran it before uninstalling McAfee. When I run the tool now, it gives me the message CLEANUP FAILED Cleanup is already running. What do you guys think of this?

 

The McAfee removal tool (MCPR.exe) was saying that it was already running when I would start it and not do anything more. So I booted in safe mode with networking and tried to see the workgroup computers with no success. I rebooted in normal safe mode and then ran MCPR. MCPR gave me the message that some parts may not be removed because it didn't have full permissions. When it was done, it said removal failed. I looked at the log and saw which registry entries it was trying to delete. I went in to regedit and gave permission to myself and then deleted those registry entries. I rebooted in safe mode and started MCPR again. This time it was successful, but gave me the same warning that it didn't have full permissions. I looked at the log again and there was still an error and a winerr (see log). I rebooted in safe mode with networking and low and behold, everything was working how it should.

I rebooted normally and now when I go to My Network Places I can see and access the shared folders on the other computers. I still cannot see or access Marty's folders from the other computers. When I do, I get the "Network path not found 0x80070035" error. I also tried running MCPR on Marty again and it gives me the message that it is already running.


Here is the beginning section of the MCPR log file run on Marty in safe mode.

MCAFEE CLEANUP
June 19, 2010 12:45:57
INFO Cleanup will be scheduled and run.
INFO Product mpfpcu to be removed from system.
INFO Product mpfp to be removed from system.
INFO Product mps to be removed from system.
INFO Product shred to be removed from system.
INFO Product mpscu to be removed from system.
INFO Product mskcu to be removed from system.
INFO Product msk to be removed from system.
INFO Product emproxy to be removed from system.
INFO Product mas to be removed from system.
INFO Product fwdriver to be removed from system.
INFO Product hw to be removed from system.
INFO Product mbk to be removed from system.
INFO Product mcproxy to be removed from system.
INFO Product mhn to be removed from system.
INFO Product mqccu to be removed from system.
INFO Product mqc to be removed from system.
INFO Product shrd to be removed from system.
INFO Product nmc to be removed from system.
INFO Product redir to be removed from system.
INFO Product mna to be removed from system.
INFO Product mwl to be removed from system.
INFO Product msad to be removed from system.
INFO Product mobk to be removed from system.
INFO Product vs to be removed from system.
INFO Product msc to be removed from system.
INFO Product mcpr to be removed from system.
INFO Product mcsvchost to be removed from system.
ERROR Internal Error
WINERR StartService() failed. Error: 1084
INFO Task Scheduler service could not be started. Continuing with cleanup as current user...
PASS Register(C:\WINDOWS\system32\jscript.dll) returns: 1
PASS Register(C:\WINDOWS\system32\vbscript.dll) returns: 1
PASS UnRegisterBHO() returns: 1
INFO Removing product mpfpcu...
INFO Removing registry key...
PASS HKEY_CURRENT_USER\Software\McAfee.com\Personal Firewall does not exist
PASS Product mpfpcu successfully removed.
...


And here is the MCPR log file run on Robert in normal mode from the beginning to where the Marty log file stops. Notice that extra first section.

MCAFEE CLEANUP
June 19, 2010 13:03:57
INFO Cleanup will be scheduled and run.
INFO Product mpfpcu to be removed from system.
INFO Product mpfp to be removed from system.
INFO Product mps to be removed from system.
INFO Product shred to be removed from system.
INFO Product mpscu to be removed from system.
INFO Product mskcu to be removed from system.
INFO Product msk to be removed from system.
INFO Product emproxy to be removed from system.
INFO Product mas to be removed from system.
INFO Product fwdriver to be removed from system.
INFO Product hw to be removed from system.
INFO Product mbk to be removed from system.
INFO Product mcproxy to be removed from system.
INFO Product mhn to be removed from system.
INFO Product mqccu to be removed from system.
INFO Product mqc to be removed from system.
INFO Product shrd to be removed from system.
INFO Product nmc to be removed from system.
INFO Product redir to be removed from system.
INFO Product mna to be removed from system.
INFO Product mwl to be removed from system.
INFO Product msad to be removed from system.
INFO Product mobk to be removed from system.
INFO Product vs to be removed from system.
INFO Product msc to be removed from system.
INFO Product mcpr to be removed from system.
INFO Product mcsvchost to be removed from system.
ERROR Internal Error
INFO Task Scheduler service started.

MCAFEE CLEANUP
June 19, 2010 13:03:59
INFO Cleanup operations will run.
INFO Product mpfpcu to be removed from system.
INFO Product mpfp to be removed from system.
INFO Product mps to be removed from system.
INFO Product shred to be removed from system.
INFO Product mpscu to be removed from system.
INFO Product mskcu to be removed from system.
INFO Product msk to be removed from system.
INFO Product emproxy to be removed from system.
INFO Product mas to be removed from system.
INFO Product fwdriver to be removed from system.
INFO Product hw to be removed from system.
INFO Product mbk to be removed from system.
INFO Product mcproxy to be removed from system.
INFO Product mhn to be removed from system.
INFO Product mqccu to be removed from system.
INFO Product mqc to be removed from system.
INFO Product shrd to be removed from system.
INFO Product nmc to be removed from system.
INFO Product redir to be removed from system.
INFO Product mna to be removed from system.
INFO Product mwl to be removed from system.
INFO Product msad to be removed from system.
INFO Product mobk to be removed from system.
INFO Product vs to be removed from system.
INFO Product msc to be removed from system.
INFO Product mcpr to be removed from system.
INFO Product mcsvchost to be removed from system.
ERROR Internal Error
PASS Register(C:\windows\system32\jscript.dll) returns: 1
PASS Register(C:\windows\system32\vbscript.dll) returns: 1
PASS UnRegisterBHO() returns: 1
INFO Removing product mpfpcu...
INFO Removing registry key...
PASS HKEY_CURRENT_USER\Software\McAfee.com\Personal Firewall does not exist
PASS Product mpfpcu successfully removed.
...


So i dunno what's going on.

 

In normal mode, I went into Task Scheduler and deleted the MCPR task. I then ran MCPR and it gave me an Incomplete Removal message. I looked at the log and it the error was:

WINERR IPersistFile::Save() failed. Error: 0x80090016
FAIL Error while running cleanup using Task Scheduler.

I found this thread and followed the advice given by Galdorf. When I rebooted, I ran MCPR and it ran successfully. The log looked the same as the log from Robert. Yippee.

I was getting excited, but the problem still persists. The other computers can see Marty, but cannot access it. Marty can see and access all the other computers.

I know this is probably not the most fun sort of troubleshooting, but anyone got any ideas?

 

It's fixed! After I did all that crazy stuff in my last post, I checked to make sure all the settings were still how they were supposed to be. Everything was fine except that Windows Firewall was on. I turned it off and tried to access Marty from Rutteger. No luck. I disabled the ESET firewall and then tried to access Marty again. It worked. So I tried to access Marty from all the other computers and they all worked, too. Yeehaw! I went back to Marty, enabled ESET and checked again. Everything works. I don't know if I even had to disable ESET. I may not have given the computers enough time between disabling Windows Firewall and checking if I could access Marty.

The moral of the story is to make sure you completely and correctly remove your old firewall. Otherwise it will interfere with networking.

 

Thanks for your excitement for my success Pete.

Unfortunately, after a restart, it was doing the same old bull. I tried restarting again to no avail. I disabled ESET's firewall and it worked. Then I enabled ESET's firewall and it worked. So that would lead me to believe that the issue is now with ESET. It's odd, though, 'cause all the other computers are running ESET as well. Even though I still have problems, I'll keep this thread marked as solved since this isn't a windows issue.

 

Okay. It works completely now. Instead of uninstalling and reinstalling ESET (which would have been my next step), I just reset all the rules and zones to default. That did the trick.