Vista - Cannot see workgroup computers

Just last night I ran into a similar problem trying to connect to my laptop
(WinXP Home) from my desktop (Vista HP).

\\laptop didn't work
\\192.168.0.183 didn't work
I couldn't ping 192.168.0.183

BUT from the laptop I could connect and ping to the desktop \\desktop (IP
192.168.0.110)

I tried changing workgroup names, I tried renewing IP's with the Router
(DHCP on). Reboots happened as a result. No luck.

What finally fixed it was changing the IP address of the laptop to
192.168.0.104. (I have reserved addresses on the router setup).
I haven't changed the laptop's reserved address back to 192.168.0.183 yet
but I will tonight. I'm curious if Vista has a problem seeing computers with
IP addresses higher than its own?


"wrtbd" wrote:

> 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.

the version that arrived yesterday Vista home Premium OEM on a Compaq
computer performs the same way.



"C. Britton" wrote:

> 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.
> > > >> >
> > >
> > >

This could be good. Where is the place to change the workgroup setting? I
have not found the option to initialize it much less change it.

"Keith Hill" wrote:

> "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 found Bruce's troubleshooting tip below more helpful than anything else I
have tried so far. But, I am wondering about the next step in getting Windows
Vista Home Premium Edition to recognize my Windows 2000 PCs over a wireless
connection.

My situation is: Bought a new HP laptop w/Vista. Have 2 other desktop PCs at
home running Windows 2k. Vista sees the router, can connect through to the
internet, can ping the other PCs by IP address, and has the same workgroup
name as the other PCs. The Windows 2k machines see the Vista laptop.

I had tried everything I could think of to connect to my other PCs and was
feeling hopeless unil the "Start, Run, \\xxx.xxx.xxx.xxx" suggestion below. I
had only tried using ComputerNames before. Hallelujah - I can connect by IP
address !

So, my question is: What do I need to do or check to get Vista to resolve
connections by NAME instead of having to rely on IP ADDRESS, which is dynamic
and can change??? Have any of you out there been able to do this
successfully???

I see a lot of posts in this newsgroup concerning this specific problem.
People are really struggling with this. Does anyone know if Microsoft is
addressing this issue??? Are there any plans on making LLTD available for
Windows 2000???

Shawn Baker

"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
>
> (remainder deleted ...)

LLTD deals with placing the computer in the Network Map, and is beside the
point for file-sharing. However, so far as I'm aware, there will not be a
W2K LLTD Responder.

If you can connect by IP, then it's clearly a name resolution issue.... You
might try connecting by name and using the Diagnose button. It should give
you more information about what types of name lookup were tried and didn't
succeed.

"Shawn Baker" <Shawn Baker@discussions.microsoft.com> a écrit dans le
message de news:64BCF7F4-A162-4684-89C0-2EAF7F257BA3@microsoft.com...
>I found Bruce's troubleshooting tip below more helpful than anything else I
> have tried so far. But, I am wondering about the next step in getting
> Windows
> Vista Home Premium Edition to recognize my Windows 2000 PCs over a
> wireless
> connection.
>
> My situation is: Bought a new HP laptop w/Vista. Have 2 other desktop PCs
> at
> home running Windows 2k. Vista sees the router, can connect through to the
> internet, can ping the other PCs by IP address, and has the same workgroup
> name as the other PCs. The Windows 2k machines see the Vista laptop.
>
> I had tried everything I could think of to connect to my other PCs and was
> feeling hopeless unil the "Start, Run, \\xxx.xxx.xxx.xxx" suggestion
> below. I
> had only tried using ComputerNames before. Hallelujah - I can connect by
> IP
> address !
>
> So, my question is: What do I need to do or check to get Vista to resolve
> connections by NAME instead of having to rely on IP ADDRESS, which is
> dynamic
> and can change??? Have any of you out there been able to do this
> successfully???
>
> I see a lot of posts in this newsgroup concerning this specific problem.
> People are really struggling with this. Does anyone know if Microsoft is
> addressing this issue??? Are there any plans on making LLTD available for
> Windows 2000???
>
> Shawn Baker
>
> "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
>>
>> (remainder deleted ...)
>

Re: LLTD, understood.

When I follow the "diagnose" path, I am basically informed that the name of
the Win2k workgroup computers are unknown to the DNS server. What's next?

