Psexec Net Use Error 1223
Contents |
Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 26 January 2006 Location: Canada Status: Offline Points: 2 Post Options Post Reply Quoteronaldknol Report Post Thanks(0) QuoteReply Topic: PsExec and psexec error code 2 "net use"Posted: 26 January 2006 at 4:15pm Having searched this forum and on the internet
Psexec Exit Code 2
I still have not been able to get my problem answered, so hence this new post. Using psexec v1.70, my PC is remotely map network drive for user Windows 2000 ProfessionalSP4, the remote machine is also Windows 2000 Professional SP4. No firewalls involved, both machines are part of a (Windows 2003) domain. The remote machine automatically logs on with a known username and password (account
Map Network Drive Remotely Powershell
and passwd), I am logged on to my PC with my own credentials (myaccount and mypasswd). The remote machine (account) automatically maps a network drive when it logs on (done through Windows Explorer with Reconnect At Logon). I am trying do remotely change that mapped drive to another server.On the remote machine locallyI can do this (works): net use W: /delete net use W: \\server\share /PERSISTENT:YES But, from my PC using PsExec this net use exit code 2 does not work and I get strange results. Here's what I did: psexec \\remote -u domain\account -p passwd -i net use W: /delete This fails with error: The network connection could not be found. More help is available by typing NET HELPMSG 2250. If I try to map a new drive psexec \\remote -u domain\account -p passwd -i net use K: \\server\share This works, and the K: drive shows up on the remote machine in Windows Explorer (but with a red X indicating disconnected) and I can access it. So then I want to disconnect it: psexec \\remote -u domain\account -p passwd -i net use K: /delete And again I get the error: The network connection could not be found. More help is available by typing NET HELPMSG 2250. But now even though I got this error, Windows on the remote machine is confused. Windows Explorer still shows the K: drive, but running "net use" on that remote machine shows no K: drive. Windows Explorer "Disconnect Network Drive" also does not show K:. I have tried this over and over, but I get the same results. PsExec with "net use K: \\server\share" works, but after that the machine does not indicate that the drive is mapped, and cannot be unmapped, even though Windows Explorer sees
is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want
Net Use Remotely
to visit from the selection below. Results 1 to 6 of 6 Thread: Remote mapped
Drivemapadd
network drives Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to map network drive remotely command prompt Hybrid Mode Switch to Threaded Mode 11-01-2005,03:07 AM #1 johnmb Guest Remote mapped network drives Hi all, Have seen a few posts mentioning the use of "net use" to get a list of mapped drives on a remote PC. Try http://forum.sysinternals.com/psexec-and-net-use_topic3796.html as I might, can't get it to work, using (I think!) pretty well all different options including different users, full path names, etc but the best I can get is a message that says "There are no entries in the list", or perhaps I can get a list of persistent mapped drives, but not those mapped by, say, a login script..... Any answers? Reply With Quote 02-01-2006,11:10 AM #2 Dee Guest Re: Remote mapped network drives I'm having the same http://www.systemtools.com/toolboard/showthread.php?3296-Remote-mapped-network-drives problem. I type psexec \\remotecomputername cmd. Then I type net use and no mapped drives are shown. Has anyone found the fix for this? Thanks, Dee Reply With Quote 05-04-2006,07:22 AM #3 Cam Guest Re: Remote mapped network drives I too have tried net use for this and I get the same result. I need to see the mapped drives from a script too. net use works on the local machine but net use over the network even with psexec only gives me a message saying none in list. Reply With Quote 05-04-2006,07:45 AM #4 cmccullough View Profile View Forum Posts Visit Homepage View Articles Senior Member Join Date Sep 2000 Location San Antonio, Texas, USA Posts 6,268 Re: Remote mapped network drives Near the bottom of this thread is a possible way to get psexec working for this: http://www.systemtools.com/toolboard...n-Clients-PC-s Reply With Quote 05-05-2006,05:50 AM #5 Cam Guest Re: Remote mapped network drives using the -u for psexec I guess you mean. This just asks for a password. My batch file contains: @echo off M: cd \PSEXEC psexec.exe \\%1 net use and I have tried putting the -u after psexec.exe. the Hyena command is: cmd /x /c m:\hyena\drives.bat Obviously the user on each machine is going to be different so is there a way of adding the user account as a self populating variable with a user$ command or similar? Reply With Quote 05-05-2006,08:02 AM #6
Support Query Forum Release Notes FAQ COMPANY Company News & Events Product Roadmap Contact Us Careers Customers Testimonials Partners PSEXEC + Shared drive access : Automation Discussions Download Trial Home»Forum»Community»Automation Discussions Login Register Ranorex FAQ PSEXEC + Shared drive access Experiences, http://www.ranorex.com/forum/psexec-shared-drive-access-t2490.html small talk, and other automation gossip. Topic locked 6 posts • Page 1 of 1 PSEXEC + Shared drive access by sdaly » Wed Aug 10, 2011 2:16 pm HiI have build an automation remote which uses https://msdn.microsoft.com/en-us/library/windows/desktop/ms681383(v=vs.85).aspx psexec underneath.The command I am using is - psexec.exe \\computerName -i "C:\Program Files\NUnit 2.5.10\bin\net-2.0\nunit-console.exe" /fixture:GFI.Automation.TestCases.AgentTests "C:\Documents and Settings\Administrator\Desktop\Automation build.79\GFI.Automation.exe" /process=multiple /domain=multipleIf I run this from a batch file locally (without psexec) everything works fine...If I run through net use psexec the tests can see the c:\ drive but not any mapped network drives. I am using the absolute path of the mapped drive for example E:\AgentsHas anyone encountered this problem before and if so, is there anything I can do to make this work?!ThanksScott sdaly Posts: 238Joined: Mon May 10, 2010 11:04 amLocation: Dundee, Scotland Top Re: PSEXEC + Shared drive access by sdaly » Wed Aug 10, 2011 2:17 pm Oh, I've map network drive tried the -s switch too with no luck sdaly Posts: 238Joined: Mon May 10, 2010 11:04 amLocation: Dundee, Scotland Top Re: PSEXEC + Shared drive access by Aracknid » Wed Aug 10, 2011 3:24 pm PSEXEC doens't likes mapped drives. You need to use the UNC paths.Aracknid. Aracknid Posts: 278Joined: Tue Aug 10, 2010 3:23 pmLocation: Toronto, Ontario, Canada Top Re: PSEXEC + Shared drive access by Ciege » Wed Aug 10, 2011 3:55 pm You can try adding 0 to the -i switch "-i 0" to force PSEXEC to use the main console session. Also, you are not passing any credentials with the -u -p switches. I think without the proper credentials, then when PSEXEC launches on the remote machine it may not have proper access to see all the mapped drives. I always pass the -accepteula switch as a just in case. If the remote machine may have never run PSEXEC before then the EULA will pop up requiring a manual click to close the EULA screen possibly causing issues with automation.In summary, I always use the following switches:-accepteula-i 0-s-u-p If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue! Ciege... Ciege Ranorex Guru Posts:
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Error Handling Error Handling Reference System Error Codes System Error Codes System Error Codes (1000-1299) System Error Codes (1000-1299) System Error Codes (1000-1299) System Error Codes (0-499) System Error Codes (500-999) System Error Codes (1000-1299) System Error Codes (1300-1699) System Error Codes (1700-3999) System Error Codes (4000-5999) System Error Codes (6000-8199) System Error Codes (8200-8999) System Error Codes (9000-11999) System Error Codes (12000-15999) TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. System Error Codes (1000-1299) Note Â