System error 1909 has occurred

Какова вероятная причина этого, если команда выполняется на Windows Server 2008? Похоже, что эта учетная запись является администратором в этом поле. Я также использую командную строку Windows в качестве администратора. C:>net use z: \uwhc-sas2SASHIMC /USER:SVC

Какова вероятная причина этого, если команда выполняется на Windows Server 2008? Похоже, что эта учетная запись является администратором в этом поле. Я также использую командную строку Windows в качестве администратора.

C:>net use z: \uwhc-sas2SASHIMC /USER:SVCdatamgmt thepassword
System error 1909 has occurred.

The referenced account is currently locked out and may not be logged on to.

Какие есть предложения по устранению такой ошибки?

РЕДАКТИРОВАТЬ @ 11:16 утра 3/8/2013:

================================================== ======================
Это не сработало прошлой ночью:

C:> net use z: \uwhc-sas2SASHIMC /USER:SVCdatamgmt thepassword

System error 1909 has occurred.
The referenced account is currently locked out and may not be logged on to.

================================================== ======================
Подождал 30 минут и потом это сработало (без домена):

C:> net use z: \uwhc-sas2SASHIMC /USER:SVCdatamgmt thepassword

The command completed successfully.

C:> net use z: /delete

z: was deleted successfully.

================================================== ======================
Это также работает (с доменом):

C:> net use z: \uwhc-sas2SASHIMC /USER:UWHISSVCdatamgmt thepassword

The command completed successfully.

================================================== ======================
Но это не работает (с полным доменным именем):

C:> net use z: \uwhc-sas2SASHIMC /USER:uwhc-sas2.uwhis.hosp.wisc.eduSVCdatamgmt thepassword

System error 86 has occurred.

The specified network password is not correct.

================================================== ======================
.NET код, который отображает диск. Мои полномочия работают (и всегда работали); Учетные данные SVCdatamgmt не работают.

public static void MapNetworkDriveToUNC()
{
    var command = @"net use " + mapDrive + " " + uncPath + " " + uncUser + " " + uncPass;
    ExecuteCommand(command, 10000);
}

public static void UnmapNetworkDriveToUNC()
{
    var command = "net use " + mapDrive + " /delete";
    ExecuteCommand(command, 5000);
}

Содержание

  1. Windows выдает команду «net use», ошибка «Произошла системная ошибка 1909»
  2. РЕДАКТИРОВАТЬ @ 11:16 утра 3/8/2013:
  3. 1 ответ
  4. System Error 1909 Has Occurred
  5. Windows «net use» command throwing error, «System error .
  6. net use to file server gives error 1909 on build 9926 .
  7. How to Fix Windows Error Code 1909
  8. Cannot map network drives : account is currently locked .
  9. System Error Codes (1700-3999) (WinError.h) — Win32 apps .
  10. Net view — System error 1231
  11. Guest access in SMB2 is disabled — Windows Server .
  12. Software Protection Service Wont Start — Windows 10 Forums
  13. [SOLVED] «The reference account is currently locked out .
  14. System Error 1909 Has Occurred Fixes & Solutions
  15. How to fix the Runtime Code 1909 Sophos Error Code 1909
  16. How To Fix WinZip Error 1909
  17. Description of Winzip Error 1909
  18. Why And When Is Runtime Error 1909 Triggered?
  19. Winzip Error 1909 Errors
  20. Epicenters of Winzip Error 1909 Headaches

Windows выдает команду «net use», ошибка «Произошла системная ошибка 1909»

Какова вероятная причина этого, если команда выполняется на Windows Server 2008? Похоже, что эта учетная запись является администратором в этом поле. Я также использую командную строку Windows в качестве администратора.

Какие есть предложения по устранению такой ошибки?

РЕДАКТИРОВАТЬ @ 11:16 утра 3/8/2013:

C:> net use z: \uwhc-sas2SASHIMC /USER:SVCdatamgmt thepassword

