home lan puzzler



Harry Putnam
07-10-2005, 02:52 AM
Setup: 3 winxp boxes
1 linux
1 winxp on laptop

All above are hooked up on home network the 3 desktop winxp boxes all
run windowsxp pro.

I'm seeing a sort of baffling problem that I'm not sure when nor how
it started.

The shares that are setup can be connected to from 2 and 3 just fine.
The baffling part is 2 and 3 when connected to 1 cannot see inside
certain folders. The folders can be access and files moved or removed
but the files cannot be seen.

I get no error messages to include here. Even setting up a mapped
drive on mach3 in explorer I see the main directory but nothing
inside.

If I type a share address into explorer like

\\mach1\mach1-share\folder\subfolder

Explorer opens them fine. But the files are invisible.

I've seen this phenomena mentioned on the windows xp newsgroups before
but don't recall seeing a resolution.

I'm coming from a unix backgroud and have grown accustomed to network
connections that are reliable and straight forward.

Somehow it seems on a windows home lan things get changed and
sometimes don't work properly for no apparent reason.

I imagine that is just that I don't know where to look.


I recently brought mach1 up to date on sp2. Haven't noticed any
particular problems but I believe the problem discussed here was
already going on before the update.

Malke
07-10-2005, 02:52 AM
Harry Putnam wrote:

> Setup: 3 winxp boxes
> 1 linux
> 1 winxp on laptop
>
> All above are hooked up on home network the 3 desktop winxp boxes all
> run windowsxp pro.
>
> I'm seeing a sort of baffling problem that I'm not sure when nor how
> it started.
>
> The shares that are setup can be connected to from 2 and 3 just fine.
> The baffling part is 2 and 3 when connected to 1 cannot see inside
> certain folders. The folders can be access and files moved or removed
> but the files cannot be seen.
>
> I get no error messages to include here. Even setting up a mapped
> drive on mach3 in explorer I see the main directory but nothing
> inside.
>
> If I type a share address into explorer like
>
> \\mach1\mach1-share\folder\subfolder
>
> Explorer opens them fine. But the files are invisible.
>
> I've seen this phenomena mentioned on the windows xp newsgroups before
> but don't recall seeing a resolution.
>
> I'm coming from a unix backgroud and have grown accustomed to network
> connections that are reliable and straight forward.
>
> Somehow it seems on a windows home lan things get changed and
> sometimes don't work properly for no apparent reason.
>
> I imagine that is just that I don't know where to look.
>
>
> I recently brought mach1 up to date on sp2. Haven't noticed any
> particular problems but I believe the problem discussed here was
> already going on before the update.

On the XP boxen, are you running XP Home or Pro? Home doesn't allow you
to share out the user's home folder (My Documents) or the Program Files
folder, although you can share out subfolders in Program Files. If this
is your case, then try using the Shared Documents folder instead.

Here are my notes on the issue of problems after a particular MS update
which may be what you are thinking of:

KB885250, an update from 2/8/2005 can cause file and printer sharing
problems under Windows networking and SAMBA. It has been reported that
both SP1 and SP2 boxen are affected. If your attempt to use SMB shares
seems compromised after last week's hotfixes, remove KB885250.

See this MS Knowledge Base article:
http://www.microsoft.com/technet/security/bulletin/ms05-011.mspx

Check in the section "Vulnerability Details, Workarounds" for several
approaches to providing the protection of the hotfix without using the
hotfix.

Those notes are a bit old by now, so the update may have been fixed. I
have a mix of XP Pro, one XP Home, and Linux boxen on my networks and
am able to share files with no problems - taking the limitations of XP
Home into account. FWIW, my XP boxen are all SP2 and completely
updated, including KB885250.

If this information didn't help, post back with more details regarding
what version of XP each box is running, if your network setup ever
worked properly, etc.

If the problem is only on the XP boxen (i.e., sharing works fine from
Linux so you know the Samba server is OK), you might try running XP's
Network Setup Wizard again on all the XP boxen. When you do this, have
all the computers on. Then run the Wizard on each box, watching for the
change in Workgroup name (it will default to MSHOME) so you can change
it. You will then need to shut down all the XP boxen and restart them.
Disable the Windows Firewall if you are using third-party software
because the Wizard will automatically enable it. If you are using the
Windows Firewall, make sure it is properly configured for file sharing
during this process.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Harry Putnam
07-10-2005, 02:52 AM
Malke <invalid@not-real.com> writes:
> On the XP boxen, are you running XP Home or Pro? Home doesn't allow you
> to share out the user's home folder (My Documents) or the Program Files
> folder, although you can share out subfolders in Program Files. If this
> is your case, then try using the Shared Documents folder instead.

Harry quotes original post:
>> All above are hooked up on home network the 3 desktop winxp boxes all
>> run windowsxp pro.

Malke wrote:
> Here are my notes on the issue of problems after a particular MS update
> which may be what you are thinking of:

Harry quotes OP:
>> I recently brought mach1 up to date on sp2. Haven't noticed any
>> particular problems but I believe the problem discussed here was
>> already going on before the update.

Malke wrote:
> If this information didn't help, post back with more details regarding
> what version of XP each box is running, if your network setup ever
> worked properly, etc.

See above regarding version info.
concerning your point about if it ever worked... yes it did. And not
long ago either. As mentioned in OP. I don't think the sp2 upgrade
is the problem since my issue was happing before the upgrade.

Malke wrote:
> If the problem is only on the XP boxen (i.e., sharing works fine from
> Linux so you know the Samba server is OK), you might try running XP's
> Network Setup Wizard again on all the XP boxen. When you do this, have
> all the computers on. Then run the Wizard on each box, watching for the
> change in Workgroup name (it will default to MSHOME) so you can change
> it. You will then need to shut down all the XP boxen and restart them.
> Disable the Windows Firewall if you are using third-party software
> because the Wizard will automatically enable it. If you are using the
> Windows Firewall, make sure it is properly configured for file sharing
> during this process.

Good idea, thanks. I'll try that out and report back.

Harry Putnam
07-10-2005, 02:52 AM
Harry Putnam <reader@newsguy.com> writes:
> Good idea, thanks. I'll try that out and report back.

I've established that the samba smbclient can access all windows xp
boxes. Further I can use samba (sambafs) to mount the drives in
question and access them from the linux box as well.

No files are invisible as in the case I described.

I have yet to run the wizard on all winxp pro boxes ... still working

Malke
07-10-2005, 02:52 AM
Harry Putnam wrote:

> Harry Putnam <reader@newsguy.com> writes:
>> Good idea, thanks. I'll try that out and report back.
>
> I've established that the samba smbclient can access all windows xp
> boxes. Further I can use samba (sambafs) to mount the drives in
> question and access them from the linux box as well.
>
> No files are invisible as in the case I described.
>
> I have yet to run the wizard on all winxp pro boxes ... still working

Harry, where are the invisible files? In which folders? Would there be
any reason for those particular folders to be hidden? Can you give more
description about this?

The only other recent thing I've seen reported about files/folders being
hidden in a network after a Windows Update had to do with Windows 98
files (after an XP update, I believe). Since you don't have any Win98
machines, this doesn't seem applicable.

Maybe if we approach the problem from what folders are "invisible", that
will help.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Harry Putnam
07-10-2005, 02:52 AM
Harry Putnam <reader@newsguy.com> writes:

> Harry Putnam <reader@newsguy.com> writes:
>> Good idea, thanks. I'll try that out and report back.
>
> I've established that the samba smbclient can access all windows xp
> boxes. Further I can use samba (sambafs) to mount the drives in
> question and access them from the linux box as well.
>
> No files are invisible as in the case I described.
>
> I have yet to run the wizard on all winxp pro boxes ... still working

I've now run the network wizard on all three winxp pro boxes.

One result was that the problematic box now sees all players in
network places display (entire network/etc/etc/)

However, from that particular machine files inside some directories
are in visible. All drives in question have the same sharing
settings.

==
User1 user2 and SYSTEM have full control
==

User1 and 2 are accounts with same name and permissions on all
machines.

I'm thinking the fact that some files are invisible is telling us
something but I can't quite grasp what.

Malke
07-10-2005, 02:52 AM
Harry Putnam wrote:

>
> I've now run the network wizard on all three winxp pro boxes.
>
> One result was that the problematic box now sees all players in
> network places display (entire network/etc/etc/)
>
> However, from that particular machine files inside some directories
> are in visible. All drives in question have the same sharing
> settings.
>
> ==
> User1 user2 and SYSTEM have full control
> ==
>
> User1 and 2 are accounts with same name and permissions on all
> machines.
>
> I'm thinking the fact that some files are invisible is telling us
> something but I can't quite grasp what.

OK, let's clarify: the problem is that (pick one):

a. From an XP box you can't see files in a Linux directory;
b. From a Linux box you can't see files in an XP directory;
c. From an XP box you can't see files in an XP directory.

And what - and where - are the files? Are all the files the same?

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Harry Putnam
07-10-2005, 02:52 AM
Malke <invalid@not-real.com> writes:

I must have a totally confusing style I guess. Sorry if it seems to
be overly obfuscated... it isn't really.

> OK, let's clarify: the problem is that (pick one):
>
> a. From an XP box you can't see files in a Linux directory;

Throw all thoughts about linux out right here. It isn't involved
here. Only maybe to test something or the like. Introducing the linux
box into the equation seems to be adding mucho confusion.

> b. From a Linux box you can't see files in an XP directory;
See above.
But .. yes I can see them from a linux box.

> c. From an XP box you can't see files in an XP directory.

Bingo.

> And what - and where - are the files? Are all the files the same?

These are totally normal files ranging from simple text to ghosted
images. There is nothing special about them.

In this scheme all boxes are running winxp pro sp/2.
mach1 is where the files in question are located at:

E:\bk1\ghost-bk1 has an assortment of files
*.txt *.html *. and two directories under it.

None of this is visible from mach2 or mach3. Both can navigate
explorer to E:\bk1\ghost-bk1 as:

\\mach1\mach1-e\bk1\ghost-bk1

But no files are visible in that directory, viewed from the remote
hosts mach2 and mach3

In fact if I navigate from Network Places on mach2 or mach3 like:

entire network/Microsoft windows network/home/

I see mach2 and mach3 but not mach1.

However the network shares I've created over the months to mach1 from
mach2 and mach3 still work with addresses like:
\\mach1\mach1-c\Program Files\
or \\mach1\mach1-d\dir\subdir\

And do display all files there.

But not so for \\mach1\mach1-e\bk1\ghost-bk1\
or \\mach1\mach1-h\bk2\ghost-bk2\

I have been able to see this stuff in the past infact most of the
images located there were placed there thru the network running ghost
on mach2 and mach3. Backed up their drives and placed the images on mach1
thru the ethernet wire as it is being compressed compiled.

I can't figure out what is changed.

Hopefully above will clarify my problem ...
I'm going to reboot everything for the umpteenth time and see if it
helps.

Malke
07-10-2005, 02:52 AM
Harry Putnam wrote:

> Malke <invalid@not-real.com> writes:
>
> I must have a totally confusing style I guess. Sorry if it seems to
> be overly obfuscated... it isn't really.

It is just that because you've been working with this for a while and
you have the network/machines in front of you so that things are very
clear in your mind. I just wasn't "seeing" it. Sorry.

>
> Throw all thoughts about linux out right here. It isn't involved
> here. Only maybe to test something or the like. Introducing the linux
> box into the equation seems to be adding mucho confusion.

Yes, because I thought you were asking about interoperability problems.

