New Windows 7 PC not connecting to mapped drives

Hi guys,

We've just stepped in as the IT provider for a small business with about 35 seats. Given a lot of them have XP or Vista systems, we are slowly working through upgrading them all (particularly XP machines due to the whole April 2014 support drop-off from Microsoft.

Rolling out our first PC yesterday, we hit a snag. All was going brilliantly until we attempted to map the network drives, but we couldn't connect. Annoyingly, if I right-click on the drive mapping on the XP laptop we're replacing, there is no edit option into which I can go to see what credentials are being used to connect. Is there another place I can go to do this?

There 'server' setup is a little different, but I don't think it's causing any problems. To explain, they have a super-grunty Windows 7 Ultimate box running VirtualBox. Around a dozen users access the server, but only into the VirtualBox (which is also Windows 7, though I think it's Professional from memory).

I have confirmed that it's a DHCP network as the old laptop was getting it's IP from the router, so there doesn't seem to be anything funky going on where I can't connect because my PC can't connect to the network (and, besides, I can access the internet with ease).

When I open Windows Explorer on the client PC and navigate to 'Network' in the left column, I can see the PC I'm wanting to map to.

When trying to map to that location on the server (which is shared as I can connect to it immediately on the old machine), I use the 'Server's' admin username and password after ticking the box to connect with different credentials, but it makes no difference.

If needed, and I suspect it will be, I can reply to this thread with the exact error message.

Help me Experts-Exchange - you're my only hope... ;)

Servant-Leggie
Servant-LeggieAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

becraigCommented:
gwmi -Query 'Select LocalName, RemoteName, UserName from Win32_NetworkConnection'

This will give you the mapped  drive, remote path and username used.
0
Servant-LeggieAuthor Commented:
Sorry becraig, I'm unfamiliar with your suggestion. Do I need to conduct a gwmi query (which I've never encourntered before) and, if so, how and where?
0
becraigCommented:
simply load a powershell window on the machines in question and run the command provided (provided powershell is installed)
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Servant-LeggieAuthor Commented:
becraig, is powershell usually installed by default on a Windows 7 Pro SP1 installation? If not, I presume I can simply grab from the Microsoft site (of course, Google can direct me!)
0
Servant-LeggieAuthor Commented:
Thanks becraig. I found it too. I typed the full command you gave but it didn't seem to work. Can you confirm I need to type the followiing, as-is:

gwmi -Query 'Select LocalName, RemoteName, UserName from Win32_NetworkConnection'
0
becraigCommented:
This must be run from the computer with the mapped drive.
0
Servant-LeggieAuthor Commented:
Thanks becraig. But to confirm, is that the exact entry I should be making or should I be substituting some of the values you mentioned above?
0
becraigCommented:
no need to substitute you can also just run

gwmi Win32_NetworkConnection
0
Servant-LeggieAuthor Commented:
becraig, tried gwmi -Query 'Select LocalName, RemoteName, UserName from Win32_NetworkConnection' and was able to bring up details (by the way, it is on a Vista laptop, not Windows 7). Was able to see that it was using the local PC credentials, so used the new computer's local PC credentials (admin user) which naturally are different than that of the old PC.

Realised I hadn't set up a password on the new PC, so did so (10 character password).

Reattempted to connect, but still no joy. Getting the error message:

'Windows cannot access \\rest-svr-lcl\rest-db

check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.'

Clicking 'details' shows:

'Error code 0x80070035
The network path was not found.'

What is this new PC doing? I'm am going to grab my own laptop to see if it can connect, just in case it's a network issue with the new PC.

Thoughts?
0
Servant-LeggieAuthor Commented:
To confirm, I was just able to create the same share on the old Vista laptop and it went through straight away, as I'd expect.

My only thought- while I know domain servers may be set to block/ allow certain PCs to access the network and create shares, I understand that this can only be done in a domain setup (not PCs set up on the same Workgroup as these are).

However, is there a program which can be used to do this same allowing/ blocking on a non-domain network? Just a thought- I feel like I'm running out of them.
0
becraigCommented:
Try the following:
Enable NetBIOS over TCP/IP:

 

1.    Go to “Control Panel\Network and Internet\Network Connections”.

2.    Right-Click on the connection and choose Properties.

3.    Click “Internet Protocol (TCP/IP) Version 4” in the list.

4.    Click Properties, and then click Advanced.

5.    On the Advanced TCP/IP settings windows, go to “WINS” tab.

6.    Under NetBIOS setting, click “Enable NetBIOS over TCP/IP”, and then click OK.

Also look at the dns suffix on the network tab of the vista machine that is working, also the dns settings.

It might just be a matter of resolving the short name
0
Servant-LeggieAuthor Commented:
becraig, I've run through all 6 steps and there's no change on the Windows 7 PC.

When you say "...dns suffix on the network tab...", do you mean on the DNS tab in the Advanced TCP/IP Settings window (as accessed in step 4 above, but clicking DNS in step 5 rather than WINS)? If so, there is nothing recorded in either text box and the 'Append Primary...' bullet is selected with its subordinate 'Append Parent Suffixes...' check box also ticked.

Since my last post, I also jumped onto the server to make sure that sharing or security was set on the server to only allow access to certain IP addresses/ PCs. It all looked fine as the applicable network shares were set up to be shared with 'Everyone'.
0
becraigCommented:
Can you try pinging the server the share is on and navigating to the ip address:

e.g

\\10.10.124.6

See if that comes up for you.
0
Servant-LeggieAuthor Commented:
Thanks becraig, the drive can be navigated to that way. An ipconfig /flushdns should do it, yes?!
0
becraigCommented:
Yes that should do it unless there is a static dns mapping or some other reason you are unable to resolve the short name.
0
Servant-LeggieAuthor Commented:
The ipconfig /flushdns did nothing, I'm sad to say.

Never dealt with a static DNS mapping before... how can I tell if this is what's going on and what do I need to do about it (either as a fix or setting up the new PC so it works 'properly' on the network)?
0
becraigCommented:
You should take a look at the troubleshooting steps below.
http://support.microsoft.com/kb/903267/en-us


If that does not help try the one below.
http://superuser.com/questions/262262/problem-with-network-shares
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Servant-LeggieAuthor Commented:
becraig, apologies for the delay- will look at those links shortly.

Here's something interesting... I came in a day later after having got all connected via an IP address and it was having trouble connection. Found the new address (I thought it was static, but clearly not(!!!)) and, before mapping to that address, tried \\<servername>\<folder> and, wouldn't you know, it worked. In fact, it's been working for days now.

What on earth would be causing that (if the answer may present itself when I look at the links you posted, just direct me back there)?
0
becraigCommented:
This happens sometimes when a computer has difficulty resolving the netbios name.

The name may have simply been resolved once the ip connection was made and the cache updated

This article below will explain a lot about how netbios works:

http://www.techrepublic.com/article/how-netbios-name-resolution-really-works/
0
Servant-LeggieAuthor Commented:
Thanks for all your help, becraig - looks like we were able to resolve this one!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.