Goline Logo

Home

    About Us

      Services

      Solutions

      Systems Architecture

      Support

      FAQ

      News

      • GOLINE SA partner with FileCloud November 25th, 2024
      • GOLINE SA partners with PowerDMARC April 24th, 2024
        In the supply and logistics sectors, email communication is pivotal. However, organizations face threats like email fraud and phishing. GOLINE SA's clients struggled with configuring email authentication protocols manually. To address this challenge, GOLINE SA became an MSP Partner of PowerDMARC, collaborating to streamline implementation and management. PowerDMARC's cloud-based platform automated DMARC, SPF, and DKIM protocols for GOLINE SA's clients. This streamlined the transition to DMARC enforcement policies, bolstering domain protection without compromising email deliverability. The intuitive platform facilitated easy navigation and provided detailed reporting for proactive issue resolution. GOLINE SA's clients experienced tangible benefits: Enhanced Email Security: Automated protocols...
      • Route RPKI validation April 1st, 2022
        RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...

      HP WebJet Admin. Problem connecting after update

      Miro Manglaviti Windows 22 June 2022

      http://h20564.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c01625441

      Error message: The service could not be contacted. Please make sure the service is started before running the client.

      When clients attach to HP Web Jetadmin, the software performs a redirect using the an IP address from the NIC that the application selected during startup. Sometimes, servers have multiple NICs and HP Web Jetadmin does not always pick the correct NIC and, during client launch, may re-direct to the wrong IP address on the network. When this happens, the client fails to start. Below is a scenario and an instruction for configuring HP Web Jetadmin to bind to the correct NIC.

      Scenario:

      Server has multiple NICs, not all of which are accessible by clients:

      • NIC1=192.168.0.35 – accessible to clients

      • NIC2=192.168.10.10 – not accessible to clients

      • NIC3=192.168.20.254 – not accessible to clients and selected by HP Web Jetadmin during startup

      In this case the clients will be browsing to 192.168.0.35 or its IP Hostname (DNS). When they do, HP Web Jetadmin will redirect to 192.168.20.254 and the client startup will fail. In this case, the administrator of the HP Web Jetadmin server will need to configure to allow H) P Web Jetadmin to bind to the correct NIC. Follow these steps to configure HP Web Jetadmin to bind to a specific NIC.

      Steps:

      1. Locate file …Program FilesHewlett-PackardWeb Jetadmin10ConfigWjaServiceSystem.Remoting.config.

      2. Open the file System.Remoting.config in a simple text editor such as Notepad.

      3. Edit the text to add the additional item as shown below:

        BEFORE (partial text):

        <channel ref="tcp" port="4088" name="CMRemotingChannel"

        rejectRemoteRequests="false" tokenImpersonationLevel="Impersonation"



        secure="true" protectionLevel="EncryptAndSign"

        impersonate="false" >

        AFTER (partial text):

        <channel ref="tcp" port="4088" name="CMRemotingChannel"

        rejectRemoteRequests="false" tokenImpersonationLevel="Impersonation"



        secure="true" protectionLevel="EncryptAndSign"

        impersonate="false" machineName="xxx.xxx.xxx.xxx" >

      4. Once the additional item ‘machineName="xxx.xxx.xxx.xxx"’ has been added to the file, save and close the file.

      5. Restart the HPWJA service.

      6. Once the service has completely started, browse to the client start page and verify success.

       

      0 0 votes
      Article Rating
      Subscribe
      Notify of
      0 Comments
      Oldest
      Newest Most Voted
      Inline Feedbacks
      View all comments
      0
      Would love your thoughts, please comment.x
      ()
      x