>> c. From an XP box you can't see files in an XP directory.
>
> Bingo.
>
>> And what - and where - are the files? Are all the files the same?
>
> These are totally normal files ranging from simple text to ghosted
> images. There is nothing special about them.
>
> In this scheme all boxes are running winxp pro sp/2.
> mach1 is where the files in question are located at:
>
> E:\bk1\ghost-bk1 has an assortment of files
> *.txt *.html *. and two directories under it.
>
> None of this is visible from mach2 or mach3. Both can navigate
> explorer to E:\bk1\ghost-bk1 as:
>
> \\mach1\mach1-e\bk1\ghost-bk1
>
> But no files are visible in that directory, viewed from the remote
> hosts mach2 and mach3
>
> In fact if I navigate from Network Places on mach2 or mach3 like:
>
> entire network/Microsoft windows network/home/
>
> I see mach2 and mach3 but not mach1.
>
> However the network shares I've created over the months to mach1 from
> mach2 and mach3 still work with addresses like:
> \\mach1\mach1-c\Program Files\
> or \\mach1\mach1-d\dir\subdir\
>
> And do display all files there.
>
> But not so for \\mach1\mach1-e\bk1\ghost-bk1\
> or \\mach1\mach1-h\bk2\ghost-bk2\
>
> I have been able to see this stuff in the past infact most of the
> images located there were placed there thru the network running ghost
> on mach2 and mach3. Backed up their drives and placed the images on
> mach1 thru the ethernet wire as it is being compressed compiled.
>
> I can't figure out what is changed.
>
> Hopefully above will clarify my problem ...
> I'm going to reboot everything for the umpteenth time and see if it
> helps.

I doubt that rebooting will work in this case. I honestly don't know the
answer, but have a couple of suggestions. I Googled for "browse with
UNC names works" and got this link which looks promising:

http://www.chicagotech.net/nettroublshooting.htm

A workaround which I got from MVP Steve Winograd (networking guru
extraordinaire) when I was having problems with my own network was to
forget about using Network Places. Instead, I used Search to search for
computers on the network and made shortcuts to the shares. I put mine
in a folder in my desktop and they worked perfectly, even when Network
Places would crash and lock up the whole machine. However, I wasn't
having the same problem as you with "invisible" files. I was having the
problem of not all computers showing on the network and running the
Network Setup Wizard the way I detailed earlier solved it for me. Like
you, I had no idea why something that was working perfectly stopped
doing that. I still don't know. ;-)

So I'm sorry I don't have a definitive answer for you.

Best of luck,

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

AJR
07-10-2005, 02:52 AM
Are NTFS permissions involved - or just share (FAT - simple file sharing)
permissions? Can you access "invisible" files by UNC? May not be the
problem but as you are probably aware NTFS permission propagation to folder
files can be denied.

Malke
07-10-2005, 02:52 AM
AJR wrote:

> Are NTFS permissions involved - or just share (FAT - simple file
> sharing)
> permissions? Can you access "invisible" files by UNC? May not be the
> problem but as you are probably aware NTFS permission propagation to
> folder files can be denied.

That's a really good point - like maybe the right permissions aren't on
the child folders. But wouldn't he get an "access denied" error instead
of just not being able to see the files? I'm asking - I don't know the
answer.

Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

Harry Putnam
07-10-2005, 02:52 AM
"AJR" <ajrjdr@comcast.net> writes:

> Are NTFS permissions involved - or just share (FAT - simple file sharing)
> permissions? Can you access "invisible" files by UNC? May not be the
> problem but as you are probably aware NTFS permission propagation to folder
> files can be denied.
>
>

Malke <invalid@not-real.com> writes:

> That's a really good point - like maybe the right permissions aren't on
> the child folders. But wouldn't he get an "access denied" error instead
> of just not being able to see the files? I'm asking - I don't know the
> answer.

Malke's point was my take as well. Yes the folders are accessable by
Unc. But again, files at:

\\Remote\share\subdir\HERE are invisible.

A reboot all around has made some changes as detailed below but still
not just working like it should.

Just now, thoroughly checking all three machines I see differences
amongst them.

mach1 (host with the subject )files

A) Mach1
1) Mach1 does not appear in its own Network places at
`Entire Netowrk\Microsoft...\Home <= clicking home gets a `unavailable [...]'
message.

Going by UNC \\chub\chub-e\bk1\ghost-bk1\etc etc

I can get to all of them nothing is hidden or invisible.
2) Now trying Entire Network\microsoft...\home works as it should

A further note is that working thru Network Places on mach1 is very
slow .. more so than the other two.

B) Mach2
1) Using mach2 `network places'
Entire Network\Microsoft...\Home\HERE
Mach1 is not visible but Mach2 anb 3 are.

2) Using UNC I can get to all files under \\chub\chub-e\bk1

Close explorer and open a new explorer and again at Netowrk Places
Mach1 is not visible at Entire Network\Microsoft...\Home

3) Mach3

Mach3 Network Places shows
Entire Network\Microsoft...\Home\HERE
Mach1 is not visible but Mach2 and mach3 are.

Using UNC addressing I can get to everything


Further NOTE:
Using the `Search for computer' on the search menu. from Mach3
mach1 is readily found and all under it appear.



This all seems pretty flaky. There must still be something wrong at
mach1.

Someone mentioned properties or permission propagation.

What I see is that all subdir under any share .. not just the ones
I'm having trouble with, when viewed at right click \Sharing:

Universally on all machines the `do not share' button is selected.

This is true whether or not I'm able to navigate to them from anywhere
on the network.

Chuck
07-10-2005, 02:52 AM
On Thu, 19 May 2005 16:56:24 GMT, Harry Putnam <reader@newsguy.com> wrote:

>"AJR" <ajrjdr@comcast.net> writes:
>
>> Are NTFS permissions involved - or just share (FAT - simple file sharing)
>> permissions? Can you access "invisible" files by UNC? May not be the
>> problem but as you are probably aware NTFS permission propagation to folder
>> files can be denied.
>>
>>
>
>Malke <invalid@not-real.com> writes:
>
>> That's a really good point - like maybe the right permissions aren't on
>> the child folders. But wouldn't he get an "access denied" error instead
>> of just not being able to see the files? I'm asking - I don't know the
>> answer.
>
>Malke's point was my take as well. Yes the folders are accessable by
>Unc. But again, files at:
>
>\\Remote\share\subdir\HERE are invisible.
>
>A reboot all around has made some changes as detailed below but still
>not just working like it should.
>
>Just now, thoroughly checking all three machines I see differences
>amongst them.
>
>mach1 (host with the subject )files
>
>A) Mach1
> 1) Mach1 does not appear in its own Network places at
> `Entire Netowrk\Microsoft...\Home <= clicking home gets a `unavailable [...]'
> message.
>
> Going by UNC \\chub\chub-e\bk1\ghost-bk1\etc etc
>
> I can get to all of them nothing is hidden or invisible.
> 2) Now trying Entire Network\microsoft...\home works as it should
>
> A further note is that working thru Network Places on mach1 is very
> slow .. more so than the other two.
>
>B) Mach2
> 1) Using mach2 `network places'
> Entire Network\Microsoft...\Home\HERE
> Mach1 is not visible but Mach2 anb 3 are.
>
> 2) Using UNC I can get to all files under \\chub\chub-e\bk1
>
> Close explorer and open a new explorer and again at Netowrk Places
> Mach1 is not visible at Entire Network\Microsoft...\Home
>
>3) Mach3
>
> Mach3 Network Places shows
> Entire Network\Microsoft...\Home\HERE
> Mach1 is not visible but Mach2 and mach3 are.
>
> Using UNC addressing I can get to everything
>
>
>Further NOTE:
> Using the `Search for computer' on the search menu. from Mach3
> mach1 is readily found and all under it appear.
>
>
>
>This all seems pretty flaky. There must still be something wrong at
>mach1.
>
>Someone mentioned properties or permission propagation.
>
> What I see is that all subdir under any share .. not just the ones
> I'm having trouble with, when viewed at right click \Sharing:
>
>Universally on all machines the `do not share' button is selected.
>
>This is true whether or not I'm able to navigate to them from anywhere
>on the network.

Harry,

Do us a favour please and provide some diagnostics to go on - "ipconfig /all"
and "browstat status" from each computer would be good.
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

Maybe you will find some help here too:
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Malke
07-10-2005, 02:52 AM
Harry Putnam wrote:

> "AJR" <ajrjdr@comcast.net> writes:
>
>> Are NTFS permissions involved - or just share (FAT - simple file
>> sharing)
>> permissions? Can you access "invisible" files by UNC? May not be the
>> problem but as you are probably aware NTFS permission propagation to
>> folder files can be denied.
>>
>>
>
> Malke <invalid@not-real.com> writes:
>
>> That's a really good point - like maybe the right permissions aren't
>> on the child folders. But wouldn't he get an "access denied" error
>> instead of just not being able to see the files? I'm asking - I don't
>> know the answer.
>
> Malke's point was my take as well. Yes the folders are accessable by
> Unc. But again, files at:
>
> \\Remote\share\subdir\HERE are invisible.
>
> A reboot all around has made some changes as detailed below but still
> not just working like it should.
>
> Just now, thoroughly checking all three machines I see differences
> amongst them.
>
> mach1 (host with the subject )files
>
> A) Mach1
> 1) Mach1 does not appear in its own Network places at
> `Entire Netowrk\Microsoft...\Home <= clicking home gets a
> `unavailable [...]' message.
>
> Going by UNC \\chub\chub-e\bk1\ghost-bk1\etc etc
>
> I can get to all of them nothing is hidden or invisible.
> 2) Now trying Entire Network\microsoft...\home works as it should
>
> A further note is that working thru Network Places on mach1 is very
> slow .. more so than the other two.
>
> B) Mach2
> 1) Using mach2 `network places'
> Entire Network\Microsoft...\Home\HERE
> Mach1 is not visible but Mach2 anb 3 are.
>
> 2) Using UNC I can get to all files under \\chub\chub-e\bk1
>
> Close explorer and open a new explorer and again at Netowrk Places
> Mach1 is not visible at Entire Network\Microsoft...\Home
>
> 3) Mach3
>
> Mach3 Network Places shows
> Entire Network\Microsoft...\Home\HERE
> Mach1 is not visible but Mach2 and mach3 are.
>
> Using UNC addressing I can get to everything
>
>
> Further NOTE:
> Using the `Search for computer' on the search menu. from Mach3
> mach1 is readily found and all under it appear.
>
>
>
> This all seems pretty flaky. There must still be something wrong at
> mach1.
>
> Someone mentioned properties or permission propagation.
>
> What I see is that all subdir under any share .. not just the ones
> I'm having trouble with, when viewed at right click \Sharing:
>
> Universally on all machines the `do not share' button is selected.
>
> This is true whether or not I'm able to navigate to them from anywhere
> on the network.

The above bit about the "do not share" being selected is very strange.
I'd try (and we're just talking about the Windows machines; leave the
Linux boxen alone):

1. *Un*share everything. Reboot.

2. On all the XP Pro boxen, go to the View tab in Folder Options and
uncheck "use Simple Sharing". This thread has gotten long, so I'm
assuming that you've already and long ago made identical user accounts
and passwords on all machines.

3. With all machines on, run the Network Setup Wizard on all machines
again. Watch for the "MSHOME gotcha" and be sure to select Share Files
& Folders. Reboot. Check the Windows Firewall settings and if you are
using it, make sure it is set to allow your lan. If you are not using
WF, make sure it is OFF and your third-party firewall is set to allow
your lan.

Now see whether All Is Well.

If it isn't, take a deep cleansing breath and whatever Adult
Beverage/Drug you prefer and make shortcuts to the shares with the
Search thing I suggested earlier.

Let me know what happens.

Malke
--
MS-MVP Windows User/Shell
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

Harry Putnam
07-10-2005, 02:52 AM
Chuck <none@example.net> writes:
[...]

> Do us a favour please and provide some diagnostics to go on - "ipconfig /all"

None of my machines know anything about the `browstatus status'

