Article
Problem:
Novell Map Network drive problem from Windows Client machine.
Solution:
Remove the Tree and the server object from Novell Connections and try to map again. This should work. The cause for the error could be the server was rebooted or network connectivity issues. Please see the example for more details:
Example:
In the above image, right corner of the Novell Connections screen shows that TREE-170 is already mapped. I am trying to map a network drive of 164.99.162.170/sys: and I am getting the error described above.
Now using Novell Connections I will remove both tree and server object of the server by selecting it and Detach followed by Refresh.
Make sure the Tree and server object is removed. Now try to map the Network drive again and this time the mapping should be successful.
Environment:
- NetWare servers: Versions can be 5.x or 6.x
- Windows client machine installed with Novell Client to access NetWare machines through Novell Map Network Drive.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
- (Error 898) NetWare Administrator Error Accessing Server Objects from Windows Client
- Solving Error when using df -h
- SSLVPN - KIOSK mode connection problem through https connection
- Stop Your Machine Status Changing to Standby Mode While Accessing Windows Machine Remotely
- How-to: Setting up Subversion for Designer on Windows
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 6226 reads




0