×
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.
On 01/06/2017 8:40 pm, tim wrote:
ok. new information. i first had split my connections from the iseries.
i had the console going to my 192.168.168 zone, i had the other on my
dmz 192.168.10 zone. i was able to connect to my console, but not to the
.10 zone. i then moved my console to the .10 zone also. now im getting a
A6005008 error.
the iseries doesnt seem to like any zone but my x1 192.168.168. im not
sure why.
There's a mismatch between the IBM i and your SonicWALL configuration
that's causing this problem. One address/subnet is as good as another --
the IBM i TCP/IP stack (and service stack) do not care what subnet you
use to configure them to use as long as the router (your SonicWALL in
this case) is in the same subnet and on the same L2 network domain.
When you plugged the PC into the X2 port, what address was it using?
When you previously said it worked, what did that mean? Could it ping
192.168.10.1?
When you moved your console now to the 192.168.10.0 subnet, what
SonicWALL port was it connected to? X2 or another port? Is the port you
used assigned to the DMZ on the SonicWALL?
Brian
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.
midrange.com
