Networking only works "one way"

[JClark]

More follow up, Chuck.

I reset tcp/ip per the manual reset instructions by MS.
Saved the log. I'll post the log after this note.
It did reset all the values, and I had to put in the IP address, DNS
servers, NetBios allow, etc and rebooted.
Sadly, no help.
The "shared" files on this computer can't be opened or seen by the
other two, although the shared folders are seen.

I tried disabling the firewalls much earlier without result. Now maybe
it's time to uninstall them completely and test again. I may simplify
the test by eliminating one of the secondary computers. If you have
any thoughts, they'd be welcome.

Much appreciation.

Jack

-------------------------------------------------------------------------------------------
reset
SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\NetbiosOptions
old REG_DWORD = 1

deleted
SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts
reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\DefaultGateway
old REG_MULTI_SZ =
192.168.1.1

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\DefaultGatewayMetric
old REG_MULTI_SZ =
0

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\EnableDhcp
old REG_DWORD = 0

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\IpAddress
old REG_MULTI_SZ =
192.168.1.150

deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\IpAutoconfigurationAddress
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\IpAutoconfigurationMask
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\IpAutoconfigurationSeed
reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\NameServer
old REG_SZ = 65.32.1.65,65.32.1.70

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{761B3B7A-475C-4B27-82C8-BF09738AB7F6}\SubnetMask
old REG_MULTI_SZ =
255.255.255.0

deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution
reset Linkage\UpperBind for
{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0057\4&1F09082D&1&01.
bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for ROOT\MS_NDISWANBH\0000. bad value was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
REG_MULTI_SZ =
PSched

<completed>

 

[Chuck]

Jack,

With Windows XP, you can only reset IP. That's step 9, and is generally more
likely when you have complete disconnectivity. Your SMBs are getting thru
("There are 3 servers..."). But step 9 is relatively painless (though a bit
anal about the format of the command - read the article).

My money is on a personal firewall. Yes, let's look at the Winsock catalogue
again.

Good Morning Chuck,
Again, thanks for sticking with me on this.

read the article

Yes, I did read the article referenced in Step 9. Seems pretty
straightforward, and I will follow the command line reset
instructions.

My money is on a personal firewall

Certainly sounds reasonable. But, the firewalls on all three machines
(Deerfield Visnetic on AMD64, ZA on other two) have rules to permit
traffic between the three IP addresses, and their logs don't show any
blocking. The BOClean now does not do its "cleanup of winsock
connctivity" and logs show no "trojans" zapped. My antivirus AVG Pro
7.1 does not seem to have a firewall component, but I've written AVG
support to have them confirm this.

If the "reset IP" doesn't work, perhaps I should uninstall all
firewalls and see what happens. Again, the built-in firewall with the
NVIDIA onboard LAN hardware is not installed.

Just musing. Here's the latest "netsh winsock show catalog" output.

Jack
******************************************************************************
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkipx [IPX]
Provider ID:
{11058240-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1012
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 2
Protocol: 1000
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1013
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX] [Pseudo
Stream]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1014
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1015
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II] [Pseudo
Stream]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1016
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] SEQPACKET
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1025
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] DATAGRAM
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1026
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] SEQPACKET
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1027
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] DATAGRAM
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1028
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] SEQPACKET
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1029
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] DATAGRAM
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1030
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] SEQPACKET
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1031
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] DATAGRAM
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1032
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA)
Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NWLink IPX/SPX/NetBIOS Compatible
Transport Protocol
Provider ID:
{E02DAAF0-7E9F-11CF-AE5A-00AA00A7112B}
Name Space: 1
Active: 1
Version: 1

OK, Jack,

Here's the difference between my computer and yours. On your computer:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkipx [IPX]

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX]

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX] [Pseudo
Stream]

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II]

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II] [Pseudo
Stream]

Name Space Provider Entry
------------------------------------------------------
Description: NWLink IPX/SPX/NetBIOS Compatible

Do the other computers have IPX/SPX? If not, this is a problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

 

[JClark]

<snipped>
<snip>
That's very interesting indeed. In your previous statement, you say "I don't
pretend to understand this.". I am closer to your condition than to the experts
here. The LSP / Winsock is a collection of programs, linked together
dynamically by pointers, that connect the Internet Protocol stack and the
applications (such as the ping command or your browser). The pointers describe
the path that a packet of data takes, as it's processed by each network program.
You can see the programs that your system uses, in the enumerations that you and
I compared.

The dynamic linking makes it possible for the good guys (makers of personal
firewalls, packet analysers, and the like) and the bad guys (makers of trojans
and password stealers, for instance) to connect their products to the network,
without requiring a system rebuild. I think that it's now time to try an LSP /
Winsock fix, and see if that will suffice without "reloading networking".
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
Hello again Chuck:

"I don't
pretend to understand this.". I am closer to your condition than to the experts
here.
Chuck, your humility is a wonderful virtue. But I feel very much in
awe of your depth of understanding. Like Chaucer's clerk, "Gladly
wolde he lerne, and glady teche." A good thing.

I did as you suggested. Netsh reset catalog did nothing. WinsockXPFIX
did some things (I had to put back all the entries in TCP/IP that had
been removed) but it didn't cure the problem.
Am I correct in assuming that the next step will be to
uninstall/reinstall TCP/IP?
I get a feeling that may be tricky. Any references or warnings?
Would you like to see my latest output from ipconfig, browstat status,
and "netsh winsock show catalog"? The latter shows a lot more entries
now.

