Vista - Cannot see workgroup computers

Shawn,
Can you please switch Vista over to DHCP and reply with more information?

1. Does your HP - Vista PC have any 3rd party firewall (or integrated
Anti-Virus/Firewall) solutions like s`Windows Live One Care, Norton Internet
Security?
2. Can you please execute the following commands on Vista (from an elevated
command prompt) and Win2k and reply with output?
nbtstat -a <VISTA_PC_NAME>
nbtstat -a <WIN2K_PC1_NAME>
nbtstat -a <WIN2K_PC2_NAME>
nbtstat -n
nbtstat -r
sc query browser
ipconfig /all
3. You dont have any WinXP PC, do you?
4. Are your computers in a domain?

Thanks,
Sen.


"Shawn Baker" wrote:

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

BINGO!

When you mentioned Norton Internet Security, it dawned on me as a
possibility. I found it was indeed installed on the Vista laptop. After
dechecking the options that were blocking NetBIOS and Windows File/Print
sharing, the laptop can now "see" the other Windows 2000 PCs on the LAN. They
now appear in network area of Explorer and I am able to do file/print sharing.

Thank you so much for the help. I was ready to give up.

And to answer my original question for anyone else who may be wondering -
YES, Windows Vista is able to network nicely with Windows 2000 computers.


"Sen [MSFT]" wrote:

> Shawn,
> Can you please switch Vista over to DHCP and reply with more information?
>
> 1. Does your HP - Vista PC have any 3rd party firewall (or integrated
> Anti-Virus/Firewall) solutions like s`Windows Live One Care, Norton Internet
> Security?
> 2. Can you please execute the following commands on Vista (from an elevated
> command prompt) and Win2k and reply with output?
> nbtstat -a <VISTA_PC_NAME>
> nbtstat -a <WIN2K_PC1_NAME>
> nbtstat -a <WIN2K_PC2_NAME>
> nbtstat -n
> nbtstat -r
> sc query browser
> ipconfig /all
> 3. You dont have any WinXP PC, do you?
> 4. Are your computers in a domain?
>
> Thanks,
> Sen.
>
>
> "Shawn Baker" wrote:
>
> > 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 ...)
> > > >> >
> > > >>
> > > >>
> > >
> > >

Shawn,
Excellent! If you have any issues with Vista' file and printer sharing, you
may want to check out
http://www.microsoft.com/technet/net.../vista_fp.mspx.

Thanks,
Sen.

"Shawn Baker" wrote:

> BINGO!
>
> When you mentioned Norton Internet Security, it dawned on me as a
> possibility. I found it was indeed installed on the Vista laptop. After
> dechecking the options that were blocking NetBIOS and Windows File/Print
> sharing, the laptop can now "see" the other Windows 2000 PCs on the LAN. They
> now appear in network area of Explorer and I am able to do file/print sharing.
>
> Thank you so much for the help. I was ready to give up.
>
> And to answer my original question for anyone else who may be wondering -
> YES, Windows Vista is able to network nicely with Windows 2000 computers.
>
>
> "Sen [MSFT]" wrote:
>
> > Shawn,
> > Can you please switch Vista over to DHCP and reply with more information?
> >
> > 1. Does your HP - Vista PC have any 3rd party firewall (or integrated
> > Anti-Virus/Firewall) solutions like s`Windows Live One Care, Norton Internet
> > Security?
> > 2. Can you please execute the following commands on Vista (from an elevated
> > command prompt) and Win2k and reply with output?
> > nbtstat -a <VISTA_PC_NAME>
> > nbtstat -a <WIN2K_PC1_NAME>
> > nbtstat -a <WIN2K_PC2_NAME>
> > nbtstat -n
> > nbtstat -r
> > sc query browser
> > ipconfig /all
> > 3. You dont have any WinXP PC, do you?
> > 4. Are your computers in a domain?
> >
> > Thanks,
> > Sen.
> >
> >
> > "Shawn Baker" wrote:
> >
> > > 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 ...)
> > > > >> >
> > > > >>
> > > > >>
> > > >
> > > >

OMG Shawn: I think I may found the answer to my problem....I hope this
resloves my Printer Problem. Can you please give me more details on this??
my E-mail is fish1_49811@yahoo.com.
Please help in giving a step by step details.

"Shawn Baker" wrote:

> 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 had fits trying to get a new Vista PC to see my two Windows 2000 PCs on my
home network. It would see them if I pinged them by IP address, but not if I
pinged them by name. There were two issues.

The first is that I had to go into the TCP/IP settings on all three machines
and force them to have NetBIOS turned on.

That alone did not fix it. I was very aggravated at that point. I had
checked before to make sure that the Windows firewall product that comes with
Vista was not running at all, so didn't think it was a firewall issue. Then I
believe someone asked if I had Norton firewall running. I found that yes,
Norton firewall was installed and was configured to block NetBIOS traffic. I
changed the settings to allow NetBIOS and then the Vista PC was able to see
the other computers. They won't be displayed in Vista's network map diagram,
but they do show up in Windows explorer.

Hope this will help you out.

-- Shawn

"Ric Sterling" wrote:

> OMG Shawn: I think I may found the answer to my problem....I hope this
> resloves my Printer Problem. Can you please give me more details on this??
> my E-mail is fish1_49811@yahoo.com.
> Please help in giving a step by step details.
>
> "Shawn Baker" wrote:
>
> > 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 have the same problem. I have a Vista computer and a XP laptop. I have
exhausted all the procedures, and now I am exhausted. It was so simple when I
had an XP computer. Hopefully someone will come up with an easy-to-follow
solution.

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

Jeff,

Many thanks for your great tip. Just a few steps to install the LLTD file
from KB, the whole WLAN Workgroup was detected and things went as they
should.

George

"Jeff" wrote: