× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



But unfortunately I cannot say why. The only changes I made were to add some DNS entries which initially didn't seem to work. But I DID have to restart the Windows server and I did have to restart the IBM i last night due to a UPS issue so somehow that fixed the issue.

I hate it when the "Microsoft fix" (reboot) takes care of the problem without knowing why.....

Pete Helgren
Value Added Software, Inc
www.petesworkshop.com
GIAC Secure Software Programmer-Java


On 4/20/2012 6:33 PM, Pete Helgren wrote:
I suspect that is part of it. It was assigned a reservation in DHCP. I
added a DNS entry and a reverse DNS entry for it. Flushed the cache on
the DNS server and the i and now when I ping the FQDN it*does* return
the correct internal IP. But still no response on the ping in either
direction. FWIW 5250 also won't connect. As far as it knows,
10.0.10.205 doesn't exist....

Still diggin'

Pete Helgren
Value Added Software, Inc
www.petesworkshop.com
GIAC Secure Software Programmer-Java

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.