Vista - Cannot see workgroup computers

Thanks for the reply Bruce. Actually I saw an earlier post from you
recommending that method and had tried it unsuccessfully. Just to be sure
nothing has changed I just tried it again and couldn't get to either the XP
Pro computer or a Windows 2000 machine. I get the "Windows cannot
access\\Cecilsjetone\SharedDocs" message telling me to check my spelling.
The error code is 0x80070035 "The network path was not found."

Thanks again for the reply.
Cecil Britton

"C. Britton" wrote:

> I am not offering a solution. I only want to say that I have the exact same
> problem on my system using RC-1 x64. I have taken every precaution mentioned
> in this thread and I still can't get around the problem. I even went so far
> as to disable the firewall in my router in case it was the culprit. That
> didn't work either.
>
> One thing I am able to do that I didn't see mentioned here is that I can see
> and access shared folders on the Vista machine from both the XP and the
> Windows 2000 machines on the network. In other words I have one-way network
> traffic only.
>
> And, no I can't see the other machines anywhere in Vista, not just in
> Windows Explorer.
>
>
>
> "Bruce Sanderson" wrote:
>
> > Do you mean "can't see" under Network in Explorer or something else?
> >
> > In Start, Run, key \\othercomputername and press Enter. What happens?
> >
> > If you haven't already, try enabling NetBIOS over TCP/IP (network connection
> > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties, Advanced...,
> > WINS).
> >
> > Vista can interoperate with XP and 2003 computers that do not have the LLTD
> > Responder installed. Adding the LLTD Responder
> > (http://www.microsoft.com/downloads/d...displaylang=en)
> > will allow XP computers to appear in the "Network Map", but is not required
> > for "normal" interoperability.
> >
> > --
> > Bruce Sanderson MVP Printing
> > http://members.shaw.ca/bsanders
> >
> > It is perfectly useless to know the right answer to the wrong question.
> >
> >
> >
> > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
> > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
> > > With WinVista RC1 Build 5600 installed, I cannot see any of the PCs in my
> > > workgroup (all WinXP or Win2K). Within Vista, I have changed the name of
> > > the
> > > workgroup to reflect the workgroup name. I have enabled discovery. I
> > > have
> > > the network identified as a private network. I can ping all of the PCs on
> > > the network, but Vista will not recognize them. I can get to the 'net (of
> > > course). Within Services, LLTD keeps stopping. I have all of the
> > > dependencies for LLTD started. I have the LLTD elements enabled in Group
> > > Policy.
> > > Can anyone offer a suggestion as to why LLTD keeps stopping and why I
> > > cannot
> > > see any other elements of my workgroup? Thanks.
> >

Try turning sharing off then back on again for the folder you want to access
on the XP machine.


Mark



"C. Britton" wrote:

> Thanks for the reply Bruce. Actually I saw an earlier post from you
> recommending that method and had tried it unsuccessfully. Just to be sure
> nothing has changed I just tried it again and couldn't get to either the XP
> Pro computer or a Windows 2000 machine. I get the "Windows cannot
> access\\Cecilsjetone\SharedDocs" message telling me to check my spelling.
> The error code is 0x80070035 "The network path was not found."
>
> Thanks again for the reply.
> Cecil Britton
>
> "C. Britton" wrote:
>
> > I am not offering a solution. I only want to say that I have the exact same
> > problem on my system using RC-1 x64. I have taken every precaution mentioned
> > in this thread and I still can't get around the problem. I even went so far
> > as to disable the firewall in my router in case it was the culprit. That
> > didn't work either.
> >
> > One thing I am able to do that I didn't see mentioned here is that I can see
> > and access shared folders on the Vista machine from both the XP and the
> > Windows 2000 machines on the network. In other words I have one-way network
> > traffic only.
> >
> > And, no I can't see the other machines anywhere in Vista, not just in
> > Windows Explorer.
> >
> >
> >
> > "Bruce Sanderson" wrote:
> >
> > > Do you mean "can't see" under Network in Explorer or something else?
> > >
> > > In Start, Run, key \\othercomputername and press Enter. What happens?
> > >
> > > If you haven't already, try enabling NetBIOS over TCP/IP (network connection
> > > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties, Advanced...,
> > > WINS).
> > >
> > > Vista can interoperate with XP and 2003 computers that do not have the LLTD
> > > Responder installed. Adding the LLTD Responder
> > > (http://www.microsoft.com/downloads/d...displaylang=en)
> > > will allow XP computers to appear in the "Network Map", but is not required
> > > for "normal" interoperability.
> > >
> > > --
> > > Bruce Sanderson MVP Printing
> > > http://members.shaw.ca/bsanders
> > >
> > > It is perfectly useless to know the right answer to the wrong question.
> > >
> > >
> > >
> > > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
> > > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
> > > > With WinVista RC1 Build 5600 installed, I cannot see any of the PCs in my
> > > > workgroup (all WinXP or Win2K). Within Vista, I have changed the name of
> > > > the
> > > > workgroup to reflect the workgroup name. I have enabled discovery. I
> > > > have
> > > > the network identified as a private network. I can ping all of the PCs on
> > > > the network, but Vista will not recognize them. I can get to the 'net (of
> > > > course). Within Services, LLTD keeps stopping. I have all of the
> > > > dependencies for LLTD started. I have the LLTD elements enabled in Group
> > > > Policy.
> > > > Can anyone offer a suggestion as to why LLTD keeps stopping and why I
> > > > cannot
> > > > see any other elements of my workgroup? Thanks.
> > >

Thanks for the suggestion. I tried it but didn't have any success.

"Mark S-123" wrote:

