Sounds like the new break/fix project management about these days.
TJ
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Wednesday, December 30, 2015 15:09
To: 'Midrange Systems Technical Discussion'
Subject: RE: Older version of iSeries Naviigator UPDATE
Thanks to all who offered their help. We discovered that beginning on November 18th, a project to disable the NetBios package was completed on about 5000 PC's. Nobody had reported any "issues", so the network kiddies decided to move forward with the next batch of PC's nationwide.
The PC's mapping drives to the Model 170 in the bayou were hit the first weekend of December, and the users there reported a problem on December 8th.
Nobody could figure out what the problem was, and the network guys didn't care, until I pointed out the necessary ports and services needed by Client Access.
The network knuckleheads swore nothing was affecting traffic on the proper ports, except they were unable to map drives.
On an email thread that copied several big bosses, I mentioned that the inability to be EPA compliant was certainly "an issue". Within 60 minutes, the network guys who got called into work had re-enable the NetBIOS stuff on just the PC's in the bayou, and magically, they were able to map the drives.
Bwahaha!
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Wednesday, December 30, 2015 7:37 AM
To: 'Midrange Systems Technical Discussion'
Subject: Older version of iSeries Naviigator
Folks,
A couple of questions - At which point did Ops Nav/iSeries Navigator stop being able to work with a V4R5 machine? Does anybody have an old copy of the software?
One of my clients has a V4R5 machine that has been used to store images in the IFS via mapped drives. A couple weeks ago, they had a power failure, and the mapping ability went out the window. The newer versions of iSeries Navigator cannot "see" the TCP servers in a machine that old.
Anybody got a suggestion? I'm stumped, and IBM is no help, even through the consult line.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
--
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.
If you recently applied for credit: Important disclosures for Equal Credit Opportunity Act and USA PATRIOT Act, please click here<
http://www.svb.com/equal-credit-opportunity-act-disclosures/>.
As an Amazon Associate we earn from qualifying purchases.