(I'm curious as to why the Win2k PCs see everything just fine by name, it's
Vista that doesn't)


"Michael A. Bishop (MSFT)" wrote:

> LLTD deals with placing the computer in the Network Map, and is beside the
> point for file-sharing. However, so far as I'm aware, there will not be a
> W2K LLTD Responder.
>
> If you can connect by IP, then it's clearly a name resolution issue.... You
> might try connecting by name and using the Diagnose button. It should give
> you more information about what types of name lookup were tried and didn't
> succeed.
>
> "Shawn Baker" <Shawn Baker@discussions.microsoft.com> a écrit dans le
> message de news:64BCF7F4-A162-4684-89C0-2EAF7F257BA3@microsoft.com...
> >I found Bruce's troubleshooting tip below more helpful than anything else I
> > have tried so far. But, I am wondering about the next step in getting
> > Windows
> > Vista Home Premium Edition to recognize my Windows 2000 PCs over a
> > wireless
> > connection.
> >
> > My situation is: Bought a new HP laptop w/Vista. Have 2 other desktop PCs
> > at
> > home running Windows 2k. Vista sees the router, can connect through to the
> > internet, can ping the other PCs by IP address, and has the same workgroup
> > name as the other PCs. The Windows 2k machines see the Vista laptop.
> >
> > I had tried everything I could think of to connect to my other PCs and was
> > feeling hopeless unil the "Start, Run, \\xxx.xxx.xxx.xxx" suggestion
> > below. I
> > had only tried using ComputerNames before. Hallelujah - I can connect by
> > IP
> > address !
> >
> > So, my question is: What do I need to do or check to get Vista to resolve
> > connections by NAME instead of having to rely on IP ADDRESS, which is
> > dynamic
> > and can change??? Have any of you out there been able to do this
> > successfully???
> >
> > I see a lot of posts in this newsgroup concerning this specific problem.
> > People are really struggling with this. Does anyone know if Microsoft is
> > addressing this issue??? Are there any plans on making LLTD available for
> > Windows 2000???
> >
> > Shawn Baker
> >
> > "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
> >>
> >> (remainder deleted ...)
> >
>
>

Vista should try using LLMNR to resolve the name first; since that's a
Vista/Longhorn technology, it will fail for a downlevel machine. Following
that, it should try a NetBIOS broadcast, which is what I believe Win2K
should be using by default. When that fails, it falls back to a DNS query
for name.local-dns-suffix, which fails because your computers aren't
registered in DNS.

One possible work-around for you -- I'm assuming your router is also
proxying your DNS queries, or can. If it's not already, try it -- it should
add the machine names and DHCP addresses to its table and let machines look
each other up that way. If it is already your DNS server, adding a DNS
suffix (domain you own or something non-existent like baker.local) in your
DHCP settings might enable it to do that. It won't make them show up in NE,
but it might just enable the name resolution.

If you're picking up the router, which I assume is over UPnP, then you're
presumably set to Private network with Discovery and File Sharing enabled
(though UPnP will work with just Discovery enabled, so double-check all
that....). If none of these help, I'll get in touch with the PM for NetBT
and see if he can help us further.

"Shawn Baker" <ShawnBaker@discussions.microsoft.com> a écrit dans le message
de news:4755AB43-9A05-4D43-8A14-27821C169240@microsoft.com...
> Re: LLTD, understood.
>
> When I follow the "diagnose" path, I am basically informed that the name
> of
> the Win2k workgroup computers are unknown to the DNS server. What's next?
>
> (I'm curious as to why the Win2k PCs see everything just fine by name,
> it's
> Vista that doesn't)
>
>
> "Michael A. Bishop (MSFT)" wrote:
>
>> LLTD deals with placing the computer in the Network Map, and is beside
>> the
>> point for file-sharing. However, so far as I'm aware, there will not be
>> a
>> W2K LLTD Responder.
>>
>> If you can connect by IP, then it's clearly a name resolution issue....
>> You
>> might try connecting by name and using the Diagnose button. It should
>> give
>> you more information about what types of name lookup were tried and
>> didn't
>> succeed.
>>
>> "Shawn Baker" <Shawn Baker@discussions.microsoft.com> a écrit dans le
>> message de news:64BCF7F4-A162-4684-89C0-2EAF7F257BA3@microsoft.com...
>> >I found Bruce's troubleshooting tip below more helpful than anything
>> >else I
>> > have tried so far. But, I am wondering about the next step in getting
>> > Windows
>> > Vista Home Premium Edition to recognize my Windows 2000 PCs over a
>> > wireless
>> > connection.
>> >
>> > My situation is: Bought a new HP laptop w/Vista. Have 2 other desktop
>> > PCs
>> > at
>> > home running Windows 2k. Vista sees the router, can connect through to
>> > the
>> > internet, can ping the other PCs by IP address, and has the same
>> > workgroup
>> > name as the other PCs. The Windows 2k machines see the Vista laptop.
>> >
>> > I had tried everything I could think of to connect to my other PCs and
>> > was
>> > feeling hopeless unil the "Start, Run, \\xxx.xxx.xxx.xxx" suggestion
>> > below. I
>> > had only tried using ComputerNames before. Hallelujah - I can connect
>> > by
>> > IP
>> > address !
>> >
>> > So, my question is: What do I need to do or check to get Vista to
>> > resolve
>> > connections by NAME instead of having to rely on IP ADDRESS, which is
>> > dynamic
>> > and can change??? Have any of you out there been able to do this
>> > successfully???
>> >
>> > I see a lot of posts in this newsgroup concerning this specific
>> > problem.
>> > People are really struggling with this. Does anyone know if Microsoft
>> > is
>> > addressing this issue??? Are there any plans on making LLTD available
>> > for
>> > Windows 2000???
>> >
>> > Shawn Baker
>> >
>> > "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
>> >>
>> >> (remainder deleted ...)
>> >
>>
>>

I tried most of the suggestions on this list to no avail. This is very unfortunate as I am a PC technician and am having this kind of difficulty, I cannot imagine a standard user going through this. Please help.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

whew.. after checking both PCs and the router, I disabled each of the firewalls and blocking services and virtually left it wide open.. It suddenly worked both ways for all intended shared purposes.. I subsequently went back and enabled just the microsoft firewalls and it is still working.. I will further diagnose to find the offending party..

Thanks everyone..

Pastor Jerry
www.NewHopeQC.com


EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

I now have NetBIOS enabled over TCP/IP on the Vista PC and both Win2k PCs.
Still can't resolve by name.

I'm not sure if the router proxies DNS. It's a Linksys WRT54G. I tried
adding a local suffix to the Vista box and one Win2k box. Still couldn't
resolve.

I did use LMHOSTS and that worked. *BUT*, I don't want to use static IPs
because the Vista laptop will be used on other networks where everything is
DHCP.

This is frustrating with a capital F. Your continued help is appreciated.


"Michael A. Bishop (MSFT)" wrote:

> Vista should try using LLMNR to resolve the name first; since that's a
> Vista/Longhorn technology, it will fail for a downlevel machine. Following
> that, it should try a NetBIOS broadcast, which is what I believe Win2K
> should be using by default. When that fails, it falls back to a DNS query
> for name.local-dns-suffix, which fails because your computers aren't
> registered in DNS.
>
> One possible work-around for you -- I'm assuming your router is also
> proxying your DNS queries, or can. If it's not already, try it -- it should
> add the machine names and DHCP addresses to its table and let machines look
> each other up that way. If it is already your DNS server, adding a DNS
> suffix (domain you own or something non-existent like baker.local) in your
> DHCP settings might enable it to do that. It won't make them show up in NE,
> but it might just enable the name resolution.
>
> If you're picking up the router, which I assume is over UPnP, then you're
> presumably set to Private network with Discovery and File Sharing enabled
> (though UPnP will work with just Discovery enabled, so double-check all
> that....). If none of these help, I'll get in touch with the PM for NetBT
> and see if he can help us further.
>
> "Shawn Baker" <ShawnBaker@discussions.microsoft.com> a écrit dans le message
> de news:4755AB43-9A05-4D43-8A14-27821C169240@microsoft.com...
> > Re: LLTD, understood.
> >
> > When I follow the "diagnose" path, I am basically informed that the name
> > of
> > the Win2k workgroup computers are unknown to the DNS server. What's next?
> >
> > (I'm curious as to why the Win2k PCs see everything just fine by name,
> > it's
> > Vista that doesn't)
> >
> >
> > "Michael A. Bishop (MSFT)" wrote:
> >
> >> LLTD deals with placing the computer in the Network Map, and is beside
> >> the
> >> point for file-sharing. However, so far as I'm aware, there will not be
> >> a
> >> W2K LLTD Responder.
> >>
> >> If you can connect by IP, then it's clearly a name resolution issue....
> >> You
> >> might try connecting by name and using the Diagnose button. It should
> >> give
> >> you more information about what types of name lookup were tried and
> >> didn't
> >> succeed.
> >>
> >> "Shawn Baker" <Shawn Baker@discussions.microsoft.com> a écrit dans le
> >> message de news:64BCF7F4-A162-4684-89C0-2EAF7F257BA3@microsoft.com...
> >> >I found Bruce's troubleshooting tip below more helpful than anything
> >> >else I
> >> > have tried so far. But, I am wondering about the next step in getting
> >> > Windows
> >> > Vista Home Premium Edition to recognize my Windows 2000 PCs over a
> >> > wireless
> >> > connection.
> >> >
> >> > My situation is: Bought a new HP laptop w/Vista. Have 2 other desktop
> >> > PCs
> >> > at
> >> > home running Windows 2k. Vista sees the router, can connect through to
> >> > the
> >> > internet, can ping the other PCs by IP address, and has the same
> >> > workgroup
> >> > name as the other PCs. The Windows 2k machines see the Vista laptop.
> >> >
> >> > I had tried everything I could think of to connect to my other PCs and
> >> > was
> >> > feeling hopeless unil the "Start, Run, \\xxx.xxx.xxx.xxx" suggestion
> >> > below. I
> >> > had only tried using ComputerNames before. Hallelujah - I can connect
> >> > by
> >> > IP
> >> > address !
> >> >
> >> > So, my question is: What do I need to do or check to get Vista to
> >> > resolve
> >> > connections by NAME instead of having to rely on IP ADDRESS, which is
> >> > dynamic
> >> > and can change??? Have any of you out there been able to do this
> >> > successfully???
> >> >
> >> > I see a lot of posts in this newsgroup concerning this specific
> >> > problem.
> >> > People are really struggling with this. Does anyone know if Microsoft
> >> > is
> >> > addressing this issue??? Are there any plans on making LLTD available
> >> > for
> >> > Windows 2000???
> >> >
> >> > Shawn Baker
> >> >
> >> > "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
> >> >>
> >> >> (remainder deleted ...)
> >> >
> >>
> >>
>
>