> Try turning sharing off then back on again for the folder you want to access
> on the XP machine.
>
>
> Mark
>
>
>
> "C. Britton" wrote:
>
> > Thanks for the reply Bruce. Actually I saw an earlier post from you
> > recommending that method and had tried it unsuccessfully. Just to be sure
> > nothing has changed I just tried it again and couldn't get to either the XP
> > Pro computer or a Windows 2000 machine. I get the "Windows cannot
> > access\\Cecilsjetone\SharedDocs" message telling me to check my spelling.
> > The error code is 0x80070035 "The network path was not found."
> >
> > Thanks again for the reply.
> > Cecil Britton
> >
> > "C. Britton" wrote:
> >
> > > I am not offering a solution. I only want to say that I have the exact same
> > > problem on my system using RC-1 x64. I have taken every precaution mentioned
> > > in this thread and I still can't get around the problem. I even went so far
> > > as to disable the firewall in my router in case it was the culprit. That
> > > didn't work either.
> > >
> > > One thing I am able to do that I didn't see mentioned here is that I can see
> > > and access shared folders on the Vista machine from both the XP and the
> > > Windows 2000 machines on the network. In other words I have one-way network
> > > traffic only.
> > >
> > > And, no I can't see the other machines anywhere in Vista, not just in
> > > Windows Explorer.
> > >
> > >
> > >
> > > "Bruce Sanderson" wrote:
> > >
> > > > Do you mean "can't see" under Network in Explorer or something else?
> > > >
> > > > In Start, Run, key \\othercomputername and press Enter. What happens?
> > > >
> > > > If you haven't already, try enabling NetBIOS over TCP/IP (network connection
> > > > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties, Advanced...,
> > > > WINS).
> > > >
> > > > Vista can interoperate with XP and 2003 computers that do not have the LLTD
> > > > Responder installed. Adding the LLTD Responder
> > > > (http://www.microsoft.com/downloads/d...displaylang=en)
> > > > will allow XP computers to appear in the "Network Map", but is not required
> > > > for "normal" interoperability.
> > > >
> > > > --
> > > > Bruce Sanderson MVP Printing
> > > > http://members.shaw.ca/bsanders
> > > >
> > > > It is perfectly useless to know the right answer to the wrong question.
> > > >
> > > >
> > > >
> > > > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
> > > > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
> > > > > With WinVista RC1 Build 5600 installed, I cannot see any of the PCs in my
> > > > > workgroup (all WinXP or Win2K). Within Vista, I have changed the name of
> > > > > the
> > > > > workgroup to reflect the workgroup name. I have enabled discovery. I
> > > > > have
> > > > > the network identified as a private network. I can ping all of the PCs on
> > > > > the network, but Vista will not recognize them. I can get to the 'net (of
> > > > > course). Within Services, LLTD keeps stopping. I have all of the
> > > > > dependencies for LLTD started. I have the LLTD elements enabled in Group
> > > > > Policy.
> > > > > Can anyone offer a suggestion as to why LLTD keeps stopping and why I
> > > > > cannot
> > > > > see any other elements of my workgroup? Thanks.
> > > >

To see if the problem is a "name resolution" problem or something else, try
these two things:

1. determine the IP address of the XP computer (e.g. using the command
ipconfig /all)
then, on the Vista computer, click Start, Run and key
\\xxx.xxx.xxx.xxx (\\ followed by the IP address of the XP
computer)

2. on the Vista computer, click Start, Run and key
\\XPComputerName (without any share name)

What happens?

Is there any possibility of using a later build of Vista? There were quite
a number of fixes between RC1 and RTM. I realize that Vista RTM is not yet
generally available, but if you have access to an MSDN, Technet subscription
Vista RTM is available for download.

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"C. Britton" <CBritton@discussions.microsoft.com> wrote in message
news81AF089-895A-4870-B675-B9ACE6C901C8@microsoft.com...
> Thanks for the reply Bruce. Actually I saw an earlier post from you
> recommending that method and had tried it unsuccessfully. Just to be sure
> nothing has changed I just tried it again and couldn't get to either the
> XP
> Pro computer or a Windows 2000 machine. I get the "Windows cannot
> access\\Cecilsjetone\SharedDocs" message telling me to check my spelling.
> The error code is 0x80070035 "The network path was not found."
>
> Thanks again for the reply.
> Cecil Britton
>
> "C. Britton" wrote:
>
>> I am not offering a solution. I only want to say that I have the exact
>> same
>> problem on my system using RC-1 x64. I have taken every precaution
>> mentioned
>> in this thread and I still can't get around the problem. I even went so
>> far
>> as to disable the firewall in my router in case it was the culprit. That
>> didn't work either.
>>
>> One thing I am able to do that I didn't see mentioned here is that I can
>> see
>> and access shared folders on the Vista machine from both the XP and the
>> Windows 2000 machines on the network. In other words I have one-way
>> network
>> traffic only.
>>
>> And, no I can't see the other machines anywhere in Vista, not just in
>> Windows Explorer.
>>
>>
>>
>> "Bruce Sanderson" wrote:
>>
>> > Do you mean "can't see" under Network in Explorer or something else?
>> >
>> > In Start, Run, key \\othercomputername and press Enter. What happens?
>> >
>> > If you haven't already, try enabling NetBIOS over TCP/IP (network
>> > connection
>> > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties,
>> > Advanced...,
>> > WINS).
>> >
>> > Vista can interoperate with XP and 2003 computers that do not have the
>> > LLTD
>> > Responder installed. Adding the LLTD Responder
>> > (http://www.microsoft.com/downloads/d...displaylang=en)
>> > will allow XP computers to appear in the "Network Map", but is not
>> > required
>> > for "normal" interoperability.
>> >
>> > --
>> > Bruce Sanderson MVP Printing
>> > http://members.shaw.ca/bsanders
>> >
>> > It is perfectly useless to know the right answer to the wrong question.
>> >
>> >
>> >
>> > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
>> > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
>> > > With WinVista RC1 Build 5600 installed, I cannot see any of the PCs
>> > > in my
>> > > workgroup (all WinXP or Win2K). Within Vista, I have changed the
>> > > name of
>> > > the
>> > > workgroup to reflect the workgroup name. I have enabled discovery.
>> > > I
>> > > have
>> > > the network identified as a private network. I can ping all of the
>> > > PCs on
>> > > the network, but Vista will not recognize them. I can get to the
>> > > 'net (of
>> > > course). Within Services, LLTD keeps stopping. I have all of the
>> > > dependencies for LLTD started. I have the LLTD elements enabled in
>> > > Group
>> > > Policy.
>> > > Can anyone offer a suggestion as to why LLTD keeps stopping and why I
>> > > cannot
>> > > see any other elements of my workgroup? Thanks.
>> >

