Re: Work computer I've run the diagnostics

"Chuck" wrote:

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

"Chuck" wrote:

On Wed, 14 Jun 2006 04:53:01 -0700, Ken W <KenW@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

"Chuck" wrote:

On Tue, 13 Jun 2006 10:27:02 -0700, Ken W <KenW@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

Chuck, two things:

1-I'm thinking the ball is in your court. Is that correct, or is there
something I should be doing?
2-I really don't know what you mean by "I'll advise you to post your
answers after mine." I'm not sure what I should do. In replying to your last
message I did delete all the prior messages.

OK, Ken,

That was the email issue the other night. Couldn't remember, when I got it
open. OK, I'm looking at 3 pictures, but not really sure what they depict. And
bitmaps of screen objects aren't really readable either - my eyes aren't quite
that good.

Let's try again.
# Net view >c:\netview.txt
# Notepad c:\netview.txt
Run those two from a command window. Copy and paste text into your next post.
And add a description, for each computer, what operating system on the computer.

And since you ask, this is me posting after your answers. Don't worry about
deleting, I'll do that periodically. Retaining context makes it easier for me
to find previous discussions.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting

I guess I still don't know what I need to do you to post after your answers.
I'm using Microsoft's reader and I just click on "reply". Should I be doing
something differently?

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

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

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.

Let's do relational analysis. Take the following code (everything INSIDE the
"#####" lines). Please DO NOT include ANY portion of the "#####" lines. (Please
verify computer names and ip addresses).

1. Open Notepad. Ensure that Format - Word Wrap is not checked. Highlight
then Copy the code (Ctrl-C), precisely as it is presented, and Paste (Ctrl-V)
into Notepad. Verify, and correct, names and addresses if necessary.
2. Save the Notepad file as "cdiag.cmd", as type "All Files", into the root
folder "C:\".
3. Run it by Start - Run - "c:\cdiag".
4. Wait patiently.
5. When Notepad opens up displaying c:\cdiag.txt, first check Format and
ensure that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A
Ctrl-C) and paste (Ctrl-V) into your next post.

Do this from all computers, please, with all computers powered up and online.

##### Start CDiag Assembled Code

