[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Mapped Network Drive 127.0.0.1 issue

Posted on 2011-03-15
16
Medium Priority
?
1,296 Views
Last Modified: 2012-08-13
I have mapped a number of drives locally to mimick the drives at work.
I have mapped the drive to \\127.0.0.1\<shared Folder>.

Recently these drives can't be found. I can ping 127.0.0.1 and get a reply. The folders share options haven't changed and i set a network drive via \\<ComputerName>\<shared Folder.

When i ping the computer name i get a MAC address, rather than an IP Address.

Not sure what is happening, but now my machine is slow to start up.
0
Comment
Question by:GegH
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
  • 3
  • +1
16 Comments
 
LVL 6

Expert Comment

by:Kody-Burg
ID: 35143439
Try turning off IPv6 and so that you can only get an IPv4 IP address. I have seen this issue when a machine only gets an IPv6 address, but not an IPv4 address.

Here is a link to instructions on how to do this:

http://windows7themes.net/disable-ipv6-windows-7.html

Regards,

Kody
0
 
LVL 5

Expert Comment

by:xylog
ID: 35143445
Check your hosts file. Are you sure you are getting your mac address and not an IPv6 address?
0
 
LVL 6

Expert Comment

by:Kody-Burg
ID: 35143516
@xylog:

That was the point of my post. I figured that it might be an IPv6 address, and since IPv6 is useless for most people, I just recommended that it be disabled.
0
Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

 
LVL 5

Expert Comment

by:xylog
ID: 35143769
Look at the times on our posts...
0
 
LVL 6

Expert Comment

by:Kody-Burg
ID: 35144155
Gotta love simultaneous posts! :)
0
 

Author Comment

by:GegH
ID: 35144494
Thankyou guys, this worked to a point.
When i now ping my machine name i get the IP address on my home network, i.e. 192.168.XX.XX.
I can still ping 127.0.0.1

So when i create a network drive to \\<Computer Name>\Folder, it is actually going off to the network and mapping a drive, rather than looping through my network card, this i believe is what is slowing the start up.

I am working on a laptop so if i leave my network i will not get my drives, hence the need for it to loop through 127.0.0.1

Any ideas why it is no longer able to loop through my network card?
0
 
LVL 30

Expert Comment

by:IanTh
ID: 35146205
what happens if you ping localhost
0
 

Author Comment

by:GegH
ID: 35146255
I get a reply from 127.0.0.1
0
 
LVL 30

Expert Comment

by:IanTh
ID: 35146379
so what error do you get on the mapped drive if localhost and 127.0.0.1 are the same

Local host in ipv6 is not 127.0.0.1 its ::1 so if your machine was uing ipv6 pinging localhost would give you that ::1
0
 

Author Comment

by:GegH
ID: 35146428
I stopped IPv6 as per the above instructions.
Before i stopped IPv6 and since i get the same error essentially.
Before it was 'Network path not found'
Now it is Windows cannot access \\127.0.0.1\<Folder Name>. the details are Error Code 0x80070035, The network path was not found.
0
 
LVL 5

Expert Comment

by:xylog
ID: 35147783
Try:

net view \\127.0.01

Does it list shares?

You can edit your hosts and lmhosts file so that your computername resolves to 127.0.0.1. Edit c:\windows\system32\drivers\etc\hosts and c:\windows\system32\drivers\etc\lmhosts (create one it if does not exist) by adding this line:

127.0.0.1     computername

That should force your computername to resolve to 127.0.0.1 both from ping (via hosts) and smb/cifs shares access (lmhosts).

0
 

Author Comment

by:GegH
ID: 35151810
Still no luck.
Ping -a 127.0.0.1 returns the name of the computer now, but i still can't connect a network drive to the 127.0.0.1 address, pinging the computer name still returns the IP address 192.xxx.xxx.xxx.

I also tried \\127.0.0.1\folder name through a web browser and it can't find the network address, \\localhost\<folder name> doesn't work either
0
 
LVL 5

Expert Comment

by:xylog
ID: 35152162
What does the net view command return? Does it display the names of the shares?
0
 

Author Comment

by:GegH
ID: 35154194
Net view \\127.0.0.1 returns:
System error 53 has occurred
Network path was not found
0
 
LVL 30

Accepted Solution

by:
IanTh earned 2000 total points
ID: 35155387
0
 

Author Closing Comment

by:GegH
ID: 35161102
Cheers. I'm away from my home network at the moment, using my mobile as a modem. With this i am on a public network and changed the network discovery to on. It works.
I will try the same when i am at home and make sure it is a prvate network with Network discovery on, Which it should be, i didn't change it.
The firewall could be the other setting to check when at home, but i think we've got to the bottom of it thanks to your directions, i was more worried that the card was stuffed, which i guess its not.
0

Featured Post

Survive A High-Traffic Event with Percona

Your application or website rely on your database to deliver information about products and services to your customers. You can’t afford to have your database lose performance, lose availability or become unresponsive – even for just a few minutes.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you try to extract and to view the contents of a Microsoft Update Standalone Package (MSU) for Windows Vista, you cannot extract the files from the MSU. Here we are going to explain how to extract those hotfix details without using any third pa…
This program is used to assist in finding and resolving common problems with wireless connections.
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question