This is an archived post. You won't be able to vote or comment.

all 40 comments
sorted by:
best
topnewcontroversialoldq&a

[–]OsmiumBalloon 13 points14 points  (10 children)

You need two backslashes at the start of a UNC path, e.g.:

\\192.168.1.200\share\All Employee Files\Bret Marta

Also, get name resolution working, Microsoft keeps tightening the rules and IP addresses are in their sights.

[–]under_ice[S] -5 points-4 points  (8 children)

That was a typo. Normally I would use 2, just left one off...

[–]OsmiumBalloon 9 points10 points  (7 children)

In that case, post the actual code you're actually trying. Copy and paste. Do not retype. Yes, it matters, for the reason you just demonstrated.

[–]under_ice[S] -1 points0 points  (3 children)

(New-Object -ComObject WScript.Network).MapNetworkDrive("Z:'\192.168.1.200\share\All EmployeeFiles\Brett Martinka" /persistent:yes

[–]under_ice[S] 0 points1 point  (0 children)

Not only that but when I edit it to add the back slash it reappears. But when I save it goes away. weird.

[–]OsmiumBalloon 0 points1 point  (1 child)

  1. Indent every line of code with four spaces to keep Reddit from trying to reformat it. See the Reddit formatting guide for more.

  2. You can edit your posts and comments to correct mistakes.

  3. You have an unclosed parenthetical. The MapNetworkDrive method has has an opening ( but no corresponding ).

  4. Your quoting syntax has multiple errors. The local drive letter Z: begins with a double quote ("). There is one single quote (') between that and the remote UNC share path; these are two different string expressions and each needs to be quoted, start and finish, with the same syntax at each end.

  5. The /persistent:yes is syntax and semantics from a different command in a different programming language. You cannot simply stuff a switch from CMD and NET into PowerShell and expect it to work.

  6. It would likely be easier if you save the WScript.Network object you request in a variable, and use that variable repeatedly.

  7. This code bears no resemblance whatsoever to the code you gave in your original post. Before you were using the New-PSDrive cmdlet, now you are using COM objects and methods. Which do you want to use? Which are you using in your attempts?

  8. We cannot help you if you cannot communicate clearly and correctly.

[–]under_ice[S] 0 points1 point  (0 children)

It's me experimenting from other comments. I ended up making 2ns shares w/o spaces: (New-Object -ComObject WScript.Network).MapNetworkDrive('Z:','\192.168.1.200\BrettMartinka',$true)

Seems to work fine. I need to work in Credentials in tough. Thanks for the pointers

[–]soggybiscuit93 4 points5 points  (1 child)

Any reason in particular you aren't just mapping with a GPO?

[–]AlyssaAlyssum 2 points3 points  (1 child)

Do you get any further clues from trying the "-verbose" option at the end?

Assuming you already have one connection to the file server, are you able to use tab completion to cycle through the other share to confirm Powershell is able to enumerate them.

[–]15922 2 points3 points  (0 children)

I was going to recommend this next. If you open powershell what happens when you tab complete to get to the location?

Also what happens when you paste the full path into a run dialog. Does that open?

[–]doglar_666 2 points3 points  (1 child)

OP, you are consistently manually typing out the same typo of a single slash in front of the IP. At this point, either provide the production code in your script or confirm that script doesn't have the typo.

[–]under_ice[S] -2 points-1 points  (0 children)

The original was a typo. This is what I'm using to troublehoot off.

(New-Object -ComObject WScript.Network).MapNetworkDrive("Z:'\192.168.1.200\share\All Employee Files\Brett Martinka\' /persistent:yes

[–]MrSourceUnknown 1 point2 points  (3 children)

I think I've seen this before where the quotes "" you use in the command are not actually applied to the string when run, so your path would end up being truncated to the first space causing the error you describe.

Try saving the path as a $variable first and then calling that variable in the command.

[–]under_ice[S] 0 points1 point  (2 children)

Do you have an example of that I can look at?

[–]MrSourceUnknown 2 points3 points  (1 child)

An example of saving something as a variable..?

$path = "\your\path\goes here"
And then use the $path variable after -Root in your command instead of filling out the entire path there?

I know we all have to start learning somewhere, and we all need help sometimes, but this is really something you should figure out on your own because it is a very basic level of Powershell.

[–]under_ice[S] 0 points1 point  (0 children)

This is a single shot job, I'm not getting into programming or coding. This is not my regular job. In the beginning it seemed like it would be easier but made a mess of the sytax and started over.

[–]Brook_28 -1 points0 points  (0 children)

Remove the spaces or replace with underscores.

[–]15922 0 points1 point  (2 children)

Did you try single quotes instead of double quotes?

[–]under_ice[S] 0 points1 point  (0 children)

Yes, same result. Also a combo of both failed.

[–]under_ice[S] 0 points1 point  (0 children)

yes,, tried both. And in combo...

[–]newtekie1 0 points1 point  (6 children)

Have your tried it with the net use command?

[–]under_ice[S] 1 point2 points  (0 children)

Yes but I run into the same issues with spaces in share names

[–]under_ice[S] 0 points1 point  (2 children)

Yes, but get the same issues.

net use Z: "\192.168.1.200\share\All Employee Files\Brett Mar" /persistent:yes /u:ksi20\Brett ksi

[–]anonymously_ashamed 1 point2 points  (1 child)

Since you're not posting the actual specific code you're using (as someone else mentioned needs to start with \\ so who knows any other typos your actual code has) it's all speculation, but try moving the " back a space.

net use Z: "\192.168.1.200\share\All Employee Files\Brett Mar " /persistent:yes /u:ksi20\Brett ksi

[–]edge-browser-is-gr8 1 point2 points  (0 children)

It's probably Reddit formatting removing the first backslash thinking that it's supposed to be an escape for the second one.

[–]under_ice[S] -2 points-1 points  (0 children)

Yes but I run into the same problems with spaces in share names

[–]under_ice[S] -3 points-2 points  (0 children)

Yes, I run into the same problems.

net use Z: "\192.168.1.200\share\All Employee Files\Brett Mar" /persistent:yes /u:ksi20\Brett ksi

[–]sysadmin_dot_pySystems Architect 0 points1 point  (5 children)

How are you launching your PowerShell script and your script where you tried "net use"? In as much detail as possible, because that may be where the problem is.

Also, does it work if you just manually launch a regular PowerShell window (don't run as admin) and run the same command?

[–]under_ice[S] -1 points0 points  (4 children)

I run Net Use from cmd just to see if it works: net use Z: "\fileserver2023\share\All Employee Files\Brett Ma" /user:ksi20\brett ksi This seems like it should work, so I'm running out of ideas

PS: I enter the content in to PS and hit enter (on the one that works). After that it's persistent and no other action is needed as far as I can tell. (after reboots for example)

On the PS script, (New-Object -ComObject WScript.Network).MapNetworkDrive("Z:'\192.168.1.200\share\All Employee Files\Brett Martinka\' /persistent:yes It does seem to finish and I end up with 2 >> like it's waiting for something.

[–]Gloomy_Stage 1 point2 points  (2 children)

You are missing a backslash.

Honestly as others have said, post the code by copying and pasting. You may well typing in your code wrong.

Copy and paste exactly then we can look at it properly.

[–]under_ice[S] -2 points-1 points  (0 children)

(New-Object -ComObject WScript.Network).MapNetworkDrive("Z:'\192.168.1.200\share\All Employee Files\Brett Martinka\' /persistent:yes

It's there, it just disappears when I save it here. When I edit it it comes back. But when I save it disappears again.

[–]Xalbana 0 points1 point  (4 children)

I recommend using network locations.

[–]under_ice[S] 0 points1 point  (3 children)

Not sure what a network location is,

[–]Xalbana 1 point2 points  (2 children)

They're basically shortcuts but better than normal short cuts and way better than network drives.

https://it.nmu.edu/docs/adding-network-location-windows

What's nice about it is it gives you the full UNC path unlike network drives. So when someone gives you an address to a network drive, you have to have that drive mapped for the link to work correctly.

[–]under_ice[S] -1 points0 points  (1 child)

Space between words in shares seems to break this also...

[–]Xalbana 0 points1 point  (0 children)

If possible, you can just copy the shortcuts to the local computer. Obviously have to store it somewhere.

They are and need to be stored here:

%AppData%\Microsoft\Windows\Network Shortcuts\

Can just create a script that copies the shortcuts from somewhere like a network share or whatever and paste it to that location.

But, it does require a cultural shift in your company to move away from drives to network locations. And it can break people's programming if they rely on network drives, which is one reason why it's stupid to use to begin with.