Re: Networking only works "one way"

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Fri, 11 Aug 2006 16:23:55 GMT, JClark <jclark@xxxxxxxxxxxxxx> wrote:

On Fri, 11 Aug 2006 08:56:15 -0700, Chuck <none@xxxxxxxxxxx> wrote:

On Fri, 11 Aug 2006 15:03:22 GMT, JClark <jclark@xxxxxxxxxxxxxx> wrote:

On Fri, 11 Aug 2006 07:42:05 -0700, Chuck <none@xxxxxxxxxxx> wrote:

On Fri, 11 Aug 2006 10:16:27 GMT, JClark <jclark@xxxxxxxxxxxxxx> wrote:

On Thu, 10 Aug 2006 20:20:28 -0700, Chuck <none@xxxxxxxxxxx> wrote:

On Fri, 11 Aug 2006 00:57:02 GMT, JClark <jclark@xxxxxxxxxxxxxx> wrote:

On Thu, 10 Aug 2006 14:34:49 -0700, Chuck <none@xxxxxxxxxxx> wrote:

On Thu, 10 Aug 2006 20:27:31 GMT, JClark <jclark@xxxxxxxxxxxxxx> wrote:

<SNIP>

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

If you can see the files and attach to the other machine it will be a file
permission problem.
If it was networking you would have a different problem.

Search Microsoft for help on file sharing.

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

With thanks.
Jack

Oh boy.

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

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

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

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

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

Let's try some relational analysis. You'll have to download PSExec (free) (I
hope). Run it on all 3 computers please. Attach output here.
<http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html>
http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html
Hello Chuck,
Wow, you've put a lot of work into my problem. I'm very grateful.
Here's the output from cpsserv for the three computers:

<SNIP>

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

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

Find TCP/IP NetBIOS Helper ("lmhosts")

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

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

.. and the above repeated for all 3 computers. You gotta have TCP/IP NetBIOS
Helper ("lmhosts") running on each computer.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components
Good Morning again, Chuck
Well, sadly, things have deteriorated a bit. I'm mystified.
I changed the TCP/IP netbios helper service to "automatic" on all
three comuters. Rebooted. This service is, of course, now "started".
This alone didn't change things. I ran the network connection wizard
again on all three computers, disabled Windows Firewall, and then
rebooted.

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

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

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

Jack

Jack,

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

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

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

Jack

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

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

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

Jack,

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

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

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

For right now, let's get administrative access working, and the RRS running, on
each computer.
Thanks, Chuck. I put remote registry service to automatic, rebooted.
Here's browstat from both. Yes, small steps are good.
Even with remote registry automatic on both computers,and rebooted, I
still get error from mbx-notebook. I'll double check again.

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

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


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

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.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.

Quantcast