We have a case where frequent access from a rogue server is creating havoc. It's not an attack, just a misbehaving actor that the Apps folks cannot locate. We have identified the offending IP address and want to block it, but we can't find a mechanism. We have long used IP filtering in our DR environment to restrict access to a handful of IP addresses that we want to *allow*. This is the other side of the coin: *stopping* a specific access.
Can someone point me to the appropriate doc? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