command or any variation I could come up with:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>browstatus status
'browstatus' is not recognized as an internal or external command,
operable program or batch file.

C:\>==========================

I can't think of a good reason to publish my hardware and IP addresses
here so only included the top half Which is the same for all machines
except the name:

=============================
C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : ansil

Three differnet names of course

Primary Dns Suffix . . . . . . . : local.net0
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local.net0

All three appear the same on second half as well with exception nof
hardware and IP addresses.

Malke <notreally@invalid.com> writes:


> The above bit about the "do not share" being selected is very strange.
> I'd try (and we're just talking about the Windows machines; leave the
> Linux boxen alone):

Wait.. are you saying that if you pick a subfolder under a share and
click on Sharing/security It shows something besides:

[x]Do not share this folder

Being checked?

All my machines show the `Do not etc' on all subfolders under shares.


> 1. *Un*share everything. Reboot.

OK, will do, but it will be a few hours after doing some driving around
chores I need to get done.

Chuck
07-10-2005, 02:52 AM
On Thu, 19 May 2005 18:18:49 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>[...]
>
>> Do us a favour please and provide some diagnostics to go on - "ipconfig /all"
>
>None of my machines know anything about the `browstatus status'
>
>command or any variation I could come up with:
>
>Microsoft Windows XP [Version 5.1.2600]
>(C) Copyright 1985-2001 Microsoft Corp.
>
>C:\>browstatus status
>'browstatus' is not recognized as an internal or external command,
>operable program or batch file.

Harry,

Try "browstat status" please. But download browstat first - follow instructions
here.
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:52 AM
Chuck <none@example.net> writes:

> Try "browstat status" please. But download browstat first - follow instructions
> here.
> <http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

(Note: READER is a linux box on this network running samba)
(Note: All winxp pro machines show the same error)

Mach1 (chub) Where subject files are located:

browstat status:
Status for domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}

=================================================

Mach2 (harvey)

Browstat status:

Status for domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}

=====================

Mach3 (Ansil)

Status for domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}

=========================================================================

Harry Putnam
07-10-2005, 02:52 AM
Chuck <none@example.net> writes:

> Harry,
>
> Try "browstat status" please. But download browstat first - follow
> instructions here.
> <http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

I've done this and posted the results. Please note that I am not
getting the error your link discusses.


--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Thu, 19 May 2005 20:34:16 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>
>> Try "browstat status" please. But download browstat first - follow instructions
>> here.
>> <http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>
>
> (Note: READER is a linux box on this network running samba)
> (Note: All winxp pro machines show the same error)
>
>Mach1 (chub) Where subject files are located:
>
>browstat status:
>Status for domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
> Browsing is active on domain.
> Master browser name is: READER
>Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
> \\\\READER . Version:04.09 Flags: 9a03 NT SERVER
> 1 backup servers retrieved from master READER
> \\READER
> There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
> There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
>
>=================================================
>
>Mach2 (harvey)
>
>Browstat status:
>
>Status for domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
> Browsing is active on domain.
> Master browser name is: READER
>Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
> \\\\READER . Version:04.09 Flags: 9a03 NT SERVER
> 1 backup servers retrieved from master READER
> \\READER
> There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
> There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
>
>=====================
>
>Mach3 (Ansil)
>
>Status for domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
> Browsing is active on domain.
> Master browser name is: READER
>Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
> \\\\READER . Version:04.09 Flags: 9a03 NT SERVER
> 1 backup servers retrieved from master READER
> \\READER
> There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
> There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
>
>=========================================================================

OK, so we're back to Samba involved.

So far, I see 3 symmetrical browstats, only NBT transports. No obvious
problems.

I still have no idea of the scope of the problem, and without the ipconfigs I
doubt that I will. What we were going to do with the ipconfigs is run CDiag,
which might show us a pattern / scope of symptoms anyway. You're welcome to run
CDiag yourself, and describe any discrepancies found, without revealing details.
I'll coach you as much as I can.
<http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck,
I'm not sure if this is noteworthy but I'm noticing that running

`net view' on all winxp pro machines fails to display the subject
machine. (chub)

The interesting part is that running:

net view chub
(on any of the winxp pro)

Displays all of chubs shares.

net view:
Server Name Remark

-------------------------------------------------------------------------------
\\ANSIL
\\HARVEY
\\READER Samba 3.0.10
The command completed successfully.
======================================

net view chub:
Shared resources at chub



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.

--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Thu, 19 May 2005 21:57:46 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>
>> Harry,
>>
>> Try "browstat status" please. But download browstat first - follow
>> instructions here.
>> <http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>
>
>I've done this and posted the results. Please note that I am not
>getting the error your link discusses.

The link name was a little limiting. I expanded the content of the article, but
I'm stuck with the blog title / link til I figure out how to rename without
losing the current link, which is now published all over.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Chuck
07-10-2005, 02:53 AM
On Thu, 19 May 2005 22:29:14 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck,
>I'm not sure if this is noteworthy but I'm noticing that running
>
> `net view' on all winxp pro machines fails to display the subject
> machine. (chub)
>
>The interesting part is that running:
>
>net view chub
>(on any of the winxp pro)
>
>Displays all of chubs shares.
>
>net view:
>Server Name Remark
>
>-------------------------------------------------------------------------------
>\\ANSIL
>\\HARVEY
>\\READER Samba 3.0.10
>The command completed successfully.
>======================================
>
>net view chub:
>Shared resources at chub
>
>
>
>Share name Type Used as Comment
>
>-------------------------------------------------------------------------------
>chub-a Disk
>chub-bk1 Disk
>chub-bk2 Disk
>chub-c Disk
>chub-d Disk
>chub-dvdb Disk sony dui 330
>chub-e Disk sata1_0
>chub-g Disk sata2_0
>chub-h Disk
>chub-printer Print HP Mult-ifunction 7130
>chub_02 Disk
>E Disk
>F Disk
>harvey_22 Disk
>IDE1_bad Disk
>Printer Print hp officejet 7100 series fax
>Printer2 Print SnagIt 7
>SharedDocs Disk
>The command completed successfully.

Harry,

I think it is. The "net view" command, I believe, comes from the browser. The
"net view xxxx", I believe, interrogates computer xxxx directly.

You're running both commands from an XP computer, but the first is data coming
thru Reader.

Did you check restrictanonymous on Chub?
<http://nitecruzr.blogspot.com/2005/05/restrictanonymous-and-enumeration-of.html>
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>

Did you check the firewall on Chub?
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#Firewall>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:


[...]

> OK, so we're back to Samba involved.

Only by showing up as a server.... I can shut that down and all
symptems remain the same.

> So far, I see 3 symmetrical browstats, only NBT transports. No obvious
> problems.
>
> I still have no idea of the scope of the problem, and without the ipconfigs I
> doubt that I will. What we were going to do with the ipconfigs is run CDiag,
> which might show us a pattern / scope of symptoms anyway. You're welcome to run
> CDiag yourself, and describe any discrepancies found, without revealing details.
> I'll coach you as much as I can.
> <http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html>

After browsing these links and you pages a while I see no evidence of
a download link for cdiag. Is it just well hidden or really not
there? The word download appears nowhere on the cdiag page.

--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Fri, 20 May 2005 00:23:51 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>
>
>[...]
>
>> OK, so we're back to Samba involved.
>
>Only by showing up as a server.... I can shut that down and all
>symptems remain the same.
>
>> So far, I see 3 symmetrical browstats, only NBT transports. No obvious
>> problems.
>>
>> I still have no idea of the scope of the problem, and without the ipconfigs I
>> doubt that I will. What we were going to do with the ipconfigs is run CDiag,
>> which might show us a pattern / scope of symptoms anyway. You're welcome to run
>> CDiag yourself, and describe any discrepancies found, without revealing details.
>> I'll coach you as much as I can.
>> <http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html>
>
>After browsing these links and you pages a while I see no evidence of
>a download link for cdiag. Is it just well hidden or really not
>there? The word download appears nowhere on the cdiag page.

Harry,

CDiag is not a downloadable product. It's straight text, copied from the web
page:
<http://nitecruzr.blogspot.com/2005/05/cdiag-comprehensive-diagnosis-source.html>

See for instructions (and why CDiag is straight text):
<http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html>

Take the following code (everything inside the "#####"). Edit computer name and
ip address in pairs without the "()" to FullTargetn lines, and edit ip address
of router to PingTargets line. For example,
set FullTarget1=chub (ip address of chub)
set FullTarget2=harvey (ip address of harvey)
set FullTarget3=ansil (ip address of ansil)
set PingTargets=www.yahoo.com 66.94.230.32 (ip address of router)

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.

#####

@echo off
set FullTarget1=
set FullTarget2=
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
Set Version=V1.31
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %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 %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

#####

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:

[...]

> I think it is. The "net view" command, I believe, comes from the browser. The
> "net view xxxx", I believe, interrogates computer xxxx directly.
>
> You're running both commands from an XP computer, but the first is data coming
> thru Reader.
>
> Did you check restrictanonymous on Chub?
> <http://nitecruzr.blogspot.com/2005/05/restrictanonymous-and-enumeration-of.html>
> <http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>

Looking at the exact address given there. I see it set to:
RestrictAnonymous 0x00000000 (0)

Bur right below it I see:
restrictAnonymoussam 0x00000001 (1)

RestrictAnonymous also appears in a 5-6 other locations in registry.

> Did you check the firewall on Chub?
> <http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#Firewall>

I've been running with it off, but on your suggestion I checked to
make sure and it was on. This has got to be a result of updating to
sp/2 ... ?

Hopefully that will turn out to be the whole problem. I can't shut
chub down right now after turning it off, as a rather hefty backup is
underway.

Back to RestrictAnonymous...

The fact that typing the UNC address
\\chub\chub-e\bk1\ghost-bk1\etc etc

Works would seem to indicate that the RestrictAnonymous thing is what
is wrong.


--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Fri, 20 May 2005 01:09:57 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>
>[...]
>
>> I think it is. The "net view" command, I believe, comes from the browser. The
>> "net view xxxx", I believe, interrogates computer xxxx directly.
>>
>> You're running both commands from an XP computer, but the first is data coming
>> thru Reader.
>>
>> Did you check restrictanonymous on Chub?
>> <http://nitecruzr.blogspot.com/2005/05/restrictanonymous-and-enumeration-of.html>
>> <http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
>
>Looking at the exact address given there. I see it set to:
> RestrictAnonymous 0x00000000 (0)
>
>Bur right below it I see:
> restrictAnonymoussam 0x00000001 (1)
>
>RestrictAnonymous also appears in a 5-6 other locations in registry.
>
>> Did you check the firewall on Chub?
>> <http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#Firewall>
>
>I've been running with it off, but on your suggestion I checked to
>make sure and it was on. This has got to be a result of updating to
>sp/2 ... ?
>
>Hopefully that will turn out to be the whole problem. I can't shut
>chub down right now after turning it off, as a rather hefty backup is
>underway.
>
>Back to RestrictAnonymous...
>
>The fact that typing the UNC address
> \\chub\chub-e\bk1\ghost-bk1\etc etc
>
>Works would seem to indicate that the RestrictAnonymous thing is what
>is wrong.

Harry,

The restrictanonymous in the location I gave you is all that matters. The
restrictanonymoussam in that same location is not important for this exercise.
Not sure what other locations you found.

The browser uses the ra setting. You're running XP Pro with Simple File Sharing
on or off?

"\\chub\..." uses local authentication, as you are running it while logged in.
My money is on the firewall, you have to enable the File and Printer Sharing
exception.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:


[...]


> The restrictanonymous in the location I gave you is all that matters. The
> restrictanonymoussam in that same location is not important for this exercise.
> Not sure what other locations you found.
>
> The browser uses the ra setting. You're running XP Pro with Simple File Sharing
> on or off?
>
> "\\chub\..." uses local authentication, as you are running it while logged in.
> My money is on the firewall, you have to enable the File and Printer Sharing
> exception.

