Results 1 to 2 of 2

Thread: Non-Detectable IP Addresses and Diagnostics

  1. #1
    Join Date
    Oct 2007
    Kansas City, MO

    Non-Detectable IP Addresses and Diagnostics

    We have two primary servers, in our DMZ, for connectivity of devices outside our network. They both have a non-detectable public IP address that routes to the appropriate server. The problem is, diagnostics is trying to connect to that external IP address which will not work when connecting from the internal network. If I wait for that to timeout, it will show proper status until a refresh occurs. Sometimes this can take a couple minutes before the status reports correctly.

    Is there a way to get Diagnostics to utilize only the internal address or force the internal address to be the primary? We are running 11.4.1 on Windows 2012 R2 servers.

  2. #2
    Join Date
    Feb 2008
    Raleigh, NC

    Re: Non-Detectable IP Addresses and Diagnostics

    Not sure, I would recommend an SR and they can research this....
    If you can't just let me know and I will see what I can dig up..............
    Any Opinions, Thoughts, Solutions, or Blog Entries are my own and may or may not be shared by Micro Focus or any Sane Person
    Please Use at your Own Risk.

    Blog - https://forums.novell.com/blog.php/5830-CRAIGDWILSON


    Want to Turbo charge your apps and put an end to compatability issues?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts