This link is in the last article link above: http://support.microsoft.c
-rich
Main Topics
Browse All TopicsI'm curious why I sometimes find that I can access a remote share only with the IP address.
Does anyone know why?
What follows is a description of the events.
Step 1: Try to "login" to a remote computer.
net use \\SOMEHOST\IPC$ /user:DOMAIN\USER
Observe the error
System error 53 has occurred.
The network path was not found.
Step 2: Try to "login" to the remote computer using the IP address
First I ping SOMEHOST, to get it's IP address, then I run the command:
net use \\IPADDRESS\IPC$ /user:DOMAIN\USER
I'm prompted to enter the password, and then I'm logged in. After this I
can map remote drives as I would expect to be able to do so.
So... What is the configuration that prevents the hostname from being used?
But allows the IP address to be used?
How can I dis-allow both?
How can I allow both? NOTE: I guess I know how to do this, it happens by default.
NOTE: I'm looking for what security policys are set to allow/disallow this behavior
and how security policies can be set (what tool is used).
I'd also like to confirm that Win2000 Active Directory Security Policy are downloaded
to domain clients (Win2000 pro clients that are in the domain).
Also, Is it possible to configure this on a host by host basis?
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
This link is in the last article link above: http://support.microsoft.c
-rich
Rich,
Thanks a bunch. I was surprised to find that my DNS server was mis-configured and reporting the wrong IP address for the host that I could not login to (aka map to). Once I fixed the DNS entry the problem went away. I was able to "net use HOSTNAME" and "net use IPADDRESS" (both worked).
Also the link on connecting to an alias (http://support.microsoft.
I experienced this very same problem and was banging my head against the wall for three days. I could not map a drive to any of the networked computers at my home network. I would get "System error 53" and "Network path not found".
I finally found what was wrong. Somehow I had disabled the lanmanworkstation dll using the sysinternal autoruns utility. I had unchecked the autorun entry the Network Providers tab which disabled a registry entry under HKLM\SYSTEM\CurrentControl
Just to add clarity, although repeating what I just wrote, here's how how my registry reads:
Registry location: HKLM\SYSTEM\CurrentControl
Name | Type | Data
ProviderOrder | REG_SZ | RDPNP,WebClient,PGPpwflt,L
Business Accounts
Answer for Membership
by: richrumblePosted on 2005-01-12 at 08:07:04ID: 13025124
Typically it's a wins/dns issue om/kb/1375 65/EN-US/ /TIP3500/r h3533.htm om/default .aspx?scid =kb;en- us; 192466
http://support.microsoft.c
http://www.jsiinc.com/SUBH
And if this is happening on a server that is using 2 or more nics for load balancing, then you'll need to try to map the the VIP not the ip of a nic (you'll need to DNS the vip also)
http://support.microsoft.c
-rich