I had a problem very similar to this. I could get my computers to all connect
via unc i.e. \\computer1\C$ and vice versa. It worked with all xp machines
and vista to all xp. But NO PC's were showing up in network neighborhood.

I started thinking that not to long ago everything worked fine on my
network. Since that time two things have changes. 1. windows vista RTM and 2.
A new netgear wifi router. Now I didnt think it was vista and I think I was
right. I resetted my router back to to the defaults. First I power cycled my
cable modem, then once all cable modem lights sync'd up I gave router power
and held down the little button in the back to get it back to factory
defaults.

Went into network neighborhood, and bam, all pc's showed up.

Other things to consider, make sure all computers are on the same domain. xp
machines are on "mshome" vista goes to "workgroup" I suggest enabling if
possible simple file sharing. I also suggest 1st try to ping a computer, if
pinging the pc is successfull then using start->run>192.168.x.y to connect to
that pc as a test.

If you can PING a XP machine from a xp machine then you should be able to
connect to it. Furthermore, you then should be able to connect to it via
computer name or ip address. THEN.....

On the vista box do the same as above. Select an xp machine to ping, then
try to connect to it via ip and or computer name. If that is all successfully
and the computers still dont show up, try power cycling your router. Thats
what I did and it worked

"Bruce Sanderson" wrote:

> To see if the problem is a "name resolution" problem or something else, try
> these two things:
>
> 1. determine the IP address of the XP computer (e.g. using the command
> ipconfig /all)
> then, on the Vista computer, click Start, Run and key
> \\xxx.xxx.xxx.xxx (\\ followed by the IP address of the XP
> computer)
>
> 2. on the Vista computer, click Start, Run and key
> \\XPComputerName (without any share name)
>
> What happens?
>
> Is there any possibility of using a later build of Vista? There were quite
> a number of fixes between RC1 and RTM. I realize that Vista RTM is not yet
> generally available, but if you have access to an MSDN, Technet subscription
> Vista RTM is available for download.
>
> --
> Bruce Sanderson MVP Printing
> http://members.shaw.ca/bsanders
>
> It is perfectly useless to know the right answer to the wrong question.
>
>
>
> "C. Britton" <CBritton@discussions.microsoft.com> wrote in message
> news81AF089-895A-4870-B675-B9ACE6C901C8@microsoft.com...
> > Thanks for the reply Bruce. Actually I saw an earlier post from you
> > recommending that method and had tried it unsuccessfully. Just to be sure
> > nothing has changed I just tried it again and couldn't get to either the
> > XP
> > Pro computer or a Windows 2000 machine. I get the "Windows cannot
> > access\\Cecilsjetone\SharedDocs" message telling me to check my spelling.
> > The error code is 0x80070035 "The network path was not found."
> >
> > Thanks again for the reply.
> > Cecil Britton
> >
> > "C. Britton" wrote:
> >
> >> I am not offering a solution. I only want to say that I have the exact
> >> same
> >> problem on my system using RC-1 x64. I have taken every precaution
> >> mentioned
> >> in this thread and I still can't get around the problem. I even went so
> >> far
> >> as to disable the firewall in my router in case it was the culprit. That
> >> didn't work either.
> >>
> >> One thing I am able to do that I didn't see mentioned here is that I can
> >> see
> >> and access shared folders on the Vista machine from both the XP and the
> >> Windows 2000 machines on the network. In other words I have one-way
> >> network
> >> traffic only.
> >>
> >> And, no I can't see the other machines anywhere in Vista, not just in
> >> Windows Explorer.
> >>
> >>
> >>
> >> "Bruce Sanderson" wrote:
> >>
> >> > Do you mean "can't see" under Network in Explorer or something else?
> >> >
> >> > In Start, Run, key \\othercomputername and press Enter. What happens?
> >> >
> >> > If you haven't already, try enabling NetBIOS over TCP/IP (network
> >> > connection
> >> > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties,
> >> > Advanced...,
> >> > WINS).
> >> >
> >> > Vista can interoperate with XP and 2003 computers that do not have the
> >> > LLTD
> >> > Responder installed. Adding the LLTD Responder
> >> > (http://www.microsoft.com/downloads/d...displaylang=en)
> >> > will allow XP computers to appear in the "Network Map", but is not
> >> > required
> >> > for "normal" interoperability.
> >> >
> >> > --
> >> > Bruce Sanderson MVP Printing
> >> > http://members.shaw.ca/bsanders
> >> >
> >> > It is perfectly useless to know the right answer to the wrong question.
> >> >
> >> >
> >> >
> >> > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
> >> > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
> >> > > With WinVista RC1 Build 5600 installed, I cannot see any of the PCs
> >> > > in my
> >> > > workgroup (all WinXP or Win2K). Within Vista, I have changed the
> >> > > name of
> >> > > the
> >> > > workgroup to reflect the workgroup name. I have enabled discovery.
> >> > > I
> >> > > have
> >> > > the network identified as a private network. I can ping all of the
> >> > > PCs on
> >> > > the network, but Vista will not recognize them. I can get to the
> >> > > 'net (of
> >> > > course). Within Services, LLTD keeps stopping. I have all of the
> >> > > dependencies for LLTD started. I have the LLTD elements enabled in
> >> > > Group
> >> > > Policy.
> >> > > Can anyone offer a suggestion as to why LLTD keeps stopping and why I
> >> > > cannot
> >> > > see any other elements of my workgroup? Thanks.
> >> >
>
>

