Networking only works "one way"

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

 

[JClark]

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.

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.

CPSServ for both computers follows:
*******************************************************************************
amd64
Start CPSServ V1.02 - AMD64

Find Computer Browser ("browser")

Checking \\AMD64...
Found browser on:

\\AMD64

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


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...
Found lmhosts on:

\\AMD64

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


Find Remote Registry ("remoteregistry")

Checking \\AMD64...
Found remoteregistry on:

\\AMD64

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


Find Server ("server")

Checking \\AMD64...
Found server on:

\\AMD64

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


Find WF / ICS ("sharedaccess")

Checking \\AMD64...
Found sharedaccess on:

\\AMD64

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


Find Workstation ("workstation")

Checking \\AMD64...
Found workstation on:

\\AMD64

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

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

Find Computer Browser ("browser")

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

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

\\MBX-NOTEBOOK


Find TCP/IP NetBIOS Helper ("lmhosts")

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

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

\\MBX-NOTEBOOK


Find Remote Registry ("remoteregistry")

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

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

\\MBX-NOTEBOOK


Find Server ("server")

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

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

\\MBX-NOTEBOOK


Find WF / ICS ("sharedaccess")

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

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

\\MBX-NOTEBOOK


Find Workstation ("workstation")

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

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

\\MBX-NOTEBOOK

End CPSServ V1.02 - MBX-NOTEBOOK

 

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

 

[JClark]

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

Hi Chuck,
Took a while to get the new account on each computer and then run the
diagnostics. I'm not sure how many of them you wanted, but we've been
focusing on browstat and cpsserv, so those are the ones I've included
in this post.
Many thanks for leading me through this.
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}
**********
Start CPSServ V1.02 - AMD64

Find Computer Browser ("browser")

Checking \\AMD64...
Found browser on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...
Found lmhosts on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Remote Registry ("remoteregistry")

Checking \\AMD64...
Found remoteregistry on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Server ("server")

Checking \\AMD64...
Found server on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find WF / ICS ("sharedaccess")

Checking \\AMD64...
Found sharedaccess on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Workstation ("workstation")

Checking \\AMD64...
Found workstation on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK

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

Start CPSServ V1.02 - MBX-NOTEBOOK

Find Computer Browser ("browser")

Checking \\AMD64...
Found browser on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...
Found lmhosts on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Remote Registry ("remoteregistry")

Checking \\AMD64...
Found remoteregistry on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Server ("server")

Checking \\AMD64...
Found server on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find WF / ICS ("sharedaccess")

Checking \\AMD64...
Found sharedaccess on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Workstation ("workstation")

Checking \\AMD64...
Found workstation on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK

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

Find Computer Browser ("browser")

Checking \\AMD64...
Found browser on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find TCP/IP NetBIOS Helper ("lmhosts")

Checking \\AMD64...
Found lmhosts on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Remote Registry ("remoteregistry")

Checking \\AMD64...
Found remoteregistry on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Server ("server")

Checking \\AMD64...
Found server on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find WF / ICS ("sharedaccess")

Checking \\AMD64...
Found sharedaccess on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK


Find Workstation ("workstation")

Checking \\AMD64...
Found workstation on:

\\AMD64

Checking \\MBX-NOTEBOOK...
\\MBX-NOTEBOOK

End CPSServ V1.02 - MBX-NOTEBOOK

 

[JClark]

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

 

[Chuck]

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

 

[JClark]

Hello Chuck,

I think I scrupulously followed your latest suggestions.

1. Advanced file sharing, with each shared folder giving full access
under "permissions" for access from the network, and each folder
giving full access under "security" to the all three user accounts,
each of which has identical names, password, and each of which has
been activated.

2. I looked for "Strange share permissions" Nothing found.
My "Restrict Anonymous" is set to 0.
The "RestrictNullSessAccess" value is not present in my registry key
[HKLM\System\CurrentControlSet\Services\LanManServer\Parameters]
The closest thing there is "AdjustedNullSessionPipes", which does in
fact have a value of "1", but I was fearful of changing it.

3. Grasping for other possible explanations, I went through secpol.msc
and services.msc. The only thing I came up with was a possible action
I might have taken in the past when I probably disabled then
re-enabled firewall service. That may mess things up apparently. From
MS:

"When you disable the Windows Firewall service on your Microsoft
Windows XP Service Pack 2 (SP2)-based computer, the Computer Browser
service stops after five minutes...."

Presumably browser service doesn't function properly thereafter,
because MS had to create a hotfix for it.

http://support.microsoft.com/default.aspx?scid=kb;en-us;889320

By the way, on your site,
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Activate
you might want to mention that if your user account name has two or
more words, you must enclose them in quotes. I know you strive to
provide details for the less computer literate.

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

 

[JClark]

<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

 

[Chuck]

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]

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.

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

 

[DBello]

Cant see old PC with new PC using XP w/File Settings and Transfer Wizard

Hi,
Dont know if this is related. My old Dell PC when connected to my new Dell Desktop (thru bi-directional network cable) can "SEE" the new PC and I can map to it. However the NEW cant see the OLD PC. When I try to PING the old PC I get timeouts. There are no firewalls currently running on the OLD PC. What is preventing me from PINGING the OLD PC? Mapping to the OLD PC?

Dave