Well, ran cdiag.cmd from Computer B. DOs Window "Blinked" on and off quickly.
A file named "cdiag.txtnotepad" was created on the C:\

Ran cdiag.cmd from Computer A. DOS Window "Blinked" on and off quickly.
A file named "cdiag.txtnotepad" was created on the C:\

On Mon, 14 Nov 2005 09:44:25 -0800, "jgarb" <jgarb@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Sun, 13 Nov 2005 16:26:01 -0800, "jgarb" <jgarb@discussions.microsoft.com>
>> wrote:
>>
>> >Is this a Solution?
>> >
>> >http://support.microsoft.com/?kbid=299357
>>
>> LSP / Winsock / TCP/IP corruption is one possible cause for your problem, but
>> there are others which you may be better off checking out first. Start from
>> this article:
>> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
>> http://nitecruzr.blogspot.com/2005/1...isibility.html

>Thanks Chuck, It was that information that prompted me to post the
>IPCONFIG/ALL and the Browstat information.
>
>I was at Step 5.
>"Make any changes in your network per the advice of the helpers in the
>forums. Retest as advised."
>
>I guess it is on to step 6.
>"Run, and examine, CDiag output for each computer."
>
>See next posting for this info.

OK, I'll bite. Where did you post it?

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

On Mon, 14 Nov 2005 10:00:03 -0800, "jgarb" <jgarb@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Mon, 14 Nov 2005 09:26:12 -0800, "jgarb" <jgarb@discussions.microsoft.com>
>> wrote:
>>
>> >Today on Computer A one problem is corrected.
>> >
>> >From exploring my computer on computer A I now only see the shared drives
>> >with the "new" Computer names. No more redundent shared drives with the "old"
>> >computer names.
>>
>> OK, if the problem "fixed" itself, then you likely have a browser conflict.
>> Start with this article, and diagnose the problem. Any problem that goes away
>> on its own will likely return the same way.
>> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
>> http://nitecruzr.blogspot.com/2005/1...isibility.html

>The Main Problem remains: Can not access any Computers from Computer B.

OK, if there is still a problem, post updated "browstat status" and "ipconfig
/all" from each computer. I will assemble CDiag for you, and we'll see if any
improvement.

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

"Chuck" wrote:
> OK, I'll bite. Where did you post it?
>
> --
> Cheers,


on Link
http://nitecruzr.blogspot.com/2005/0...ssistance.html

Step 6 States:
Run the Assembled Code on each computer with an NT based OS (NT / 2000 /
2003 / XP).

* Start - Run - "c:\cdiag".
* Wait patiently.
* When Notepad opens up displaying the CDiag Log (c:\cdiag.txt), first check
Format and ensure that Word Wrap is NOT checked! Then, print it, or set it
aside, for interpretation.

************************

As stated in one of the above replies:
I ran cdiag.cmd from both Computer A & B.
The DOS (Command) Window "Blinked" on and off quickly.
but Notepad did not open displaying the CDiag Log

A file named "cdiag.txtnotepad" was created on the C:\.
Do you want this file?

The CDiag was run Today. If you want Browstat and IPconfig/all again I can do
so.

The Probmel that was "fixed" was a minor displaying problem in the "my
Networks" Folder structure on Computer A. It WAS displaying previous Computer
names in the Tree. Today the Folder Stucture is correctly displaying.

Computer B's problem, not being able to access Computer A, has not changed.
I can not even "see" the network from Computer B.


"Chuck" wrote:

> On Mon, 14 Nov 2005 10:00:03 -0800, "jgarb" <jgarb@discussions.microsoft.com>
> wrote:
>
> >"Chuck" wrote:
> >
> >> On Mon, 14 Nov 2005 09:26:12 -0800, "jgarb" <jgarb@discussions.microsoft.com>
> >> wrote:
> >>
> >> >Today on Computer A one problem is corrected.
> >> >
> >> >From exploring my computer on computer A I now only see the shared drives
> >> >with the "new" Computer names. No more redundent shared drives with the "old"
> >> >computer names.
> >>
> >> OK, if the problem "fixed" itself, then you likely have a browser conflict.
> >> Start with this article, and diagnose the problem. Any problem that goes away
> >> on its own will likely return the same way.
> >> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
> >> http://nitecruzr.blogspot.com/2005/1...isibility.html
>
> >The Main Problem remains: Can not access any Computers from Computer B.
>
> OK, if there is still a problem, post updated "browstat status" and "ipconfig
> /all" from each computer. I will assemble CDiag for you, and we'll see if any
> improvement.
>
> --
> 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.
>

On Mon, 14 Nov 2005 11:23:05 -0800, "jgarb" <jgarb@discussions.microsoft.com>
wrote:

>"Chuck" wrote:
>
>> On Mon, 14 Nov 2005 10:00:03 -0800, "jgarb" <jgarb@discussions.microsoft.com>
>> wrote:
>>
>> >"Chuck" wrote:
>> >
>> >> On Mon, 14 Nov 2005 09:26:12 -0800, "jgarb" <jgarb@discussions.microsoft.com>
>> >> wrote:
>> >>
>> >> >Today on Computer A one problem is corrected.
>> >> >
>> >> >From exploring my computer on computer A I now only see the shared drives
>> >> >with the "new" Computer names. No more redundent shared drives with the "old"
>> >> >computer names.
>> >>
>> >> OK, if the problem "fixed" itself, then you likely have a browser conflict.
>> >> Start with this article, and diagnose the problem. Any problem that goes away
>> >> on its own will likely return the same way.
>> >> <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
>> >> http://nitecruzr.blogspot.com/2005/1...isibility.html
>>
>> >The Main Problem remains: Can not access any Computers from Computer B.
>>
>> OK, if there is still a problem, post updated "browstat status" and "ipconfig
>> /all" from each computer. I will assemble CDiag for you, and we'll see if any
>> improvement.

>The CDiag was run Today. If you want Browstat and IPconfig/all again I can do
>so.
>
>The Probmel that was "fixed" was a minor displaying problem in the "my
>Networks" Folder structure on Computer A. It WAS displaying previous Computer
>names in the Tree. Today the Folder Stucture is correctly displaying.
>
>Computer B's problem, not being able to access Computer A, has not changed.
>I can not even "see" the network from Computer B.

The time that you might save, from NOT refreshing browstat, is way less than the
time you waste when trying to run from one that's inaccurate.

Please update and repost them.

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

Here is the Solution -

To my knowledge this was not mentioned on any support link that I was given,
or in any help that I received here.

Maybe the solution was just to simple. Like Q - "my monitor is blank" A- "Is
it pluged in."

Computer A can not be read by Computer B, because within the Windows
Firewall Settings under the General Tab the "Don't allow exceptions" box was
CHECKED.

With File and Print sharing an exception, Computer B (or any other computer
for that matter) could not access Computer A.

On Tue, 15 Nov 2005 10:28:03 -0800, "jgarb" <jgarb@discussions.microsoft.com>
wrote:

>Here is the Solution -
>
>To my knowledge this was not mentioned on any support link that I was given,
>or in any help that I received here.
>
>Maybe the solution was just to simple. Like Q - "my monitor is blank" A- "Is
>it pluged in."
>
>Computer A can not be read by Computer B, because within the Windows
>Firewall Settings under the General Tab the "Don't allow exceptions" box was
>CHECKED.
>
>With File and Print sharing an exception, Computer B (or any other computer
>for that matter) could not access Computer A.

We thank you for the update. Allowing exceptions is indeed a critical step in
making file sharing work, on any computer protected by WF. This step is
documented, though you do need to follow each troubleshooting guide in careful
sequence, if it is to be seen.

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