C:> net use z: \uwhc-sas2SASHIMC /USER:SVCdatamgmt thepassword

C:> net use z: /delete

C:> net use z: \uwhc-sas2SASHIMC /USER:UWHISSVCdatamgmt thepassword

C:> net use z: \uwhc-sas2SASHIMC /USER:uwhc-sas2.uwhis.hosp.wisc.eduSVCdatamgmt thepassword

================================================== ======================
.NET код, который отображает диск. Мои полномочия работают (и всегда работали); Учетные данные SVCdatamgmt не работают.

1 ответ

Давайте шаг за шагом рассмотрим это:

Скорее всего, аккаунт был заблокирован в AD в первый раз. Большинство политик блокировки блокируют учетную запись только на 15-30 минут, чтобы остановить перебор. Вы, должно быть, пару раз набрали неверный пароль или не смогли войти в систему с этой учетной записью в другом месте, чтобы вызвать это. При попытке через 30 минут учетная запись автоматически разблокировалась, скорее всего, в соответствии с политикой блокировки учетной записи. Обратитесь к вашей политике домена по умолчанию для более подробной информации.

Что-то где-то заблокировало эту учетную запись (обратитесь к журналам вашего контроллера домена). Затем он разблокируется через указанный интервал блокировки, и вы можете использовать его как обычно. Не похоже, что здесь есть реальная проблема.

Источник

System Error 1909 Has Occurred

We have collected for you the most relevant information on System Error 1909 Has Occurred, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered System Error 1909 Has Occurred before you, so use the ready-made solutions.

Windows «net use» command throwing error, «System error .

    https://serverfault.com/questions/486025/windows-net-use-command-throwing-error-system-error-1909-has-occurred
    Stack Exchange network consists of 176 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share …

net use to file server gives error 1909 on build 9926 .

    https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web-insiderplat_pc/net-use-to-file-server-gives-error-1909-on-build/1ce4f84f-c89b-4724-a938-9fd4aa6497fe
    Jan 27, 2015 · System error 1909 has occurred. The referenced account is currently locked out and may not be logged on to. My domainusername account is not locked out, and I was able to do this with a previous version of Windows 10 Preview.

How to Fix Windows Error Code 1909

    http://www.cleanwindowserrors.com/1909.php
    The windows error code 1909 is generally generated due to errors reported by the driver itself meaning that this error is a software problem or compatibility issues between the hardware installed and the …

Cannot map network drives : account is currently locked .

    https://www.tek-tips.com/viewthread.cfm?qid=1673462
    Jan 31, 2012 · Instead of being offered to enter a username and password, it just instantly errors with a 1909 and claims the account is currently locked. I have checked the PDC and the account isn’t locked. I have checked ‘Control userpasswords2’ and cannot find any conflicting accounts.

System Error Codes (1700-3999) (WinError.h) — Win32 apps .

    https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes—1700-3999-
    This information is intended for developers debugging system errors. For other errors, such as issues with Windows Update, there is a list of resources on the Error codes page. The following list describes system error codes for errors 1700 to 3999. They are returned by …

Net view — System error 1231

    https://social.technet.microsoft.com/Forums/en-US/6f102ed1-8e76-4cb7-8dec-05714466d441/net-view-system-error-1231
    Apr 19, 2020 · Hi, I ’ m wondering what ’ s your OS version? And does your machine a domain member or workgroup member? I ’ ve tested the «net view» command in my lab with a Windows10, workgroup machine and met the same problem with you.. Based on my research, it may be caused by the SMBv1 protocol not being installed by default.

Guest access in SMB2 is disabled — Windows Server .

    https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default
    Configured registry value: [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanWorkstationParameters] «AllowInsecureGuestAuth»=dword:1. Guidance. This event indicates that an administrator has enabled insecure guest logons. An insecure guest logon occurs when a server logs on the user as an …