Many thanks.

Jack

Jack,

With Windows XP, you can only reset IP. That's step 9, and is generally more
likely when you have complete disconnectivity. Your SMBs are getting thru
("There are 3 servers..."). But step 9 is relatively painless (though a bit
anal about the format of the command - read the article).

My money is on a personal firewall. Yes, let's look at the Winsock catalogue
again.

Good Morning Chuck,
Again, thanks for sticking with me on this.

read the article

Yes, I did read the article referenced in Step 9. Seems pretty
straightforward, and I will follow the command line reset
instructions.

My money is on a personal firewall

Certainly sounds reasonable. But, the firewalls on all three machines
(Deerfield Visnetic on AMD64, ZA on other two) have rules to permit
traffic between the three IP addresses, and their logs don't show any
blocking. The BOClean now does not do its "cleanup of winsock
connctivity" and logs show no "trojans" zapped. My antivirus AVG Pro
7.1 does not seem to have a firewall component, but I've written AVG
support to have them confirm this.

If the "reset IP" doesn't work, perhaps I should uninstall all
firewalls and see what happens. Again, the built-in firewall with the
NVIDIA onboard LAN hardware is not installed.

Just musing. Here's the latest "netsh winsock show catalog" output.

Jack
******************************************************************************
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkipx [IPX]
Provider ID:
{11058240-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1012
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 2
Protocol: 1000
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1013
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX] [Pseudo
Stream]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1014
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1015
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II] [Pseudo
Stream]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1016
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] SEQPACKET
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1025
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] DATAGRAM
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1026
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] SEQPACKET
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1027
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] DATAGRAM
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1028
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] SEQPACKET
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1029
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] DATAGRAM
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1030
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] SEQPACKET
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1031
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] DATAGRAM
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1032
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA)
Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NWLink IPX/SPX/NetBIOS Compatible
Transport Protocol
Provider ID:
{E02DAAF0-7E9F-11CF-AE5A-00AA00A7112B}
Name Space: 1
Active: 1
Version: 1

OK, Jack,

Here's the difference between my computer and yours. On your computer:

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkipx [IPX]

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX]

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX] [Pseudo
Stream]

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II]

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II] [Pseudo
Stream]

Name Space Provider Entry
------------------------------------------------------
Description: NWLink IPX/SPX/NetBIOS Compatible

Do the other computers have IPX/SPX? If not, this is a problem.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Chuck, I guess I'm getting addle-brained after a week of this. I don't
know where that stuff came from. I don't even know what IPX/SPX is. I
will, however, read the referenced section.

I did also notice that the "authentication" tab in my TCP/IP had the
"Enable IEE 802.1x authentication" checked. Maybe in my "furor
mutandi" I changed too many things, grasping for anything like the
proverbial drowning man. Anyway, I changed it now to non-checked.
Maybe that will make a difference. Here's the current netsh winsock
show catalog. It looks different. I'll print them both and compare.

Jack
************************************************************************************


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkipx [IPX]
Provider ID:
{11058240-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1012
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 2
Protocol: 1000
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1013
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX] [Pseudo
Stream]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1014
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1015
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II] [Pseudo
Stream]
Provider ID:
{11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1016
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] SEQPACKET
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1025
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] DATAGRAM
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1026
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] SEQPACKET
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1027
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] DATAGRAM
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1028
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] SEQPACKET
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1029
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] DATAGRAM
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1030
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] SEQPACKET
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1031
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] DATAGRAM
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1032
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA)
Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NWLink IPX/SPX/NetBIOS Compatible
Transport Protocol
Provider ID:
{E02DAAF0-7E9F-11CF-AE5A-00AA00A7112B}
Name Space: 1
Active: 1
Version: 1

 

[JClark]

<snip>
Chuck ... an interim report. And thanks again for the advice.
I couldn't find IPX/SPX to uninstall, so I installed it then
uninstalled it. When I uninstalled it, I got the hourglass for about
fifteen minutes, then closed the program. But it seems to no longer be
there. And I don't see any IPX/SPX entries in my winsock catalog,
which follows.

Jack
********************************************************************************

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] SEQPACKET
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1043
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] DATAGRAM
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1044
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] SEQPACKET
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1045
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] DATAGRAM
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1046
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] SEQPACKET
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1047
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] DATAGRAM
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1048
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] SEQPACKET
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1049
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] DATAGRAM
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1050
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA)
Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0

 

[Chuck]

<snip>
Chuck ... an interim report. And thanks again for the advice.
I couldn't find IPX/SPX to uninstall, so I installed it then
uninstalled it. When I uninstalled it, I got the hourglass for about
fifteen minutes, then closed the program. But it seems to no longer be
there. And I don't see any IPX/SPX entries in my winsock catalog,
which follows.

Jack
********************************************************************************

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] SEQPACKET
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1043
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] DATAGRAM
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1044
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] SEQPACKET
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1045
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] DATAGRAM
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1046
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] SEQPACKET
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1047
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] DATAGRAM
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1048
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] SEQPACKET
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1049
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] DATAGRAM
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1050
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA)
Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0

Jack,

This looks better now. So what of the problems? Does the other computer look
similar?

 

[JClark]

<snip>
Chuck ... an interim report. And thanks again for the advice.
I couldn't find IPX/SPX to uninstall, so I installed it then
uninstalled it. When I uninstalled it, I got the hourglass for about
fifteen minutes, then closed the program. But it seems to no longer be
there. And I don't see any IPX/SPX entries in my winsock catalog,
which follows.