Thanks Bruce, I just tried it and neither attempt worked. What is strange is
that when the Vista machine fails to connect, it automatically asks if you
want to diagnose the failure. I clicked yes and it said a problem was found,
I was asked if I wanted to fix the problem and about 30 seconds later got a
messaged that it was fixed. I immediately entered the same run command and
didn't connect, but this time I ran the diagnosis and got the message that no
problem was found.

Now I ran the command using the computer name and went through the same
routine but the result of the diagnostic was that it found a serious problem
and I should contact my ISP or my network Administrator. Out of curiosity I
ran the exact same command and this time the diagnostic again said there was
no network problem.

From all this I would assume that the diagnostic routine is getting random
results from its queries.

I would love to get a copy of the RTM but unfortunately I don't subscribe to
Technet and don't have anyone around here who does that I know of. I guess I
will have to just wait until the 30th and take the $399 gamble on the retail
version of Ultimate. That is going to take some soul searching because I
would never stop kicking myself if I spend that amount on something I haven't
seen work correctly so far. Then again if I didn't have problems I'd be
bored.

Cecil

"Bruce Sanderson" wrote:

> To see if the problem is a "name resolution" problem or something else, try
> these two things:
>
> 1. determine the IP address of the XP computer (e.g. using the command
> ipconfig /all)
> then, on the Vista computer, click Start, Run and key
> \\xxx.xxx.xxx.xxx (\\ followed by the IP address of the XP
> computer)
>
> 2. on the Vista computer, click Start, Run and key
> \\XPComputerName (without any share name)
>
> What happens?
>
> Is there any possibility of using a later build of Vista? There were quite
> a number of fixes between RC1 and RTM. I realize that Vista RTM is not yet
> generally available, but if you have access to an MSDN, Technet subscription
> Vista RTM is available for download.
>
> --
> Bruce Sanderson MVP Printing
> http://members.shaw.ca/bsanders
>
> It is perfectly useless to know the right answer to the wrong question.
>
>
>
> "C. Britton" <CBritton@discussions.microsoft.com> wrote in message
> news81AF089-895A-4870-B675-B9ACE6C901C8@microsoft.com...
> > Thanks for the reply Bruce. Actually I saw an earlier post from you
> > recommending that method and had tried it unsuccessfully. Just to be sure
> > nothing has changed I just tried it again and couldn't get to either the
> > XP
> > Pro computer or a Windows 2000 machine. I get the "Windows cannot
> > access\\Cecilsjetone\SharedDocs" message telling me to check my spelling.
> > The error code is 0x80070035 "The network path was not found."
> >
> > Thanks again for the reply.
> > Cecil Britton
> >
> > "C. Britton" wrote:
> >
> >> I am not offering a solution. I only want to say that I have the exact
> >> same
> >> problem on my system using RC-1 x64. I have taken every precaution
> >> mentioned
> >> in this thread and I still can't get around the problem. I even went so
> >> far
> >> as to disable the firewall in my router in case it was the culprit. That
> >> didn't work either.
> >>
> >> One thing I am able to do that I didn't see mentioned here is that I can
> >> see
> >> and access shared folders on the Vista machine from both the XP and the
> >> Windows 2000 machines on the network. In other words I have one-way
> >> network
> >> traffic only.
> >>
> >> And, no I can't see the other machines anywhere in Vista, not just in
> >> Windows Explorer.
> >>
> >>
> >>
> >> "Bruce Sanderson" wrote:
> >>
> >> > Do you mean "can't see" under Network in Explorer or something else?
> >> >
> >> > In Start, Run, key \\othercomputername and press Enter. What happens?
> >> >
> >> > If you haven't already, try enabling NetBIOS over TCP/IP (network
> >> > connection
> >> > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties,
> >> > Advanced...,
> >> > WINS).
> >> >
> >> > Vista can interoperate with XP and 2003 computers that do not have the
> >> > LLTD
> >> > Responder installed. Adding the LLTD Responder
> >> > (http://www.microsoft.com/downloads/d...displaylang=en)
> >> > will allow XP computers to appear in the "Network Map", but is not
> >> > required
> >> > for "normal" interoperability.
> >> >
> >> > --
> >> > Bruce Sanderson MVP Printing
> >> > http://members.shaw.ca/bsanders
> >> >
> >> > It is perfectly useless to know the right answer to the wrong question.
> >> >
> >> >
> >> >
> >> > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
> >> > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
> >> > > With WinVista RC1 Build 5600 installed, I cannot see any of the PCs
> >> > > in my
> >> > > workgroup (all WinXP or Win2K). Within Vista, I have changed the
> >> > > name of
> >> > > the
> >> > > workgroup to reflect the workgroup name. I have enabled discovery.
> >> > > I
> >> > > have
> >> > > the network identified as a private network. I can ping all of the
> >> > > PCs on
> >> > > the network, but Vista will not recognize them. I can get to the
> >> > > 'net (of
> >> > > course). Within Services, LLTD keeps stopping. I have all of the
> >> > > dependencies for LLTD started. I have the LLTD elements enabled in
> >> > > Group
> >> > > Policy.
> >> > > Can anyone offer a suggestion as to why LLTD keeps stopping and why I
> >> > > cannot
> >> > > see any other elements of my workgroup? Thanks.
> >> >
>
>

