Goline Logo

News

  • 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,...
  • RIPE – Atlas Anchor February 17th, 2022
    We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems.https://atlas.ripe.net/probes/7073/RIPE Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
  • MANRS June 20th, 2020
    GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

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
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x