Jack
********************************************************************************

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID:
{E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID:
{9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] SEQPACKET
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1043
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}] DATAGRAM
4
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1044
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -4
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] SEQPACKET
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1045
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8917A5D8-CD1B-426B-9E58-627A8486CA95}] DATAGRAM
0
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1046
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] SEQPACKET
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1047
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{132F559B-0745-4EDA-95EF-986866472281}] DATAGRAM
1
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1048
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] SEQPACKET
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1049
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BCD5277A-C759-44A2-8BB9-C63A8523F1DC}] DATAGRAM
2
Provider ID:
{8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1050
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID:
{22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID:
{3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA)
Namespace
Provider ID:
{6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0

Jack,

This looks better now. So what of the problems? Does the other computer look
similar? Good Morning, Chuck.
what of the problems?

(Sigh...) The problem is still there. One-way networking. AMD64, the
primary computer can do anything it wants with shared files on the
other two. Neither of the other two secondary computers can open the
shared folders on amd64, although the shared folders are clearly
visible on the other two computers. When you click to open them, the
hourglass appears next to the pointer for about five seconds, then
disappears. There is no error message. No blocked connection attempts
in firewall logs.

Does the other computer look

Yes, the "netsh winsock show catalog" output on all three computers
now looks very similar, at least for the "entry type" and
"description" lines. There are no references to IPX/SPX now.

The winsock catalog is identical with one exception: The notebook has
one extra entry at the beginning of the report. It refers to MSAFD
Irda [IrDA]. I'm assuming this is something peculiar to the notebook
or to its inactive wireless system.

Any further thoughts about opening this one-way street? You've been
very supportive and I appreciate it.

Jack

 

[Chuck]

Jack,

This looks better now. So what of the problems? Does the other computer look
similar? Good Morning, Chuck.
what of the problems?

(Sigh...) The problem is still there. One-way networking. AMD64, the
primary computer can do anything it wants with shared files on the
other two. Neither of the other two secondary computers can open the
shared folders on amd64, although the shared folders are clearly
visible on the other two computers. When you click to open them, the
hourglass appears next to the pointer for about five seconds, then
disappears. There is no error message. No blocked connection attempts
in firewall logs.

Does the other computer look

Yes, the "netsh winsock show catalog" output on all three computers
now looks very similar, at least for the "entry type" and
"description" lines. There are no references to IPX/SPX now.

The winsock catalog is identical with one exception: The notebook has
one extra entry at the beginning of the report. It refers to MSAFD
Irda [IrDA]. I'm assuming this is something peculiar to the notebook
or to its inactive wireless system.

Any further thoughts about opening this one-way street? You've been
very supportive and I appreciate it.

Jack

Jack,

IRDA is an Infrared adapter, common on portable computers.

I think we're back to the nVidia nForce in AMD64. Armor-On firewall or not, you
loaded the drivers. Go back to the nVidia forums, linked from my article.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

 

[JClark]

<snip>
Chuck ... an interim report. And thanks again for the advice.
I couldn't find IPX/SPX to uninstall, so I installed it then
uninstalled it. When I uninstalled it, I got the hourglass for about
fifteen minutes, then closed the program. But it seems to no longer be
there. And I don't see any IPX/SPX entries in my winsock catalog,
which follows.

Jack

Jack,

This looks better now. So what of the problems? Does the other computer look
similar? Good Morning, Chuck.
what of the problems?

(Sigh...) The problem is still there. One-way networking. AMD64, the
primary computer can do anything it wants with shared files on the
other two. Neither of the other two secondary computers can open the
shared folders on amd64, although the shared folders are clearly
visible on the other two computers. When you click to open them, the
hourglass appears next to the pointer for about five seconds, then
disappears. There is no error message. No blocked connection attempts
in firewall logs.

Does the other computer look
similar?

Yes, the "netsh winsock show catalog" output on all three computers
now looks very similar, at least for the "entry type" and
"description" lines. There are no references to IPX/SPX now.

The winsock catalog is identical with one exception: The notebook has
one extra entry at the beginning of the report. It refers to MSAFD
Irda [IrDA]. I'm assuming this is something peculiar to the notebook
or to its inactive wireless system.

Any further thoughts about opening this one-way street? You've been
very supportive and I appreciate it.

Jack

Jack,

IRDA is an Infrared adapter, common on portable computers.

I think we're back to the nVidia nForce in AMD64. Armor-On firewall or not, you
loaded the drivers. Go back to the nVidia forums, linked from my article.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

Chuck,
Will do ASAP. Interestingly, though, I've had the computer for over a
year, and I never changed the onboard LAN settings, and I used to be
able to copy files from the primary computer onto the notebook. Hmmmm.
But what is that old saying (?Sherlock Holmes) which states, more or
less, that if you eliminate all the possibilities except one, that is
the one you want, no matter how improbable. Obviously we can't know if
we've eliminated *all* the possibilities, but we must be getting
close!
I'll report the NVIDIA support group's input. Many thanks.

Jack

 

[Chuck]

<snip>
Chuck ... an interim report. And thanks again for the advice.
I couldn't find IPX/SPX to uninstall, so I installed it then
uninstalled it. When I uninstalled it, I got the hourglass for about
fifteen minutes, then closed the program. But it seems to no longer be
there. And I don't see any IPX/SPX entries in my winsock catalog,
which follows.

Jack

Jack,

This looks better now. So what of the problems? Does the other computer look
similar?
Good Morning, Chuck.
what of the problems?
(Sigh...) The problem is still there. One-way networking. AMD64, the
primary computer can do anything it wants with shared files on the
other two. Neither of the other two secondary computers can open the
shared folders on amd64, although the shared folders are clearly
visible on the other two computers. When you click to open them, the
hourglass appears next to the pointer for about five seconds, then
disappears. There is no error message. No blocked connection attempts
in firewall logs.
Does the other computer look
similar?
Yes, the "netsh winsock show catalog" output on all three computers
now looks very similar, at least for the "entry type" and
"description" lines. There are no references to IPX/SPX now.

The winsock catalog is identical with one exception: The notebook has
one extra entry at the beginning of the report. It refers to MSAFD
Irda [IrDA]. I'm assuming this is something peculiar to the notebook
or to its inactive wireless system.

Any further thoughts about opening this one-way street? You've been
very supportive and I appreciate it.

Jack

Jack,

IRDA is an Infrared adapter, common on portable computers.

I think we're back to the nVidia nForce in AMD64. Armor-On firewall or not, you
loaded the drivers. Go back to the nVidia forums, linked from my article.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

Chuck,
Will do ASAP. Interestingly, though, I've had the computer for over a
year, and I never changed the onboard LAN settings, and I used to be
able to copy files from the primary computer onto the notebook. Hmmmm.
But what is that old saying (?Sherlock Holmes) which states, more or
less, that if you eliminate all the possibilities except one, that is
the one you want, no matter how improbable. Obviously we can't know if
we've eliminated *all* the possibilities, but we must be getting
close!
I'll report the NVIDIA support group's input. Many thanks.

Jack

Jack,

That's a good point. What changed recently? How recently did this work
properly? Maybe we can work from that angle, while you research the nVidia
issue.

 

[JClark]

<snip>
Chuck ... an interim report. And thanks again for the advice.
I couldn't find IPX/SPX to uninstall, so I installed it then
uninstalled it. When I uninstalled it, I got the hourglass for about
fifteen minutes, then closed the program. But it seems to no longer be
there. And I don't see any IPX/SPX entries in my winsock catalog,
which follows.

Jack

<SNIP>

Jack,

This looks better now. So what of the problems? Does the other computer look
similar?
Good Morning, Chuck.
what of the problems?
(Sigh...) The problem is still there. One-way networking. AMD64, the
primary computer can do anything it wants with shared files on the
other two. Neither of the other two secondary computers can open the
shared folders on amd64, although the shared folders are clearly
visible on the other two computers. When you click to open them, the
hourglass appears next to the pointer for about five seconds, then
disappears. There is no error message. No blocked connection attempts
in firewall logs.
Does the other computer look
similar?
Yes, the "netsh winsock show catalog" output on all three computers
now looks very similar, at least for the "entry type" and
"description" lines. There are no references to IPX/SPX now.

The winsock catalog is identical with one exception: The notebook has
one extra entry at the beginning of the report. It refers to MSAFD
Irda [IrDA]. I'm assuming this is something peculiar to the notebook
or to its inactive wireless system.

Any further thoughts about opening this one-way street? You've been
very supportive and I appreciate it.

Jack

Jack,

IRDA is an Infrared adapter, common on portable computers.

I think we're back to the nVidia nForce in AMD64. Armor-On firewall or not, you
loaded the drivers. Go back to the nVidia forums, linked from my article.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

Chuck,
Will do ASAP. Interestingly, though, I've had the computer for over a
year, and I never changed the onboard LAN settings, and I used to be
able to copy files from the primary computer onto the notebook. Hmmmm.
But what is that old saying (?Sherlock Holmes) which states, more or
less, that if you eliminate all the possibilities except one, that is
the one you want, no matter how improbable. Obviously we can't know if
we've eliminated *all* the possibilities, but we must be getting
close!
I'll report the NVIDIA support group's input. Many thanks.

Jack

Jack,

That's a good point. What changed recently? How recently did this work
properly? Maybe we can work from that angle, while you research the nVidia
issue.

Chuck,
Unfortunately, it's been several months, maybe longer, since I had to
to a ppt presentation and copied it from the primary computer onto the
notebook. I'm always playing around with the computer, and I have no
idea what I might have done since then to mess this up. I certainly
didn't do anything with the NVIDIA networking controller. I had
forgotten it was there and never changed the settings it came with.
The guy who put the system together for me must have installed the
drivers for it. But now it's been uninstalled and reinstalled without
the firewall and with ActiveArmor disabled. But I never had any
trouble with it before.
So it's a good point, as you say, but probably not helpful in the
current situation.
The only reply I've gotten from the NVIDIA group says we are barking
up the wrong tree:

If you can see the files and attach to the other machine it will be a file

permission problem.
If it was networking you would have a different problem.

Search Microsoft for help on file sharing.

And I did search Microsoft again. I wasn't aware that with simple file
sharing (which is implemented on all three computers, all the network
transmission goes through the guest accounts. Eureka! I thought....
But I activated all three guest accounts, rebooted. Same problem.
Another dead end. Do I need to keep the guest accounts open?

With thanks.
Jack

 

[Chuck]

<snip>
Chuck ... an interim report. And thanks again for the advice.
I couldn't find IPX/SPX to uninstall, so I installed it then
uninstalled it. When I uninstalled it, I got the hourglass for about
fifteen minutes, then closed the program. But it seems to no longer be
there. And I don't see any IPX/SPX entries in my winsock catalog,
which follows.

Jack

<SNIP>

Jack,

This looks better now. So what of the problems? Does the other computer look
similar?
Good Morning, Chuck.
what of the problems?
(Sigh...) The problem is still there. One-way networking. AMD64, the
primary computer can do anything it wants with shared files on the
other two. Neither of the other two secondary computers can open the
shared folders on amd64, although the shared folders are clearly
visible on the other two computers. When you click to open them, the
hourglass appears next to the pointer for about five seconds, then
disappears. There is no error message. No blocked connection attempts
in firewall logs.
Does the other computer look
similar?
Yes, the "netsh winsock show catalog" output on all three computers
now looks very similar, at least for the "entry type" and
"description" lines. There are no references to IPX/SPX now.

The winsock catalog is identical with one exception: The notebook has
one extra entry at the beginning of the report. It refers to MSAFD
Irda [IrDA]. I'm assuming this is something peculiar to the notebook
or to its inactive wireless system.

Any further thoughts about opening this one-way street? You've been
very supportive and I appreciate it.

Jack

Jack,

IRDA is an Infrared adapter, common on portable computers.

I think we're back to the nVidia nForce in AMD64. Armor-On firewall or not, you
loaded the drivers. Go back to the nVidia forums, linked from my article.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html
Chuck,
Will do ASAP. Interestingly, though, I've had the computer for over a
year, and I never changed the onboard LAN settings, and I used to be
able to copy files from the primary computer onto the notebook. Hmmmm.
But what is that old saying (?Sherlock Holmes) which states, more or
less, that if you eliminate all the possibilities except one, that is
the one you want, no matter how improbable. Obviously we can't know if
we've eliminated *all* the possibilities, but we must be getting
close!
I'll report the NVIDIA support group's input. Many thanks.

Jack

Jack,

That's a good point. What changed recently? How recently did this work
properly? Maybe we can work from that angle, while you research the nVidia
issue.

Chuck,
Unfortunately, it's been several months, maybe longer, since I had to
to a ppt presentation and copied it from the primary computer onto the
notebook. I'm always playing around with the computer, and I have no
idea what I might have done since then to mess this up. I certainly
didn't do anything with the NVIDIA networking controller. I had
forgotten it was there and never changed the settings it came with.
The guy who put the system together for me must have installed the
drivers for it. But now it's been uninstalled and reinstalled without
the firewall and with ActiveArmor disabled. But I never had any
trouble with it before.
So it's a good point, as you say, but probably not helpful in the
current situation.
The only reply I've gotten from the NVIDIA group says we are barking
up the wrong tree:

If you can see the files and attach to the other machine it will be a file

permission problem.
If it was networking you would have a different problem.

Search Microsoft for help on file sharing.

And I did search Microsoft again. I wasn't aware that with simple file
sharing (which is implemented on all three computers, all the network
transmission goes through the guest accounts. Eureka! I thought....
But I activated all three guest accounts, rebooted. Same problem.
Another dead end. Do I need to keep the guest accounts open?

With thanks.
Jack

Oh boy.

No, being able to "see" another computer, but not access it, isn't necessarily
going to indicate a permissioning problem.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

The hardware guys don't know how complex Windows Networking is. Now, if you
were getting an error message "...access denied...", then a permissioning
problem would be a possible cause. But without you getting any more than the
hourglass appearing then disappearing, that's not so likely.

But let's see what we do know.
# AMD64 is the master browser.
# AMD64 has the nVidia network card.
# AMD64 is the non accessible computer. There is no error message. You click on
the folder, the hourglass appears for a few seconds and then disappears.
# Both ASUS-AMD and MBX-Notebook show "Could not connect to registry, error =
53", in browstat.

This says that the SMBs that are used for name resolution, to provide the
address for AMD64, are being blocked. With both ASUS-AMD and MBX-Notebook
showing the same error, it's likely that the problem is with AMD64.

Once again, is NetBT Enabled consistently?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Let's try some relational analysis. You'll have to download PSExec (free) (I
hope). Run it on all 3 computers please. Attach output here.
<http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html>
http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html

 

[Dr Teeth]

PMFJI.

Apologies to both Jack and Chuck for butting in.

Jack's problem seems spookily similar to mine in the thread titled
"Selling my soul to the devil is the next step..."; I wonder if we
really do have the same problem.

I'm watching this thread with interest just in case.

--
Cheers,

Guy

** Stress - the condition brought about by having to
** resist the temptation to beat the living daylights
** out of someone who richly deserves it.

 

[JClark]

PMFJI.

Apologies to both Jack and Chuck for butting in.

Jack's problem seems spookily similar to mine in the thread titled
"Selling my soul to the devil is the next step..."; I wonder if we
really do have the same problem.

I'm watching this thread with interest just in case.

Hello Doc,
Not butting in at all. We can share our misery.
I need to get to work on Chuck's latest advice. His argument seems
cogent.
Best regards,
Jack

 

[JClark]

<snip>
Chuck ... an interim report. And thanks again for the advice.
I couldn't find IPX/SPX to uninstall, so I installed it then
uninstalled it. When I uninstalled it, I got the hourglass for about
fifteen minutes, then closed the program. But it seems to no longer be
there. And I don't see any IPX/SPX entries in my winsock catalog,
which follows.

Jack

<SNIP>

Jack,

This looks better now. So what of the problems? Does the other computer look
similar?
Good Morning, Chuck.
what of the problems?
(Sigh...) The problem is still there. One-way networking. AMD64, the
primary computer can do anything it wants with shared files on the
other two. Neither of the other two secondary computers can open the
shared folders on amd64, although the shared folders are clearly
visible on the other two computers. When you click to open them, the
hourglass appears next to the pointer for about five seconds, then
disappears. There is no error message. No blocked connection attempts
in firewall logs.
Does the other computer look
similar?
Yes, the "netsh winsock show catalog" output on all three computers
now looks very similar, at least for the "entry type" and
"description" lines. There are no references to IPX/SPX now.

The winsock catalog is identical with one exception: The notebook has
one extra entry at the beginning of the report. It refers to MSAFD
Irda [IrDA]. I'm assuming this is something peculiar to the notebook
or to its inactive wireless system.

Any further thoughts about opening this one-way street? You've been
very supportive and I appreciate it.

Jack

Jack,

IRDA is an Infrared adapter, common on portable computers.

I think we're back to the nVidia nForce in AMD64. Armor-On firewall or not, you
loaded the drivers. Go back to the nVidia forums, linked from my article.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html
Chuck,
Will do ASAP. Interestingly, though, I've had the computer for over a
year, and I never changed the onboard LAN settings, and I used to be
able to copy files from the primary computer onto the notebook. Hmmmm.
But what is that old saying (?Sherlock Holmes) which states, more or
less, that if you eliminate all the possibilities except one, that is
the one you want, no matter how improbable. Obviously we can't know if
we've eliminated *all* the possibilities, but we must be getting
close!
I'll report the NVIDIA support group's input. Many thanks.

Jack

Jack,

That's a good point. What changed recently? How recently did this work
properly? Maybe we can work from that angle, while you research the nVidia
issue.

Chuck,
Unfortunately, it's been several months, maybe longer, since I had to
to a ppt presentation and copied it from the primary computer onto the
notebook. I'm always playing around with the computer, and I have no
idea what I might have done since then to mess this up. I certainly
didn't do anything with the NVIDIA networking controller. I had
forgotten it was there and never changed the settings it came with.
The guy who put the system together for me must have installed the
drivers for it. But now it's been uninstalled and reinstalled without
the firewall and with ActiveArmor disabled. But I never had any
trouble with it before.
So it's a good point, as you say, but probably not helpful in the
current situation.
The only reply I've gotten from the NVIDIA group says we are barking
up the wrong tree:

If you can see the files and attach to the other machine it will be a file

permission problem.
If it was networking you would have a different problem.

Search Microsoft for help on file sharing.

And I did search Microsoft again. I wasn't aware that with simple file
sharing (which is implemented on all three computers, all the network
transmission goes through the guest accounts. Eureka! I thought....
But I activated all three guest accounts, rebooted. Same problem.
Another dead end. Do I need to keep the guest accounts open?

With thanks.
Jack

Oh boy.

No, being able to "see" another computer, but not access it, isn't necessarily
going to indicate a permissioning problem.
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

The hardware guys don't know how complex Windows Networking is. Now, if you
were getting an error message "...access denied...", then a permissioning
problem would be a possible cause. But without you getting any more than the
hourglass appearing then disappearing, that's not so likely.

But let's see what we do know.
# AMD64 is the master browser.
# AMD64 has the nVidia network card.
# AMD64 is the non accessible computer. There is no error message. You click on
the folder, the hourglass appears for a few seconds and then disappears.
# Both ASUS-AMD and MBX-Notebook show "Could not connect to registry, error =
53", in browstat.

This says that the SMBs that are used for name resolution, to provide the
address for AMD64, are being blocked. With both ASUS-AMD and MBX-Notebook
showing the same error, it's likely that the problem is with AMD64.

Once again, is NetBT Enabled consistently?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Let's try some relational analysis. You'll have to download PSExec (free) (I
hope). Run it on all 3 computers please. Attach output here.
<http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html>
http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html

Hello Chuck,
Wow, you've put a lot of work into my problem. I'm very grateful.
Here's the output from cpsserv for the three computers:
Jack
*********************************************************************************
AMD64
Start CPSServ V1.02 - AMD64

Find Computer Browser ("browser")

Checking \\AMD64...
Found browser on:

\\AMD64

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...
Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:
No active service named lmhosts found.


Find Remote Registry ("remoteregistry")

Checking \\AMD64...
Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:
No active service named remoteregistry found.


Find Server ("server")

Checking \\AMD64...
Found server on:

\\AMD64

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find WF / ICS ("sharedaccess")

Checking \\AMD64...
Found sharedaccess on:

\\AMD64

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find Workstation ("workstation")

Checking \\AMD64...
Found workstation on:

\\AMD64

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:

End CPSServ V1.02 - AMD64
***************************************************************************************
ASUS-AMD

Start CPSServ V1.02 - ASUS-AMD

Find Computer Browser ("browser")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found browser on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:
No active service named lmhosts found.


Find Remote Registry ("remoteregistry")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found remoteregistry on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find Server ("server")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found server on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find WF / ICS ("sharedaccess")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found sharedaccess on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find Workstation ("workstation")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found workstation on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:

End CPSServ V1.02 - ASUS-AMD
**************************************************************************************
MBX-notebook
Start CPSServ V1.02 - MBX-NOTEBOOK

Find Computer Browser ("browser")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK... No active service named browser found.


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK... No active service named lmhosts found.


Find Remote Registry ("remoteregistry")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK... No active service named remoteregistry
found.


Find Server ("server")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...
Found server on:

\\MBX-NOTEBOOK


Find WF / ICS ("sharedaccess")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...
Found sharedaccess on:

\\MBX-NOTEBOOK


Find Workstation ("workstation")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...
Found workstation on:

\\MBX-NOTEBOOK

End CPSServ V1.02 - MBX-NOTEBOOK
***********************************************************************************************

 

[Chuck]

Hello Chuck,
Wow, you've put a lot of work into my problem. I'm very grateful.
Here's the output from cpsserv for the three computers:

<SNIP>

OK, here's part of the problem diagnosing the problem. The Remote Registry
service is running only on ASUS-AMD. With the RRS not running on AMD64, the
error = 53 is normal.

But here's the problem (cross my fingers):

Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...
Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:
No active service named lmhosts found.

... and the above repeated for all 3 computers. You gotta have TCP/IP NetBIOS
Helper ("lmhosts") running on each computer.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components

 

[JClark]

<SNIP>

OK, here's part of the problem diagnosing the problem. The Remote Registry
service is running only on ASUS-AMD. With the RRS not running on AMD64, the
error = 53 is normal.

But here's the problem (cross my fingers):

Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...
Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:
No active service named lmhosts found.

.. and the above repeated for all 3 computers. You gotta have TCP/IP NetBIOS
Helper ("lmhosts") running on each computer.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components

Good Morning again, Chuck
Well, sadly, things have deteriorated a bit. I'm mystified.
I changed the TCP/IP netbios helper service to "automatic" on all
three comuters. Rebooted. This service is, of course, now "started".
This alone didn't change things. I ran the network connection wizard
again on all three computers, disabled Windows Firewall, and then
rebooted.

Now I don't even see the amd64 shared folders from the two secondary
computers. I see the printers only.

I ran cpsserv again. Still have errors about "unable to open service
control manager" Looking this up, everybody says it's because "file
and print sharing" is not enabled. Of course it is on all three
computers, so it must be something else. I even uninstalled "file and
print sharing" on amd64 and reinstalled it after a reboot. No
difference.

Here's the output for cpsserv. Should I start over and get outputs
from browstat, etc etc?
Thanks again for sticking with me through this. It really is a
challenge.

Jack
*********************************************************************************
amd64
Start CPSServ V1.02 - AMD64

Find Computer Browser ("browser")

Checking \\AMD64...
Found browser on:

\\AMD64

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find TCP/IP NetBIOS Helper ("lmhosts")
Error browsing network:
No active service named lmhosts found.


Find Remote Registry ("remoteregistry")

Checking \\AMD64...
Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:
No active service named remoteregistry found.


Find Server ("server")

Checking \\AMD64...
Found server on:

\\AMD64

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find WF / ICS ("sharedaccess")

Checking \\AMD64...
Found sharedaccess on:

\\AMD64

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find Workstation ("workstation")

Checking \\AMD64...
Found workstation on:

\\AMD64

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:

End CPSServ V1.02 - AMD64
**************************************************************************************
asus-amd
Start CPSServ V1.02 - ASUS-AMD

Find Computer Browser ("browser")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found browser on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found lmhosts on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find Remote Registry ("remoteregistry")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:
No active service named remoteregistry found.


Find Server ("server")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found server on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find WF / ICS ("sharedaccess")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found sharedaccess on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:


Find Workstation ("workstation")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...
Found workstation on:

\\ASUS-AMD

Checking \\MBX-NOTEBOOK...Unable to open Service Control Manager
database on \\\MBX-NOTEBOOK:

End CPSServ V1.02 - ASUS-AMD
**************************************************************************************
mbx-notebook
Start CPSServ V1.02 - MBX-NOTEBOOK

Find Computer Browser ("browser")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK... No active service named browser found.


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...
Found lmhosts on:

\\MBX-NOTEBOOK


Find Remote Registry ("remoteregistry")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK... No active service named remoteregistry
found.


Find Server ("server")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...
Found server on:

\\MBX-NOTEBOOK


Find WF / ICS ("sharedaccess")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...
Found sharedaccess on:

\\MBX-NOTEBOOK


Find Workstation ("workstation")

Checking \\AMD64...Unable to open Service Control Manager database on
\\\AMD64:

Checking \\ASUS-AMD...Unable to open Service Control Manager database
on \\\ASUS-AMD:

Checking \\MBX-NOTEBOOK...
Found workstation on:

\\MBX-NOTEBOOK

End CPSServ V1.02 - MBX-NOTEBOOK
********************************************************************************************

 

[Chuck]

Good Morning again, Chuck
Well, sadly, things have deteriorated a bit. I'm mystified.
I changed the TCP/IP netbios helper service to "automatic" on all
three comuters. Rebooted. This service is, of course, now "started".
This alone didn't change things. I ran the network connection wizard
again on all three computers, disabled Windows Firewall, and then
rebooted.

Now I don't even see the amd64 shared folders from the two secondary
computers. I see the printers only.

I ran cpsserv again. Still have errors about "unable to open service
control manager" Looking this up, everybody says it's because "file
and print sharing" is not enabled. Of course it is on all three
computers, so it must be something else. I even uninstalled "file and
print sharing" on amd64 and reinstalled it after a reboot. No
difference.

Here's the output for cpsserv. Should I start over and get outputs
from browstat, etc etc?
Thanks again for sticking with me through this. It really is a
challenge.

Jack

Jack,

The advice that you got was close. You will get "unable to open service control
manager", while you are using Simple File Sharing. You have to have
administrative access to open the service control manager. Which mean that you
have to disable SFS, and you have to enable an administrative account, on each
computer, for network access.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Advanced>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Advanced

And let's look at "browstat status" for all 3 computers too.

 

[JClark]

Jack,

The advice that you got was close. You will get "unable to open service control
manager", while you are using Simple File Sharing. You have to have
administrative access to open the service control manager. Which mean that you
have to disable SFS, and you have to enable an administrative account, on each
computer, for network access.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Advanced>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Advanced

And let's look at "browstat status" for all 3 computers too.

Hi Chuck:
First of all, we are down to two computers now. Asus-amd is making
BIOS beeping noises with power on, so I've put it aside for now. But
since the problem is with primary amd64, and we have mbx-notebook, we
can continue to work on the problem. I say "we" with respect and
thanks, again.
Second, somewhere during my manipulations, all my shared folders on
amd64 got "unshared". I reshared them. But they still don't show up
from mbx-notebook.
Thirdly, I wasn't aware that I could not use simple file sharing for
this network, using my usual login name and password. I'll read your
reference above on advanced (classic) file sharing and start
implementing it. But, again, I'm sure I was able to share the files
before with my current system, but at this stage I'm willing to try
anything.
Here's the browstat output currently from the remaining 2 computers:

Jack

***********************************************************************************
AMD64

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
Browsing is active on domain.
Master browser name is: AMD64
Master browser is running build 2600
1 backup servers retrieved from master AMD64
\\AMD64
There are 2 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
****************************************************************************************
mbx-notebook

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}
Browsing is active on domain.
Master browser name is: AMD64
Could not connect to registry, error = 53 Unable to determine
build of browser master: 53
\\\\AMD64 . Version:05.01 Flags: 51203 NT POTENTIAL
MASTER
1 backup servers retrieved from master AMD64
\\AMD64
There are 2 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}
*************************************************************************************

 

[Chuck]

Hi Chuck:
First of all, we are down to two computers now. Asus-amd is making
BIOS beeping noises with power on, so I've put it aside for now. But
since the problem is with primary amd64, and we have mbx-notebook, we
can continue to work on the problem. I say "we" with respect and
thanks, again.
Second, somewhere during my manipulations, all my shared folders on
amd64 got "unshared". I reshared them. But they still don't show up
from mbx-notebook.
Thirdly, I wasn't aware that I could not use simple file sharing for
this network, using my usual login name and password. I'll read your
reference above on advanced (classic) file sharing and start
implementing it. But, again, I'm sure I was able to share the files
before with my current system, but at this stage I'm willing to try
anything.
Here's the browstat output currently from the remaining 2 computers:

Jack

***********************************************************************************
AMD64

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
Browsing is active on domain.
Master browser name is: AMD64
Master browser is running build 2600
1 backup servers retrieved from master AMD64
\\AMD64
There are 2 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
****************************************************************************************
mbx-notebook

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}
Browsing is active on domain.
Master browser name is: AMD64
Could not connect to registry, error = 53 Unable to determine
build of browser master: 53
\\\\AMD64 . Version:05.01 Flags: 51203 NT POTENTIAL
MASTER
1 backup servers retrieved from master AMD64
\\AMD64
There are 2 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}
*************************************************************************************

Jack,

You can use Simple File Sharing if you want. You just can't do administrative
access, like accessing the service control database. With SFS enabled, you are
left with Guest-only access thru the network.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest

And you need to start the Remote Registry service on AMD54, if you're going to
resolve the "error = 53" in browstat from mbx-notebook.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53

After we get the actual problem fixed, you can reverse all of the tweaks that we
are making. Just make them one at a time, and when shite stops working, reverse
what you just changed.

For right now, let's get administrative access working, and the RRS running, on
each computer.

 

[JClark]

Jack,

You can use Simple File Sharing if you want. You just can't do administrative
access, like accessing the service control database. With SFS enabled, you are
left with Guest-only access thru the network.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest

And you need to start the Remote Registry service on AMD54, if you're going to
resolve the "error = 53" in browstat from mbx-notebook.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53

After we get the actual problem fixed, you can reverse all of the tweaks that we
are making. Just make them one at a time, and when shite stops working, reverse
what you just changed.

For right now, let's get administrative access working, and the RRS running, on
each computer.

Thanks, Chuck. I put remote registry service to automatic, rebooted.
Here's browstat from both. Yes, small steps are good.
Even with remote registry automatic on both computers,and rebooted, I
still get error from mbx-notebook. I'll double check again.

Jack
********************************************************************************
amd64

Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
Browsing is active on domain.
Master browser name is: AMD64
Master browser is running build 2600
1 backup servers retrieved from master AMD64
\\AMD64
There are 1 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
**********************************************************************************
mbx-notebook


Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}
Browsing is active on domain.
Master browser name is: AMD64
Could not open key in registry, error = 5 Unable to determine
build of browser master: 5
\\\\AMD64 . Version:05.01 Flags: 51203 NT POTENTIAL
MASTER
1 backup servers retrieved from master AMD64
\\AMD64
There are 2 servers in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}
There are 1 domains in domain WORKGROUP on transport
\Device\NetBT_Tcpip_{C33CF1D9-D7A5-43EA-AF9B-4E6E1B28B1D5}