Lets hope so...

You've provided really indepth help on this I really appreciate it.
I'm afraid to do much more on chub while the backup is running so will
get back on the group tomorrow morning.

I'll provide the output of the cdiag runs.

You've been very helpfull ... thank you.

Harry Putnam
07-10-2005, 02:53 AM
Harry Putnam <reader@newsguy.com> writes:

> You've provided really indepth help on this I really appreciate it.
> I'm afraid to do much more on chub while the backup is running so will
> get back on the group tomorrow morning.
>
> I'll provide the output of the cdiag runs.
>
> You've been very helpfull ... thank you.

Chuck,
I managed to get two reports with cdiag.cmd which are inline below.

However two things of possible note first:
1)
Your instructions say to run diag.cmd from the `run' command on
start menu. That fails to find the command on all my machines.

However, double clicking C:\diag.cmd gets it done.

2)
On the one machine with the problems (chub), cdiag.cmd only produces
a long string of pings, no reports. I suspected it was finding the
wrong ping command since I have Cygwin (unix tools) installed.

I tried to rewrite you script and added the absolute filename of
ping command where ever the script said `ping' by itself.

That didn't work any better.

Below find 2 diag.cmd reports from (ansil and harvey)

NOTE:
The script was saved 3 times from one source to C:\ on each
machine (not the rewritten one) so it is identical on each
machine yet it fails to work right on chub.

The final part of this message is my rewritten cdiag.cmd. Maybe you
can see how to make it work on chub. Or what I've mucked up by
rewriting.

Cdiag reports:
===== Harvey ===
CDiagnosis V1.31
Start diagnosis for HARVEY
Full Targets 127.0.0.1

Target 127.0.0.1

"HARVEY 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

"HARVEY net view 127.0.0.1"

Shared resources at 127.0.0.1


Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.

Ping Targets www.yahoo.com 192.168.0.20

Target www.yahoo.com

"HARVEY ping www.yahoo.com"

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

Reply from 216.109.118.71: bytes=32 time=27ms TTL=51

Reply from 216.109.118.71: bytes=32 time=28ms TTL=51

Reply from 216.109.118.71: bytes=32 time=27ms TTL=50

Reply from 216.109.118.71: bytes=32 time=27ms TTL=50

Ping statistics for 216.109.118.71:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

Target 192.168.0.20

"HARVEY ping 192.168.0.20"

Pinging 192.168.0.20 with 32 bytes of data:

Reply from 192.168.0.20: bytes=32 time=1ms TTL=127

Reply from 192.168.0.20: bytes=32 time<1ms TTL=127

Reply from 192.168.0.20: bytes=32 time<1ms TTL=127

Reply from 192.168.0.20: bytes=32 time<1ms TTL=127

Ping statistics for 192.168.0.20:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

End diagnosis for HARVEY

=== Ansil ===
CDiagnosis V1.31
Start diagnosis for ANSIL
Full Targets 127.0.0.1

Target 127.0.0.1
"ANSIL 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

"ANSIL net view 127.0.0.1"

Shared resources at 127.0.0.1

Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.

Ping Targets www.yahoo.com 192.168.0.20

Target www.yahoo.com
"ANSIL ping www.yahoo.com"

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

Reply from 216.109.118.69: bytes=32 time=26ms TTL=50

Reply from 216.109.118.69: bytes=32 time=26ms TTL=51

Reply from 216.109.118.69: bytes=32 time=26ms TTL=51

Reply from 216.109.118.69: bytes=32 time=27ms TTL=50


Ping statistics for 216.109.118.69:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 27ms, Average = 26ms


Target 192.168.0.20
"ANSIL ping 192.168.0.20"

Pinging 192.168.0.20 with 32 bytes of data:

Reply from 192.168.0.20: bytes=32 time<1ms TTL=127

Reply from 192.168.0.20: bytes=32 time<1ms TTL=127

Reply from 192.168.0.20: bytes=32 time<1ms TTL=127

Reply from 192.168.0.20: bytes=32 time<1ms TTL=127

Ping statistics for 192.168.0.20:

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 ANSIL

===============

Rewritten script (added absolute address for ping.exe)
@echo off
set FullTarget1=chub (192.168.0.2)
set FullTarget2=harvey (192.168.0.22)
set FullTarget3=ansil (192.168.0.21)
set FullTarget4=
set FullTargets=%FullTargets% 127.0.0.1
set PngTargets=www.yahoo.com 192.168.0.20
Set Version=V1.31
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %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% C:\WINDOWS\system32\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 %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% C:\WINDOWS\system32\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

--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Harry Putnam
07-10-2005, 02:53 AM
I've sent ipconfig /all reports to your private address

--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Fri, 20 May 2005 14:13:51 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Harry Putnam <reader@newsguy.com> writes:
>
>> You've provided really indepth help on this I really appreciate it.
>> I'm afraid to do much more on chub while the backup is running so will
>> get back on the group tomorrow morning.
>>
>> I'll provide the output of the cdiag runs.
>>
>> You've been very helpfull ... thank you.
>
>Chuck,
>I managed to get two reports with cdiag.cmd which are inline below.
>
>However two things of possible note first:
>1)
> Your instructions say to run diag.cmd from the `run' command on
> start menu. That fails to find the command on all my machines.
>
> However, double clicking C:\diag.cmd gets it done.
>
>2)
> On the one machine with the problems (chub), cdiag.cmd only produces
> a long string of pings, no reports. I suspected it was finding the
> wrong ping command since I have Cygwin (unix tools) installed.
>
> I tried to rewrite you script and added the absolute filename of
> ping command where ever the script said `ping' by itself.
>
> That didn't work any better.
>
>Below find 2 diag.cmd reports from (ansil and harvey)
>
>NOTE:
> The script was saved 3 times from one source to C:\ on each
> machine (not the rewritten one) so it is identical on each
> machine yet it fails to work right on chub.
>
>The final part of this message is my rewritten cdiag.cmd. Maybe you
>can see how to make it work on chub. Or what I've mucked up by
>rewriting.
>
>Cdiag reports:
>===== Harvey ===
>CDiagnosis V1.31
>Start diagnosis for HARVEY
>Full Targets 127.0.0.1
>
>Target 127.0.0.1
>
>"HARVEY 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
>
> "HARVEY net view 127.0.0.1"
>
>Shared resources at 127.0.0.1
>
>
>Share name Type Used as Comment
>
>-------------------------------------------------------------------------------
>chub2-g Disk IDE1_1
>Harry Disk
>harvey-c Disk
>harvey-d Disk
>Harvey-dvdburn Disk
>harvey-e Disk
>harvey-g Disk
>harvey-printer Print Epson R800 photo
>Printer Print SnagIt 7
>SharedDocs Disk
>The command completed successfully.
>
> Ping Targets www.yahoo.com 192.168.0.20
>
>Target www.yahoo.com
>
>"HARVEY ping www.yahoo.com"
>
>Pinging www.yahoo.akadns.net [216.109.118.71] with 32 bytes of data:
>
>Reply from 216.109.118.71: bytes=32 time=27ms TTL=51
>
>Reply from 216.109.118.71: bytes=32 time=28ms TTL=51
>
>Reply from 216.109.118.71: bytes=32 time=27ms TTL=50
>
>Reply from 216.109.118.71: bytes=32 time=27ms TTL=50
>
>Ping statistics for 216.109.118.71:
>
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
> Minimum = 27ms, Maximum = 28ms, Average = 27ms
>
> Target 192.168.0.20
>
>"HARVEY ping 192.168.0.20"
>
>Pinging 192.168.0.20 with 32 bytes of data:
>
>Reply from 192.168.0.20: bytes=32 time=1ms TTL=127
>
>Reply from 192.168.0.20: bytes=32 time<1ms TTL=127
>
>Reply from 192.168.0.20: bytes=32 time<1ms TTL=127
>
>Reply from 192.168.0.20: bytes=32 time<1ms TTL=127
>
>Ping statistics for 192.168.0.20:
>
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 1ms, Average = 0ms
>
> End diagnosis for HARVEY
>
>=== Ansil ===
>CDiagnosis V1.31
>Start diagnosis for ANSIL
>Full Targets 127.0.0.1
>
>Target 127.0.0.1
> "ANSIL 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
>
> "ANSIL net view 127.0.0.1"
>
>Shared resources at 127.0.0.1
>
>Share name Type Used as Comment
>
>-------------------------------------------------------------------------------
>ansil-c Disk
>ansil-d Disk
>ansil-dvd Disk
>ansil-g Disk
>SharedDocs Disk
>The command completed successfully.
>
>Ping Targets www.yahoo.com 192.168.0.20
>
>Target www.yahoo.com
>"ANSIL ping www.yahoo.com"
>
>Pinging www.yahoo.akadns.net [216.109.118.69] with 32 bytes of data:
>
>Reply from 216.109.118.69: bytes=32 time=26ms TTL=50
>
>Reply from 216.109.118.69: bytes=32 time=26ms TTL=51
>
>Reply from 216.109.118.69: bytes=32 time=26ms TTL=51
>
>Reply from 216.109.118.69: bytes=32 time=27ms TTL=50
>
>
>Ping statistics for 216.109.118.69:
>
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 26ms, Maximum = 27ms, Average = 26ms
>
>
>Target 192.168.0.20
> "ANSIL ping 192.168.0.20"
>
>Pinging 192.168.0.20 with 32 bytes of data:
>
>Reply from 192.168.0.20: bytes=32 time<1ms TTL=127
>
>Reply from 192.168.0.20: bytes=32 time<1ms TTL=127
>
>Reply from 192.168.0.20: bytes=32 time<1ms TTL=127
>
>Reply from 192.168.0.20: bytes=32 time<1ms TTL=127
>
>Ping statistics for 192.168.0.20:
>
> 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 ANSIL
>
>===============
>
>Rewritten script (added absolute address for ping.exe)
>@echo off
>set FullTarget1=chub (192.168.0.2)
>set FullTarget2=harvey (192.168.0.22)
>set FullTarget3=ansil (192.168.0.21)
>set FullTarget4=
>set FullTargets=%FullTargets% 127.0.0.1
>set PngTargets=www.yahoo.com 192.168.0.20
>Set Version=V1.31
>@echo CDiagnosis %Version% >c:\cdiag.txt
>@echo Start diagnosis for %computername% >>c:\cdiag.txt
>@echo Full Targets %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% C:\WINDOWS\system32\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 %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% C:\WINDOWS\system32\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

Harry,

The assembled code that you're running on Ansil and Harvey appears to have:
set FullTarget1=
set FullTarget2=
set FullTarget3=

IOW, you aren't adding in the computer names and ip addresses.

The assembled code that you're running on Chub has:
set FullTarget1=chub (192.168.0.2)
set FullTarget2=harvey (192.168.0.22)
set FullTarget3=ansil (192.168.0.21)

Correctly written, this would be (copy this to all 3 computers):
set FullTarget1=chub 192.168.0.2
set FullTarget2=harvey 192.168.0.22
set FullTarget3=ansil 192.168.0.21

The assembled code that you're running on Chub has (in two places):
@echo "%computername% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt

Correctly written (copy this to Chub, in 2 places in the code):
@echo "%computername% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
C:\WINDOWS\system32\ping %%a >>c:\cdiag.txt

What's "192.168.0.20"?

So please try correcting and rerunning assembled CDiag code on all 3 computers.

You might find more help in my newest article:
<http://nitecruzr.blogspot.com/2005/05/using-cdiag-without-assistance.html>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:
>
> Harry,
>
> The assembled code that you're running on Ansil and Harvey appears to have:
> set FullTarget1=
> set FullTarget2=
> set FullTarget3=
>
> IOW, you aren't adding in the computer names and ip addresses.

