Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    2
  • Subscribers subscribers
    6
  • Views views
    371
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Site OES Server Iprint and Mapped Drives problems

Sean Wirebaugh

Hello,

I have recently started management on a number of microfocus servers for a school district.  Yesterday we had a massive power outage and I have been successful getting the majority of

our servers back online and running.

I have one server though that after a reboot is having problems with Iprint and Mapped drives for users.  I restarted  tomcat / apache / and novell-ipsmd.service and still no iprint when going to address/ipp I get code - "An error occurred while trying to communicate with the Print Manager (502)"  I'm also having issues with the users at the facility with this server are having difficulties with mapped drives mapping when logging in some drives map correctly and some do not.

I have ran this test to ensure LDAP is working right on the server and it tested as it should -

OES 2018 SP1:
LDAPTLS_CACERT=/etc/opt/novell/certs/SSCert.pem /opt/novell/eDirectory/bin/ldapsearch -H ldaps://10.1.10.117:636 -D cn=admin,o=emg -w novell -b o=emg -x cn=admin cn
I have checked a lot of things trying to find a cause for this behavior if you have any other things I can check that may help find the cause of this strange behavior it would be super appreciated.
Respectfully, Sean

 

Parents
  • 0

    I would like to add this morning I have also ran through the steps located here to ensure NSS is working properly.  The drives are available and mounted.  I used nssmu to dismount all volumes and then remounted them, unfortunately my guess is these drives will continue to no map correctly because when I go into file explorer and navigate to these drives on the network and then try to access them I get a message that says - "Windows cannot access" and when I hit the diagnose button to see what windows will find it tells me windows cannot find the top level domain name.  Which this is strange behavior because no other servers in organization are having this issue at any other location.

Reply
  • 0

    I would like to add this morning I have also ran through the steps located here to ensure NSS is working properly.  The drives are available and mounted.  I used nssmu to dismount all volumes and then remounted them, unfortunately my guess is these drives will continue to no map correctly because when I go into file explorer and navigate to these drives on the network and then try to access them I get a message that says - "Windows cannot access" and when I hit the diagnose button to see what windows will find it tells me windows cannot find the top level domain name.  Which this is strange behavior because no other servers in organization are having this issue at any other location.

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.