Mapp \\localhost\share does not work but \\computername\share does.

  • Thread starter Thread starter Martin Rådbo
  • Start date Start date
M

Martin Rådbo

This must be simple but I really can not get it right.

I've got a Win2k server, IP-number 10.1.1.30 and some shared directories.
Working only locally on this machine (to make it simple when discussing it
with you). It works fine to connect to \\computername\share and also
\\10.1.1.30\share and even \\127.0.0.1\share but it does not work when
trying to connect to \\localhost\share

But making a ping request to localhost works fine so the name resolution
itself seems to work. I have also tried to put a line in either 'hosts' or
'lmhosts' like:
<<10.1.1.30 test #PRE>>
but that gives the same result, it does work to ping "test" but connecting
to \\test\share is impossible.

I've also tried with a WinXP prof computer with exactly the same result.
Any idea? My real situation is that I am having two IIS servers there the
websites points to \\fileserver\share at both servers but since the files is
local on both machines I simply want to make a line in the lmhosts-file at
every server, pointing to its own IP-nr. This way I can have both
IIS-servers pointing to their local files but anyway I will be able to copy
IIS-config between the two servers without problem.

Anyone having a sollution?

Best regards
Martin Rådbo
Teknologia (Sweden)
 
Martin Rådbo said:
This must be simple but I really can not get it right.

I've got a Win2k server, IP-number 10.1.1.30 and some shared directories.
Working only locally on this machine (to make it simple when discussing it
with you). It works fine to connect to \\computername\share and also
\\10.1.1.30\share and even \\127.0.0.1\share but it does not work when
trying to connect to \\localhost\share

But making a ping request to localhost works fine so the name resolution
itself seems to work. I have also tried to put a line in either 'hosts' or
'lmhosts' like:
<<10.1.1.30 test #PRE>>
but that gives the same result, it does work to ping "test" but connecting
to \\test\share is impossible.

I've also tried with a WinXP prof computer with exactly the same result.
Any idea? My real situation is that I am having two IIS servers there the
websites points to \\fileserver\share at both servers but since the files is
local on both machines I simply want to make a line in the lmhosts-file at
every server, pointing to its own IP-nr. This way I can have both
IIS-servers pointing to their local files but anyway I will be able to copy
IIS-config between the two servers without problem.

Anyone having a sollution?

Best regards
Martin Rådbo
Teknologia (Sweden)
Click to expand...

Use this syntax:

net use s: \\%ComputerName%\share
 
You should be able to find a file called HOSTS - no extension, just HOSTS.

It should contain the following default text... if it's missing the
localhost entry add it and see if that makes a difference.

Starts below here.....

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
 
The file "hosts" does contain the mapping for localhost, i.e.
<<127.0.0.1 localhost>>

I've tried to put the name resolving thing at many different places now,
i.e.:
-dns server
-wins server
-hosts
-lmhosts

and in all cases the name resolution does work, i.e., when pinging the name
it does resolve the ip-nummer. Perfekt!!!
But, connecting to that name in any way, for example in Explorer I simply
wrote \\name it does not work.
Maybe it is a MS-stupid-limitation that the "calling name" and the
computername must be the same if it should work.

%computername% is one sollution, I will try if it works smoothly with my IIS
server to point my websites to \\%computername%\sharename

Any other ideas?

Regards
Martin
 
Sorry Guys you can't connect to the share using localhost as it is not the
NetBIOS name of the computer. Use %Computername% if you wish to use the local
machine.
 
Just to bu sure,

is it totally impossible to connect to a name which has the correct IP-nr of
the box but not the correct name. ?

I.e. the netbios-name of the PC is "homer", IP-nr 10.1.1.30 and in DNS I
have also manually put a connection between the name "bart" and 10.1.1.30.
Is it the true fact that I will never be able to mount any thing by
\\bart\share?

%computername% works when mapping drives, but not then pointing a website in
IIS 5.0 to a share. I need a solution for that.

// Martin



"Wendel Hamilton" <[email protected]> skrev i
 
Have you tried \\127.0.0.1\ShareName


Martin Rådbo said:
Just to bu sure,

is it totally impossible to connect to a name which has the correct IP-nr of
the box but not the correct name. ?

I.e. the netbios-name of the PC is "homer", IP-nr 10.1.1.30 and in DNS I
have also manually put a connection between the name "bart" and 10.1.1.30.
Is it the true fact that I will never be able to mount any thing by
\\bart\share?

%computername% works when mapping drives, but not then pointing a website in
IIS 5.0 to a share. I need a solution for that.

// Martin



"Wendel Hamilton" <[email protected]> skrev i
individual also
Click to expand...
 
Have you tried \\127.0.0.1\ShareName

Yes, it works fine. The reason why I think that \\bart\sharename is a better
solution is that in case of the need to point all websites to a fileserver
in the future, all I would have to do would be to change the settings for
CNAME-record "bart" in my dns server.

But maybe I have to realize that I can not get it all and therefor ends up
with using 127.0.0.1 anyway.

Still I think it is a stupid MS thing not to be able to user anything else
than the real Netbios name for a cumputer.

// Martin
 
Jag föreslår att du försöker ta reda på hur Microsoft
utvecklade sin implementation av NetBIOS i stället för
att kalla den "dum". Kanske finns det en tvingande
anledning att inte tilllåta något alias namn.
 
Då fortsätter jag väl på svenska då...

Jag tycker att en MS-maskin kunde svara utan att netbios-namnet var korrekt
vilket inte är samma sak som att jag tycker att den borde kunna ha flera
NETBIOS-namn.

/
 
Back
Top