Wrong. Not sure why you would think such a thing but it is wrong.
I'm running the exact same code on all machines. Only after original
code failed on chub, I tried editing it as posted.

The source file was copied to chub,ansil, harvey from the same file.
No way it is different on any of the machines.

You now have full reports on ansil and harvey. You mentioned that
those full reports would enable you to know the `scope' of the
problem. Not sure what you mean by that but the scope is a home
network with 3 winxp pro machines and a linux machine on it.

cdiag.cmd seems to basically run a few pings and the net view command.

As I've already posted, chub is able to ping itself and all other
machines with no problems.

I'll include those here since I haven't been able to successfully run
cdiag.cmd on chub for some unknown reason.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
NOTE: running these commands from computer chub on C:\WINDOWS\system3
C:\>cd C:\Windows\system32
C:\WINDOWS\system32>ping chub

Pinging chub [192.168.0.2] with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32> ping ansil
Pinging ansil [192.168.0.21] with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>ping harvey

Pinging harvey [192.168.0.22] with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>net view
Server Name Remark

-------------------------------------------------------------------------------
\\ANSIL
\\HARVEY
\\READER Samba 3.0.10
The command completed successfully.

--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Fri, 20 May 2005 22:33:54 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>>
>> Harry,
>>
>> The assembled code that you're running on Ansil and Harvey appears to have:
>> set FullTarget1=
>> set FullTarget2=
>> set FullTarget3=
>>
>> IOW, you aren't adding in the computer names and ip addresses.
>
>Wrong. Not sure why you would think such a thing but it is wrong.
>I'm running the exact same code on all machines. Only after original
>code failed on chub, I tried editing it as posted.

Harry,

Look at the first 3 lines of the CDiag output from Harvey.
===== Harvey ===
CDiagnosis V1.31
Start diagnosis for HARVEY
Full Targets 127.0.0.1

Here's the first 3 lines of CDiag output from my computer (I just ran it as a
test):
===== Chuck1 ===
CDiagnosis V1.31
Start diagnosis for chuck1
Full Targets chuck1 192.168.0.50 chuck2 192.168.0.51 127.0.0.1

And here's the top lines of my assembled CDiag code:
@echo off
set FullTarget1=chuck1 192.168.0.50
set FullTarget2=chuck2 192.168.0.51
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.0.1
Set Version=V1.31
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %FullTargets% >>c:\cdiag.txt

Harry, CDiag outputs a header line, which lists the input in the run. That's so
I can take any CDiag run, and know what input was used. In my case,
Full Targets chuck1 192.168.0.50 chuck2 192.168.0.51 127.0.0.1

And the input is:
set FullTarget1=chuck1 192.168.0.50
set FullTarget2=chuck2 192.168.0.51

Your output was:
Full Targets 127.0.0.1

Which means your input was:
set FullTarget1=
set FullTarget2=

I'll try to help you Harry, but you have to trust me, and not to pull my leg. I
know how CDiag works - I wrote it.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:

> I'll try to help you Harry, but you have to trust me, and not to pull my leg. I
> know how CDiag works - I wrote it.

Yikes ... sorry about that.. but it was not leg pulling. Somewhere I
got parens around the IPs. Not sure where that crept in. I think
it was one of your posts that says:

> Take the following code (everything inside the "#####"). Edit computer name and
> ip address in pairs without the "()" to FullTargetn lines, and edit ip address
> of router to PingTargets line. For example,
> set FullTarget1=chub (ip address of chub)
> set FullTarget2=harvey (ip address of harvey)
> set FullTarget3=ansil (ip address of ansil)
> set PingTargets=www.yahoo.com 66.94.230.32 (ip address of router)

I think those parens are the culprit.
Further: I explained why I changed the cdiag.cmd on chub. Only after
it failing as written. We'll see in a minute if the corrected cdiag
will do the trick.

Again sorry to be such a pain in the butt but it was not intentional.

You asked about 192.168.0.20
That is a gateway DSL/router/firewall All the winxp pro machines are
pointed at it as gateway in the tcp/ip setup.

Please note that running the cdiag.cmd as presented on chub fails. It
pops up a dos window at C:\windows\system32\cmd.exe

But notepad never appears with the printout. I've let it run as long
as ten minutes but do not get output.

I've included the intire cdiag.cmd I'm using on all computers at the
very end


Ansil output:

CDiagnosis V1.31
Start diagnosis for ANSIL
Full Targets chub 192.168.0.2 harvey 192.168.0.22 ansil 192.168.0.21 127.0.0.1

Target chub

"ANSIL ping chub"


Pinging chub [192.168.0.2] with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view chub"

Shared resources at chub



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk Y:
chub-bk2 Disk Z:
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.2

"ANSIL ping 192.168.0.2"


Pinging 192.168.0.2 with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view 192.168.0.2"

Shared resources at 192.168.0.2



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target harvey

"ANSIL ping harvey"


Pinging harvey [192.168.0.22] with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view harvey"

Shared resources at harvey



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.22

"ANSIL ping 192.168.0.22"


Pinging 192.168.0.22 with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view 192.168.0.22"

Shared resources at 192.168.0.22



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target ansil

"ANSIL ping ansil"


Pinging ansil.local.net0 [192.168.0.21] with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view ansil"

Shared resources at ansil



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.21

"ANSIL ping 192.168.0.21"


Pinging 192.168.0.21 with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view 192.168.0.21"

Shared resources at 192.168.0.21



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"ANSIL 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

"ANSIL net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"ANSIL ping www.yahoo.com"


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

Reply from 216.109.118.66: bytes=32 time=27ms TTL=51
Reply from 216.109.118.66: bytes=32 time=27ms TTL=50
Reply from 216.109.118.66: bytes=32 time=28ms TTL=50
Reply from 216.109.118.66: bytes=32 time=27ms TTL=50

Ping statistics for 216.109.118.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

Target 66.94.230.32

"ANSIL ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=63ms TTL=49
Reply from 66.94.230.32: bytes=32 time=64ms TTL=49
Reply from 66.94.230.32: bytes=32 time=63ms TTL=49
Reply from 66.94.230.32: bytes=32 time=63ms TTL=49

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 64ms, Average = 63ms

End diagnosis for ANSIL

======================================
======================================

Harvey output:

CDiagnosis V1.31
Start diagnosis for HARVEY
Full Targets chub 192.168.0.2 harvey 192.168.0.22 ansil 192.168.0.21 127.0.0.1

Target chub

"HARVEY ping chub"


Pinging chub [192.168.0.2] with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view chub"

Shared resources at chub



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.2

"HARVEY ping 192.168.0.2"


Pinging 192.168.0.2 with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view 192.168.0.2"

Shared resources at 192.168.0.2



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target harvey

"HARVEY ping harvey"


Pinging harvey.local.net0 [192.168.0.22] with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view harvey"

Shared resources at harvey



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.22

"HARVEY ping 192.168.0.22"


Pinging 192.168.0.22 with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view 192.168.0.22"

Shared resources at 192.168.0.22



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target ansil

"HARVEY ping ansil"


Pinging ansil [192.168.0.21] with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view ansil"

Shared resources at ansil



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.21

"HARVEY ping 192.168.0.21"


Pinging 192.168.0.21 with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view 192.168.0.21"

Shared resources at 192.168.0.21



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"HARVEY 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

"HARVEY net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Ping Targets www.yahoo.com 66.94.230.32

Target www.yahoo.com

"HARVEY ping www.yahoo.com"


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

Reply from 68.142.226.55: bytes=32 time=27ms TTL=50
Reply from 68.142.226.55: bytes=32 time=27ms TTL=50
Reply from 68.142.226.55: bytes=32 time=27ms TTL=51
Reply from 68.142.226.55: bytes=32 time=28ms TTL=51

Ping statistics for 68.142.226.55:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

Target 66.94.230.32

"HARVEY ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=64ms TTL=49
Reply from 66.94.230.32: bytes=32 time=62ms TTL=49
Reply from 66.94.230.32: bytes=32 time=63ms TTL=49
Reply from 66.94.230.32: bytes=32 time=63ms TTL=49

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 64ms, Average = 63ms

End diagnosis for HARVEY

===========================================
===========================================

As reported `cdiag.cmd' never completes on chub.


--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Harry Putnam
07-10-2005, 02:53 AM
Harry Putnam <reader@newsguy.com> writes:

> I've included the intire cdiag.cmd I'm using on all computers at the
> very end

I didn't include it but here it is:

@echo off
set FullTarget1=chub 192.168.0.2
set FullTarget2=harvey 192.168.0.22
set FullTarget3=ansil 192.168.0.21
set FullTarget4=
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32
Set Version=V1.31
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %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 %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


--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Sat, 21 May 2005 02:13:20 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Harry Putnam <reader@newsguy.com> writes:
>
>> I've included the intire cdiag.cmd I'm using on all computers at the
>> very end
>
>I didn't include it but here it is:
>
>@echo off
>set FullTarget1=chub 192.168.0.2
>set FullTarget2=harvey 192.168.0.22
>set FullTarget3=ansil 192.168.0.21
>set FullTarget4=
>set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
>set FullTargets=%FullTargets% 127.0.0.1
>set PingTargets=www.yahoo.com 66.94.230.32
>Set Version=V1.31
>@echo CDiagnosis %Version% >c:\cdiag.txt
>@echo Start diagnosis for %computername% >>c:\cdiag.txt
>@echo Full Targets %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 %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

Harry,

Did you change CDiag on Chub as I mentioned before:

The assembled code that you're running on Chub has (in two places):
@echo "%computername% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt

Correctly written (copy this to Chub, in 2 places in the code):
@echo "%computername% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
C:\WINDOWS\system32\ping %%a >>c:\cdiag.txt

And it looks like you left 192.168.0.20 out of PingTargets above?

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:

> Correctly written (copy this to Chub, in 2 places in the code):
> @echo "%computername% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
> @echo. >>c:\cdiag.txt
> C:\WINDOWS\system32\ping %%a >>c:\cdiag.txt
>
> And it looks like you left 192.168.0.20 out of PingTargets above?

Chuck you have been very patient and I thank you for that. Not sure
why I'm having such a hard time with this. It appears to be a simple
enough request. Only excuse I can come up with is that my background
is nearly exclusively unix and I have a very thick skull...

NOTE: I made another small change in cdiag.cmd on chub to get the
result to pop up in notepad. Needed the full path similar to the ping
command. (Full text at very end)

> And it looks like you left 192.168.0.20 out of PingTargets above?

I thought we were interested only in the winxp pro boxes... sorry.
192.168.0.20 is an hardware gateway/firewall. (NETGEAR FVS-318)

I've included fw 192.168.0.20 in this output.

Due to having made so many blunders thus far here I will post the
results from the three runs of cdiag.cmd and the full text of what I
ran.
So an outline of this message looks like:

cdiag out from ansil
cdiag out from harvey
Full text of cdiag run on ansil and harvey
cdiag out from chub
Full text of cdiag run on chub


Ansil and Harvey diagnostic output
Ansil:
CDiagnosis V1.31
Start diagnosis for ANSIL
Full Targets chub 192.168.0.2 harvey 192.168.0.22 ansil 192.168.0.21 127.0.0.1

Target chub

"ANSIL ping chub"


Pinging chub [192.168.0.2] with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view chub"

Shared resources at chub



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk Y:
chub-bk2 Disk Z:
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.2

"ANSIL ping 192.168.0.2"


Pinging 192.168.0.2 with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view 192.168.0.2"

Shared resources at 192.168.0.2



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target harvey

"ANSIL ping harvey"


Pinging harvey [192.168.0.22] with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view harvey"

Shared resources at harvey



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.22

"ANSIL ping 192.168.0.22"


