Supergeeky question ref 127.0.0.1

Sigh.

Right, I've got a Windoze 2000 domain, and a laptop user who is disconnected at home, but logged onto the domain using a cached authenticated password. They're online, but that is irrelevant, they're not directly on the 10.x.x.x network.

They're trying to map a local disk folder (C:\folder say) to another drive letter (N using the loopback address and a system share of C$.

Its not working, and they're being forced to authenticate over and over again.

The domain user that they're logged in as has full admin rights locally, and even creating a new local user with full local admin rights does not let the mapping happen using different credentials.

What've I missed?

The bottom line is that using any logon details, Start - Run - \\127.0.0.1 ALWAYS requires authentication, and never succeeds.

An attempt at \\127.0.0.1\c$ returns

"The system detected a possible attempt to compromise security, please ensure that you can contact the server that authenticated you"

--but why do I need to go back to the DC to map a 127 local IP (its specified in the HOSTS file too)?

The laptop is XP Pro SP2 with ZoneAlarm, which I've turned off for all of the above test results. Windows firewall is off.

Any idea?

Don't map it, use Subst instead

do subst /? and it should tell you what you need to know, you can then put it in their login script.

im pretty sure you cant actualy map drives to 127.0.0.1 as its a loopback address and not "real" for want of a better word

[MiniMac]

Originally Posted by wyntrblue

im pretty sure you cant actualy map drives to 127.0.0.1 as its a loopback address and not "real" for want of a better word

I thought this too, it certainly isn't the recommended way!

subst would be good, or reserve them an IP and they can use that instead of 127.

A combination of things it seems.

Subst will do the trick, yes. I'll opt for that in future.

Mapping to private 127 addresses does work, but its certainly far from reliable it seems, and can also play havoc with personal firewalls. It also isn't recommended, I'll give you that, though MS say its OK and will work....

The reason? The user has a program that resides on the laptop and on the desktop and shares configuration settings between the machines. Therefore a reference to N: on desktop = n: on laptop.

After asking said user about the desktop....."oh no, it was taken away months ago"

Give me strength.

Thanks.