|
maybe you need to have some ping script or something, are the odbc setups
done via local host table, dns or straight IP.
On Mon, Sep 17, 2012 at 3:34 PM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:
In theory, neither. users dont user 5250. They just open a java app--
and that java app starts an odbc connection to the server. They do
however authenticate that odbc conn with the same user/pass they use
on windows. But i'm not sure if it uses some kind of ntlm passthru or
what. In any case, even if it used it, it should NOT hang the entire
system until the dc is reacheable again...
Best Regards,
On Mon, Sep 17, 2012 at 4:26 PM, Jack Kingsley <iseriesflorida@xxxxxxxxx>
wrote:
Are you using 5250 with the bypass signon feature or some sort ofkereberos
tickets.list
On Mon, Sep 17, 2012 at 3:22 PM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:
I'm having a texbook case of "Let's fire the people who know the
system, they seem to be slacking anyways"..
v5r4 on a i520, only used for odbc connections to the DB2 database.
Used to be in one location. Moved to new location but with network
link to the old location.
IF the link goes down, down goes the i520 (you can log via 5250 but it
stops responding). Only weird thing is:
Lots and lots of outbound ldap connections (port 389) to the old
domain controller in the old location. System does NOT have EIM nor
LDAP configured (ldap tcpip server is stopped), people log in using
windows credentials but user/pass is not in sync, if pwd changes in DC
it has to be changed on the i.
What could be causing those connections? as a side note, ss1 op3 is
broken (reports as *error) since it has to do with directory servers
it might be related...
Ideas?
Best Regards,
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.