Networking only works "one way"

J

JClark

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
 
G

Guest

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.
 
J

JClark

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.
Click to expand...
Hello Bob:
Do you see all three computers
Click to expand...
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
Click to expand...
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?
Click to expand...

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
 
C

Chuck

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
Click to expand...

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
 
G

Guest

Hi Jack,

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
 
J

JClark

Hi Jack,

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
Click to expand...
Bob,
If there is a VPN running, I don't know about it and didn't set it up
(or don't remember!)
Here are the results of the netstat -a for each computer. I downloaded
Sysinternals TCPView, but haven't had a chance to work with it yet.
Thanks again.
Jack
****************************************************************************
Computer "A" (Is DomainMaster=TRUE) Name: AMD64

Active Connections

Proto Local Address Foreign Address State
TCP AMD64:smtp AMD64:0 LISTENING
TCP AMD64:http AMD64:0 LISTENING
TCP AMD64:epmap AMD64:0 LISTENING
TCP AMD64:https AMD64:0 LISTENING
TCP AMD64:microsoft-ds AMD64:0 LISTENING
TCP AMD64:1026 AMD64:0 LISTENING
TCP AMD64:3476 AMD64:0 LISTENING
TCP AMD64:1027 AMD64:0 LISTENING
TCP AMD64:3476 AMD64:0 LISTENING
TCP AMD64:10110 AMD64:0 LISTENING
TCP AMD64:netbios-ssn AMD64:0 LISTENING
TCP AMD64:1055 news.easynews.com:nntp ESTABLISHED
UDP AMD64:microsoft-ds *:*
UDP AMD64:1025 *:*
UDP AMD64:3456 *:*
UDP AMD64:ntp *:*
UDP AMD64:1900 *:*
UDP AMD64:ntp *:*
UDP AMD64:netbios-ns *:*
UDP AMD64:netbios-dgm *:*
UDP AMD64:1900 *:*
************************************************************************************
Computer "B" (IsDomainMaster=FALSE) Name: Asus-AMD

Active Connections

Proto Local Address Foreign Address State
TCP asus-amd:epmap asus-amd:0 LISTENING
TCP asus-amd:microsoft-ds asus-amd:0 LISTENING
TCP asus-amd:1025 asus-amd:0 LISTENING
TCP asus-amd:10110 asus-amd:0 LISTENING
TCP asus-amd:netbios-ssn asus-amd:0 LISTENING
UDP asus-amd:microsoft-ds *:*
UDP asus-amd:isakmp *:*
UDP asus-amd:1026 *:*
UDP asus-amd:4500 *:*
UDP asus-amd:ntp *:*
UDP asus-amd:1900 *:*
UDP asus-amd:ntp *:*
UDP asus-amd:netbios-ns *:*
UDP asus-amd:netbios-dgm *:*
UDP asus-amd:1900 *:*
**********************************************************************************************
Computer "C" (IsDomainMaster=False) Name: MBX-Notebook

Active Connections

Proto Local Address Foreign Address State
TCP MBX-NOTEBOOK:epmap MBX-NOTEBOOK:0 LISTENING
TCP MBX-NOTEBOOK:microsoft-ds MBX-NOTEBOOK:0 LISTENING
TCP MBX-NOTEBOOK:1025 MBX-NOTEBOOK:0 LISTENING
TCP MBX-NOTEBOOK:1027 MBX-NOTEBOOK:0 LISTENING
TCP MBX-NOTEBOOK:10110 MBX-NOTEBOOK:0 LISTENING
TCP MBX-NOTEBOOK:netbios-ssn MBX-NOTEBOOK:0 LISTENING
TCP MBX-NOTEBOOK:1091 64.21.46.136:http TIME_WAIT
TCP MBX-NOTEBOOK:1092 64.21.46.137:http TIME_WAIT
UDP MBX-NOTEBOOK:microsoft-ds *:*
UDP MBX-NOTEBOOK:isakmp *:*
UDP MBX-NOTEBOOK:1028 *:*
UDP MBX-NOTEBOOK:1030 *:*
UDP MBX-NOTEBOOK:1031 *:*
UDP MBX-NOTEBOOK:1032 *:*
UDP MBX-NOTEBOOK:1033 *:*
UDP MBX-NOTEBOOK:1034 *:*
UDP MBX-NOTEBOOK:1035 *:*
UDP MBX-NOTEBOOK:4500 *:*
UDP MBX-NOTEBOOK:ntp *:*
UDP MBX-NOTEBOOK:1900 *:*
UDP MBX-NOTEBOOK:ntp *:*
UDP MBX-NOTEBOOK:netbios-ns *:*
UDP MBX-NOTEBOOK:netbios-dgm *:*
UDP MBX-NOTEBOOK:1900 *:*
***********************************************************************************************************
 
J

JClark

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
Click to expand...
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}
******************************************************************************************
 
C

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}
******************************************************************************************
Click to expand...

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
 
J

JClark

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
Click to expand...
Hi Chuck:
I've printed the above instructions and will comply. But I want to be
sure that you want me to disble the computer browser service *only* on
the laptop (mbx-notebook) and leave computer browser service on
automatic for both the desktops (amd64 and asus-amd)?
(AMD64 is the one I want to be the master browser.)

Incidentally, I had already changed the value in the registry
HKLM_SYSTEM_CURRENT
CONTROLSET_SERVICES_BROWSER_PARAMETERS_IsDomainMaster
to TRUE for AMD64 and to FALSE for the other two computers. I must
have gotten that from your site somewhere, but it's all getting a bit
foggy. Should I leave the settings that way? Doesn't seem to be
helping.

Thanks again
Jack
 
J

JClark

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
Click to expand...
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}
 
C

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}
Click to expand...

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.
 
J

JClark

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.
Click to expand...
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
*****************************************************************************
 
C

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
*****************************************************************************
Click to expand...

Hi Jack,

OK, here's a problem.
Windows IP Configuration
Host Name . . . . . . . . . . . . : AMD64
Click to expand...
Ethernet adapter Local Area Connection :
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Click to expand...
<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.
Click to expand...

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
 
J

JClark

Hi Jack,

OK, here's a problem.


<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

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
Click to expand...
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
 
C

Chuck

Hi Jack,

OK, here's a problem.


<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

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
Click to expand...
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
Click to expand...

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
 
J

JClark

<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
 
C

Chuck

<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
Click to expand...

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
 
J

JClark

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
Click to expand...
Hello again Chuck:
"I don't
Click to expand...
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
 
C

Chuck

Hello again Chuck:

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
Click to expand...

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.
 
J

JClark

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.
Click to expand...
Good Morning Chuck,
Again, thanks for sticking with me on this.
read the article
Click to expand...
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
Click to expand...
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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

workgroup File sharing problem XP SP2 2
One Way Connectivity for 2 of 3 computers on Win XP Workgroup Netw 2
workgroup networking with home and pro 4
why is "my network places" empty? 0
File Sharing Issues - Can't Get My Home Network Running 5
File sharing problem WinXP Home and WinXP Pro 1
2 network pc's problem 1
VPN - can see files but can't access 1

Top