Pinging 192.168.0.22 with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view 192.168.0.22"

Shared resources at 192.168.0.22



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target ansil

"ANSIL ping ansil"


Pinging ansil.local.net0 [192.168.0.21] with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view ansil"

Shared resources at ansil



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.21

"ANSIL ping 192.168.0.21"


Pinging 192.168.0.21 with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"ANSIL net view 192.168.0.21"

Shared resources at 192.168.0.21



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"ANSIL 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

"ANSIL net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Ping Targets [url]www.yahoo.com[/url] 66.94.230.32

Target [url]www.yahoo.com[/url]

"ANSIL ping www.yahoo.com"


Pinging [url]www.yahoo.akadns.net[/url] [216.109.118.66] with 32 bytes of data:

Reply from 216.109.118.66: bytes=32 time=27ms TTL=51
Reply from 216.109.118.66: bytes=32 time=27ms TTL=50
Reply from 216.109.118.66: bytes=32 time=28ms TTL=50
Reply from 216.109.118.66: bytes=32 time=27ms TTL=50

Ping statistics for 216.109.118.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

Target 66.94.230.32

"ANSIL ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=63ms TTL=49
Reply from 66.94.230.32: bytes=32 time=64ms TTL=49
Reply from 66.94.230.32: bytes=32 time=63ms TTL=49
Reply from 66.94.230.32: bytes=32 time=63ms TTL=49

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 64ms, Average = 63ms

End diagnosis for ANSIL

=======================================================

Harvey:
CDiagnosis V1.31
Start diagnosis for HARVEY
Full Targets chub 192.168.0.2 harvey 192.168.0.22 ansil 192.168.0.21 127.0.0.1

Target chub

"HARVEY ping chub"


Pinging chub [192.168.0.2] with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view chub"

Shared resources at chub



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.2

"HARVEY ping 192.168.0.2"


Pinging 192.168.0.2 with 32 bytes of data:

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

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view 192.168.0.2"

Shared resources at 192.168.0.2



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target harvey

"HARVEY ping harvey"


Pinging harvey.local.net0 [192.168.0.22] with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view harvey"

Shared resources at harvey



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.22

"HARVEY ping 192.168.0.22"


Pinging 192.168.0.22 with 32 bytes of data:

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

Ping statistics for 192.168.0.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view 192.168.0.22"

Shared resources at 192.168.0.22



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target ansil

"HARVEY ping ansil"


Pinging ansil [192.168.0.21] with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view ansil"

Shared resources at ansil



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.21

"HARVEY ping 192.168.0.21"


Pinging 192.168.0.21 with 32 bytes of data:

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

Ping statistics for 192.168.0.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"HARVEY net view 192.168.0.21"

Shared resources at 192.168.0.21



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"HARVEY 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

"HARVEY net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Ping Targets [url]www.yahoo.com[/url] 66.94.230.32

Target [url]www.yahoo.com[/url]

"HARVEY ping www.yahoo.com"


Pinging [url]www.yahoo.akadns.net[/url] [68.142.226.55] with 32 bytes of data:

Reply from 68.142.226.55: bytes=32 time=27ms TTL=50
Reply from 68.142.226.55: bytes=32 time=27ms TTL=50
Reply from 68.142.226.55: bytes=32 time=27ms TTL=51
Reply from 68.142.226.55: bytes=32 time=28ms TTL=51

Ping statistics for 68.142.226.55:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

Target 66.94.230.32

"HARVEY ping 66.94.230.32"


Pinging 66.94.230.32 with 32 bytes of data:

Reply from 66.94.230.32: bytes=32 time=64ms TTL=49
Reply from 66.94.230.32: bytes=32 time=62ms TTL=49
Reply from 66.94.230.32: bytes=32 time=63ms TTL=49
Reply from 66.94.230.32: bytes=32 time=63ms TTL=49

Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 64ms, Average = 63ms

End diagnosis for HARVEY


Full text of cdiag.txt run on Ansil and Harvey:

@echo off
set FullTarget1=chub 192.168.0.2
set FullTarget2=harvey 192.168.0.22
set FullTarget3=ansil 192.168.0.21
set FullTarget4=fw 192.168.0.20
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32
Set Version=V1.31
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %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 %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

======================================================

Diagnostic output from chub:

Chub:
CDiagnosis V1.31
Start diagnosis for CHUB
Full Targets chub 192.168.0.2 harvey 192.168.0.22 ansil 192.168.0.21 fw 192.168.0.20 127.0.0.1

Target chub

"CHUB C:\WINDOWS\system32\ping chub"

Pinging chub [192.168.0.2] with 32 bytes of data:Reply from 192.168.0.2: bytes=32 time<1ms TTL=64Reply from 192.168.0.2: bytes=32 time<1ms TTL=64Reply from 192.168.0.2: bytes=32 time<1ms TTL=64Reply from 192.168.0.2: bytes=32 time<1ms TTL=64Ping statistics for 192.168.0.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"CHUB net view chub"

Shared resources at chub



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.2

"CHUB C:\WINDOWS\system32\ping 192.168.0.2"

Pinging 192.168.0.2 with 32 bytes of data:Reply from 192.168.0.2: bytes=32 time<1ms TTL=64Reply from 192.168.0.2: bytes=32 time<1ms TTL=64Reply from 192.168.0.2: bytes=32 time<1ms TTL=64Reply from 192.168.0.2: bytes=32 time<1ms TTL=64Ping statistics for 192.168.0.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"CHUB net view 192.168.0.2"

Shared resources at 192.168.0.2



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target harvey

"CHUB C:\WINDOWS\system32\ping harvey"

Pinging harvey [192.168.0.22] with 32 bytes of data:Reply from 192.168.0.22: bytes=32 time<1ms TTL=128Reply from 192.168.0.22: bytes=32 time<1ms TTL=128Reply from 192.168.0.22: bytes=32 time<1ms TTL=128Reply from 192.168.0.22: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.22: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"CHUB net view harvey"

Shared resources at harvey



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk (UNC)
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target 192.168.0.22

"CHUB C:\WINDOWS\system32\ping 192.168.0.22"

Pinging 192.168.0.22 with 32 bytes of data:Reply from 192.168.0.22: bytes=32 time<1ms TTL=128Reply from 192.168.0.22: bytes=32 time<1ms TTL=128Reply from 192.168.0.22: bytes=32 time<1ms TTL=128Reply from 192.168.0.22: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.22: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"CHUB net view 192.168.0.22"

Shared resources at 192.168.0.22



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub2-g Disk IDE1_1
Harry Disk
harvey-c Disk
harvey-d Disk
Harvey-dvdburn Disk
harvey-e Disk
harvey-g Disk
harvey-printer Print Epson R800 photo
Printer Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Target ansil

"CHUB C:\WINDOWS\system32\ping ansil"

Pinging ansil [192.168.0.21] with 32 bytes of data:Reply from 192.168.0.21: bytes=32 time<1ms TTL=128Reply from 192.168.0.21: bytes=32 time<1ms TTL=128Reply from 192.168.0.21: bytes=32 time<1ms TTL=128Reply from 192.168.0.21: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"CHUB net view ansil"

Shared resources at ansil



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk (UNC)
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.0.21

"CHUB C:\WINDOWS\system32\ping 192.168.0.21"

Pinging 192.168.0.21 with 32 bytes of data:Reply from 192.168.0.21: bytes=32 time<1ms TTL=128Reply from 192.168.0.21: bytes=32 time<1ms TTL=128Reply from 192.168.0.21: bytes=32 time<1ms TTL=128Reply from 192.168.0.21: bytes=32 time<1ms TTL=128Ping statistics for 192.168.0.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"CHUB net view 192.168.0.21"

Shared resources at 192.168.0.21



Share name Type Used as Comment

-------------------------------------------------------------------------------
ansil-c Disk
ansil-d Disk
ansil-dvd Disk
ansil-g Disk
SharedDocs Disk
The command completed successfully.


Target fw

"CHUB C:\WINDOWS\system32\ping fw"

Pinging fw.local.net0 [192.168.0.20] with 32 bytes of data:Reply from 192.168.0.20: bytes=32 time<1ms TTL=63Reply from 192.168.0.20: bytes=32 time<1ms TTL=63Reply from 192.168.0.20: bytes=32 time<1ms TTL=63Reply from 192.168.0.20: bytes=32 time<1ms TTL=63Ping statistics for 192.168.0.20: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"CHUB net view fw"


Target 192.168.0.20

"CHUB C:\WINDOWS\system32\ping 192.168.0.20"

Pinging 192.168.0.20 with 32 bytes of data:Reply from 192.168.0.20: bytes=32 time<1ms TTL=63Reply from 192.168.0.20: bytes=32 time<1ms TTL=63Reply from 192.168.0.20: bytes=32 time<1ms TTL=63Reply from 192.168.0.20: bytes=32 time<1ms TTL=63Ping statistics for 192.168.0.20: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
"CHUB net view 192.168.0.20"


Target 127.0.0.1

"CHUB C:\WINDOWS\system32\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=64Reply from 127.0.0.1: bytes=32 time<1ms TTL=64Reply from 127.0.0.1: bytes=32 time<1ms TTL=64Reply from 127.0.0.1: bytes=32 time<1ms TTL=64Ping 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
"CHUB net view 127.0.0.1"

Shared resources at 127.0.0.1



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.


Ping Targets [url]www.yahoo.com[/url] 66.94.230.32

Target [url]www.yahoo.com[/url]

"CHUB C:\WINDOWS\system32\ping www.yahoo.com"

Pinging [url]www.yahoo.akadns.net[/url] [216.109.117.106] with 32 bytes of data:Reply from 216.109.117.106: bytes=32 time=26ms TTL=51Reply from 216.109.117.106: bytes=32 time=26ms TTL=51Reply from 216.109.117.106: bytes=32 time=27ms TTL=51Reply from 216.109.117.106: bytes=32 time=27ms TTL=51Ping statistics for 216.109.117.106: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 26ms, Maximum = 27ms, Average = 26ms
Target 66.94.230.32

"CHUB C:\WINDOWS\system32\ping 66.94.230.32"

Pinging 66.94.230.32 with 32 bytes of data:Reply from 66.94.230.32: bytes=32 time=74ms TTL=45Reply from 66.94.230.32: bytes=32 time=74ms TTL=45Reply from 66.94.230.32: bytes=32 time=74ms TTL=45Reply from 66.94.230.32: bytes=32 time=74ms TTL=45Ping statistics for 66.94.230.32: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 74ms, Maximum = 74ms, Average = 74ms
End diagnosis for CHUB

========================================

Full text of cdiag.cmd from chub:

@echo off
set FullTarget1=chub 192.168.0.2
set FullTarget2=harvey 192.168.0.22
set FullTarget3=ansil 192.168.0.21
set FullTarget4=fw 192.168.0.20
set FullTargets=%FullTarget1% %FullTarget2% %FullTarget3% %FullTarget4%
set FullTargets=%FullTargets% 127.0.0.1
set PingTargets=www.yahoo.com 66.94.230.32
Set Version=V1.31
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% >>c:\cdiag.txt
@echo Full Targets %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% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
C:\WINDOWS\system32\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 %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% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
C:\WINDOWS\system32\ping %%a >>c:\cdiag.txt
)
@echo. >>c:\cdiag.txt
@echo End diagnosis for %computername% >>c:\cdiag.txt
C:\WINDOWS\system32\notepad c:\cdiag.txt
:EOF

--
For those interested in pediatrics
[url]http://www.caringbridge.com/in/jkaela[/url]
Baby JKaela was born with Pentology of Cantrell syndrome

Harry Putnam
07-10-2005, 02:53 AM
Harry Putnam <reader@newsguy.com> writes:

