Hi,
Got stuck with the home network. This is the situation:
Vista => XP: works as expected, can access shared XP folders from Vista.
XP => Vista: no way Jose:
On the XP machine, I can see in Entire network / Microsoft Windows Network
the workgroup I use. When I open that workgroup, I see the various PCs on my
home network, including the Vista (Ultimate) one. From the XP machine, I can
click any of the other XP (or 98SE) machines and see the shared folders,
access them etc. HOWEVER, I can see the icon of the Vista machine, but any
attempt to access it gives "\\LOMMEL is not accessible. You might not have
permission to use this network resource. Contact the adminstrator of this
server to find out if you have access permissions. The network path was not
found'. On the Vista machine I have in the 'Network and Sharing center' the
following 'on': Network Discovery, File Sharing and Public Folder sharing.
The network on Vista is set as 'Private'. The N&S center also reports the
'public' folder as shared.

Where did I go wrong? Any tip welcome!
Wytze

http://www.microsoft.com/technet/net.../vista_fp.mspx

The above link should help you

Have you tried the following:
In Vista Networking and Sharing:
1 Network Discovery ON
2 File Sharing ON
3 Public Folder Sharing ON
4 Password Protected OFF
5 and the Network should be set to “Private�

And have you made sure that the workgroup names are the same on XP, 98 and
Vista.
By default XP is MSHOME and Vista is WORKGROUP; they should be the same.
Also "Shared Docs" in XP is called "Public Folder" in Vista


"Wytze" wrote:

> Hi,
> Got stuck with the home network. This is the situation:
> Vista => XP: works as expected, can access shared XP folders from Vista.
> XP => Vista: no way Jose:
> On the XP machine, I can see in Entire network / Microsoft Windows Network
> the workgroup I use. When I open that workgroup, I see the various PCs on my
> home network, including the Vista (Ultimate) one. From the XP machine, I can
> click any of the other XP (or 98SE) machines and see the shared folders,
> access them etc. HOWEVER, I can see the icon of the Vista machine, but any
> attempt to access it gives "\\LOMMEL is not accessible. You might not have
> permission to use this network resource. Contact the adminstrator of this
> server to find out if you have access permissions. The network path was not
> found'. On the Vista machine I have in the 'Network and Sharing center' the
> following 'on': Network Discovery, File Sharing and Public Folder sharing.
> The network on Vista is set as 'Private'. The N&S center also reports the
> 'public' folder as shared.
>
> Where did I go wrong? Any tip welcome!
> Wytze
>

On Thu, 23 Aug 2007 13:30:03 -0700, Wytze <wytze.removethis@hoogslag.dot.com>
wrote:

>Hi,
>Got stuck with the home network. This is the situation:
>Vista => XP: works as expected, can access shared XP folders from Vista.
>XP => Vista: no way Jose:
>On the XP machine, I can see in Entire network / Microsoft Windows Network
>the workgroup I use. When I open that workgroup, I see the various PCs on my
>home network, including the Vista (Ultimate) one. From the XP machine, I can
>click any of the other XP (or 98SE) machines and see the shared folders,
>access them etc. HOWEVER, I can see the icon of the Vista machine, but any
>attempt to access it gives "\\LOMMEL is not accessible. You might not have
>permission to use this network resource. Contact the adminstrator of this
>server to find out if you have access permissions. The network path was not
>found'. On the Vista machine I have in the 'Network and Sharing center' the
>following 'on': Network Discovery, File Sharing and Public Folder sharing.
>The network on Vista is set as 'Private'. The N&S center also reports the
>'public' folder as shared.
>
>Where did I go wrong? Any tip welcome!
>Wytze

The error "... network path was not found" indicates a name resolution problem.
This will frequently be caused by a misconfigured or overlooked personal
firewall, or by an inconsistent NetBT setting.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/0...ing-using.html

Also, check name resolution on each computer.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/0...on-on-lan.html

Finally, read about other possible problems.
<http://nitecruzr.blogspot.com/2006/12/windows-xp-and-vista-on-lan-together.html>
http://nitecruzr.blogspot.com/2006/1...-together.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.

Mick, Chuck: Thanks, you did the job!

Since I would guess I'm not the only one with this problem, let me summarize
the solution. See the problem description in my initial post.

"Caused by" not using Windows Firewall. I'm using 'One Care' and this one
was not automatically configured when I setup file and printer sharing. And I
thought that using a MS product like One Care would forever get rid of these
of annoying problems …

There is indeed a 'warning' displayed in the 'Network Sharing Center' which
I wondered about, but I though "what the heck, I'm using a MS firewall, that
will be OK". The message states: "For sharing and discovery to work properly,
make sure the settings in your firewall program match the following setting."
(there is no further clue). The links provided by Mick and Chuck mention this
potential firewall pitfall (and Chuck was right in his first suggestion :-))
and give a list of ports/protocols to be opened (see somewhere at the end of
http://www.microsoft.com/technet/net.../vista_fp.mspx)

To solve, go to the firewall settings of One Care and in the 'Firewall
connection tool' tick the obvious boxes. Your done!

Suggestions for those who can influence:
- One Care to behave similar as Windows Firewall
- Network Sharing Center to give additional information with the warning
message mentioned above

Bottom line: Posting here solved the issue - Thanks!
Wytze

On Sat, 25 Aug 2007 00:12:01 -0700, Wytze <wytze.removethis@hoogslag.dot.com>
wrote:

>Mick, Chuck: Thanks, you did the job!
>
>Since I would guess I'm not the only one with this problem, let me summarize
>the solution. See the problem description in my initial post.
>
>"Caused by" not using Windows Firewall. I'm using 'One Care' and this one
>was not automatically configured when I setup file and printer sharing. And I
>thought that using a MS product like One Care would forever get rid of these
>of annoying problems …
>
>There is indeed a 'warning' displayed in the 'Network Sharing Center' which
>I wondered about, but I though "what the heck, I'm using a MS firewall, that
>will be OK". The message states: "For sharing and discovery to work properly,
>make sure the settings in your firewall program match the following setting."
>(there is no further clue). The links provided by Mick and Chuck mention this
>potential firewall pitfall (and Chuck was right in his first suggestion :-))
>and give a list of ports/protocols to be opened (see somewhere at the end of
>http://www.microsoft.com/technet/net.../vista_fp.mspx)
>
>To solve, go to the firewall settings of One Care and in the 'Firewall
>connection tool' tick the obvious boxes. Your done!
>
>Suggestions for those who can influence:
>- One Care to behave similar as Windows Firewall
>- Network Sharing Center to give additional information with the warning
>message mentioned above
>
>Bottom line: Posting here solved the issue - Thanks!
>Wytze

Thanks for the feedback. I have heard that some folks pronounce "One Care" as
"Wan Kare". Do you know any British people who could explain the pun?

I'm going to write about "Wanker" now. Thanks for the details.

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.