RE: Question about support related to Windows 7 -- MIDRANGE-L

You should look into VNC or an equivalent. Helps tremendously when you can
see what they are really doing remotely.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Friday, May 17, 2013 5:23 PM
To: Midrange Systems Technical Discussion
Subject: Re: Question about support related to Windows 7

He has been doing the net use. He says there is no provision to drop a
drive. I am not on 7 yet - not real eager to change just yet. I only
received an XP computer two years ago.

I haven't seen his computer. I suggested he right click the drive. His
claim is that he did.

People miss simple things.

He gets defensive when he is shown in error. On the other hand, I was
pursuing a wild fowl for about four hours today. User 500 miles away
reported she could not connect to the i. Made no sense. She could get to a
terminal server just fine. What happened, I was finally told, was that she
transposed user name and device name on a connect screen. I give her credit
for fessing up. Really hard to diagnose some issues like that. She had
been using the computer just fine. Her report to the help desk stating the
connection had dropped. That could have been her statement, or an error by
the help desk. Yesterday's six hour bore-a-thon and then today's tracing a
user error. Glad the weekend is here.

John McKee

On Fri, May 17, 2013 at 4:22 PM, Matt Olson <Matt.Olson@xxxxxxxx> wrote:

You can also be a bit sadistic and do it from the command line:

1.Click Start, and then click Run.
2.In the Open box, type cmd.
3.Type net use x: /delete, where x: is the drive letter of the shared
resource.

-----Original Message-----
From: John Jones [mailto:chianime@xxxxxxxxx]
Sent: Friday, May 17, 2013 3:42 PM
To: Midrange Systems Technical Discussion
Subject: Re: Question about support related to Windows 7

"He also tells me that there does appear to be a function to unmap a
drive from Windows Explorer - Windows 7."

I'm doing this in Windows 8 but I think it's the same in 7. In
Explorer, right-click the drive & select Disconnect.

On Fri, May 17, 2013 at 1:56 PM, John McKee <jmmckee@xxxxxxxxxxxxxx>
wrote:

From my XP box, that works great. From my co-worker's 7 box, it
swirls

around a bit, then comes up with an error. One of three errors.

He also tells me that there does appear to be a function to unmap a
drive from Windows Explorer - Windows 7.

John McKee

On Fri, May 17, 2013 at 11:24 AM, TheBorg <sjl_abc@xxxxxxxxxxx> wrote:

If you click the Start -> Run, you can enter \\iSeriesName to view
the shared IFS folders.

On the login panel presented by Windows, the proper syntax is
iSeriesName\iSeriesUserID in the upper box, and iSeries password
in the lower box.

"John McKee" wrote in message
news:mailman.4656.1368803206.7202.midrange-l@xxxxxxxxxxxx...

He tried using a dummy domain as suggested by IBM. Also, the IP
address

of

the i, and I >think< the names in DNS, not sure about that. Then,
there

is

the issue of no leading \\ or not. I think he tried both ways as

well.

On Fri, May 17, 2013 at 9:02 AM, TheBorg <sjl_abc@xxxxxxxxxxx> wrote:

When attempting to access the folder and the login panel
appears, the

user

should enter the iSeries systemname\user name and password.
-sjl

"John McKee" wrote in message
news:mailman.4622.1368764923.7202.midrange-l@xxxxxxxxxxxx...

A co-worker was given a new computer with Windows 7. He tried
to

recreate

the drive assignments to IFS folders he used on his Windows XP

computer.

The drive assignment works. He is unable to access the contents.
I do not recall the exact error he received.

His i user profile is different from his network id. I asked
him to

check

that his i password was 10 characters or less. Same for his
network password. And that network password had no mixed case
or special characters. Still not authorized.

When he tries to access the folder, he is presented with a
box,

presumably from Windows, requesting a user name and password.
<<<

I called IBM support. Initially, I was routed to support for i

issues.

Checked a few system values. Then, I was forwarded to, I think,
CA support. Co-worker can not install CA, as it is on a share
on

the i.

Initially, I was in the middle. Then, I suggested to my
co-worker that

he

respond to the IBM support person.

IBM support sent him an email with things to try. Last was to
run a communications trace. Exact command parameters were detailed.
Start trace, try to access folder, end the trace. I logged on
as QSRCOFR on

his

computer, and we did what was requested. Nothing was said about
the resulting two spool files that were produced. I used
CPYFRMSPLF to a

PF,

then CPYTOSTMF, using *PCASCII. Resulting files can be viewed
with Notepad. Thinking the files were wanted by IBM, I sent
them to the IBM person and copy to co-worker. He could not do
that, again, because he could not access any shares. First IBM
contact had me check to see if his

(it

is
late, and am tired. I am thinking network profile on the i
)profile

was

disabled. It wasn't.

I asked the first IBM contact if a PTF needed to be installed
and was

told

none addressed the issue.

This morning, the second IBM person sent an email reply back
about my email with two attachments. He didn't know what they
were or how to open

them.

Co-worker replied to use Notepad. We have heard nothing else.

A very long buildup. I apologize. Since there was nothing
stated to

do

with any spool files, did I do what was needed? I only ask
based on

the

email reply from IBM. I am very confused by this.

Before calling IBM, I also looked through the Midrange archives.
Thus

the

ideas on password length, special characters, and case.

I still wonder if a PTF is missing. V5R4M0. Today was a
complete

waste.

Spent six hours in training on how to use help desk software.

Otherwise,

I
might have been able to try searching myself. Tomorrow, I get
to face

new

issues and try to get caught up on undone tasks from Thursday.

So, any ideas, and did I do what IBM needed?

John McKee

--
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.

--
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.

--
John Jones, CISSP
No security, no privacy. Know security, know privacy.
--
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.

--
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.