> Chuck <none@example.net> writes:
>
>> Correctly written (copy this to Chub, in 2 places in the code):
>> @echo "%computername% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
>> @echo. >>c:\cdiag.txt
>> C:\WINDOWS\system32\ping %%a >>c:\cdiag.txt
>>
>> And it looks like you left 192.168.0.20 out of PingTargets above?
>
> Chuck you have been very patient and I thank you for that. Not sure
> why I'm having such a hard time with this. It appears to be a simple
> enough request. Only excuse I can come up with is that my background
> is nearly exclusively unix and I have a very thick skull...
>

Chuck, can this disappearing act thing be the result of update
KB885250? That one has been reported here as causing a disappearing
act similar to what I see.

http://groups-beta.google.com/group/microsoft.public.windowsxp.network_web/browse_thread/thread/7acb091e65fcb8ca/35dc88f659e58bf1?q=KB885250+group:*windowsxp*&rnum=12&hl=en#35dc88f659e58bf1

It is installed. I don't think it was very recently installed though

Chuck
07-10-2005, 02:53 AM
On Sat, 21 May 2005 22:33:48 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Harry Putnam <reader@newsguy.com> writes:
>
>> Chuck <none@example.net> writes:
>>
>>> Correctly written (copy this to Chub, in 2 places in the code):
>>> @echo "%computername% C:\WINDOWS\system32\ping %%a" >>c:\cdiag.txt
>>> @echo. >>c:\cdiag.txt
>>> C:\WINDOWS\system32\ping %%a >>c:\cdiag.txt
>>>
>>> And it looks like you left 192.168.0.20 out of PingTargets above?
>>
>> Chuck you have been very patient and I thank you for that. Not sure
>> why I'm having such a hard time with this. It appears to be a simple
>> enough request. Only excuse I can come up with is that my background
>> is nearly exclusively unix and I have a very thick skull...
>>
>
>Chuck, can this disappearing act thing be the result of update
>KB885250? That one has been reported here as causing a disappearing
>act similar to what I see.
>
>http://groups-beta.google.com/group/microsoft.public.windowsxp.network_web/browse_thread/thread/7acb091e65fcb8ca/35dc88f659e58bf1?q=KB885250+group:*windowsxp*&rnum=12&hl=en#35dc88f659e58bf1
>
>It is installed. I don't think it was very recently installed though

Harry,

Well, we have ruled out any overall networking / file sharing problem. All
tests were negative on any problem, so KB885250 is a good candidate in my book.

It's not too hard to try. Just un install, reboot, and check it out. How
consistent are the symptoms - how long does it take til you typically notice a
problem?

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:

>>Chuck, can this disappearing act thing be the result of update
>>KB885250? That one has been reported here as causing a disappearing
>>act similar to what I see.
>>
>>http://groups-beta.google.com/group/microsoft.public.windowsxp.network_web/browse_thread/thread/7acb091e65fcb8ca/35dc88f659e58bf1?q=KB885250+group:*windowsxp*&rnum=12&hl=en#35dc88f659e58bf1
>>
>>It is installed. I don't think it was very recently installed though
>
> Harry,
>
> Well, we have ruled out any overall networking / file sharing problem. All
> tests were negative on any problem, so KB885250 is a good candidate in my book.

> It's not too hard to try. Just un install, reboot, and check it out. How
> consistent are the symptoms

Doing that now...

> ..... . ................- how long does it take til you typically notice a
> problem?

I work thru a KVM alot, so accessing machines by filesharing isn't as
often as without KVM.

Further, the problem doens't appear until you've drilled down 3 layers
in file hierarchy. So it could have been a month or more I guess.

Not seeing chub in netowrk places wouldn't necessarily raise an
eyebrow because various machines at times are missing for short
periods following reboots.

--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Sat, 21 May 2005 22:59:01 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>
>>>Chuck, can this disappearing act thing be the result of update
>>>KB885250? That one has been reported here as causing a disappearing
>>>act similar to what I see.
>>>
>>>http://groups-beta.google.com/group/microsoft.public.windowsxp.network_web/browse_thread/thread/7acb091e65fcb8ca/35dc88f659e58bf1?q=KB885250+group:*windowsxp*&rnum=12&hl=en#35dc88f659e58bf1
>>>
>>>It is installed. I don't think it was very recently installed though
>>
>> Harry,
>>
>> Well, we have ruled out any overall networking / file sharing problem. All
>> tests were negative on any problem, so KB885250 is a good candidate in my book.
>
>> It's not too hard to try. Just un install, reboot, and check it out. How
>> consistent are the symptoms
>
>Doing that now...
>
>> ..... . ................- how long does it take til you typically notice a
>> problem?
>
>I work thru a KVM alot, so accessing machines by filesharing isn't as
>often as without KVM.
>
>Further, the problem doens't appear until you've drilled down 3 layers
>in file hierarchy. So it could have been a month or more I guess.
>
>Not seeing chub in netowrk places wouldn't necessarily raise an
>eyebrow because various machines at times are missing for short
>periods following reboots.

If that isn't KB885250, then it's a ringer for the symptoms.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:

> If that isn't KB885250, then it's a ringer for the symptoms.

Only nagging worry is that the MS fix for KB885250 talks about this
happening with win 95/98 on the lan only. And goes on to say if my
symptoms don't match that.... not to uninstall.

..... 5 min

Well chub is backup after uninstalling that update. A quick test from
ansil shows the problem is still there. I'm rebooting all around once
to make sure.
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Sat, 21 May 2005 23:15:49 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>
>> If that isn't KB885250, then it's a ringer for the symptoms.
>
>Only nagging worry is that the MS fix for KB885250 talks about this
>happening with win 95/98 on the lan only. And goes on to say if my
>symptoms don't match that.... not to uninstall.
>
>.... 5 min
>
>Well chub is backup after uninstalling that update. A quick test from
>ansil shows the problem is still there. I'm rebooting all around once
>to make sure.

Harry,

DOHH.

If the problem is still there, then we just have to look harder. How can we
define the scope of the problem - that may be the next step. When do you see
the problem, how long do you see the problem, is it the same files / folders
each time, how do you get around the problem, maybe you could come up with more
questions and answers, I dunno, but let's try and define the symptoms so we can
look for the causes.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:

> If the problem is still there, then we just have to look harder. How can we
> define the scope of the problem - that may be the next step.

Not sure what you mean by scope here. As I see it the problem is that
chub is inaccessable via the Nework Places mechanism unless the
absolute address is typed in.

> When do you see the problem,
> how long do you see the problem,

It appears to be continuous.
One thing is very consistent. chub does not appear in Network Places
from any machine, even itself.

> is it the same files / folders

Some drives on chub seem to be more accessable than others. I see no
problem at \\chub\chub-c\Program Files\Adobe or even deeper and in
any location on C:\ I've tried.

Oddities include: \\chub\chub-g\images\ stops right there although
there are several more layers. However any other directories on
\\chub\chub-g seem to work at any depth.

\\chub\chub-h works to any depth
\\chub\chub-d ditto

And it seem to change overtime. At one time today
\\chub\chub-e\bk1\ghost-bk1
Wouldn't display any deeper but now it does..

> [...] how do you get around the problem

Typing \\chub into an explorer address locator box will make chub
appear in `entire network' listing., From there some directories are
simply not available and do not display any files. So far it doesn't
seem to be consistently the same ones. But others work ok.

I see this phenomena consistently: \\chub\chub-e\bk1\ghost-bk
Fails to display any deeper always. So I guess at least one directory
heirarch is consistently invisible below layer 3

However I've gone to chub and created actual shares at a lower depth
in that same heirarchy. That share appears on other machines display
of Network Places and will reveal the files under it.

All of chubs shares appear under Network Places but chub itself does
not. And of course other machines do appear there.

I rechecked the Registry setting for RestrictAnonymous to ensure it
was at 0, even set it to 1 and rebooted. I saw no difference to reset
to 0 and again rebooted.

I'm probably getting stumped too easily but can't really think of much
else to even try. Only maybe Malke's suggestiong of disabling sharing
and removing all shares ... then rebuild from there.

Something I haven't mentioned yet is that chub is an athlon64, the
others are intel. Chub originally was installed with winxp-pro pre
sp/2. The others original install was winxp-pro with sp/2 included.
I updated chub to sp/2 fairly recently... not sure exactly when. I
had hoped to uninstall sp/2 and see this problem go away but did that
in the last hour or so and still see the problem.

One other fact. Chub did not always have this problem. I'm thinking
its no older than 1 1/2 mnths if that. Only really noticed by me this
week.
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Sun, 22 May 2005 00:52:08 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck <none@example.net> writes:
>
>> If the problem is still there, then we just have to look harder. How can we
>> define the scope of the problem - that may be the next step.
>
>Not sure what you mean by scope here. As I see it the problem is that
>chub is inaccessable via the Nework Places mechanism unless the
>absolute address is typed in.
>
>> When do you see the problem,
>> how long do you see the problem,
>
>It appears to be continuous.
>One thing is very consistent. chub does not appear in Network Places
>from any machine, even itself.
>
>> is it the same files / folders
>
>Some drives on chub seem to be more accessable than others. I see no
>problem at \\chub\chub-c\Program Files\Adobe or even deeper and in
>any location on C:\ I've tried.
>
>Oddities include: \\chub\chub-g\images\ stops right there although
>there are several more layers. However any other directories on
>\\chub\chub-g seem to work at any depth.
>
>\\chub\chub-h works to any depth
>\\chub\chub-d ditto
>
>And it seem to change overtime. At one time today
> \\chub\chub-e\bk1\ghost-bk1
>Wouldn't display any deeper but now it does..
>
>> [...] how do you get around the problem
>
>Typing \\chub into an explorer address locator box will make chub
>appear in `entire network' listing., From there some directories are
>simply not available and do not display any files. So far it doesn't
>seem to be consistently the same ones. But others work ok.
>
>I see this phenomena consistently: \\chub\chub-e\bk1\ghost-bk
>Fails to display any deeper always. So I guess at least one directory
>heirarch is consistently invisible below layer 3
>
>However I've gone to chub and created actual shares at a lower depth
>in that same heirarchy. That share appears on other machines display
>of Network Places and will reveal the files under it.
>
>All of chubs shares appear under Network Places but chub itself does
>not. And of course other machines do appear there.
>
>I rechecked the Registry setting for RestrictAnonymous to ensure it
>was at 0, even set it to 1 and rebooted. I saw no difference to reset
>to 0 and again rebooted.
>
>I'm probably getting stumped too easily but can't really think of much
>else to even try. Only maybe Malke's suggestiong of disabling sharing
>and removing all shares ... then rebuild from there.
>
>Something I haven't mentioned yet is that chub is an athlon64, the
>others are intel. Chub originally was installed with winxp-pro pre
>sp/2. The others original install was winxp-pro with sp/2 included.
>I updated chub to sp/2 fairly recently... not sure exactly when. I
>had hoped to uninstall sp/2 and see this problem go away but did that
>in the last hour or so and still see the problem.
>
>One other fact. Chub did not always have this problem. I'm thinking
>its no older than 1 1/2 mnths if that. Only really noticed by me this
>week.

Harry,

Welcome to Chuck's School of Diagnostic Analysis. Just a fancy term for
identifying what the problem might be related to, and what it might not be
related to.

Scope is simply a way of seeing what factors might help narrow the search for
the cause of your problem.

Please don't go deleting any shares unless you absolutely run out of patience.
We may solve this yet.

So what do we know?
- The problem is on Chub only, Ansil and Harvey no problem.
- The problem is continuous.
- The problem is suspected to have started recently (how old is Chub?).
- The problem is not related to KB885250 (DOHH).

