RE: Networking only works "one way"
Bob Campbell
computers tool in My Network Places? (This doesn't always accurately report
sharing, so you can also use the Net View command at the command prompt). Do
you get any errors?
Have you shared your drive C on all 3 computers? When you set up the share,
it will ask you if you want to allow access for others to see (that is, open)
the shared folder.
--
The Software Tailor
Las Vegas USA
"JClark" wrote:
> Hello Group:
>
> I have a networking problem I've been working on for about a week,
> without success. I've read through Chuck's amazingly comprehensive
> website, but I'm a little overwhelmed. Let me state my problem
> as simply as I can, and I'll request and gratefully accept suggestions
> about pinning down the problem.
>
> The System:
> Three computers networked through Linksys router.
> Static IP address.
> Router addresses for computers:
> A - 192.168.1.150
> B - 192.168.1.151
> C - 192.168.1.152
> All have Win XP Pro/ SP2
> All have simple file sharing enabled.
> All have same account name and login ID.
> All belong to "workgroup"
>
> The Problem:
> All three computers can access the internet.
> "A" can view and open shared folders on "B" and "C"
> "B" and "C" can view and open shared folders on each other.
> "B" and "C" can view shared folders on "A". BUT the shared folders on
> "A" cannot be opened, and files cannot be veiwed. There is no error
> message. You click on the folder, the hourglass appears for a few
> seconds and then disappears.
>
> What I have tried so far:
> Software firewalls all have rules to permit access to each other on
> ports 135-139. Logs show that incoming and outgoing TCP connections
> are going through.
> I've tried disabling all firewalls and antivirus programs.
> All computers have identical setups in TCP/IP and advanced.
> Linksys router settings have been gone over carefully and seem to be
> correct.
> Network setup wizard has been run on all three computers. (It enables
> Windows firewall, which I have then disabled.)
> Cable modem and router have been reset.
> Motherboard (ASUS A8N-SLI) on computer "A" has onboard LAN with Nvidia
> nForce controller, but I've uninstalled it and reinstalled it without
> installing the firewall component and have not enabled the Armor On
> feature.
>
> My take: Something is preventing sharing of folders on "A" since they
> can be seen by but not opened by "B" and "C"
>
> Does anyone have any suggestions about how to make this sharing a
> "two-way" street?
>
> Many thanks.
>
> Jack
>
>
>
>
Chuck
Jack,
Well, the "amazingly comprehensive" website only got that way from questions
like yours. Maybe you have something new here - let's see.
How about we start with "browstat status" from each computer. Maybe there's a
detail there that will give a clue.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
Bob Campbell
I think you have a VPN running or something like it which is blocking the
connection.
You can do a netstat -a on each computer (at the command prompt) and see if
they are all the same.
You could also download from Sysinternals a free utility called TCPView,
which is similar to netstat -a, but is much nicer and easier to see and watch
what's going on.
When I start my Cisco VPN service (right click on My Computer | Manage |
Services and Applications | Services), I can see several processes start for
cvpnd.exe with port addresses at 625xx. When my Cisco VPN service is started,
I can't network my local computers, in the same way that you describe your
network.
You can download TCPView from
http://www.sysinternals.com/Utilities/TcpView.html
--
The Software Tailor
Las Vegas USA
"JClark" wrote:
> On Fri, 4 Aug 2006 18:00:02 -0700, Bob Campbell
> <Softwar...@msn.com> wrote:
>
> >Do you see all three computers on each computer using the View network
> >computers tool in My Network Places? (This doesn't always accurately report
> >sharing, so you can also use the Net View command at the command prompt). Do
> >you get any errors?
> >
> >Have you shared your drive C on all 3 computers? When you set up the share,
> >it will ask you if you want to allow access for others to see (that is, open)
> >the shared folder.
> Hello Bob:
>
> >Do you see all three computers
> The computers and folders are all visible all the way around the three
> boxes in My Network Places|Entire Network|Microsoft Windows
> Network|Workgroup
> When I click on Computer "A" from "B" or "C" in Workgroup, I see the
> shared folders on "A" but I can't open that folder or see the files. I
> can see the folders and open the files going the other way, that is
> from "A" to "B" and from "A" to "C"
>
> >the Net View command
> Net view from cmd shows all shared folders in all directions, as does
> ping \\computer_name or ipaddress.
>
> >Have you shared your drive C on all 3 computers?
>
> I haven't shared the root folder on the computers, just individual
> folders. When I share a folder, however, I don't get asked if I want
> to allow access for others to see or open the folders. There is a box
> to allow others to "change" the files. Maybe it's different with
> Simple File sharing, which I am using.
>
> I appreciate your input and suggestions. Right now I'm working on
> possibilities that the NVIDIA nforce LAN may be messing me up, since
> it is on computer "A", which is the one which refuses to share its
> files. Problems have been reported with this networking controller.
>
> Thanks again!
>
> Jack
>
Chuck
>Hi Chuck,
>Thanks for your interest. Here are the results of the "browstat
>status" from each computer. I also have results of "ipconfig /all" and
>"net config server" for each one, as suggested on your site. But to
>avoid clutter, I'll post just the "browstat status", as you requested.
>Much appreciation!
>Jack
>***************************************************************************************
>Computer "A" (AMD64)
>
>Status for domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
> Browsing is active on domain.
> Master browser name is: ASUS-AMD
>Could not open key in registry, error = 5 Unable to determine
>build of browser master: 5
> \\\\ASUS-AMD . Version:05.01 Flags: 51003 NT POTENTIAL
>MASTER
> 1 backup servers retrieved from master ASUS-AMD
> \\ASUS-AMD
> There are 3 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}
>**************************************************************************************
>Computer "B" (ASUS-AMD)
>
>Status for domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
> 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 3 servers in domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
> There are 1 domains in domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
>*****************************************************************************************
>Computer "C" (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 3 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}
>******************************************************************************************
OK, Jack,
Interesting. To start, look at AMD64 and ASUS-AMD.
Computer "A" (AMD64)
Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{761B3B7A-475C-4B27-82C8-BF09738AB7F6}
Browsing is active on domain.
Master browser name is: ASUS-AMD
Could not open key in registry, error = 5 Unable to determine
build of browser master: 5
Computer "B" (ASUS-AMD)
Status for domain WORKGROUP on transport
\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
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 and ASUS-AMD see each other as master browsers. Are both of them desktop
units?
# Shut off the browser service on MBX-notebook.
# Power all 3 computers off.
# Decide which computer you want to reliably be the master browser. Power that
computer on.
# As soon as the master browser computer is online, power the other desktop
computer on.
# Power the laptop on.
Now the good news is that all 3 computers see each other ("There are 3 servers
in domain WORKGROUP" and there's only one workgroup segment "There are 1 domains
in domain WORKGROUP"). The error 53 against AMD64, and the error 5 against
ASUS-AMD, though, may be a challenge.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error53
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error5>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error5
Chuck
>Chuck:
>Here are the browstat results for the three computers, with AMD64 and
>ASUS-AMD running the computer browser service, and disabled on
>mbx-notebook.
>An aside: I notice when I run browstat on the second desktop
>(ASUS-AMD), my firewall tells me "Windows browser service is trying to
>access the internet. Destination IP: 149.174.36.116:DNS. If I don't
>allow it, browstat doesn't complete.
>I'm not sure what this means ... DNS not accessible from that computer
>only?
>Anyway, here's browstat for the three computers:
>Now I'll go look at your references for error 53.
>
>Appreciate your help greatly
>
>Jack
>**********************************************************************************************
>AMD64 (now recognized as master browser!) I didn't suspect the order
>of turning on the computers was important.
>
>
>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 3 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}
>****************************************************************************************************
>ASUS-AMD
>
>
>Status for domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
> 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 3 servers in domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
> There are 1 domains in domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
>******************************************************************************************************
>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 3 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,
The master browser election is an intriguing process. Generally, one computer
should be elected as master browser, and that's it. One of the criteria for
election is "was previously a master browser". So if there's another election,
both computers may continue electing themselves, unless you start one without
the other being up. That one gets elected, and when the second and third
restart, they both recognise the first.
Now the error = 53, and "(ASUS-AMD), my firewall tells me "Windows browser
service is trying to access the internet. Destination IP: 149.174.36.116:DNS.""
Let's look at "ipconfig /all" now, on all computers.
Chuck
>Hello Chuck. The ipconfig /all output for the three computers follows.
>Meanwhile, I've put computer names and ip addresses into the hosts
>file on all computers. I am now able to ping all computers back and
>forth both with ip addresses and computer names.
>Many thanks again.
>Jack
>********************************************************************************************
>AMD64
>
>Windows IP Configuration
> Host Name . . . . . . . . . . . . : AMD64
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
>Ethernet adapter Local Area Connection :
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : NVIDIA nForce Networking
>Controller
> Physical Address. . . . . . . . . : 00-11-D8-70-4A-01
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.150
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 65.32.1.65
> 65.32.1.70
>*************************************************************************
>ASUS-AMD
>
>Windows IP Configuration
> Host Name . . . . . . . . . . . . : asus-amd
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
>Ethernet adapter Local Area Connection:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
>PCI TX NIC (3C905B-TX)
> Physical Address. . . . . . . . . : 00-04-76-E3-76-AD
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.151
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 65.32.1.65
> 65.32.1.70
>*****************************************************************************
>MBX-Notebook
>
>Windows IP Configuration
> Host Name . . . . . . . . . . . . : MBX-NOTEBOOK
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
>Ethernet adapter Wireless Network Connection:
> Media State . . . . . . . . . . . : Media disconnected
> Description . . . . . . . . . . . : Intel(R) PRO/Wireless
>2200BG Network Connection
> Physical Address. . . . . . . . . : 00-0E-35-E4-82-74
>
>Ethernet adapter Local Area Connection:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
>Ethernet
> Physical Address. . . . . . . . . : 00-11-D8-25-65-2C
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.152
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 65.32.1.65
> 65.32.1.70
>*****************************************************************************
Hi Jack,
OK, here's a problem.
>Windows IP Configuration
> Host Name . . . . . . . . . . . . : AMD64
>Ethernet adapter Local Area Connection :
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : NVIDIA nForce Networking
>Controller
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html
Now you said earlier
> Motherboard (ASUS A8N-SLI) on computer "A" has onboard LAN with Nvidia
> nForce controller, but I've uninstalled it and reinstalled it without
> installing the firewall component and have not enabled the Armor On
> feature.
But you did install the driver (or it wouldn't work). Do us both a favour, and
enumerate the LSP / Winsock. Let's not try any LSP fixes just yet, but see what
you have, OK?
<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
Chuck
>Chuck: Here's the output of the winsock info. Only for the master
>browser computer AMD64.
>With thanks,
>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
>
>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
Interesting, Jack. Here's mine:
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_{17977DB7-58BE-4500-B84B-304D9D82FD31}] SEQPACKET 0
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1038
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_{17977DB7-58BE-4500-B84B-304D9D82FD31}] DATAGRAM 0
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1039
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_{3B6F355E-0FDE-4618-8E02-725904C9E32E}] SEQPACKET 4
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1040
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_{3B6F355E-0FDE-4618-8E02-725904C9E32E}] DATAGRAM 4
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1041
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_{ABE1143C-2029-4AE5-8894-2915F7A0F789}] SEQPACKET 1
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1042
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_{ABE1143C-2029-4AE5-8894-2915F7A0F789}] DATAGRAM 1
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: 2
Protocol: -1
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{481012E9-6F98-411D-A3E4-3839A42E481E}] SEQPACKET 2
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: 5
Protocol: -2
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{481012E9-6F98-411D-A3E4-3839A42E481E}] DATAGRAM 2
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: 2
Protocol: -2
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8E91B3C2-4AE1-48D1-A459-9F686EE93F81}] SEQPACKET 3
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: 5
Protocol: -3
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{8E91B3C2-4AE1-48D1-A459-9F686EE93F81}] DATAGRAM 3
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: 2
Protocol: -3
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{C56BAAC4-54FA-48E8-8EDC-C99FB4DF3CAD}] SEQPACKET 5
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: 5
Protocol: -5
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{C56BAAC4-54FA-48E8-8EDC-C99FB4DF3CAD}] DATAGRAM 5
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: 2
Protocol: -5
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{3DF3312A-3647-4CB2-A63F-9E5DC57C49F5}] SEQPACKET 6
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: 5
Protocol: -6
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{3DF3312A-3647-4CB2-A63F-9E5DC57C49F5}] DATAGRAM 6
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1051
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -6
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
There's a bit of a difference.
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html
Chuck
>On Tue, 08 Aug 2006 08:21:00 GMT, JClark <jcl...@nomail.invalid>
>wrote:
><snipped>
>Chuck:
>Apologies for another post before getting your reply to the last one,
>but I thought it might be important.
>
>Another hypothesis for cause of this problem came into my mind this
>morning. I have been running an anti-Trojan program on this computer
>for a long time (BOClean). There is one function of the program which
>is called "Automatic cleanup of Winsock Connectivity".
>This is turned "off" in my configuration currently, but I don't
>remember when I disabled that function. It's possible that my current
>problem may have been caused by BOClean changing connectivity/Winsock
>functions while it was cleaning up after discovering a Trojan.
>According to the online Help page,
>http://www.nsclean.com/supboc.html#section6
>(Look under "Right side" "Fifth item")
>when a Trojan is discovered, BOClean does the following things:
>1. Deletes the Hosts file
>2. Removes settings placed into "Zones" registry keys for "Domains",
>"Ranges" and "Protocol" Defaults settings.
>3. Examines the Winsock2 keys, and if a trojan is found which affects
>the LSP stack, BOClean will reshuffle the the winsock subkeys. This
>will require completely reloading networking.
> ******************
>
>BOClean also advises using automatic network configuration using DHCP,
>and if you do not, to leave "unchecked" the configuration item
>"Automatic cleanup of winsock connectivity".
>
>
>If this hypothesis is true, it would seem that BOClean may have done
>what LSPFIX does, and that I will need to "reinstall networking"
>...whatever that means!
>
>Jack
Jack,
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
Chuck
>On Tue, 08 Aug 2006 15:21:31 -0700, Chuck <no...@example.net> wrote:
>
>>On Tue, 08 Aug 2006 16:44:50 GMT, JClark <jcl...@nomail.invalid> wrote:
>>
>>>On Tue, 08 Aug 2006 08:21:00 GMT, JClark <jcl...@nomail.invalid>
>>>wrote:
>>
>>><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.
Chuck
>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
>******************************************************************************
>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
>
>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
>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
>************************************************************************************
Jack,
IPX/SPX is a protocol, like TCP/IP. It's like a different language. If the
other computers in your network aren't speaking IPX/SPX, it just gets in the
way. And even with two (or more) computers both speaking IPX/SPX, in addition
to TCP/IP, it's a nuisance.
Now the Winsock catalogue lists that you provided late in the day 8/7 had
neither NetBT (which you need) nor IPX/SPX (which you don't need). You reset
IP, and both NetBT and IPX/SPX came back. So let's see what happens when you un
install IPX/SPX.
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
>********************************************************************************
>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
Jack,
This looks better now. So what of the problems? Does the other computer look
similar?
Chuck
>On Wed, 09 Aug 2006 21:07:37 -0700, Chuck <no...@example.net> wrote:
>
>>On Thu, 10 Aug 2006 01:22:20 GMT, JClark <jcl...@nomail.invalid> wrote:
>>
>>><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
>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
>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
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.
Chuck
>On Thu, 10 Aug 2006 14:34:49 -0700, Chuck <no...@example.net> wrote:
>
>>On Thu, 10 Aug 2006 20:27:31 GMT, JClark <jcl...@nomail.invalid> wrote:
<SNIP>
>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
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.
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.
Chuck
>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}
OK, Jack,
We are making progress. You're seeing "error = 5" on mbx-notebook. In other
words, it's doing name resolution properly, and being blocked from registry
access.
<http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error5>
http://nitecruzr.blogspot.com/2005/05/browstat-utility-from-microsoft.html#Error5
Now it gets tricky. You could get an "error = 5" ("access denied") from a
firewall, or from (lack of) authentication. Are you certain that your non-Guest
authentication is properly setup? If so, then you're looking at a firewall
issue again. If not, looking at a firewall issue will be a waste of time.
<http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html>
http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html
From mbx-notebook, hit Start, select Run, and type in "\\amd64\c$" (less the
""), and hit OK. What do you get?
And let's see what CPSServ shows us.
Chuck
>Hello Chuck,
>With \\amd64\c$ from mbx-notebook, I get a box with "keys" logo at the
>top, labelled "Connect to AMD64". Then below that there is text
>"connecting to AMD64" Box below that is greyed out: Username
>amd64\guest, below that is a non-greyed out box for password.
>(The guest account on both computers has blank password, and I've
>reset it that way to be sure). But when I click OK, nothing happens.
<SNIP>
OK, Jack,
If AMD64 is requesting Guest authentication, then you don't have non-Guest
authentication setup properly.
1) Disable Simple File Sharing.
<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
2) Setup a common, non-Guest account on each computer, with identical, non-blank
password.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Activate>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Activate
Then try all diagnostics again.
Chuck
<SNIP>
>Good Morning, Chuck. And for the twentieth time, I appeciate your
>tenacity and effort in trying to help me solve this frustrating
>problem.
>
>Update:
>I think I followed your suggestions properly. Here's what I did:
>1. Established a new account on all three (ASUS-AMD is back up!)
>computers. They are adminstrative accounts with identical passwords.
>2. Simple file sharing disabled on all three.
>3. Created a test folder on AMD64, with full permissions for everyone
>under "sharing" tab, and with "read" permissions for each user and
>group under the "security" tab. (Some were greyed out).
>4. Activated this user name on each computer with "net user name
>/active:yes"
>5. Checked TCP/IP for correct settings and did "repair" to flush.
>6. Put remote registry service on automatic. There are very few
>services now disabled (alerter, messenger, clip book)
>6. Rebooted.
>7. Tested system...Result --->No change. Working from amd64, I can
>easily see and copy files from the other two computers. Working from
>either asus-amd or mbx-notebook, I can see files and folders on amd64,
>but I cannot open them. Tried again with all firewalls disabled. No
>change.
>
>Here is output from all three computers for browstat and cpsserv.
>****************************************************************************
>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 3 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}
> *******
>Start CPSServ V1.02 - AMD64
>
>Find Computer Browser ("browser")
>
>Checking \\AMD64...
>Found browser on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find TCP/IP NetBIOS Helper ("lmhosts")
>
>Checking \\AMD64...
>Found lmhosts on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Remote Registry ("remoteregistry")
>
>Checking \\AMD64...
>Found remoteregistry on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Server ("server")
>
>Checking \\AMD64...
>Found server on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find WF / ICS ("sharedaccess")
>
>Checking \\AMD64...
>Found sharedaccess on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Workstation ("workstation")
>
>Checking \\AMD64...
>Found workstation on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>End CPSServ V1.02 - AMD64
>****************************************************************************
>asus-amd
>
>
>Status for domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
> 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 3 servers in domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
> There are 1 domains in domain WORKGROUP on transport
>\Device\NetBT_Tcpip_{8CD7E588-9C98-4987-96B1-1EAAE0359F75}
> ******************
>Start CPSServ V1.02 - ASUS-AMD
>
>Find Computer Browser ("browser")
>
>Checking \\AMD64...
>Found browser on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find TCP/IP NetBIOS Helper ("lmhosts")
>
>Checking \\AMD64...
>Found lmhosts on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Remote Registry ("remoteregistry")
>
>Checking \\AMD64...
>Found remoteregistry on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Server ("server")
>
>Checking \\AMD64...
>Found server on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find WF / ICS ("sharedaccess")
>
>Checking \\AMD64...
>Found sharedaccess on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Workstation ("workstation")
>
>Checking \\AMD64...
>Found workstation on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>End CPSServ V1.02 - ASUS-AMD
>***************************************************************
>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
> Master browser is running build 2600
> 1 backup servers retrieved from master AMD64
> \\AMD64
> There are 3 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}
> ********************
>Start CPSServ V1.02 - MBX-NOTEBOOK
>
>Find Computer Browser ("browser")
>
>Checking \\AMD64...
>Found browser on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find TCP/IP NetBIOS Helper ("lmhosts")
>
>Checking \\AMD64...
>Found lmhosts on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Remote Registry ("remoteregistry")
>
>Checking \\AMD64...
>Found remoteregistry on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Server ("server")
>
>Checking \\AMD64...
>Found server on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find WF / ICS ("sharedaccess")
>
>Checking \\AMD64...
>Found sharedaccess on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>
>Find Workstation ("workstation")
>
>Checking \\AMD64...
>Found workstation on:
>
>\\AMD64
>
>Checking \\ASUS-AMD...
>\\ASUS-AMD
>
>Checking \\MBX-NOTEBOOK...
>\\MBX-NOTEBOOK
>
>End CPSServ V1.02 - MBX-NOTEBOOK
> *********
Jack,
OK, you have all 3 computers talking to each other properly. All 3 computers
recognise the same master browser. All 3 able to access the registry on the
master browser. Clean diagnostic readings are a good starting point.
Now, it's time to start looking at NTFS and share permissions on AMD64. Note
the differences between share and NTFS permissions. NTFS affects local and
network access; share affects network access.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help
<http://nitecruzr.blogspot.com/2005/09/server-access-authorisation.html>
http://nitecruzr.blogspot.com/2005/09/server-access-authorisation.html
Look at strange share permissions.
<http://nitecruzr.blogspot.com/2005/11/irregularities-in-individual-share.html>
http://nitecruzr.blogspot.com/2005/11/irregularities-in-individual-share.html
Look at how granular (detailed) NTFS permissions can be. You can specify
permissions to read, to write, to even list contents of a given folder. Make
sure that you don't have any odd NTFS settings.
And there's always the possibility of the nVidia firewall being involved. Or
another personal firewall that you have overlooked.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html
Chuck
>On Sat, 12 Aug 2006 18:42:04 GMT, JClark <jcl...@nomail.invalid>
>wrote:
>>>><snip>
>>
>><snip>
>>***********************************************************
>>Soooo, Chuck, I guess I am essentially out of luck, and if my
>>persistent search for a "hidden" firewall proves to be fruitless, I
>>guess I must accept defeat. Or reinstall Windows.
>>
>>Nothing came of the NVIDIA forum post except the one reply I quoted,
>>and there is nothing there which applies to my situation, although
>>they've had lots of firewall and driver problems, but not this kind.
>>
>>I sincerely appreciate all your time and effort.
>>I will post a followup.
>>Of course if you have any other suggestions (please!), I'll be most
>>eager to pursue them
>>
>>Jack
>>
>>
>Hello Chuck,
>Well, finally some good news. Success! You were right all along in
>suspecting a "hidden firewall" in the NVIDIA system. Apparently when I
>installed the latest drivers, a network manager was installed. This
>was acting as a firewall despite not having the actual NVIDIA firewall
>installed and despite not activating the firewall software (Active
>Armor or Armor On or something like that.) Fortunately, I was able to
>uninstall this manager without uninstalling the "NVIDIA drivers" which
>was a separate entity in the "Add-Remove programs". When I rebooted
>and went into Device Manager, I could see that there was now an older
>date on the driver for the NVIDIA network controller, which Windows
>must have silently installed.
>Caveat Emptor!
>My mind is so muddled now that I can't remember the exact name of the
>function I deleted.
>But I get easy access to the "server" now from the two secondary
>computers. Amen!
>Can't thank you enough for all the work you put in on this with me. I
>hope others may learn from this. If I have the energy (a bit burnt out
>now), I may go through this process again and make some notes to post
>for those who may be faced with this problem in the future. No help
>from NVIDIA or their forum, sadly.
>Sincere appreciation,
>Jack
All right, Jack!! Way to go!!
YOU will be the help to nVidia customers. Please write up what you can, and
whatever you write up will go into my article, and you will be able to help
other folks like you.
JClark
Hi Chuck.
I went through the process of reinstalling and uninstalling the
troublesome NVIDIA network access manager, just so I could plan a post
with some specific instructions for some unfortunate individual like
me and try to save that person some time and frustration. So I plan to
post it as a new topic under the heading
"NVIDIA "hidden firewall" causes networking problem"
I thought it might be more retrievable for someone with a similar
problem if I put NVIDIA in the title of the topic.
Many thanks again!
Jack