Re: Work computer I've run the diagnostics

On Sun, 18 Jun 2006 09:29:01 -0700, Ken W <KenW@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

"Chuck" wrote:

On Fri, 16 Jun 2006 04:46:02 -0700, Ken W <KenW@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

"Chuck" wrote:

On Thu, 15 Jun 2006 05:55:03 -0700, Ken W <KenW@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

<SNIP>

As you requested, following your instructions, this is the result on the
work computer running XP Professional:

Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.

Below is the home computer, running XP Media Edition:
Server Name Remark

-------------------------------------------------------------------------------
\\JANET

\\WOLFEKE Ken Wolfe

The command completed successfully.

OK, Ken,

I covered (hopefully tested) the bottom posting issue in my other post. So
let's address the problem.

So both computers see each other, in "net view".

Now "net view" gives a high level view of the network, from each computer. To
diagnose this problem, we need "browstat status", "ipconfig /all", "net config
server", and "net config workstation", from each computer.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Thanks for the instructions on how to post under a message. I think I did it
this time. Hopefully, it worked.

Here are the results for the work computer, running windows XP Professional
SP2:

<SNIP>

Ken,

You nailed it. The posting anyway.

The diagnostics, so far, are clean.
# Both computers on same physical segment 192.168.1.0/24.
# Both computers in same workgroup "HORIZONTECH", acknowledging the same master
browser "WOLFEKE", and seeing 2 computers.
# Both computers showing NetBT, neither hidden.

<BIG SNIP>

OK, Ken,

CDiag shows 2 positives:
# WOLFEKE cannot "net view" itself by IP address - neither as "192.168.1.102",
nor as "127.0.0.1".
# JANET, on the other hand, CAN "net view" WOLFEKE, as "192.168.1.102".

First, is NetBT explicitly Enabled on WOLFEKE?
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Next, are there any misconfigured or overlooked personal firewalls, or other
security component on WOLFEKE? There are several other possibilities too, and
any might be the cause of your problem. Read this article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

Finally, we'll look at LSP / Winsock / TCP/IP corruption.
<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

I explicitly enabled NetBT per your instructions on both computers. They
were both set to default. I then tried to read shared folders of the work
computer (WOLFEKE) from the home computer (JANET) (you may recall that it
seems to work fine the other way - work (WOLFEKE) is able to read and write
files on home (JANET)). All of the shared folders that I created on WOLFEKE
were not accessible, but the WOLFEKE\SHARE folder that XP created was both
read and write accessible. It's possible that it's always been this way
because I never checked every shared folder before, but there is definitely,
at least now, a difference between shared folders that I created and the
shared folder that XP created on the work computer (WOLFEKE).

I didn't try your other suggestions below making sure NetBT was enabled on
both machines because I didn't think it was relevant anymore in light of the
information I learned in the previous paragraph.

Ken,

OK, with NetBT properly Enabled, we have a start. Now, if you have a situation
where some folders are accessible, and others aren't, you have to adjust
permissioning.
<http://nitecruzr.blogspot.com/2005/11/irregularities-in-individual-share.html>
http://nitecruzr.blogspot.com/2005/11/irregularities-in-individual-share.html

So let's try one suggestion at a time. LSP / Winsock corruption may not be an
issue here. That's good news. Keep going now.

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

Relevant Pages

  • Re: Work computer Ive run the diagnostics
    ... <SNIP> ... Here are the results for the work computer, ... # Both computers showing NetBT, ... is NetBT explicitly Enabled on WOLFEKE? ...
    (microsoft.public.windowsxp.network_web)
  • Re: 2 different networks at the same time?
    ... When I left clicked on My Network Places on the work computer, ... eventually the home computer appears in the shared ... and I could view the files in the shared folders on the home ...
    (microsoft.public.windowsxp.network_web)
  • Re: Work computer Ive run the diagnostics
    ... <SNIP> ... Here are the results for the work computer, ... is NetBT explicitly Enabled on WOLFEKE? ... All of the shared folders that I created on WOLFEKE ...
    (microsoft.public.windowsxp.network_web)
  • Re: Work computer Ive run the diagnostics
    ... <SNIP> ... is NetBT explicitly Enabled on WOLFEKE? ... All of the shared folders that I created on WOLFEKE ... You cannot add permissions to a remote account. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Work computer Ive run the diagnostics
    ... <SNIP> ... is NetBT explicitly Enabled on WOLFEKE? ... All of the shared folders that I created on WOLFEKE ... You cannot add permissions to a remote account. ...
    (microsoft.public.windowsxp.network_web)