Software Protection Service Wont Start — Windows 10 Forums

    https://www.tenforums.com/general-support/153032-software-protection-service-wont-start.html
    Mar 27, 2020 · Once or twice a day I get a half second of stutter where my video and audio will stutter for half a second. The only thing I’ve found in the Windows Logs seems to be the Software Protection Service starts when the stutter happens.

[SOLVED] «The reference account is currently locked out .

    https://community.spiceworks.com/topic/496038-the-referenced-account-is-currently-locked-out-and-my-not-be-logged-on-to
    May 26, 2016 · Ok, what you have to do first is, check if your system administrator is assign with password or more than one account, if yes, go to Control panel>>User account>>Remove password from administrator and delete the other account (Not the administrator) Then check time and date if correct restart the system and try joining the system to domain again.

System Error 1909 Has Occurred Fixes & Solutions

We are confident that the above descriptions of System Error 1909 Has Occurred and how to fix it will be useful to you. If you have another solution to System Error 1909 Has Occurred or some notes on the existing ways to solve it, then please drop us an email.

Источник

How to fix the Runtime Code 1909 Sophos Error Code 1909

This article features error number Code 1909, commonly known as Sophos Error Code 1909 described as Error 1909: Sophos Antivirus has encountered a problem and needs to close. We are sorry for the inconvenience.

Error Information

Error name: Sophos Error Code 1909
Error number: Code 1909
Description: Error 1909: Sophos Antivirus has encountered a problem and needs to close. We are sorry for the inconvenience.
Software: Sophos Antivirus
Developer: Sophos Ltd.

This repair tool can fix common computer errors like BSODs, system freezes and crashes. It can replace missing operating system files and DLLs, remove malware and fix the damage caused by it, as well as optimize your PC for maximum performance.

About Runtime Code 1909

Runtime Code 1909 happens when Sophos Antivirus fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.

Definitions (Beta)

Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!

  • Antivirus — Antivirus or anti-virus software is software used to prevent, detect and remove malware.
  • Error code — An error code is a value returned to provide context on why an error occurred
Symptoms of Code 1909 — Sophos Error Code 1909

Runtime errors happen without warning. The error message can come up the screen anytime Sophos Antivirus is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.

There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.

(Sophos Error Code 1909) Repair Tool»/>
(For illustrative purposes only)

Causes of Sophos Error Code 1909 — Code 1909

During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.

Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.

Repair Methods

Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.

If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.

Источник

How To Fix WinZip Error 1909

Error Number: Error 1909
Error Name: Winzip Error 1909
Error Description: Error 1909: WinZip has encountered a problem and needs to close. We are sorry for the inconvenience.
Developer: WinZip Computing, S.L.
Software: WinZip
Applies to: Windows XP, Vista, 7, 8, 10, 11

Description of Winzip Error 1909

Commonly, PC professionals refer to Winzip Error 1909 as a type of «runtime error». To make sure that the functionality and operations are all working in a usable condition, software developers like WinZip Computing, S.L. do debugging before software releases. Unfortunately, sometimes errors such as error 1909 might get missed during this process.

Error 1909 is also displayed as «Winzip Error 1909». It is a common error that might occur after installation of the software. If Winzip Error 1909 occurs, developers will be told about that issue though error reporting built-into the application. The programming team can use this info to find and fix the issue (developing an update). If there is notification for a WinZip update, it can be a solution for fixing issues like error 1909 and additional issues discovered.

Why And When Is Runtime Error 1909 Triggered?

The most common occurrences Winzip Error 1909 problems is when loading up WinZip. We can identify the origin of error 1909 runtime errors as follows:

Error 1909 Crash — Error 1909 will stop the machine from performing a regular program operation. This emerges when WinZip fails to respond to input properly, or does not know what output is required in return.

Winzip Error 1909 Memory Leak — Error 1909 memory leak occurs and exposes WinZip as a culprit, dragging down your PC performance. Possible provocations include lack of memory de-allocation and having reference to bad code such as infinite loops.

Error 1909 Logic Error — Logic errors manifest when the user inputs the correct data but the device produces the wrong result. It materializes when WinZip Computing, S.L.’s source code is flawed due to faulty design.

