Can't use "net use"

[CaptainLunatic]

I'm trying to mount a remote folder (on a WHS machine) as a drive in a windows 7 machine. Both computers are in the same homegroup and I can access the remote folders via the file browser.

So, I open up a DOS prompt and enter net use as normal:

C:\>net use x: \\WHS_Server
System error 53 has occurred.


The network path was not found.

Doesn't work. (It gives the same error if I use the IP)

I ping it to make sure the two computers and 'see' each other.
C:\>ping -a WHS_Server

Pinging WHS_Server [192.168.1.104] with 32 bytes of data:
Reply from [URL="http://192.168.1.104/"]192.168.1.104[/URL]: bytes=32 time<1ms TTL=128
Reply from [URL="http://192.168.1.104/"]192.168.1.104[/URL]: bytes=32 time<1ms TTL=128
Reply from [URL="http://192.168.1.104/"]192.168.1.104[/URL]: bytes=32 time<1ms TTL=128
Reply from [URL="http://192.168.1.104/"]192.168.1.104[/URL]: bytes=32 time<1ms TTL=128


Ping statistics for [URL="http://192.168.1.104/"]192.168.1.104[/URL]:
     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Seems all good.

Now I have exhausted my windows networking skills.

Any suggestions?

TIA

 

[Tepid]

Try

C:\>net use x: \\WHS_Server\temp

just to see if it works.

I have seen this problem before. It can usually mean you don't have proper rights. Can you access it by bringing up explorer and try getting to it direct from the address bar? If not, then you may have a rights issue.

If this is a Windows Home Server, is your PC a member of the Domain?
Is your user a Domain user?

I am not familiar with Windows Home Server so not sure exactly how it is setup by default.

 

[chev65]

You do realize that the only version of Windows server that is made to function properly with Homegroups is the new one code named VAIL. None of the other Windows servers are made to work with Homegroups, you would need to set up a standard Workgroup type network for that. You can try it but it may not work exactly perfect.

If you plan on sharing an entire drive or a folder as a drive you may need to go into the security settings to allow for drive shares to work properly. I'm not too sure exactly what you are trying to do but this might help. It's much safer from a security standpoint to share a folder rather than an entire drive.

To share the entire drive:
Open My Computer -> right click Local Disk D or which ever drive letter your drive is using -> select Properties -> select Security tab -> click Edit button -> click Add button -> enter the name of the User you want to set Security permissions (it is the same user name you've set the sharing permissions for, ex. Everyone will set the read permissions to every user. Put check marks in the boxes for full access and control -> click OK hit apply-> select the desired permissions -> click OK -> wait while permissions are set -> and your Done.

You will also need to use the Advanced sharing tab Sharing>Advanced put a check in the box to share the drive, then click on the permissions tab and "add Everyone" then use the check boxes to allow Everyone full access. Hit the apply button on both windows.

 

[CaptainLunatic]

Try
C:\>net use x: \\WHS_Server\temp

Tried and got the same system error 53.

Can you access it by bringing up explorer and try getting to it direct from the address bar?

Yes, typing \\WHS_Server\ in the address bar takes me to the shared folders after entering my username/password. In the guided setup for the WHS it asked for the username on the win7 machine (rather than add a user from scratch) so i think that should be all link up correctly.

You do realize that the only version of Windows server that is made to function properly with Homegroups is the new one code named VAIL.

Sorry, I misspoke in my OP. The computers ARE set up in a workgroup, not a homegroup. Also, the folders seemed to be shared okay, since I can access them via explorer.

thanks again...

 

[Tepid]

Can you map a drive through the GUI? (ie. Map Network Drive)

Again, I have seen this before, all attempts to mapping drives fails.
Even if you can access it through Explorer.

Try a different drive letter?

Shutdown all PC's including server...
Let them sit for about 5 min
Turn the server on and let it sit for about 20 min
Then turn on one PC and try mapping the drive. May have to let that system sit logged in for a period of time (20 min or so) and then try again. If this is a Master Browser issue, this might resolve it. Seems odd to me in this environment, but I don't discount anything.

Chev65:
Could this be a Master Browser issue? just a thought

 

[Tepid]

I am doing some experimenting in Virtual Machines with WHS and 7.
I am having some issues myself, but this is with Virtual Machines not talking to each other. When I get this figured out I will see if I can tell you what else to try.

Have you installed Power Pack 3 yet?

 

[CaptainLunatic]

Tepid, per your post, I revisited mapping through the GUI. I had started there, but went to net use, because win7 would not remember my credentials despite checking the 'remember my credentials' box.

In playing with it again, I found that immediately after mapping the drive, credentials would show up in the credentials manager, but upon reboot the credential manager would be empty. Therefore the drives would appear broken and you'd have to pass them credentials again.

I deleted the mapped drives, entered my credentials in the credentials manager, and then remapped the drives. I rebooted and it worked. So, it seems that if you put the credentials in the manager directly (instead of allowing windows to automate the process) it seems to remember them. Now I can access remote folders via the cmd console, which was my aim.

I'm still baffled as two why 'net use' can't seem to see any other computers, but at least I have a way around it. FYI, I do have power pack 3 installed and the I tried the reboot sequence you mentioned to no avail.

 

[Barman58]

Just a silly thought

have you tried running the net use command in an elevated command prompt?

 

[CaptainLunatic]

Barman, just tried it and I get the same system error 53.

Thanks tho.

Also, I got a hold of another win 7 machine and hooked it up and i get the same 'net use' problem.

Another FYI, I happened to just input 'net use' and it sees the mapped drives I create through the GUI.

 

[Barman58]

I just tried it on this machine (no net) and I also got the "new connections will be remembered" prompt - do you also get this?

If not we may be onto something

 

[CaptainLunatic]

I get that as well. Here's the output:

C:\>net use
New connections will be remembered.


Status       Local     Remote                    Network

-------------------------------------------------------------------------------
OK           Y:        \\WHS_Server\Music      Microsoft Windows Network
OK           Z:        \\WHS_Server\Photos     Microsoft Windows Network
The command completed successfully.

 

[Tepid]

Ok,, I setup Windows Home Server in a Windows VirtualPC and also installed a Win7 x86 Win VirtualPC
They are talking to each other and I had no problems mapping drives.

What I can say is that Windows Home Server is actually pretty damn sweet.
Very easy to configure and setup (sort of). There are some things you need to know.

1.) Once the Server is setup and completely updated with all Power Packs ( the latest is Power Pack 3)
2.) Login to a Win7 (or other) system and open IE, type in http://whs:55000 and hit enter
3.) Install the Windows Home Server Connector Software and follow all instructions and let it do it's thing
4.) On the WHS system go into Windows Home Server Console
5.) Go into User Accounts and create a New User, this should be the same as the user you are using to login to your Win7 (or other) system. Same UserID and Password
6.) Go back to the Win7 (or other) system and you should be able to map drives as needed.