Thanks for the reply Brandon. Actually I have tried all the things you
suggested without success. I can ping or send files back and forth from the
XP computer and the Win 2000 computers to each other. I can do the same from
those computers to the Vista machine. But, I can't see the other computers
at all from the Vista computer. I've checked every setting and I have done a
power reset on the network components, I have even turned off the router
firewall and still nothing works. I'm relatively sure the problem lies in
the new TCP/IP stack but turning off then newer facets of that haven't worked
either.

I only hope this problem has been fixed in the retail version so I don't
spend the rest of my life on the phone with MS support.

"Brandon" wrote:

> I had a problem very similar to this. I could get my computers to all connect
> via unc i.e. \\computer1\C$ and vice versa. It worked with all xp machines
> and vista to all xp. But NO PC's were showing up in network neighborhood.
>
> I started thinking that not to long ago everything worked fine on my
> network. Since that time two things have changes. 1. windows vista RTM and 2.
> A new netgear wifi router. Now I didnt think it was vista and I think I was
> right. I resetted my router back to to the defaults. First I power cycled my
> cable modem, then once all cable modem lights sync'd up I gave router power
> and held down the little button in the back to get it back to factory
> defaults.
>
> Went into network neighborhood, and bam, all pc's showed up.
>
> Other things to consider, make sure all computers are on the same domain. xp
> machines are on "mshome" vista goes to "workgroup" I suggest enabling if
> possible simple file sharing. I also suggest 1st try to ping a computer, if
> pinging the pc is successfull then using start->run>192.168.x.y to connect to
> that pc as a test.
>
> If you can PING a XP machine from a xp machine then you should be able to
> connect to it. Furthermore, you then should be able to connect to it via
> computer name or ip address. THEN.....
>
> On the vista box do the same as above. Select an xp machine to ping, then
> try to connect to it via ip and or computer name. If that is all successfully
> and the computers still dont show up, try power cycling your router. Thats
> what I did and it worked
>
> "Bruce Sanderson" wrote:
>
> > To see if the problem is a "name resolution" problem or something else, try
> > these two things:
> >
> > 1. determine the IP address of the XP computer (e.g. using the command
> > ipconfig /all)
> > then, on the Vista computer, click Start, Run and key
> > \\xxx.xxx.xxx.xxx (\\ followed by the IP address of the XP
> > computer)
> >
> > 2. on the Vista computer, click Start, Run and key
> > \\XPComputerName (without any share name)
> >
> > What happens?
> >
> > Is there any possibility of using a later build of Vista? There were quite
> > a number of fixes between RC1 and RTM. I realize that Vista RTM is not yet
> > generally available, but if you have access to an MSDN, Technet subscription
> > Vista RTM is available for download.
> >
> > --
> > Bruce Sanderson MVP Printing
> > http://members.shaw.ca/bsanders
> >
> > It is perfectly useless to know the right answer to the wrong question.
> >
> >
> >
> > "C. Britton" <CBritton@discussions.microsoft.com> wrote in message
> > news81AF089-895A-4870-B675-B9ACE6C901C8@microsoft.com...
> > > Thanks for the reply Bruce. Actually I saw an earlier post from you
> > > recommending that method and had tried it unsuccessfully. Just to be sure
> > > nothing has changed I just tried it again and couldn't get to either the
> > > XP
> > > Pro computer or a Windows 2000 machine. I get the "Windows cannot
> > > access\\Cecilsjetone\SharedDocs" message telling me to check my spelling.
> > > The error code is 0x80070035 "The network path was not found."
> > >
> > > Thanks again for the reply.
> > > Cecil Britton
> > >
> > > "C. Britton" wrote:
> > >
> > >> I am not offering a solution. I only want to say that I have the exact
> > >> same
> > >> problem on my system using RC-1 x64. I have taken every precaution
> > >> mentioned
> > >> in this thread and I still can't get around the problem. I even went so
> > >> far
> > >> as to disable the firewall in my router in case it was the culprit. That
> > >> didn't work either.
> > >>
> > >> One thing I am able to do that I didn't see mentioned here is that I can
> > >> see
> > >> and access shared folders on the Vista machine from both the XP and the
> > >> Windows 2000 machines on the network. In other words I have one-way
> > >> network
> > >> traffic only.
> > >>
> > >> And, no I can't see the other machines anywhere in Vista, not just in
> > >> Windows Explorer.
> > >>
> > >>
> > >>
> > >> "Bruce Sanderson" wrote:
> > >>
> > >> > Do you mean "can't see" under Network in Explorer or something else?
> > >> >
> > >> > In Start, Run, key \\othercomputername and press Enter. What happens?
> > >> >
> > >> > If you haven't already, try enabling NetBIOS over TCP/IP (network
> > >> > connection
> > >> > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties,
> > >> > Advanced...,
> > >> > WINS).
> > >> >
> > >> > Vista can interoperate with XP and 2003 computers that do not have the
> > >> > LLTD
> > >> > Responder installed. Adding the LLTD Responder
> > >> > (http://www.microsoft.com/downloads/d...displaylang=en)
> > >> > will allow XP computers to appear in the "Network Map", but is not
> > >> > required
> > >> > for "normal" interoperability.
> > >> >
> > >> > --
> > >> > Bruce Sanderson MVP Printing
> > >> > http://members.shaw.ca/bsanders
> > >> >
> > >> > It is perfectly useless to know the right answer to the wrong question.
> > >> >
> > >> >
> > >> >
> > >> > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
> > >> > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
> > >> > > With WinVista RC1 Build 5600 installed, I cannot see any of the PCs
> > >> > > in my
> > >> > > workgroup (all WinXP or Win2K). Within Vista, I have changed the
> > >> > > name of
> > >> > > the
> > >> > > workgroup to reflect the workgroup name. I have enabled discovery.
> > >> > > I
> > >> > > have
> > >> > > the network identified as a private network. I can ping all of the
> > >> > > PCs on
> > >> > > the network, but Vista will not recognize them. I can get to the
> > >> > > 'net (of
> > >> > > course). Within Services, LLTD keeps stopping. I have all of the
> > >> > > dependencies for LLTD started. I have the LLTD elements enabled in
> > >> > > Group
> > >> > > Policy.
> > >> > > Can anyone offer a suggestion as to why LLTD keeps stopping and why I
> > >> > > cannot
> > >> > > see any other elements of my workgroup? Thanks.
> > >> >
> >
> >

