SP2 and network mappings

[gunny]

In Windows XP SP1a I was able to map a local share to a
drive letter. This enabled me to keep entire CD's on the
hard drive. This was especially useful in burning CD's
that needed root level files and wouldn't appear nested.

Example: c:\cd1 is a directory containing all
files I would burn to a CD. I share it as cd1.
My machine name is host1 and gets a DHCP address.
I map as \\host1\cd1 to z:. I write all of z: to the
CD/DVD.
It is real handy for setting virtual drives of the c:
drive.

Now in XP SP2 I can do it only while attached to a network.
If I disconnect from a network (no wireless cards,
disconnect ethernet cables) and try it I get an error
message.
"Error Msg: The mapped network address could not be
created because the following error has occured. The
network location could not be reached. "
I have tried using c:\windows\system32\drivers\etc\hosts
and mapping 127.0.0.1 to any name but still the same error.
Each mapping will ping OK (i.e. host2 ... 127.0.0.1 -
ping host2 returns active pings)
I have disabled the firewall completely but that doesn't
do it.
Has anyone come across this or any work arounds?

 

[Hans-Georg Michna]

In Windows XP SP1a I was able to map a local share to a
drive letter. This enabled me to keep entire CD's on the
hard drive. This was especially useful in burning CD's
that needed root level files and wouldn't appear nested.

Example: c:\cd1 is a directory containing all
files I would burn to a CD. I share it as cd1.
My machine name is host1 and gets a DHCP address.
I map as \\host1\cd1 to z:. I write all of z: to the
CD/DVD.
It is real handy for setting virtual drives of the c:
drive.

Gunny,

try this command instead:

subst z: c:\cd1

Hans-Georg

 

[gunny]

There has to be a reason why it doesn't work.
Any ideas?

 

[Hans-Georg Michna]

There has to be a reason why it doesn't work.
Any ideas?

Gunny,

no clue. But there are similar things when you detach the
Ethernet cable. Then the stack also doesn't work, and that was a
problem before Service Pack 2. Microsoft says it's by design.

Usually one is happy when a workaround can be found. Even if
Microsoft acknowledged that it is a defect and will be repaired,
which they never do, can you wait an indefinite time?

Perhaps there is a better workaround, but I don't know it.

Hans-Georg