the browse option in the map network drive option

[Guest]

-i have several winxp computers belonging to a windows nt domain
-most can use the map network drive's browse option to see the domain and
all the shares in it
-however, one computer's map network drive browse option shows just the icon
for the domain, and when you click on it, nothing else shows up
-then, i cannot map a network drive from this computer
-i am thinking this has something to do with the local computer, not the
fact that it is still an nt domain
-does anyone know how/why these things happen?

thank you in advance...

 

[Chuck [MVP]]

-i have several winxp computers belonging to a windows nt domain
-most can use the map network drive's browse option to see the domain and
all the shares in it
-however, one computer's map network drive browse option shows just the icon
for the domain, and when you click on it, nothing else shows up
-then, i cannot map a network drive from this computer
-i am thinking this has something to do with the local computer, not the
fact that it is still an nt domain
-does anyone know how/why these things happen?

thank you in advance...

Michael,

Is the problem computer joined to the domain, like the others? Is its name
resolution setup the same?
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html

If the problem isn't domain membership / name resolution, look at the personal
firewall issue.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

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

 

[Guest]

hello chuck,
i visited your website, and it is very informative

yes, the problem computer is joined to the domain, but the user is still
logging into the local computer instead of the domain (i do not know why, i
am trying to implement a networked application on someone else's network).

pardon me if i sound naive, but what exactly do you mean by "is the name
resolution set up the same"?

if this helps:
-this computer can ping the nt server and other computers
-this computer can browse the internet, but it cannot map network drives
-i have installed VNC on all of the computers in this network. this computer
cannot vnc to any other computer by computer name, but it can by ip.
-however, other computers can vnc to it by name

-it sounds like there a connection between these 'symptoms'?

 

[Lanwench [MVP - Exchange]]

hello chuck,
i visited your website, and it is very informative

(pardon my rudely jumping in here....)

yes, the problem computer is joined to the domain, but the user is
still logging into the local computer instead of the domain (i do not
know why, i am trying to implement a networked application on someone
else's network).

Users should not have local workstation accounts. Talk to whomever runs this
network (if someone does) about this. There will be other problems even if
you resolve the name resolution issue.

pardon me if i sound naive, but what exactly do you mean by "is the
name resolution set up the same"?

You could compare an ipconfig /all on each computer.....in a command
prompt,

ipconfig /all >c:\myipinfo.txt

.....will dump it out to a file you can read/print/post. You might also do
one from the server if you have access to it.

if this helps:
-this computer can ping the nt server and other computers
-this computer can browse the internet, but it cannot map network
drives
-i have installed VNC on all of the computers in this network. this
computer cannot vnc to any other computer by computer name, but it
can by ip. -however, other computers can vnc to it by name

-it sounds like there a connection between these 'symptoms'?

Yes, name resolution. There are two kinds - DNS, which must be configured
properly for AD to work, and NetBIOS, which you'd use when browsing Network
Neighborhood.

For DNS: all computers/servers must specify only the internal DNS server in
their IP config, no public DNS servers. The internal DNS server should be
configured with forwarders and/or use root hints to handle any non-local
name resolution. The primary (or sole) DNS suffix needs to match....e.g.,
mycompany.local. This is the most common cause of the problem you're
experiencing. If they use a DHCP server, this is easy to fix - if they use
statics, it has to be done at each computer.

For NetBIOS: If they're going to use this at all, they should use WINS, not
rely on broadcast traffic.

 

[Chuck [MVP]]

hello chuck,
i visited your website, and it is very informative

yes, the problem computer is joined to the domain, but the user is still
logging into the local computer instead of the domain (i do not know why, i
am trying to implement a networked application on someone else's network).

pardon me if i sound naive, but what exactly do you mean by "is the name
resolution set up the same"?

if this helps:
-this computer can ping the nt server and other computers
-this computer can browse the internet, but it cannot map network drives
-i have installed VNC on all of the computers in this network. this computer
cannot vnc to any other computer by computer name, but it can by ip.
-however, other computers can vnc to it by name

-it sounds like there a connection between these 'symptoms'?

Michael,

Name resolution, the ability for a computer to translate a computer name to an
address, is an important issue in most networks.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

In most small LANs, broadcast resolution is used. Broadcasts use SMBs, which is
a key element in Browsing (ability to "see" other computers), and in File
Sharing itself.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

In large LANs, you may use a local DNS server for name resolution. This
requires specific setup of each client, and of the server. This is why I asked
you to check the setup on the problem computer, and compare it to the others.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html

Your problem sounds like an SMB issue. SMBs are typically blocked by
misconfigured or overlooked personal firewalls, or other security programs.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

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