Well, hard to know what to say. Vista RTM is working fine with respect to
interroperating over the network with Windows XP and Windows Server 2003,
both here at home and at work.

This, of course, is no guarantee it will work correctly with your particular
hardware.

What is the make and model of the network adapter in your Vista computer?
Is there any possibility of trying a different network adapter?

If Vista is detecting "problems" with your network, check that the IP
configuration is correct for your network (e.g. using the command ipconfig
/all). It might be that Vista RC1 is not able to get "good stuff" from the
DHCP service (e.g. in your router) for some reason.

You might want to try setting the IP configuration manually.

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"C. Britton" <CBritton@discussions.microsoft.com> wrote in message
news:F317A498-B601-476A-B44B-925BFF73E728@microsoft.com...
> Thanks Bruce, I just tried it and neither attempt worked. What is strange
> is
> that when the Vista machine fails to connect, it automatically asks if you
> want to diagnose the failure. I clicked yes and it said a problem was
> found,
> I was asked if I wanted to fix the problem and about 30 seconds later got
> a
> messaged that it was fixed. I immediately entered the same run command
> and
> didn't connect, but this time I ran the diagnosis and got the message that
> no
> problem was found.
>
> Now I ran the command using the computer name and went through the same
> routine but the result of the diagnostic was that it found a serious
> problem
> and I should contact my ISP or my network Administrator. Out of curiosity
> I
> ran the exact same command and this time the diagnostic again said there
> was
> no network problem.
>
> From all this I would assume that the diagnostic routine is getting random
> results from its queries.
>
> I would love to get a copy of the RTM but unfortunately I don't subscribe
> to
> Technet and don't have anyone around here who does that I know of. I
> guess I
> will have to just wait until the 30th and take the $399 gamble on the
> retail
> version of Ultimate. That is going to take some soul searching because I
> would never stop kicking myself if I spend that amount on something I
> haven't
> seen work correctly so far. Then again if I didn't have problems I'd be
> bored.
>
> Cecil
>
> "Bruce Sanderson" wrote:
>
>> To see if the problem is a "name resolution" problem or something else,
>> try
>> these two things:
>>
>> 1. determine the IP address of the XP computer (e.g. using the command
>> ipconfig /all)
>> then, on the Vista computer, click Start, Run and key
>> \\xxx.xxx.xxx.xxx (\\ followed by the IP address of the XP
>> computer)
>>
>> 2. on the Vista computer, click Start, Run and key
>> \\XPComputerName (without any share name)
>>
>> What happens?
>>
>> Is there any possibility of using a later build of Vista? There were
>> quite
>> a number of fixes between RC1 and RTM. I realize that Vista RTM is not
>> yet
>> generally available, but if you have access to an MSDN, Technet
>> subscription
>> Vista RTM is available for download.
>>
>> --
>> Bruce Sanderson MVP Printing
>> http://members.shaw.ca/bsanders
>>
>> It is perfectly useless to know the right answer to the wrong question.
>>
>>
>>
>> "C. Britton" <CBritton@discussions.microsoft.com> wrote in message
>> news81AF089-895A-4870-B675-B9ACE6C901C8@microsoft.com...
>> > Thanks for the reply Bruce. Actually I saw an earlier post from you
>> > recommending that method and had tried it unsuccessfully. Just to be
>> > sure
>> > nothing has changed I just tried it again and couldn't get to either
>> > the
>> > XP
>> > Pro computer or a Windows 2000 machine. I get the "Windows cannot
>> > access\\Cecilsjetone\SharedDocs" message telling me to check my
>> > spelling.
>> > The error code is 0x80070035 "The network path was not found."
>> >
>> > Thanks again for the reply.
>> > Cecil Britton
>> >
>> > "C. Britton" wrote:
>> >
>> >> I am not offering a solution. I only want to say that I have the
>> >> exact
>> >> same
>> >> problem on my system using RC-1 x64. I have taken every precaution
>> >> mentioned
>> >> in this thread and I still can't get around the problem. I even went
>> >> so
>> >> far
>> >> as to disable the firewall in my router in case it was the culprit.
>> >> That
>> >> didn't work either.
>> >>
>> >> One thing I am able to do that I didn't see mentioned here is that I
>> >> can
>> >> see
>> >> and access shared folders on the Vista machine from both the XP and
>> >> the
>> >> Windows 2000 machines on the network. In other words I have one-way
>> >> network
>> >> traffic only.
>> >>
>> >> And, no I can't see the other machines anywhere in Vista, not just in
>> >> Windows Explorer.
>> >>
>> >>
>> >>
>> >> "Bruce Sanderson" wrote:
>> >>
>> >> > Do you mean "can't see" under Network in Explorer or something else?
>> >> >
>> >> > In Start, Run, key \\othercomputername and press Enter. What
>> >> > happens?
>> >> >
>> >> > If you haven't already, try enabling NetBIOS over TCP/IP (network
>> >> > connection
>> >> > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties,
>> >> > Advanced...,
>> >> > WINS).
>> >> >
>> >> > Vista can interoperate with XP and 2003 computers that do not have
>> >> > the
>> >> > LLTD
>> >> > Responder installed. Adding the LLTD Responder
>> >> > (http://www.microsoft.com/downloads/d...displaylang=en)
>> >> > will allow XP computers to appear in the "Network Map", but is not
>> >> > required
>> >> > for "normal" interoperability.
>> >> >
>> >> > --
>> >> > Bruce Sanderson MVP Printing
>> >> > http://members.shaw.ca/bsanders
>> >> >
>> >> > It is perfectly useless to know the right answer to the wrong
>> >> > question.
>> >> >
>> >> >
>> >> >
>> >> > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
>> >> > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
>> >> > > With WinVista RC1 Build 5600 installed, I cannot see any of the
>> >> > > PCs
>> >> > > in my
>> >> > > workgroup (all WinXP or Win2K). Within Vista, I have changed the
>> >> > > name of
>> >> > > the
>> >> > > workgroup to reflect the workgroup name. I have enabled
>> >> > > discovery.
>> >> > > I
>> >> > > have
>> >> > > the network identified as a private network. I can ping all of
>> >> > > the
>> >> > > PCs on
>> >> > > the network, but Vista will not recognize them. I can get to the
>> >> > > 'net (of
>> >> > > course). Within Services, LLTD keeps stopping. I have all of the
>> >> > > dependencies for LLTD started. I have the LLTD elements enabled
>> >> > > in
>> >> > > Group
>> >> > > Policy.
>> >> > > Can anyone offer a suggestion as to why LLTD keeps stopping and
>> >> > > why I
>> >> > > cannot
>> >> > > see any other elements of my workgroup? Thanks.
>> >> >
>>
>>

