Problems and error messages

Problems and error messages

  • "Can not find the host name or share name"

    Possible causes: - The server name or share name you have entered is incorrect.
    - In some cases it is possible that your computer can not convert the name of the server, so it can not be addressed properly by the protocol. Mostly, you can work around this problem by entering the server's full domain name.

    \\files.UGent.be\log-in
    
    - In case you are using a firewall, you can encounter problems as well. Disable it in order to determine whether the firewall could be the cause of the problem. In that case, configure your firewall correctly to enable mounting.

  • "wrong password"

    Possible causes: - You did not use your UGent log-in name when signing on to Windows Networks, but a log-in name that you have picked inside your Windows environment. In that case, close down your PC and when starting up, sign on with your UGent log-in name.
    - The problem is caused by the password itself: do not use any letters with accents, diaereses, etc. in your password. If you are using this kind of characters, choose an other password.
    - In case you are trying to mount via VPN, another possible cause is that you did not implement adjustments as necessary in some cases in order to mount through a VPN connection. Check the description VPN for your operating system.

  • "Not logged on"

    This means that you did not log on to Windows Networks when starting up Windows. Check whether Client for MS networks has been set as your primary network log-in, restart Windows and log on!

  • "Access denied or "The network cannot be found" after successfully mounting a networkdrive but after clicking on 'home' for example.

    Disconnect the networkdrive connection and when mounting the network drive again use the option 'Connect using a different user name'. Then enter your user name and central UGent password.

  • "System error 67 has occurred. The network name cannot be found"
    Windows version 5.1 (Build 2600.xpsp_sp2_gdr.050301-1519: Service Pack 2).

    This problem could be caused by one or more services that have been "disabled". Enable the following services (go to control panel - system management - services):
    "Remote Access Auto Connection Manager"
    "TCP/IP Netbios helper"
    "Secondary Logon"
    "Remote Procedure Call"
    After restarting, you should be able to mount the network drive.

  • "The drive could not be mapped because no network was found" (winXP)
    This problem could be caused by one or more services that have been 'disabled'. Enable the following services (go to control panel - system management - services):
    "Remote Access Auto Connection Manager"
    "TCP/IP Netbios helper"
    "Secondary Logon"
    "Remote Procedure Call"
    After restarting, you should be able to mount the network drive.