you probably already do this:
You can see more if you switch to normal tree+filepane view (not "tasks"). This
screenshot may be from win2000:
http://technet.microsoft.com/en-us/library/Cc750987.pp6_big%28en-
us,TechNet.10%29.gif
___________
(i am not :-0 )
Post by stronglineI got a user who got "access denied" if he opens the folder directly
using UNC path. However if he navigates thru "network places" then he
has no problem at all! Needless to say, his permissions are set
properly on the target folder.
so these fail:
pasting unc path to FOLDER into addressbar of explorer
double clicking a shortcut (.lnk) of same path
succeeds:
navigate method goes through
Post by stronglineEntire Network
Microsoft Windows Network
ourWorkgroup (workgroup name, such as MSHOME)
You may or may not see the othe pc names. You may or may not see them in tree
pane of explore, but may or may not see them in file pane (when you click on
ourWorkgroup)
expanders at pcnames may not exist, or disappear when clicked. or do show, and
can see shared folders.
http://www.microsoft.com/library/media/1033/windowsxp/images/using/networking/
expert/docshare02.jpg
[that screenshot looks edited. as if showing tasks and tree simultaneously.)
Post by stronglineHe can map to that share fine, but again if he tries to open the
driver letter, access denied.
so when navigating, dosen't open EVERY level in filepane? because the "drive
letter" (is that the pc name?) would balk. Instead, must navigate
there's a more direct navigation. once "network" is open, a bunch of "automatically
saved" nethood folders will show. I can't find a screenshot. They'll have icon like
this http://images.google.com/images?q=%22shared+folder%22+icon+site%
3Amicrosoft.com
paste this into addressbar (path) in explorer:
%UserProfile%\NetHood
Post by stronglineCan any one explain why so? What's the difference between accessing a
network share from UNC and accessing from "network places"?
the other pc is also xp? only one other pc, from your description.
Some things to TRY.
What are the results when try same experiments in reverse direction?
network logs.
Enable logging or "asking" for some rules in firewall(s). Do this for svchost and
System, possibly for explorer.exe (any others?). Then watch the firewall log during
your experiments.
disable firewalls
Disconnect modem power or data-in cable, but leave router on.
then, one pc at a time: disable software firewall (kaspersky, outpost, comodo, etc.
or windows builtin fw). Check network navigating.
__
I used these searches:
http://images.google.com/images?q=mshome+|+workgroup+%22entire+network%
22
http://images.google.com/images?q=~pcs+%
7C+computers+shared+folder+expand+%22network+neighborhood%22+%
7C+nethood
http://images.google.com/images?
q=~pcs+|+computers+workgroup+site:microsoft.com+%
22network+neighborhood%22+|+nethood
http://images.google.com/images?&q=~pcs%20%7C%20computers%
20mshome%20site:microsoft.com