What do I not know?
- What other patches have you applied recently? From Windows Update, look at
Installation History, and see what other patches have been applied in the past 2
months.
- How old is Chub? Ansil / Harvey?
- Compare patch history on Chub with Ansil and Harvey?
- What's different between the problematic folders and the working ones?
Creation date? Created under different accounts? Maybe accessed differently?
- Is Ansil / Chub / Harvey SFS or AFS?

How does Chub differ from Ansil and Harvey?
- Chub has Unix components.
- Chub was originally installed as Windows XP pre-SP2, the other 2 as Windows
XP SP2.

Interesting details now:
Typing \\chub into an explorer address locator box will make chub appear in
`entire network' listing., From there some directories are simply not available
and do not display any files. So far it doesn't seem to be consistently the
same ones. But others work ok.

Windows NT with NTFS (not FAT) AFS (not SFS) has a lot of ability to configure
(block access of) ability to access and even see contents of individual folders,
and you can specify that to the file level. Look at a working folder, and a
non-working one. From Properties - Security - Advanced, look at the items in
Advanced Security Settings. There's a shiteload of possible ways to fsck up
folder access - differences in Inherited and Effective Permissions create lots
of possibilities, and could relate to the directory hierarchy bit.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Just some responses that may help while I try a few things.

Chuck <none@example.net> writes:

> Please don't go deleting any shares unless you absolutely run out of patience.
> We may solve this yet.

One thing I'm trying right now is to disable all winxp machines
computer browser service. I thought maybe having one master browser
on the lan would have some kind of good effect. Rember there is also
a linux machine running samba that is seen as a master browser.

>
> So what do we know?
> - The problem is on Chub only, Ansil and Harvey no problem.
> - The problem is continuous.
> - The problem is suspected to have started recently (how old is Chub?).
> - The problem is not related to KB885250 (DOHH).

Chub was built early last year and is an Athlon64 +3400 with 2.2ghz
and 1.5GB ram

> What do I not know?
> - What other patches have you applied recently? From Windows Update, look at
> Installation History, and see what other patches have been applied in the past 2
> months.

working on that now. But in general all winxp machines are up to date
on windows updates. Currently chub (as of the last hour) does not
have sp/2 installed. (This was done just now and will change soon)

> - How old is Chub? Ansil / Harvey?

Ansil and Harvey were built a few mnths ago at about the same time and
are intel 3.2 Ghz with 2GB ram each.

All machines are used primarily for graphic and video work.

> - Compare patch history on Chub with Ansil and Harvey?

Soon...

> - What's different between the problematic folders and the working ones?
> Creation date? Created under different accounts? Maybe accessed differently?

Looking at share/security on each of the inaccessable ones I see
accessable ones with the same settings. I mean exactly the same on
each screen. (However I haven't checked all players yet)

> - Is Ansil / Chub / Harvey SFS or AFS?

What are SFS and AFS

> How does Chub differ from Ansil and Harvey?
> - Chub has Unix components.
> - Chub was originally installed as Windows XP pre-SP2, the other 2 as Windows
> XP SP2.

Ansil and Harvey also have unix conponents. At one time I had UWIN
(Unix for windows David Korn of korn shell fame's creation) installed
on all three but recently as in 2 days ago changed chub over to cygwin
and uninstalled the UWIN tools. Can't imagine if that would cause
this but I believe the problem was already present before making the change.

> Interesting details now:
> Typing \\chub into an explorer address locator box will make chub appear in
> `entire network' listing., From there some directories are simply not available
> and do not display any files. So far it doesn't seem to be consistently the
> same ones. But others work ok.

> Windows NT with NTFS (not FAT) AFS (not SFS) has a lot of ability to configure
> (block access of) ability to access and even see contents of individual folders,
> and you can specify that to the file level. Look at a working folder, and a
> non-working one. From Properties - Security - Advanced, look at the items in
> Advanced Security Settings. There's a shiteload of possible ways to fsck up
> folder access - differences in Inherited and Effective Permissions create lots
> of possibilities, and could relate to the directory hierarchy bit.

I found something that got me all excited... on the heirarch
E:\bk1\ghost-bk1

On properties/security/advanced I noticed that harry was listed
twice. The first one has `This directory only' and `not inherited'
along side.

Then I noticed a second Harry listing with `this directory,
subdirectory and files' `Inherited from E' along side.

I removed the first one thinking I'd really hit on something. Went to
ansil to try it out but I see the same behavior... maybe rebooting
them both will chnage that.... I'll know shortly.


--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Harry Putnam
07-10-2005, 02:53 AM
Harry Putnam <reader@newsguy.com> writes:

> I removed the first one thinking I'd really hit on something. Went to
> ansil to try it out but I see the same behavior... maybe rebooting
> them both will chnage that.... I'll know shortly.

No such luck....

Now I've gone to the top level of E H G the most problematic ones and
checked the box that removes all permissions done the heirarchy then
makes them all have the same as the top level.

Rebooting that change now.

--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Sun, 22 May 2005 02:42:34 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Harry Putnam <reader@newsguy.com> writes:
>
>> I removed the first one thinking I'd really hit on something. Went to
>> ansil to try it out but I see the same behavior... maybe rebooting
>> them both will chnage that.... I'll know shortly.
>
>No such luck....
>
>Now I've gone to the top level of E H G the most problematic ones and
>checked the box that removes all permissions done the heirarchy then
>makes them all have the same as the top level.
>
>Rebooting that change now.

Well, if you're looking at Properties - Security - Advanced, then you must have
AFS (Advanced File Sharing). SFS (Simple File Sharing) won't give you any of
that.

Can you make a list of all the non-working folders and see if they all have the
same settings under Security - Advanced? That would confirm or deny our hopes -
maybe we'll see another direction to look in too.

I looked at the browstat logs again, and note that they're all identical -
Reader is the master browser, and the only backup browser. Did you actually
have any of the 3 XP systems running the browser too?

I don't know a lot about Samba, I can see one difference between it an Windows.
All 3 Windows systems are getting "error = -1073741809" trying to open the
registry on Reader, I wonder if that's a "error = 5" (access denied in Windows)?
Any definable difference between the Unix components on Chub and on Ansil and
Harvey?

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:

> On Sun, 22 May 2005 02:42:34 GMT, Harry Putnam <reader@newsguy.com> wrote:
>
>>Harry Putnam <reader@newsguy.com> writes:
>>
>>> I removed the first one thinking I'd really hit on something. Went to
>>> ansil to try it out but I see the same behavior... maybe rebooting
>>> them both will chnage that.... I'll know shortly.
>>
>>No such luck....
>>
>>Now I've gone to the top level of E H G the most problematic ones and
>>checked the box that removes all permissions done the heirarchy then
>>makes them all have the same as the top level.
>>
>>Rebooting that change now.
>
> Well, if you're looking at Properties - Security - Advanced, then you must have
> AFS (Advanced File Sharing). SFS (Simple File Sharing) won't give you any of
> that.

OK, didn't understand the acronym Simple sharing has been off on all
three since install.

> Can you make a list of all the non-working folders and see if they all have the
> same settings under Security - Advanced? That would confirm or deny our hopes -
> maybe we'll see another direction to look in too.

I'll work on that ...

> I looked at the browstat logs again, and note that they're all identical -
> Reader is the master browser, and the only backup browser. Did you actually
> have any of the 3 XP systems running the browser too?

All three were set to Automatic and were running. I turned them all
off and had a look but saw no difference. They are all back on now.

> I don't know a lot about Samba, I can see one difference between it an Windows.
> All 3 Windows systems are getting "error = -1073741809" trying to open the
> registry on Reader, I wonder if that's a "error = 5" (access denied in Windows)?

I shut down the linux box to see what effect it had. All I saw from
browstat was that a different (windowsxp-pro) machine was elected
master. I didn't think to check if the error was there.

If you think it would add to diagnostics I can turn off samba and
rerun browstat..

> Any definable difference between the Unix components on Chub and on Ansil and
> Harvey?

There are differences yes, but I don't really know how extensive.
Chub is running `Cygwin' the others are running `Uwin'.

Cygwin is under more active development and may be more developed than
Uwin. Also the differnce between korn shell and bash shell would be
involved but I doubt unix shell differences would mean much in this.

Both unix tool sets either make or require user to make changes in
PATH variable and HOME variables.

There may be other differences that do something to shares. I doubt it
but It does seem kind of suspicious that cygwin was installed in the
last few days. Both unix shells as installed understand UNC
addressing so user can type at a shell prompt:
cd //chub/chub-e
and go to that share.

I'll have to continue with this tomorrow... its time for me to go pick
up my wife. Then I'll be hitting the sack.
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Harry Putnam
07-10-2005, 02:53 AM
Harry Putnam <reader@newsguy.com> writes:

>> Can you make a list of all the non-working folders and see if they
>> all have the same settings under Security - Advanced? That would
>> confirm or deny our hopes - maybe we'll see another direction to
>> look in too.
>
> I'll work on that ...

I've been tinkering all day again on this. I'm not finding a patter
to what is or is not available. For one thing it appears that once a
share level is forced by typing the exact address, that the OS
remembers for a while or untill that instance of explorer is closed.

But on a fresh start it seem that the depth at which things get
invisible is completely arbitrary both in drive and in depth of
heirarchy.

One thing seems to remain constant chub (the troublesome one) in
`NEVER' in `Network Places' even on itself. Only if one forces it by
typing \\chub\ into an explorer locator box. The OS then remembers
for a while but not long.

I'm convinced this is not a permissions problem at all. Here's why:
I carefully removed all shares on chub in Administrative tools by
`unsharing' them. Then rebooted.

I then shared each drive with Harry, reader <=(my dummy user on
allmachines with admin powers) and system having full permissions.
Then went to the security/advanced screen and made sure all subfolders
and files was enabled. Then selected the box where you force the
permissions displayed on that screen to be the only permissions on all
subfolders and files. Again a reboot.

That should ensure that the permissions are universally the same
throughout.

None of this affected the problem in any way. It is still randomely
possible to drill down in a share all the way and not in others.

At this point it may make some sense to just try to deal with the fact
that chub never shows up in Netowrk Places. How can I force it to
show up there?

One way is to type a share name \\chub\ but its only temporary.
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Harry Putnam
07-10-2005, 02:53 AM
Chuck, are you still with me? If so do you think the problem is
likely to be something to do with the browser subsytem?
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome

Chuck
07-10-2005, 02:53 AM
On Mon, 23 May 2005 00:55:19 GMT, Harry Putnam <reader@newsguy.com> wrote:

>Chuck, are you still with me? If so do you think the problem is
>likely to be something to do with the browser subsytem?

Harry,

If you don't get any help from Malke, and un sharing / re sharing, I'd be
inclined IIWY to stop the browser on Reader and start it on Chub. I don't know
too much about your Unix for Intel software but I see how the browser on Reader
reacts to attempts by the XP boxes to interrogate its build info.

I suspect that the Unix / Samba browser is just enough like the NT browser but
has one little difference.

But let's see how you do with Malke's instructions, and we'll try something else
if we get a chance.

I think the browser affects the Network Neighborhood thing, but I'm hesitant to
think that it has anything to do with your ability to walk down the tree of
folders.

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

Harry Putnam
07-10-2005, 02:53 AM
Chuck <none@example.net> writes:

> I suspect that the Unix / Samba browser is just enough like the NT browser but
> has one little difference.
>
> But let's see how you do with Malke's instructions, and we'll try something else
> if we get a chance.
>
> I think the browser affects the Network Neighborhood thing, but I'm hesitant to
> think that it has anything to do with your ability to walk down the tree of
> folders.

I wondered if samba was complicating things too. But I've run this
setup for several mnths now without this problem. Anyway I'm shutting
down samba too in addition to Malke's instructions.
I'm in the middle of it now.
--
For those interested in pediatrics
http://www.caringbridge.com/in/jkaela
Baby JKaela was born with Pentology of Cantrell syndrome


home lan puzzler