"C. Britton" <CBritton@discussions.microsoft.com> wrote in message
news:3AAC3CFF-CAEA-4BE9-A7BA-6485EBA57BA0@microsoft.com...
> Thanks for the reply Brandon. Actually I have tried all the things you
> suggested without success. I can ping or send files back and forth from
> the
> XP computer and the Win 2000 computers to each other. I can do the same
> from
> those computers to the Vista machine. But, I can't see the other
> computers
> at all from the Vista computer. I've checked every setting and I have
> done a
> power reset on the network components, I have even turned off the router
> firewall and still nothing works. I'm relatively sure the problem lies in
> the new TCP/IP stack but turning off then newer facets of that haven't
> worked
> either.

Sorry I haven't read the whole thread but I ran into this problem just the
other day and in my case it turned out that I had changed the workgroup
names on my XP pcs when I set them up ages ago. With Vista, I had changed
it from the default "Workgroup" name. When I changed Vista to have the same
Workgroup name as the rest of my PCs then they all showed up.

--
Keith

I've been having a similar problem trying to connect to LAN computers (RC1).
What is peculiar here is that NETBIOS over TCPip will not turn on. I expect
that is the root of my connection problem but since it doesn't respond to
any of the switches that would enable it (under Advanced -WINS) I'm at a
loss.

Not that this is the only problem with this Vista install... , in Network
and Sharing Center neither Manage Wireless Networks or View Full Map work
at all. At some point the RUN button on the Start menu stopped working as
well.

"Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message
news:eVs6mpoNHHA.4152@TK2MSFTNGP06.phx.gbl...
> Well, hard to know what to say. Vista RTM is working fine with respect to
> interroperating over the network with Windows XP and Windows Server 2003,
> both here at home and at work.
>
> This, of course, is no guarantee it will work correctly with your
> particular hardware.
>
> What is the make and model of the network adapter in your Vista computer?
> Is there any possibility of trying a different network adapter?
>
> If Vista is detecting "problems" with your network, check that the IP
> configuration is correct for your network (e.g. using the command ipconfig
> /all). It might be that Vista RC1 is not able to get "good stuff" from
> the DHCP service (e.g. in your router) for some reason.
>
> You might want to try setting the IP configuration manually.
>
> --
> Bruce Sanderson MVP Printing
> http://members.shaw.ca/bsanders
>
> It is perfectly useless to know the right answer to the wrong question.
>
>
>
> "C. Britton" <CBritton@discussions.microsoft.com> wrote in message
> news:F317A498-B601-476A-B44B-925BFF73E728@microsoft.com...
>> Thanks Bruce, I just tried it and neither attempt worked. What is
>> strange is
>> that when the Vista machine fails to connect, it automatically asks if
>> you
>> want to diagnose the failure. I clicked yes and it said a problem was
>> found,
>> I was asked if I wanted to fix the problem and about 30 seconds later got
>> a
>> messaged that it was fixed. I immediately entered the same run command
>> and
>> didn't connect, but this time I ran the diagnosis and got the message
>> that no
>> problem was found.
>>
>> Now I ran the command using the computer name and went through the same
>> routine but the result of the diagnostic was that it found a serious
>> problem
>> and I should contact my ISP or my network Administrator. Out of
>> curiosity I
>> ran the exact same command and this time the diagnostic again said there
>> was
>> no network problem.
>>
>> From all this I would assume that the diagnostic routine is getting
>> random
>> results from its queries.
>>
>> I would love to get a copy of the RTM but unfortunately I don't subscribe
>> to
>> Technet and don't have anyone around here who does that I know of. I
>> guess I
>> will have to just wait until the 30th and take the $399 gamble on the
>> retail
>> version of Ultimate. That is going to take some soul searching because I
>> would never stop kicking myself if I spend that amount on something I
>> haven't
>> seen work correctly so far. Then again if I didn't have problems I'd be
>> bored.
>>
>> Cecil
>>
>> "Bruce Sanderson" wrote:
>>
>>> To see if the problem is a "name resolution" problem or something else,
>>> try
>>> these two things:
>>>
>>> 1. determine the IP address of the XP computer (e.g. using the command
>>> ipconfig /all)
>>> then, on the Vista computer, click Start, Run and key
>>> \\xxx.xxx.xxx.xxx (\\ followed by the IP address of the
>>> XP
>>> computer)
>>>
>>> 2. on the Vista computer, click Start, Run and key
>>> \\XPComputerName (without any share name)
>>>
>>> What happens?
>>>
>>> Is there any possibility of using a later build of Vista? There were
>>> quite
>>> a number of fixes between RC1 and RTM. I realize that Vista RTM is not
>>> yet
>>> generally available, but if you have access to an MSDN, Technet
>>> subscription
>>> Vista RTM is available for download.
>>>
>>> --
>>> Bruce Sanderson MVP Printing
>>> http://members.shaw.ca/bsanders
>>>
>>> It is perfectly useless to know the right answer to the wrong question.
>>>
>>>
>>>
>>> "C. Britton" <CBritton@discussions.microsoft.com> wrote in message
>>> news81AF089-895A-4870-B675-B9ACE6C901C8@microsoft.com...
>>> > Thanks for the reply Bruce. Actually I saw an earlier post from you
>>> > recommending that method and had tried it unsuccessfully. Just to be
>>> > sure
>>> > nothing has changed I just tried it again and couldn't get to either
>>> > the
>>> > XP
>>> > Pro computer or a Windows 2000 machine. I get the "Windows cannot
>>> > access\\Cecilsjetone\SharedDocs" message telling me to check my
>>> > spelling.
>>> > The error code is 0x80070035 "The network path was not found."
>>> >
>>> > Thanks again for the reply.
>>> > Cecil Britton
>>> >
>>> > "C. Britton" wrote:
>>> >
>>> >> I am not offering a solution. I only want to say that I have the
>>> >> exact
>>> >> same
>>> >> problem on my system using RC-1 x64. I have taken every precaution
>>> >> mentioned
>>> >> in this thread and I still can't get around the problem. I even went
>>> >> so
>>> >> far
>>> >> as to disable the firewall in my router in case it was the culprit.
>>> >> That
>>> >> didn't work either.
>>> >>
>>> >> One thing I am able to do that I didn't see mentioned here is that I
>>> >> can
>>> >> see
>>> >> and access shared folders on the Vista machine from both the XP and
>>> >> the
>>> >> Windows 2000 machines on the network. In other words I have one-way
>>> >> network
>>> >> traffic only.
>>> >>
>>> >> And, no I can't see the other machines anywhere in Vista, not just in
>>> >> Windows Explorer.
>>> >>
>>> >>
>>> >>
>>> >> "Bruce Sanderson" wrote:
>>> >>
>>> >> > Do you mean "can't see" under Network in Explorer or something
>>> >> > else?
>>> >> >
>>> >> > In Start, Run, key \\othercomputername and press Enter. What
>>> >> > happens?
>>> >> >
>>> >> > If you haven't already, try enabling NetBIOS over TCP/IP (network
>>> >> > connection
>>> >> > Properties, Internet Protocol Version 4 (TCP/IPv4), Properties,
>>> >> > Advanced...,
>>> >> > WINS).
>>> >> >
>>> >> > Vista can interoperate with XP and 2003 computers that do not have
>>> >> > the
>>> >> > LLTD
>>> >> > Responder installed. Adding the LLTD Responder
>>> >> > (http://www.microsoft.com/downloads/d...displaylang=en)
>>> >> > will allow XP computers to appear in the "Network Map", but is not
>>> >> > required
>>> >> > for "normal" interoperability.
>>> >> >
>>> >> > --
>>> >> > Bruce Sanderson MVP Printing
>>> >> > http://members.shaw.ca/bsanders
>>> >> >
>>> >> > It is perfectly useless to know the right answer to the wrong
>>> >> > question.
>>> >> >
>>> >> >
>>> >> >
>>> >> > "wrtbd" <wrtbd@discussions.microsoft.com> wrote in message
>>> >> > news:F9EABFCE-F0C7-45AD-81FF-DD42F440C6F8@microsoft.com...
>>> >> > > With WinVista RC1 Build 5600 installed, I cannot see any of the
>>> >> > > PCs
>>> >> > > in my
>>> >> > > workgroup (all WinXP or Win2K). Within Vista, I have changed the
>>> >> > > name of
>>> >> > > the
>>> >> > > workgroup to reflect the workgroup name. I have enabled
>>> >> > > discovery.
>>> >> > > I
>>> >> > > have
>>> >> > > the network identified as a private network. I can ping all of
>>> >> > > the
>>> >> > > PCs on
>>> >> > > the network, but Vista will not recognize them. I can get to the
>>> >> > > 'net (of
>>> >> > > course). Within Services, LLTD keeps stopping. I have all of
>>> >> > > the
>>> >> > > dependencies for LLTD started. I have the LLTD elements enabled
>>> >> > > in
>>> >> > > Group
>>> >> > > Policy.
>>> >> > > Can anyone offer a suggestion as to why LLTD keeps stopping and
>>> >> > > why I
>>> >> > > cannot
>>> >> > > see any other elements of my workgroup? Thanks.
>>> >> >
>>>
>>>
>