- Products
- Network Security
- Threat Protection
- Secure Access Service Edge (SASE)
- Cloud Security
- Endpoint Security
- Email Security
- Secure Access
-
Wi-Fi 6 Access Points
SonicWall SonicWave 600 series access points provide always-on, always-secure connectivity for complex, multi-device environments.
Read More
- Solutions
- Industries
- Use Cases
- Solutions Widgets
- Solutions Content Widgets
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
- Solutions Image Widgets
-
- Partners
- SonicWall Partners
- Partner Resources
- Partner Widgets
- Custom HTML : Partners Content WIdgets
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
- Partners Image Widgets
-
- Support
- Support
- Resources
- Capture Labs
- Support Widget
- Custom HTML : Support Content WIdgets
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
- Support Image Widgets
-
- COMPANY
- PROMOTIONS
- MANAGED SERVICES
- Contact Sales
-
- Menu
- Solutions
- Solutions Widgets
- Solutions Image Widgets
-
- Solutions Widgets
- Partners
- Partner Widgets
- Partners Image Widgets
-
- Partner Widgets
- Support
- Support Widget
- Support Image Widgets
-
- Support Widget
- Solutions
- Solutions Widgets
- Solutions Image Widgets
-
- Solutions Widgets
- Partners
- Partner Widgets
- Partners Image Widgets
-
- Partner Widgets
- Support
- Support Widget
- Support Image Widgets
-
- Support Widget
Novell Client for Windows Fails to Find Tree During Logon Attempt
03/26/2020 
4 People found this article helpful
210,169 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 deploy SMA100 series virtual appliance (SMA 500v) from one platform to another.
- SMA100:After upgrading to 10.2.1.7, began receiving nonstop alert emails stating "WAF threat prevented:
- SMA1000:When both IPv4 and IPv6 are enabled for the network interface, the first few connection attempts fail, but everything works fine after that.
YES
NO