WinZip Computing, S.L. issues related Winzip Error 1909 can be attributed in most cases to corrupt, missing, or infected WinZip files. As a first troubleshootiong step, most PC professionals will attempt to replace the applicable version of the WinZip Computing, S.L. file. Also, maintaining a clean and optimized Windows registry can help in preventing invalid WinZip Computing, S.L. file path references, so we highly recommend running a registry scan on a regular basis.

Winzip Error 1909 Errors

These Winzip Error 1909-related WinZip Troubles Include:

  • «Winzip Error 1909 Software Error.»
  • «Winzip Error 1909 is not a valid Win32 application.»
  • «Winzip Error 1909 has encountered a problem and needs to close. We are sorry for the inconvenience.»
  • «Winzip Error 1909 can’t be located.»
  • «Winzip Error 1909 not found.»
  • «Start-up error in application: Winzip Error 1909.»
  • «Winzip Error 1909 is not running.»
  • «Winzip Error 1909 quit.»
  • «Winzip Error 1909: App Path is Faulting.»

Winzip Error 1909 EXE errors happen during WinZip installation, while running Winzip Error 1909-related applications (WinZip), during startup or shutdown, or during installation of Windows OS. It’s important to note when Winzip Error 1909 issues happen, as it helps troubleshoot WinZip problems (and report to WinZip Computing, S.L.).

Epicenters of Winzip Error 1909 Headaches

These Winzip Error 1909 troubles are created by missing or corrupt Winzip Error 1909 files, invalid WinZip registry entries, or malicious software.

In particular, Winzip Error 1909 problems originate through:

  • Corrupted or invalid Winzip Error 1909 registry entry.
  • Virus or malware infection that has corrupted the Winzip Error 1909 file or related WinZip program files.
  • Winzip Error 1909 maliciously, or mistakenly, removed by another software (apart from WinZip).
  • Another program is in conflict with WinZip and its shared referenced files.
  • WinZip (Winzip Error 1909) corrupted during download or install.

Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000

Источник

Какова вероятная причина этого , если команда запускается на Windows Server 2008? Похоже, что эта учетная запись является администратором этого ящика. Я также запускаю командную строку Windows как администратор.

C:>net use z: \uwhc-sas2SASHIMC /USER:SVCdatamgmt thepassword
System error 1909 has occurred.

The referenced account is currently locked out and may not be logged on to.

Какие есть предложения по устранению такой ошибки?

РЕДАКТИРОВАТЬ @ 11:16, 08.03.2013:

==================== ================================================== ==
Вчера вечером это не сработало:

C:> net use z: \ uwhc-sas2 SASHIMC / USER: SVCdatamgmt thepassword

System error 1909 has occurred.
The referenced account is currently locked out and may not be logged on to.

========= ================================================== =============

Подождал 30 минут, а затем это сработало (без домена):

C:> net use z: \ uwhc- sas2 SASHIMC / ПОЛЬЗОВАТЕЛЬ: SVCdatamgmt thepassword

The command completed successfully.

C:> net use z: / delete

z: was deleted successfully.

======================== ================================================
Это также работает (с доменом):

C:> net use z: \ uwhc-sas2 SASHIMC / USER: UWHIS SVCdatamgmt thepassword

The command completed successfully.

=========== ================================================== ===========
Но это не работает (с полным доменным именем):

C:> net use z: \ uwhc-sas2 SASHIMC / USER : uwhc-sas2.uwhis.hosp.wisc.edu SVCdatamgmt thepassword

System error 86 has occurred.

The specified network password is not correct.

=========================================== =============================
.NET-код, отображающий диск. Мои учетные данные работают (и всегда работали); Учетные данные SVCdatamgmt не работают.

public static void MapNetworkDriveToUNC()
{
    var command = @"net use " + mapDrive + " " + uncPath + " " + uncUser + " " + uncPass;
    ExecuteCommand(command, 10000);
}

public static void UnmapNetworkDriveToUNC()
{
    var command = "net use " + mapDrive + " /delete";
    ExecuteCommand(command, 5000);
}

Как я могу сделать так, чтобы код .NET отображал диск Z: на путь UNC для учетной записи SVNdatamgmt?

Я пытаюсь сопоставить локальный диск с сетевым UNC-путем в консольном приложении .NET. Кажется, что код работает из командной строки как для учетной записи службы (№2 и №3), так и с моими учетными данными (№4). Но при запуске из консольного приложения с использованием исходного кода .NET учетная запись службы не работает (№5), но мои учетные данные работают (№6).

Вчера вечером заметил, что у меня ошибка (№1). Подождав 30 минут, все заработало. Итак, вы можете игнорировать №1. Я подумал, что упомяну об этом, на случай, если он даст понять, что происходит.

Консольное приложение запускается от имени администратора в системе Windows Server 2008. И SVCdatamgmt, и macgyver являются администраторами на этом компьютере. Команды также выполняются на этом же компьютере.

================================================== ======================
1.) Прошлой ночью это не сработало:

C:> net use z: \uwhc-sas2SASHIMC /USER:SVCdatamgmt thepassword

System error 1909 has occurred.
The referenced account is currently locked out and may not be logged on to.

================================================== ======================
2.) Подождал 30 минут, а затем это сработало (без домена):

C:> net use z: \uwhc-sas2SASHIMC /USER:SVCdatamgmt thepassword

The command completed successfully.

================================================== ======================
3.) Это также работает (с доменом):

C:> net use z: \uwhc-sas2SASHIMC /USER:UWHISSVCdatamgmt thepassword

The command completed successfully.

================================================== ======================
4.) Это также работает с моими учетными данными:

C:> net use z: \uwhc-sas2SASHIMC /USER:macgyver thepassword

The command completed successfully.

================================================== ======================
5.) .NET-код, отображающий диск. Учетные данные SVCdatamgmt не работают.

public static void MapNetworkDriveToUNC()
{
    var command = @"net use " + mapDrive + " " + uncPath + " " + uncUser + " " + uncPass;
    ExecuteCommand(command, 10000);
}

public static void UnmapNetworkDriveToUNC()
{
    var command = "net use " + mapDrive + " /delete";
    ExecuteCommand(command, 5000);
}

================================================== ======================
6.) .NET-код, отображающий диск. Мои учетные данные работают (macgyver)

— тот же код, что и # 5 —

================================================== ======================
К вашему сведению: перед выполнением каждой приведенной выше команды я должен отключить (отменить сопоставление) накопитель с помощью этого кода …

C:>net use z: /delete

z: was deleted successfully.

INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!

  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It’s Free!

*Tek-Tips’s functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Cannot map network drives : account is currently locked

Cannot map network drives : account is currently locked

(OP)

31 Jan 12 06:17

Hi,

I have a remote user that seems unable to map the company network drives when connected via VPN.

Everytime the batch script runs or if I try to manually map the network drives with the ‘net use’ command.

Instead of being offered to enter a username and password, it just instantly errors with a 1909 and claims the account is currently locked.

I have checked the PDC and the account isn’t locked.

I have checked ‘Control userpasswords2’ and cannot find any conflicting accounts.

So what credentials is Vista trying to use?

Where has it got these credentials from?

What is claiming the account is locked as it doesn’t seem to be the DC?

How do I resolve this?

We have 3 other Vista users and we don’t get this problem.

Thanks,
1DMF

«In complete darkness we are all the same, only our knowledge and wisdom separates us, don’t let your eyes deceive you.»

«If a shortcut was meant to be easy, it wouldn’t be a shortcut, it would be the way!»

MIME::Lite TLS Email Encryption — Perl v0.02 beta

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Join Tek-Tips® Today!

Join your peers on the Internet’s largest technical computer professional community.
It’s easy to join and it’s free.

