The next steps I think would be communication traces on both ends if
possible or at least on your end. Catch the outbound traffic or lack of
inbound traffic. Export it as a .pcap file and hand it to the network
guys. "Here is my outbound traffic. Since you've completely blocked all
troubleshooting opportunities it's now your problem."
I can tell you that there have been days it's a good thing the network
guys were not local. Up and down they swear it's not their problem!
However, since they cannot show the traffic sending/arriving we just
continue to throw it back in their face until someone with sufficient
'chooch factor' gets them to focus on the problem. Then, often with a
complete denial of any change, suddenly it works.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 8/21/2018 12:33 PM, David Gibbs wrote:
On 8/21/2018 11:24 AM, DrFranken wrote:
You might also try SSH from QSH if the system on the far end has SSH
running.
SSH is also locked down.
If I had NMAP on the i, I would try that (and get a nastygram from the
network security people).
david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.