Form the Win7 (or other) system.....
However,,, you Can Not Map A Drive Direct to the root server ( ie. net use x: \\yourservername ) it must be a shared folder such as "net use x: \\yourservername\music"

On a First Time Use,, From Win7 (or Other) system....
When you type in the address field of either Explorer or IE \\yourservername it should take you direct to IE and open http://whs:55000 automatically, where you can install the Connector Software.
This will also happen if you go into Explorer / Network Other Devices \\yourservername for the first time.
It will give a page where at the bottom is a link to http://whs:55000.

Once you have configured things properly. Everything should work without issue, well,, should is a big word I know.

So, what is exactly going on with OP?

2 things I think at least....

1.) You Do Not want to share the Root of your server.
Create Shared Drives as needed under the Data Drive ( D: ) that is automatically created on install.
This is the proper method of setting up shared folders.
And actually all shared folders should be created under D:\shares
You will need to then Right Click that new folder and click on Sharing
Click Share this folder
Click Permissions
Remove Everyone group and add Administrators Group and any users you want to have access
Then assign as you would like

But, it is actually easier just to add folder shares through the Windows Home Server Console

This will populate the Shared Folders when you do access \\yourservername (ie. \\wsh_server) from Explorer or IE automatically. The only thing you can do is Create a Shortcut on your Desktop to \\yourservername. This is by design I do believe.

2.) Rights may not be setup properly if you are not able to map or access any shares that are already created.. (ie. \\yourservername\music)

Beyond this, I am not sure what the issue is.

Now that I have played around with it, WHS is a stripped down version of Windows Server 2003 that auto configures itself. The other features such as Backup and Remote Access that allows you to access all your systems on your network via IIS setup and a Domain name created and (appears to be) assigned to a LiveID account. Kinda nice if it works well and is secure. This can be achieved with a regular Windows Server setup, but can be more difficult in configuring manually, and way more expensive.

All in All..... Windows Home Server is (as long as it is secure and does work well) a very nice addition to any home network.

More study and testing on my part needs to be done before I would endorse it completely.

Edit:

I have mapped drives from command line and through the GUI and they are staying active regardless of how many times I reboot. So, I have no idea what is going on with your system. other than maybe network issues of systems dropping? just guessing.

 

[WindowsStar]

I'm trying to mount a remote folder (on a WHS machine) as a drive in a windows 7 machine. Both computers are in the same homegroup and I can access the remote folders via the file browser.

So, I open up a DOS prompt and enter net use as normal:

C:\>net use x: \\WHS_Server
System error 53 has occurred.
 
 
The network path was not found.

Doesn't work. (It gives the same error if I use the IP)

I ping it to make sure the two computers and 'see' each other.
C:\>ping -a WHS_Server

Pinging WHS_Server [192.168.1.104] with 32 bytes of data:
Reply from [URL="http://192.168.1.104/"]192.168.1.104[/URL]: bytes=32 time<1ms TTL=128
Reply from [URL="http://192.168.1.104/"]192.168.1.104[/URL]: bytes=32 time<1ms TTL=128
Reply from [URL="http://192.168.1.104/"]192.168.1.104[/URL]: bytes=32 time<1ms TTL=128
Reply from [URL="http://192.168.1.104/"]192.168.1.104[/URL]: bytes=32 time<1ms TTL=128
 
 
Ping statistics for [URL="http://192.168.1.104/"]192.168.1.104[/URL]:
     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Seems all good.

Now I have exhausted my windows networking skills.

Any suggestions?

TIA

Looks like you forgot the share name: (replace ShareName with your share name)

That should be:

net use x: [URL="file://\\WS_Server\ShareName"]\\WS_Server\ShareName[/URL]

Try this:

net use x: [URL="file://\\192.168.1.104\ShareName"]\\192.168.1.104\ShareName[/URL][URL="file://\\WS_Server\ShareName"][U][COLOR=#0066cc][/COLOR][/U][/URL]

Does it work with the IP?

Does this work:

explorer [U][COLOR=#0066cc][URL="file://\\WS_Server\Sharename"]\\WS_Server\Sharename[/URL][/COLOR][/U]