Here’s Why Members Love Tek-Tips Forums:

  • Tek-Tips ForumsTalk To Other Members
  • Notification Of Responses To Questions
  • Favorite Forums One Click Access
  • Keyword Search Of All Posts, And More…

Register now while it’s still free!

Already a member? Close this window and log in.

Join Us             Close

  • Reply with quote

Cannot log in to Windows mapped drives in VM

I have a hp8540W notebook with 159GB free space on the HDD, 4GB RAM, 2.8GHz i7 and Windows 7 pro SP1 64-bits.
I’m a VB newbie, and installed 4.1.14. My colleague has the same PC, and his system folder containing WinXP + a big application that doesn’t run on Win7 was copied to my PC.
I changed his user name to mine — the same user name I use regularly for login and whatever.
For my application to work, I need access to some mapped network drives, but when I try to log in to those, they tell me ID or password is wrong. I can ping the servers in a command window…
Tried disconnecting and remapping… same result.
I looked at the shared folder thing without really understanding what to do… when I go to devices — shared folders I get a warning saying «The VirtualBox Guest Additions do not appear to be available on this virtual machine, and shared folders cannot be used without them. But I did reinstall the guest additions from the website (for the right version). I suspect the problem is here, somehow.
From a command window I tried this:
C:>net use P: \servernamefoldername
after a long time it responds:
System error 1909 has occurred.
The referenced account is currently locked out and may not be logged on to.

So happy for any advice you may have!

MartinST
 
Posts: 7
Joined: 1. May 2012, 12:30

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby Perryg » 2. May 2012, 16:07

I think you are misunderstanding the difference of shared folders and mapped network drives.
Shared folders only map the hosts folders that are shared.
Also for mapped network drives you would need to be using Bridged mode for the virtual adapter.

Perryg
Site Moderator
 
Posts: 34373
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby MartinST » 3. May 2012, 12:35

You are right — I could find no hint about mapped network drives so…
Anyway, now I set up the network tab for ‘bridged adaptor’ but that made no difference at all — I still cannot get access to my network drives. It claims my ID or password are wrong, although they do work on the ‘real’ machine.
Any ideas?

MartinST
 
Posts: 7
Joined: 1. May 2012, 12:30

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby Perryg » 3. May 2012, 14:19

If you have issues (permission) on a real network mapping then that would be a question to take up with your IT department. In bridged mode the guest appears as just another PC on the LAN.

Perryg
Site Moderator
 
Posts: 34373
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby Leak » 3. May 2012, 16:43

Perryg wrote:Also for mapped network drives you would need to be using Bridged mode for the virtual adapter.

Why would you? As long as you can open a TCP connection to the server it should work…

You might have to add the domain to the username (i.e. «DOMAINUsername») for it to work, though.

Leak
 
Posts: 242
Joined: 31. Mar 2009, 13:00
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Debian Testing, Windows XP, Windows Server 2003/2008 R2

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby naemrr » 4. May 2012, 00:55

MartinST wrote:System error 1909 has occurred.
The referenced account is currently locked out and may not be logged on to.

this tells me, that ether;
A: the account on the computer/server that has the shared file you are after, is locked,
or
B: the account on the computer/server that has the shared file you are after, is not allowed to access windows shares due to a policy restriction.

A can occur if you tryed to log in too many times.
A and B can occur in a professional IT environment, if you tryed to log in from an UNAUTHORIZED computer! your guest, would be seen as unauthorized by the network regardless of networking mode used if the authority server happens to be a windows AD server or equivalent.

also be aware, that without a username passed via the net use command, it will assume the ORIGINAL name of the windows account you are on (renaming does not change the name it passes to the network!!)

workaround;
net use P: \servernamefoldername /USER:servernameusername

naemrr
 
Posts: 83
Joined: 17. Dec 2011, 22:56
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: ubuntu natty, windows 2k3, windows xp pro, windows vista x86 & x64, debian squeeze

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby MartinST » 7. May 2012, 16:52

