Vista doesn't see Windows 2000 remote server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Two offices. One (main) has a Windows 2003 server and is the exchange server
for both offices. The remote office has Windows 2000 server....entire company
is a mixed OS (mostly XP, one or two W2K, and maybe one or two NT
machines).....VPN......Two new pcs w/ Vista.....Did the following on one
Vista machine....Found an article about the Link Layer Topology Discovery
(LLTD) responder....installed that on one XP machine in the office....Before
I did this I couldn't see any other pcs on the network on the Vista pc when i
went to map a network drive. Now I can see all the pcs and main server in
main office (where I am) but cannot see the remote server. I suspect there is
something that needs to be done on the W2K server similar to what i did here
w/ LLTD.....

Anyone know?

TIA
 
I found the answer and this is unacceptable from Microsoft.......

To be able to see a Windows XP server from a Vista client, using the Vista
Network Map, you need to install (KB922120): the LLTD Responder on any
Windows XP computers. ******The LLTD Responder isn't available for Windows
2000, so you won't be able to see a Windows 2000 server from a Vista client,
using the Vista Network Map.*****
 
Richard,

Enlighten us please.......

Richard G. Harper said:
One should not be mapping drives by browsing the network. There are other
ways that do work.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


KBJM said:
I found the answer and this is unacceptable from Microsoft.......

To be able to see a Windows XP server from a Vista client, using the Vista
Network Map, you need to install (KB922120): the LLTD Responder on any
Windows XP computers. ******The LLTD Responder isn't available for Windows
2000, so you won't be able to see a Windows 2000 server from a Vista
client,
using the Vista Network Map.*****
Click to expand...
Click to expand...
 
Mapping drives should be done with Network Places preferably, otherwise with
drive letters, using known UNC paths to the resource(s) in question.
Browsing the network has always been inherently unstable since rebooting a
single PC in a workgroup can disrupt browsing for up to 15 minutes.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


KBJM said:
Richard,

Enlighten us please.......

Richard G. Harper said:
One should not be mapping drives by browsing the network. There are
other
ways that do work.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


KBJM said:
I found the answer and this is unacceptable from Microsoft.......

To be able to see a Windows XP server from a Vista client, using the
Vista
Network Map, you need to install (KB922120): the LLTD Responder on any
Windows XP computers. ******The LLTD Responder isn't available for
Windows
2000, so you won't be able to see a Windows 2000 server from a Vista
client,
using the Vista Network Map.*****

:

Two offices. One (main) has a Windows 2003 server and is the exchange
server
for both offices. The remote office has Windows 2000 server....entire
company
is a mixed OS (mostly XP, one or two W2K, and maybe one or two NT
machines).....VPN......Two new pcs w/ Vista.....Did the following on
one
Vista machine....Found an article about the Link Layer Topology
Discovery
(LLTD) responder....installed that on one XP machine in the
office....Before
I did this I couldn't see any other pcs on the network on the Vista pc
when i
went to map a network drive. Now I can see all the pcs and main server
in
main office (where I am) but cannot see the remote server. I suspect
there is
something that needs to be done on the W2K server similar to what i
did
here
w/ LLTD.....

Anyone know?

TIA
Click to expand...
Click to expand...
Click to expand...
 
Richard,

Since i'm on Vista I have no idea how that would work so i went to Network
Places on an XP machine.....and my reply is HUH?.....there is no option there
to map a network drive.....I've always mapped drives by going into Tools>Map
Network Drive and then browse the network.......Where is the ability to Map a
drive in Network Places and how is it done?

Richard G. Harper said:
Mapping drives should be done with Network Places preferably, otherwise with
drive letters, using known UNC paths to the resource(s) in question.
Browsing the network has always been inherently unstable since rebooting a
single PC in a workgroup can disrupt browsing for up to 15 minutes.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


KBJM said:
Richard,

Enlighten us please.......

Richard G. Harper said:
One should not be mapping drives by browsing the network. There are
other
ways that do work.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


I found the answer and this is unacceptable from Microsoft.......

To be able to see a Windows XP server from a Vista client, using the
Vista
Network Map, you need to install (KB922120): the LLTD Responder on any
Windows XP computers. ******The LLTD Responder isn't available for
Windows
2000, so you won't be able to see a Windows 2000 server from a Vista
client,
using the Vista Network Map.*****

:

Two offices. One (main) has a Windows 2003 server and is the exchange
server
for both offices. The remote office has Windows 2000 server....entire
company
is a mixed OS (mostly XP, one or two W2K, and maybe one or two NT
machines).....VPN......Two new pcs w/ Vista.....Did the following on
one
Vista machine....Found an article about the Link Layer Topology
Discovery
(LLTD) responder....installed that on one XP machine in the
office....Before
I did this I couldn't see any other pcs on the network on the Vista pc
when i
went to map a network drive. Now I can see all the pcs and main server
in
main office (where I am) but cannot see the remote server. I suspect
there is
something that needs to be done on the W2K server similar to what i
did
here
w/ LLTD.....

Anyone know?

TIA
Click to expand...
Click to expand...
Click to expand...
 
Add a network place and follow along.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


KBJM said:
Richard,

Since i'm on Vista I have no idea how that would work so i went to Network
Places on an XP machine.....and my reply is HUH?.....there is no option
there
to map a network drive.....I've always mapped drives by going into
Tools>Map
Network Drive and then browse the network.......Where is the ability to
Map a
drive in Network Places and how is it done?

Richard G. Harper said:
Mapping drives should be done with Network Places preferably, otherwise
with
drive letters, using known UNC paths to the resource(s) in question.
Browsing the network has always been inherently unstable since rebooting
a
single PC in a workgroup can disrupt browsing for up to 15 minutes.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


KBJM said:
Richard,

Enlighten us please.......

:

One should not be mapping drives by browsing the network. There are
other
ways that do work.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


I found the answer and this is unacceptable from Microsoft.......

To be able to see a Windows XP server from a Vista client, using the
Vista
Network Map, you need to install (KB922120): the LLTD Responder on
any
Windows XP computers. ******The LLTD Responder isn't available for
Windows
2000, so you won't be able to see a Windows 2000 server from a Vista
client,
using the Vista Network Map.*****

:

Two offices. One (main) has a Windows 2003 server and is the
exchange
server
for both offices. The remote office has Windows 2000
server....entire
company
is a mixed OS (mostly XP, one or two W2K, and maybe one or two NT
machines).....VPN......Two new pcs w/ Vista.....Did the following
on
one
Vista machine....Found an article about the Link Layer Topology
Discovery
(LLTD) responder....installed that on one XP machine in the
office....Before
I did this I couldn't see any other pcs on the network on the Vista
pc
when i
went to map a network drive. Now I can see all the pcs and main
server
in
main office (where I am) but cannot see the remote server. I
suspect
there is
something that needs to be done on the W2K server similar to what i
did
here
w/ LLTD.....

Anyone know?

TIA
Click to expand...
Click to expand...
Click to expand...
 
Back
Top