Failed to connect local disk

Forums / NoMachine for Windows / Failed to connect local disk

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #21010
    Avatarpcts
    Participant

    Hi all – hoping some one can help/advise me on this issue. I have NoMachine (free) installed on a Windows 7 desktop acting as a NoMachine server and have 3-4 other NoMachine (free) clients (Windows 10 and Windows 7 mix) that remote into the PC the NoMachine server is installed on.

    Today the clients were unable to map the local disk. In the settings area in NoMachine where you choose to map the local drive to the remote session – it gave an error “Failed to connect to the disk C:\”.

    At first I thought it might be a firewall issue however after much troubleshooting I have found that restarting the “Noah Device Server” service on the PC they are remoting into – the local disk then mapped. But if one user disconnects and then another user connects later in the day  – the “Connect a disk” wont work until the “Noah Device Server” service is restarted on the PC they are remoting into.

    Does anyone know what might cause this or how to permanently fix it?

    All PC’s are using the latest 6.4.6 version.

    Thanks

    PCTS

    #21012
    Avatarmkub
    Participant

    Hi pcts,

    To resolve this problem we would need more information.

    Can you send us server’s logs after failed mapping? You can find them under this path: C:/ProgramData/NoMachine/var/log/node/C-"username"-1002-"numbers"/session.

    What is the type of disk forwarding (Private/Public)?

    Can you tell us what happens if you change the name of mount point? You may do this in the editable field described as Export as when choosing Public or Private mapping type. By default, it’s C.
    Is the directory then created? If yes, what are its permissions? Is it empty? If yes, try to remove it then forward disk again.

    Thanks
    mkub

    #21018
    Avatarmkub
    Participant

    Hi pcts,

    More detailed information how to gather logs you can find here:

    https://www.nomachine.com/DT07M00098

    under ‘Gather server side logs on Windows’. Please send files to this email address:

    forum at nomachine dot com

    Thanks
    mkub

    #21060
    Avatarpcts
    Participant

    Hi there – thanks for your reply. Sorry for my delayed reply.

    I checked the logs – there are folders with

    F-C-“PCName”-1001-“numbers”

    F-C-“PCName”-1002-“numbers”

    C-“PCName”-1001-“numbers”

    C-“PCName”-1002-“numbers”

    F-M-“PCName”-13001-“numbers”

    Its funny when I try to connect the drive and it fails – the session file in that folder does not update until I start the debug logging – this must be by design.

    I have pasted the  server session log below. Let me know if you want all the logs in that folder or if you need the client logs.

    Disk type is private.

    Changing name of mount point – doesn’t work. No directory created.

    Log File Name: C-<PCName>-1001-<Numbers>

    ——————————————-

     

    NXAGENT – Version 6.4.6 Copyright (C) 2001, 2018 NoMachine. See http://www.nomachine.com/ for more information.

    Session: Starting session at Mon Jan 14 08:24:29 2019. Info: Agent running with pid 8968. Info: Slave server running with pid 11248.

    Info: Listening to slave connections on port 12002. Info: Display running with pid 11204.

    NXShadowMirrorDriveIsActive: WARNING! Shadowing not initialized.

    Session: Session started at Mon Jan 14 08:24:29 2019.

    The XKEYBOARD keymap compiler (nxkb) reports:

    > Warning:          Type “ONE_LEVEL” has 1 levels, but <RALT> has 2 symbols

    >                   Ignoring extra symbols

    Errors from nxkb are not fatal to the X server

    Session: Connected to display server ‘127.0.0.1:1001’ at ‘Mon Jan 14 08:24:29 2019’.

    Session: Connected to events server ‘127.0.0.1:1001’ at ‘Mon Jan 14 08:24:29 2019’.

    Info: Using screen size 1920×1080.

    8968 5208 08:24:34 810.899 UdpProxyConnector/UdpProxyConnector: WARNING! Aborting current negotiation after timeout.

    Info: Connection with remote peer completed. Info: Using link parameters 5/1/3200/25/200. Info: Using cache parameters 16384KB/16384KB/16384KB. Info: Using pack method dynamic with session physical-desktop. Info: Using product WSN/None. Info: Transport running with pid 5208. Info: Established display connection. Info: Using image parameters 1/1. Info: Accepted new connection to display server.

    Session: Session reconnected at Mon Jan 14 08:24:35 2019. Info: Using screen size 1920×1080. Info: Accepted new slave connection. Info: Closed connection to slave server. Info: Forwarded new slave connection. Info: Closed connection to slave server. Info: Forwarded new slave connection. Info: Closed connection to slave server. Info: Forwarded new slave connection. Info: Closed connection to slave server. Info: Forwarded new slave connection. Info: Accepted new connection to filesystem server. Info: Closed connection to slave server. Info: Forwarded new slave connection. Info: Closed connection to slave server. Session: Terminating session at Mon Jan 14 08:32:53 2019. Info: Closed connection to display server. Info: Closed connection to slave server.

    Session: Session terminated at Mon Jan 14 08:32:53 2019.

    8968 5088 08:32:53 630.299 Utility: ERROR! Failed to read from output of child process.

    8968 5088 08:32:53 630.299 Utility: ERROR! Error ‘108’, Connection reset by peer.

    8968 5088 08:32:53 630.299 Thread: WARNING! Thread signaling not available on Windows.

    —-End Of Log—-

     

    Log File Name: F-C-<PCName>-1001-<Numbers>

    ——————————————-

    NXAGENT – Version 6.4.6 Copyright (C) 2001, 2018 NoMachine. See http://www.nomachine.com/ for more information. Session: Starting session at Mon Jan 07 11:05:52 2019. Info: Agent running with pid 16740. Info: Slave server running with pid 17040. Info: Listening to slave connections on port 12001. Info: Display running with pid 17088. Info: Audio server started with pid 17108. Info: Audio client started with pid 17104. Info: Display server started with pid 17132. NXShadowMirrorDriveIsActive: WARNING! Shadowing not initialized. Session: Session started at Mon Jan 07 11:05:53 2019.

    —-End Of Log—-

    #21072
    AvatarBritgirl
    Keymaster

    We’re still unable to reproduce the problem. If we send you a debug library with further instructions, would you be able to resubmit some new logs? This would allow us to get more debug information.

    #21076
    Avatarpcts
    Participant

    Hi there  – thanks for helping looking into the issue for me. Yes that will be fine. Send them over and I will resubmit some new logs.

    #21131
    Avatarmkub
    Participant

    Hi pcts,

    Logs we’ve received from you, helped us to locate the problem, but still we don’t know the exact reason and were not able to reproduce this situation. Can you tell something more about Noah software and also about Noah Device Server? What this server does? How do you create it?

    Can you check if disk driver is mounted properly? You can do this by opening CMD and running:

    driverquery /nh | find "nxfs"

    Output should look like this:
    nxfs NoMachine FileSystem A File System "date"

    Thanks for logs and for help.
    mkub

    #21169
    Avatarpcts
    Participant

    Hi guys

    What did you find in the logs that showed the problem? And in which log?

    “Noah device server” was a typo in my previous post meant to say “nomachine device server” service.

    Output is correct.

    C:\Users\joebloggs>driverquery /nh | find “nxfs”

    nxfs         NoMachine Filesystem A File System   11/21/2018 1:45:19 PM

    #21183
    Avatarmkub
    Participant

    Hi pcts,

    According to logs, there is a problem with performing a disk mount operation directly by our driver. This is why I asked about output. In this case, it looks like driver is available for the system. We got this information from line: ‘Received output from the nxfs: ‘DEBUG: DokanMain failed.’. Still, we’re not able to reproduce your problem.

    mkub

    #21245
    Avatarpcts
    Participant

    Hi there

    Thanks for the reply. What is involved in the disk mount operation – could something be blocking it intermittently? I ran that command on the client – should I also run it on the server?

    Thanks

    PCTS

    #21275
    Avatarmkub
    Participant

    Hi pcts,

    You should run this command on the server as well. The output should be similar. Did you make some changes in configuration files? According to the logs, some device features are disabled. Make sure that those files are edited correctly or try to move back to the default values. The file connected to the disk is placed in %InstallDir%/etc/node.cfg. If this problem is still present, please send us Windows Event logs after repeating the problem (instruction how to collect them are below). NoMachine installation logs will be also helpful. You may find them in “C:\Users\<username>\AppData\Local\Temp” saved as “Setup Log <date>.txt”.

    Thanks
    mkub

    1. Export Event Viewer logs:

    – Open Control Panel -> System and Security -> Administrative Tools -> Event Viewer

    – To export events, select the type of logs you want to export, click on Action menu and pick Save All Events As.

    We’re interested in ‘Windows Logs/System’, ‘Windows Logs/Application’ and ‘Application and Services Logs/Hardware Events’ logs.

Viewing 11 posts - 1 through 11 (of 11 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.