Unable to access local share through UNC path when Network is disc

I have a software application that accesses data files through a shared
folder via the UNC path – for example \\computername\sharename. On some
systems where that share is on the local system, I am unable to access that
shared folder when the network is disconnected. From a DOS prompt -

C:\ dir \\mycomputer\share
(* output is correct directory listing *)

Then if I disconnect the computer from the network (and recieve the "A
network cable is unplugged" popup)

C:\ dir \\mycomputer\share

I get the message

“The network location cannot be reached. For information about network
troubleshooting, see Windows help.�

I have two XP systems sitting next to each other (both IBM laptops.) One
can access data through the UNC path when the network is disconnected and the
other can’t.

Any suggestions? Thanks!

it's normaly

if you unplug you cable, you don't have ip and your system cant talk on
netbios layer of you card.
but if you write dir \\127.0.0.1\share
you can take the good reply.

if you want to use permanetly the name of pc in dir \\compurtername\share
you need have an virtual card on you computer ( look in new hard drivers -
microsoft virtual network card) and assigne an ip.

By

"MEnglerth" wrote:

I have a software application that accesses data files through a shared
folder via the UNC path – for example \\computername\sharename. On some
systems where that share is on the local system, I am unable to access that
shared folder when the network is disconnected. From a DOS prompt -

C:\ dir \\mycomputer\share
(* output is correct directory listing *)

Then if I disconnect the computer from the network (and recieve the "A
network cable is unplugged" popup)

C:\ dir \\mycomputer\share

I get the message

“The network location cannot be reached. For information about network
troubleshooting, see Windows help.�

I have two XP systems sitting next to each other (both IBM laptops.) One
can access data through the UNC path when the network is disconnected and the
other can’t.

Any suggestions? Thanks!

Thanks Lord Mathius! Creating a virtual network adapter did the trick. For
those neophytes (like me) who are unsure how to do this, here are the steps
in Windows XP.

Step 1: Right-click on the “My Computer� icon on your desktop and select
“Properties.�

Step 2: On the System Properties Window, select the “Hardware� tab and click
the “Add Hardware Wizard� button.

Step 3: Hit the “Next� button on the initial “Add Hardware Wizard� window.

Step 4: Select “Yes� on the “Add Hardware Wizard.� Press “Next� to continue.

Step 5: In the “Installed hardware� list, scroll to the bottom and select
“Add a new hardware device.� Press “Next� to continue.

Step 6: In the “What do you want the wizard to do� section, select “Install
the hardware that I manually select from a list (Advanced).� Press “Next� to
continue.

Step 7: Select “Network Adapters� from the scroll down list. Press “Next�
to continue.

Step 8: On the Select Network Adapter screen, first select “Microsoft� as
the Manufacturer and then select “Microsoft Loopback Adapter� as the Network
Adapter. Press “Next� to continue.

Step 9: Press “Next� on the next screen to install the device.

Step 10: Press “Finish� to close the Add Hardware Wizard.

Step 11: From the “Start� button, select “Settings-Network Connections�.
Then select the last Local Area Connection (likely “Local Area Connection 2�)

Step 12: Click on the “Properties� button.

Step 13: On the “Properties� window, verify that the connection is using the
Microsoft Loopback Adapter. If there is an actual hardware adapter listed,
you have selected the wrong network connection. Go back to step 11 and
select the correct connection.

Step 14: On the “Properties� window, check the “Internet Protocol (TCP/IP)�
box and select “Properties.�

Step 15: On the TCP/IP Properties window, select “Use the following IP
address� and enter in values for the IP address, Subnet mask and Default
Gateway. The values are not important, but they must follow tcp/ip
convention. Also select “Use the following DNS server address� and type in a
value for the Preferred DNS server. Select OK to close the window.

Step 16: Click on the “Close� button to close the Local Area Connection
properties window.

Step 17: Click on the “Close� button to close the Local Area Connection
status window.
"Lord Mathius" wrote:

it's normaly

if you unplug you cable, you don't have ip and your system cant talk on
netbios layer of you card.
but if you write dir \\127.0.0.1\share
you can take the good reply.

if you want to use permanetly the name of pc in dir \\compurtername\share
you need have an virtual card on you computer ( look in new hard drivers -
microsoft virtual network card) and assigne an ip.

By

"MEnglerth" wrote:

I have a software application that accesses data files through a shared
folder via the UNC path – for example \\computername\sharename. On some
systems where that share is on the local system, I am unable to access that
shared folder when the network is disconnected. From a DOS prompt -

C:\ dir \\mycomputer\share
(* output is correct directory listing *)

Then if I disconnect the computer from the network (and recieve the "A
network cable is unplugged" popup)

C:\ dir \\mycomputer\share

I get the message

“The network location cannot be reached. For information about network
troubleshooting, see Windows help.�

I have two XP systems sitting next to each other (both IBM laptops.) One
can access data through the UNC path when the network is disconnected and the
other can’t.

Any suggestions? Thanks!

yes is good. you have think the good card

"MEnglerth" wrote:

Thanks Lord Mathius! Creating a virtual network adapter did the trick. For
those neophytes (like me) who are unsure how to do this, here are the steps
in Windows XP.

Step 1: Right-click on the “My Computer� icon on your desktop and select
“Properties.�

Step 2: On the System Properties Window, select the “Hardware� tab and click
the “Add Hardware Wizard� button.

Step 3: Hit the “Next� button on the initial “Add Hardware Wizard� window.

Step 4: Select “Yes� on the “Add Hardware Wizard.� Press “Next� to continue.

Step 5: In the “Installed hardware� list, scroll to the bottom and select
“Add a new hardware device.� Press “Next� to continue.

Step 6: In the “What do you want the wizard to do� section, select “Install
the hardware that I manually select from a list (Advanced).� Press “Next� to
continue.

Step 7: Select “Network Adapters� from the scroll down list. Press “Next�
to continue.

Step 8: On the Select Network Adapter screen, first select “Microsoft� as
the Manufacturer and then select “Microsoft Loopback Adapter� as the Network
Adapter. Press “Next� to continue.

Step 9: Press “Next� on the next screen to install the device.

Step 10: Press “Finish� to close the Add Hardware Wizard.

Step 11: From the “Start� button, select “Settings-Network Connections�.
Then select the last Local Area Connection (likely “Local Area Connection 2�)

Step 12: Click on the “Properties� button.

Step 13: On the “Properties� window, verify that the connection is using the
Microsoft Loopback Adapter. If there is an actual hardware adapter listed,
you have selected the wrong network connection. Go back to step 11 and
select the correct connection.

Step 14: On the “Properties� window, check the “Internet Protocol (TCP/IP)�
box and select “Properties.�

Step 15: On the TCP/IP Properties window, select “Use the following IP
address� and enter in values for the IP address, Subnet mask and Default
Gateway. The values are not important, but they must follow tcp/ip
convention. Also select “Use the following DNS server address� and type in a
value for the Preferred DNS server. Select OK to close the window.

Step 16: Click on the “Close� button to close the Local Area Connection
properties window.

Step 17: Click on the “Close� button to close the Local Area Connection
status window.
"Lord Mathius" wrote:

it's normaly

if you unplug you cable, you don't have ip and your system cant talk on
netbios layer of you card.
but if you write dir \\127.0.0.1\share
you can take the good reply.

if you want to use permanetly the name of pc in dir \\compurtername\share
you need have an virtual card on you computer ( look in new hard drivers -
microsoft virtual network card) and assigne an ip.

By

"MEnglerth" wrote:

I have a software application that accesses data files through a shared
folder via the UNC path – for example \\computername\sharename. On some
systems where that share is on the local system, I am unable to access that
shared folder when the network is disconnected. From a DOS prompt -

C:\ dir \\mycomputer\share
(* output is correct directory listing *)

Then if I disconnect the computer from the network (and recieve the "A
network cable is unplugged" popup)

C:\ dir \\mycomputer\share

I get the message

“The network location cannot be reached. For information about network
troubleshooting, see Windows help.�

I have two XP systems sitting next to each other (both IBM laptops.) One
can access data through the UNC path when the network is disconnected and the
other can’t.

Any suggestions? Thanks!