I've done this and posted the results. Please note that I am not
getting the error your link discusses.
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.
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>
[...]
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.
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>
[...]
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.
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.
Harry Putnam said: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 said: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
Chuck said: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.
Chuck said: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.
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)
Harry Putnam said: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
Chuck said: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?
And it looks like you left 192.168.0.20 out of PingTargets above?
Harry Putnam said: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...up:*windowsxp*&rnum=12&hl=en#35dc88f659e58bf1
It is installed. I don't think it was very recently installed though
Chuck said: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?
Doing that now...
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.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.