@echo off
set FullTarget1=WOLFEKE 192.168.1.102
set FullTarget2=JANET 192.168.1.106
set FullTarget3=
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32 192.168.1.1
Set Version=V1.40
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt
@echo Ping Targets %PingTargets% >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Over All Analysis >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Enumerate Shares >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net share >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Adhoc Browser View >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo Full Targets Analysis %FullTargets% >>c:\cdiag.txt
for %%a in (%FullTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% net view %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo Ping Targets Analysis %PingTargets% >>c:\cdiag.txt
for %%a in (%PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo "%computername% ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

##### End CDiag Assembled Code


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


THE RESULTS FROM THE WORK COMPUTER:
CDiagnosis V1.40
Start diagnosis for WOLFEKE
Full Targets WOLFEKE 192.168.1.102 JANET 192.168.1.106 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

C$ C:\ Default share

ArgoData C:\_Data\My Documents\Horizon\Argos\ArgoData

Fax Cover Sheets
C:\_Data\My Documents\Horizon\Fax Cover Sheets

Quicken C:\_Data\My Documents\Quicken
Quotes-Ken PC
C:\_Data\My Documents\Horizon\Quotes

Share C:\Share
Statements C:\_Data\My Documents\Horizon\Financial\Financial
Statements\Statements

The command completed successfully.


Adhoc Browser View

Server Name Remark

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

\\WOLFEKE Ken Wolfe

The command completed successfully.


Full Targets Analysis WOLFEKE 192.168.1.102 JANET 192.168.1.106 127.0.0.1

Target WOLFEKE

"WOLFEKE ping WOLFEKE"



Pinging WOLFEKE.horizontechnology.local [192.168.1.102] with 32 bytes of data:



Reply from 192.168.1.102: bytes=32 time<1ms TTL=128

Reply from 192.168.1.102: bytes=32 time<1ms TTL=128

Reply from 192.168.1.102: bytes=32 time<1ms TTL=128

Reply from 192.168.1.102: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.102:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"WOLFEKE net view WOLFEKE"

Shared resources at WOLFEKE

Ken Wolfe

Share name Type Used as Comment

-------------------------------------------------------------------------------
ArgoData Disk
Fax Cover Sheets Disk
Quicken Disk
Quotes-Ken PC Disk
Share Disk
Statements Disk
The command completed successfully.


Target 192.168.1.102

"WOLFEKE ping 192.168.1.102"



Pinging 192.168.1.102 with 32 bytes of data:



Reply from 192.168.1.102: bytes=32 time<1ms TTL=128

Reply from 192.168.1.102: bytes=32 time<1ms TTL=128

Reply from 192.168.1.102: bytes=32 time<1ms TTL=128

Reply from 192.168.1.102: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.102:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"WOLFEKE net view 192.168.1.102"


Target JANET

"WOLFEKE ping JANET"



Pinging JANET [192.168.1.106] with 32 bytes of data:



Reply from 192.168.1.106: bytes=32 time=44ms TTL=128

Reply from 192.168.1.106: bytes=32 time=65ms TTL=128

Reply from 192.168.1.106: bytes=32 time=88ms TTL=128

Reply from 192.168.1.106: bytes=32 time=8ms TTL=128



Ping statistics for 192.168.1.106:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 8ms, Maximum = 88ms, Average = 51ms


"WOLFEKE net view JANET"


Target 192.168.1.106

"WOLFEKE ping 192.168.1.106"



Pinging 192.168.1.106 with 32 bytes of data:



Reply from 192.168.1.106: bytes=32 time=60ms TTL=128

Reply from 192.168.1.106: bytes=32 time=84ms TTL=128

Reply from 192.168.1.106: bytes=32 time=4ms TTL=128

Reply from 192.168.1.106: bytes=32 time=26ms TTL=128



Ping statistics for 192.168.1.106:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 4ms, Maximum = 84ms, Average = 43ms


"WOLFEKE net view 192.168.1.106"


Target 127.0.0.1

"WOLFEKE ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"WOLFEKE net view 127.0.0.1"


Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"WOLFEKE ping www.yahoo.com"



Pinging www.yahoo.akadns.net [68.142.197.85] with 32 bytes of data:



Reply from 68.142.197.85: bytes=32 time=84ms TTL=53

Reply from 68.142.197.85: bytes=32 time=83ms TTL=53

Reply from 68.142.197.85: bytes=32 time=84ms TTL=53

Reply from 68.142.197.85: bytes=32 time=83ms TTL=53



Ping statistics for 68.142.197.85:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 83ms, Maximum = 84ms, Average = 83ms


Target 66.94.230.32

"WOLFEKE ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=112ms TTL=52

Reply from 66.94.230.32: bytes=32 time=108ms TTL=52

Reply from 66.94.230.32: bytes=32 time=107ms TTL=52

Reply from 66.94.230.32: bytes=32 time=110ms TTL=52



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 107ms, Maximum = 112ms, Average = 109ms


Target 192.168.1.1

"WOLFEKE ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


End diagnosis for WOLFEKE
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
THE RESULTS FROM THE HOME COMPUTER:
CDiagnosis V1.40
Start diagnosis for JANET
Full Targets WOLFEKE 192.168.1.102 JANET 192.168.1.106 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.1.1

Over All Analysis

Enumerate Shares


Share name Resource Remark

-------------------------------------------------------------------------------
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers

C$ C:\ Default share

ADMIN$ C:\WINDOWS Remote Admin

IPC$ Remote IPC

SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

Printer Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
The command completed successfully.


Adhoc Browser View

Server Name Remark

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

\\WOLFEKE Ken Wolfe

The command completed successfully.


Full Targets Analysis WOLFEKE 192.168.1.102 JANET 192.168.1.106 127.0.0.1

Target WOLFEKE

"JANET ping WOLFEKE"



Pinging WOLFEKE [192.168.1.102] with 32 bytes of data:



Reply from 192.168.1.102: bytes=32 time=1ms TTL=128

Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

Reply from 192.168.1.102: bytes=32 time=3ms TTL=128

Reply from 192.168.1.102: bytes=32 time=2ms TTL=128



Ping statistics for 192.168.1.102:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 3ms, Average = 2ms


"JANET net view WOLFEKE"

Shared resources at WOLFEKE

Ken Wolfe

Share name Type Used as Comment

-------------------------------------------------------------------------------
ArgoData Disk
Fax Cover Sheets Disk
Quicken Disk
Quotes-Ken PC Disk
Share Disk
Statements Disk
The command completed successfully.


Target 192.168.1.102

"JANET ping 192.168.1.102"



Pinging 192.168.1.102 with 32 bytes of data:



Reply from 192.168.1.102: bytes=32 time=1ms TTL=128

Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

Reply from 192.168.1.102: bytes=32 time=2ms TTL=128

Reply from 192.168.1.102: bytes=32 time=3ms TTL=128



Ping statistics for 192.168.1.102:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 3ms, Average = 2ms


"JANET net view 192.168.1.102"

Shared resources at 192.168.1.102

Ken Wolfe

Share name Type Used as Comment

-------------------------------------------------------------------------------
ArgoData Disk
Fax Cover Sheets Disk
Quicken Disk
Quotes-Ken PC Disk
Share Disk
Statements Disk
The command completed successfully.


Target JANET

"JANET ping JANET"



Pinging JANET [192.168.1.106] with 32 bytes of data:



Reply from 192.168.1.106: bytes=32 time<1ms TTL=128

Reply from 192.168.1.106: bytes=32 time<1ms TTL=128

Reply from 192.168.1.106: bytes=32 time<1ms TTL=128

Reply from 192.168.1.106: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.106:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"JANET net view JANET"

Shared resources at JANET



Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 192.168.1.106

"JANET ping 192.168.1.106"



Pinging 192.168.1.106 with 32 bytes of data:



Reply from 192.168.1.106: bytes=32 time<1ms TTL=128

Reply from 192.168.1.106: bytes=32 time<1ms TTL=128

Reply from 192.168.1.106: bytes=32 time<1ms TTL=128

Reply from 192.168.1.106: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.106:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"JANET net view 192.168.1.106"

Shared resources at 192.168.1.106



Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"JANET ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"JANET net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print Microsoft Office Document Image Writer
SharedDocs Disk
The command completed successfully.


Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.1.1

Target www.yahoo.com

"JANET ping www.yahoo.com"



Pinging www.yahoo.akadns.net [68.142.197.68] with 32 bytes of data:



Reply from 68.142.197.68: bytes=32 time=96ms TTL=53

Reply from 68.142.197.68: bytes=32 time=87ms TTL=53

Reply from 68.142.197.68: bytes=32 time=140ms TTL=53

Reply from 68.142.197.68: bytes=32 time=149ms TTL=53



Ping statistics for 68.142.197.68:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 87ms, Maximum = 149ms, Average = 118ms


Target 66.94.230.32

"JANET ping 66.94.230.32"



Pinging 66.94.230.32 with 32 bytes of data:



Reply from 66.94.230.32: bytes=32 time=197ms TTL=52

Reply from 66.94.230.32: bytes=32 time=131ms TTL=52

Reply from 66.94.230.32: bytes=32 time=155ms TTL=52

Reply from 66.94.230.32: bytes=32 time=179ms TTL=52



Ping statistics for 66.94.230.32:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 131ms, Maximum = 197ms, Average = 165ms


Target 192.168.1.1

"JANET ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time=4ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 4ms, Average = 2ms


End diagnosis for JANET

.

Loading