I tried the ‘net use…’ command qualified with a username, but it did not help, although the ‘System Error 1909 disappeared’. I also generated a new user — with the old one it seems I was logging on using my colleagues ID — the one I copied the VM from. Now he is locked out from his drives… And my mapping attempts are rejected as if I gave a faulty password.
Normally, we log on a domain and the login is authenticated by the server. So when I log in as a local WinXP user, apparently the domain never accepts me.
I went back to NAT mode, thinking it would be better not to look like a different PC attached, but still no go. (My colleague operates in NAT mode).
@Leak: TCP connection would not help, my application needs these mapped drives to access directly.

Well, solution still not found :-(

MartinST
 
Posts: 7
Joined: 1. May 2012, 12:30

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby naemrr » 7. May 2012, 16:57

one solution you could try.

If the host machine can access the shared folder you are after;
goto the VM settings for your guest, and then to shared folders
now create a new shared folder, and direct it to access the network share/network mapped drive on the host

from the guest open my computer, and in the address bar try to open \vboxsrv

if it can see the contents of the folder you shared via the VM settings, you can then map any drive you need to from the \vboxsrv «server»

also if login authentication is handled by a domain server, you can try net use one more time with

net use P: \servernamefoldername /USER:DOMAINusername
replace DOMAIN with your networks domain name (example: /USER:thabox.orgnaemr)

naemrr
 
Posts: 83
Joined: 17. Dec 2011, 22:56
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: ubuntu natty, windows 2k3, windows xp pro, windows vista x86 & x64, debian squeeze

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby naemrr » 7. May 2012, 17:02

Perryg wrote:on a real network mapping then that would be a question to take up with your IT department

On a side note along those lines, by far the EASIEST method to do ALL of this, is to talk to your IT department.
if this whole project is indeed work related, they could very easily add the virtual machine to the domain, make you a local only admin, and even help get all of your shares setup such that it would be a no mess setup.

naemrr
 
Posts: 83
Joined: 17. Dec 2011, 22:56
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: ubuntu natty, windows 2k3, windows xp pro, windows vista x86 & x64, debian squeeze

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby MartinST » 8. May 2012, 13:21

Thanks again, naemrr,
The host machine can acces the relevant network locations as mapped drives. I set up one of these as a new shared folder, but in my guest \vboxsrv in the address line of ‘my computer’ produces the message «Windows cannot find ‘\vboxsrv’…..»
The ‘net use…’ including the domain name was already tried yesterday, didn’t help.
I also tried our local IT support yesterday, but they do not support VirtualBox. The application I need to use, of course, is supported by different people. So even if this application is really crucial to us hardware developers and new PCs in the company have come with Win7 for about a year — there apparently is no official solution. So I hoped VirtualBox could be my workaround… so frustrating…

MartinST
 
Posts: 7
Joined: 1. May 2012, 12:30

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby naemrr » 9. May 2012, 01:08

the shared folder needs to be setup in the virtual box settings for the virtual machine, and guest addidions must be installed in the guest or using the virtualbox shared folders will not work

naemrr
 
Posts: 83
Joined: 17. Dec 2011, 22:56
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: ubuntu natty, windows 2k3, windows xp pro, windows vista x86 & x64, debian squeeze

  • Reply with quote

Re: Cannot log in to Windows mapped drives in VM

Postby MartinST » 9. May 2012, 15:27

That prompted me to check the ‘guest additions’, which I had been installing from the VB server. Or downloaded at least — now I understood there is installation to be done inside the guest machine, and after that I have access to the network drives :D .
My application still doesn’t run, I think I need to check the environment variables…
Thank you very much for helping!

MartinST
 
Posts: 7
Joined: 1. May 2012, 12:30


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 25 guests

Понравилась статья? Поделить с друзьями:
  • System error 1722 has occurred the rpc server is unavailable
  • System error 1722 has occurred 0x000006ba
  • System error 1378 has occurred
  • System error 1371 has occurred
  • System error 1355 has occurred