Vista does NOT allow drive mapping with computer name? PLEASE HELP

Previously, I can map a network drive in Windows XP such as this:

COMPUTER 1: ABC
COMPUTER 2: XYZ

XYZ have folder "Download" shared, so in ABC I just type \\XYZ\Download

But with Vista, I can NOT do that. I have to type the IP address such as \\192.168.0.5\Download.

Problem is, many of my application, such as Acronis TrueImage can ONLY connect to the mapped drive using NAME, not IP.

Can anyone help?

 

Right click on the network icon in the task bar and choose Network and Sharing Center. Make sure that Network Discovery and File Sharing are turned on

 

I know Vista allows it. I do it myself. My only advice is like the above poster, make sure that file sharing is on. Have you disabled any services recently? One of them might be necessary.

 

If you did all of the tweaks, you might have disabled some of the networking features in Vista. Other than that, everyone else here seems to have said everything I can think of.

Greg

 

By Default the service for Mapping is disabled on most computers (i had same problem)... Type services.msc ..check if the Mapping service is set to Automatic & Started.


Enable Link-Layer Topology Discovery Mapper

 

and once again, we have a misleading thread title where the Poster, in his ignorance, blames something on Vista when in fact, it is the user who is in error.

 

Not sure where to to start with this, but--

Notebookyoozer,

I'm sorry, but where exactly is the user error? He cannot do something that he ought to be able to do. He is simply saying his copy of VISTA is not permitting him to map with Netbios names. What possible help is it when you wander in and make assumptions like you are.

Something is not correct with his system. If you cannot help, move on.

Nocturnal,

I don't think Mapping services....or rather as you point out, Link Layer Topology Discovery Mapper, has anything to do with what the user is experiencing. First, I am pretty sure it is not disabled by default, it is manual by default--meaning a service that needs it can start it (no user intervention required). Second, Link Layer Topology Discovery doesn't involve mapping drives, it involves mapping networks.

It is the service that creates the Network Map available through Network Sharing center...it creates a visual representation of the network for Vista and other LLTP aware devices (which is why XP does not show up in the map, but is listed in devices that cannot be placed--XP lacks LLTP awareness.)

I have two possible thoughts on the problem, given the information presented...

when you set up the network, was it set up as a public or private network? Go to Network and Sharing Center and click on CUSTOMIZE, check the location type on BOTH machines---private or public--if public, make it private.

Also, under network connection details, is netbios over tcpip enabled?

 

I didn turn network sharing, but what I found out is that SOMETIMES it work sometimes it doesn't. When it doesn't work, I have to use IP instead of computer name.

I haven't tried it with a fresh install of Vista yet, but I so far I didn't install anything other than Spy Sweeper, ThreatFire, and AVG Anti-Virus. I did try disabling it.

For the past 2 days, it seems working fine mapping with network name, so I'll monitor again.

Err, what exactly did I do wrong?

 

Under network connection, it is set as DEFAULT, where it says:
Use NetBIOS setting from DHCP server. I use STATIC DHCP server from my router, where based on the MAC address of my laptops the Router DHCP server will give the same IP all the time but dynamically.

The machine is setup as PUBLIC under Network and Sharing Center. But even with Public, I can SOMETIMES map it using network name.

Oh one thing: both laptops have different network name, but I setup the same Admin username and password and the same WORKGROUP. When I map the drive, I don't have to enter username and password. Not sure if this have any bearing.

 

webroot does have a firewall on it--are you using it, or default Windows firewall?

 

I have the standard Spy Sweeper without the built-in firewall. I don't use any other firewall, built-in or 3rd party.

 

I'd change it to PRIVATE and see if the issue goes away....not sure why it is working with PUBLIC sometimes.

 

Awesome! I'll try this when I am back at work.

I wish my Vista Home Premium allows RDP connection TO the machine, just like my XP Professional so I can try this solution...