-
Products
-
SonicPlatform
SonicPlatform is the cybersecurity platform purpose-built for MSPs, making managing complex security environments among multiple tenants easy and streamlined.
Discover More
-
-
Solutions
-
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn MoreFederalProtect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn More - Industries
- Use Cases
-
-
Partners
-
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
Learn MorePartner PortalAccess to deal registration, MDF, sales and marketing tools, training and more
Learn More - SonicWall Partners
- Partner Resources
-
-
Support
-
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn MoreSupport PortalFind answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn More - Support
- Resources
- Capture Labs
-
- Company
- Contact Us
Novell Client for Windows Fails to Find Tree During Logon Attempt
03/26/2020 
4 People found this article helpful
484,597 Views
Description
Novell Client for Windows Fails to Find Tree During Logon Attempt
Resolution
Problem Description
The Novell Client for Windows fails to find the tree or node name when a user attempts to log in to a Windows system with Connect tunnel as the access method on the client system.
Workaround and Resolution
Workaround
In the Novell Client settings, find the eDirectory tab and change the Tree address to the IP address of the primary Novell server instead of the hostname. This should allow users to log on.
Resolution
The workaround above has to be performed on all client systems. Also, some environments may have multiple trees. A more permanent resolution involves adding a few network resources to the appliance:
| Resource name | Address |
| Novell Multicast SLP | 224.0.1.22 |
| Novell Multicast DA | 224.0.1.35 |
| Novell Multicast A * | 239.255.255.253 |
| Novell Multicast B * | 239.255.255.250 |
* Although the SLP and DA address should suffice, some environments may require these additional addresses to be entered.
Related Articles
- How to Set Timeout for Inactive Tunnel Connections
- Commands for silent installation of NetExtender via CMD line
- Users on Netextender 10.3.0 version failing to connect with the following error message " Cannot get a response from the server "
YES
NO